Strange burn/dissolve looking end of track fade

MarkAnthony121 wrote on 12/19/2025, 8:36 PM

Please, needing urgent help, does anyone know why doing a regular fade out of a track looks like this? I made the fade out in the clip extra long so that you can better see what's happening. Not sure if I hit a setting or what but it's a fresh project and no effects. VP21.208. 13900K with 4070ti windows 11. Footage is CLOG2, HEVC 422. Same happens graded or ungraded and same if project is 8 bit or 32bit. It didn't always do this. It would just beautifully and perfectly fade to black. Let me know what other info you may need.

Comments

Dexcon wrote on 12/19/2025, 9:12 PM

 It didn't always do this. It would just beautifully and perfectly fade to black.

Do you mean that the fade to black with this particular shot worked before but now it doesn't, or do you mean that fading to black is different with this particular shot than with fading to black on other different shots?

If the former, the fade to black looks to be as expected - there's flashing lights and the higher luminance parts of the image will take longer to fade to black than occurs with the darker parts of the image. What you might want to try is to R click the fade and then click on 'Fade type' at the top of the context window that opens and try out the other fade curves to see if one of those better meets what you are looking for:

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition; Samsung S23 Ultra smart phone

Installed: Vegas Pro 13, 15, 16, 17, 18, 19, 20, 21, 22 & 23, HitFilm Pro 2021.3, DaVinci Resolve Studio 20.3, BCC 2026, Mocha Pro 2026, NBFX TotalFX 7, Neat NR 6, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 12, iZotope RX11 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11 25H2

Dell Alienware Aurora 11:

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 2TB Samsung 990 PCIe 4.0 NVMe M.2 PCIe SSD

D: drive: 4TB Samsung 870 SATA SSD (used for media for editing current projects)

E: drive: 2TB Samsung 870 SATA SSD

F: drive: 6TB WD 7200 rpm Black HDD 3.5"

Dell Ultrasharp 32" 4K Color Calibrated Monitor

 

LAPTOP:

Dell Inspiron 5310 EVO 13.3"

i5-11320H CPU

C Drive: 1TB Corsair Gen4 NVMe M.2 2230 SSD (upgraded from the original 500 GB SSD)

Monitor is 2560 x 1600 @ 60 Hz

MarkAnthony121 wrote on 12/19/2025, 9:32 PM

 It didn't always do this. It would just beautifully and perfectly fade to black.

Do you mean that the fade to black with this particular shot worked before but now it doesn't, or do you mean that fading to black is different with this particular shot than with fading to black on other different shots?

If the former, the fade to black looks to be as expected - there's flashing lights and the higher luminance parts of the image will take longer to fade to black than occurs with the darker parts of the image. What you might want to try is to R click the fade and then click on 'Fade type' at the top of the context window that opens and try out the other fade curves to see if one of those better meets what you are looking for:

See this though? This is not a normal clean fade out. Unless I'm losing my mind. It's happening in resolve too so I don't know if something is wrong with my gpu/color settings. It's like the last few frames of the fade out. The contrast/banding is all jacked up. It looks like Nintendo 8-bit color in those last few frames

This CAN'T be right lol. I've been editing for 20 year and extremely anal about this stuff. I find it hard to believe that I JUST started noticing this and it's normal.

MarkAnthony121 wrote on 12/19/2025, 10:07 PM

Whelp I don't know WHAT is causing this but it seems to be a system issue because it's not doing this on my laptop. But on this system it's both Vegas and Resolve. I had a monitor RMA and replaced it/updated drivers, changed setting and I think I jacked something up

Dexcon wrote on 12/19/2025, 10:18 PM

Ah! I see what you mean with the latest image. I looked at the video again and it makes me wonder if the relatively low-lit scene (the dance floor) contrasted with flashing bright lights is giving the camera a hard time especially in relation to the rolling shutter issue (if that applies to the camera's image sensor being used).

Another suggestion but which probably won't make any difference - rather than using a fade out to the blank video track, try putting a solid black Vegas media generated event on the track and make the transition a dissolve from the video event to the black media generated event.

Hopefully, others on the forum will be able to offer other suggestions.

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition; Samsung S23 Ultra smart phone

Installed: Vegas Pro 13, 15, 16, 17, 18, 19, 20, 21, 22 & 23, HitFilm Pro 2021.3, DaVinci Resolve Studio 20.3, BCC 2026, Mocha Pro 2026, NBFX TotalFX 7, Neat NR 6, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 12, iZotope RX11 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11 25H2

Dell Alienware Aurora 11:

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 2TB Samsung 990 PCIe 4.0 NVMe M.2 PCIe SSD

D: drive: 4TB Samsung 870 SATA SSD (used for media for editing current projects)

E: drive: 2TB Samsung 870 SATA SSD

F: drive: 6TB WD 7200 rpm Black HDD 3.5"

Dell Ultrasharp 32" 4K Color Calibrated Monitor

 

LAPTOP:

Dell Inspiron 5310 EVO 13.3"

i5-11320H CPU

C Drive: 1TB Corsair Gen4 NVMe M.2 2230 SSD (upgraded from the original 500 GB SSD)

Monitor is 2560 x 1600 @ 60 Hz

john_dennis wrote on 12/20/2025, 12:52 AM

@MarkAnthony121

I downloaded your original example video and stepped through each frame on a Vegas timeline. I didn't see any frame from that video that appeared to match your still frame example. Even three render generations later.

@MarkAnthony121 said: "It's happening in resolve too so I don't know if something is wrong with my gpu/color settings."

I would be more suspicious of hardware/driver if it's happening in two very different applications.