dirty fades ( again...)

Mindmatter wrote on 11/12/2014, 12:46 PM

Hi all,

I found myself somewhat clueless again today after seeing a rendered mp4 file ( 1080p from Canon t2i footage on timeline ) at 21mb/s bitrate) totally mess up a simple fade in from black to white, using solid color generated media for both colors.( I used to fade to and from "nothing, but some helpful folks here explained that Vegas is using "illegal black" for " nothing", so I don't do that anymore. )
Fact is, the fade in to solid white has jumps and horizontal artifacts at several moments, more so towards the end of the fade in. I also noticed a jerky credit roll ( again), 4 lines of colored text scrolling over a simple white background.
Is there any solution to this, anything I'm misssing?
Thanks!

Comments

rs170a wrote on 11/12/2014, 2:24 PM

Make sure your blacks are set to 16-16-16, whites are set to 235-235-235 and that you put a piece of solid black set to 16-16-16 under the whole thing.

Mike

johnmeyer wrote on 11/12/2014, 2:24 PM

Have you tried doing a RAM preview by first selecting the transition area, using a loop region, and then pressing Shift-B in order to create a RAM preview? That should let you get a smooth preview of your transition.

If this doesn't fix the problem, then we need to look further for solutions ...

Mindmatter wrote on 11/12/2014, 4:05 PM

Thank you both. Setting to legal values did not solve the problem.
Concerning RAM preview, V13 went a little haywire. Each time I set a loop region and pressed shift+B, the loop region shrank to like 200ms . I pulled it back to like 10 seconds - same thing. Shift B, region shrinks to unusable size. I tried different RAM preview size settings - same thing.
No idea what's going on.

johnmeyer wrote on 11/12/2014, 5:21 PM

Each time I set a loop region and pressed shift+B, the loop region shrank to like 200ms . I pulled it back to like 10 seconds - same thing. Shift B, region shrinks to unusable size. I tried different RAM preview size settings - same thing. No idea what's going on.I can't offer any advice based on actually experiencing this exact same problem. However, I have seen something similar when using "Best-Full" for preview resolution, and when the transition, compositing, multiple cameras, etc. are giving Vegas a lot to digest.

One thing to try -- not as a solution, but as a troubleshooting step -- is to temporarily change the Vegas preview resolution to "Preview-Auto." Try Shift-B and see if the loop collapses.

Also, are you using an external monitor, and if so, how is it connected? As always, turning off GPU acceleration (in the Preferences dialog) seems to fix a lot of strange Vegas problems.

astar wrote on 11/14/2014, 9:51 PM

The 200ms thing has to do with your preview ram setting. You may need to increase your system ram, or kick that preview ram setting to like 4GB or 8. That way when you do a ram preview there is enough space to build the length of the preview you want. With to little preview ram set, the app builds until it runs out of memory. If that is set to 200MB, that will seem like a faction of a second.

+1 to managing the black and white levels.

Mindmatter wrote on 11/17/2014, 8:19 AM

Thanks all, I now created 2 .png with legal white and black respectively, and that seemed to help smoothing the fades out. I tried both fading in the white over an underlying black as well as fading out the black to an underlying white. Both seem ever so slightly different in behaviour but both look clean.