Bug with "Fade Thru Color" Transition

smhontz wrote on 7/27/2004, 3:05 PM
I'm seeing some glitches with using the "Fade Thru Color" Transition - in particular with the "Fade Through Transparent" preset. (Vegas 5.0b, Build 160). Using the standard NTSC settings. If someone could confirm...

To repro:

1. In preferences, set the default still image length to 15 seconds, and the overlap time to 5 seconds. Enable the option to automatically overlap multiple media.

2. On track 1, drag about 6 stills JPGs. They should overlap as set by the preferences.

3. On track 2, drop a RED solid color and drag it the length of the stills in track 1. (This is just to make the glitch more pronounced.)

4. Select Events to End on track 1 to select all events.

5. Drag the "Fade Through Transparent" transition from the Dissolve group to the first crossfade; it should automatically apply it to all crossfades.

6. Now watch carefully as the transitions execute. At the end of one of the transitions (usually the fade-up to the third picture) the transition glitches - it goes from nearly complete (i.e., 98% visibility of the picture) to 0% visibility then back to 100% right at the end of the transition.

I've confirmed this with the other Fade Thru Color transitions. If I manually adjust the length of the transition, it goes away. And, yes, it appears in the final rendered output. In fact, although I only saw one glitch when playing a series of 6 pics in the timeline, I saw 3 in the final rendered output.

Quantize to Frames is ON.

Comments

smhontz wrote on 7/30/2004, 8:58 AM
Can anyone else reproduce this? It seems if you use the automatic overlap feature with this transition type, it doesn't make the transition on a frame boundary or something...

I sent a request in to tech support, but no reply yet...
Grazie wrote on 7/30/2004, 9:18 AM
SM any good I try in PAL?
HPV wrote on 7/30/2004, 9:40 AM
Even though you have quantize to frames turned on, Vegas is making partial frame stills and partial frame cut to overlaps for you. The trick is to adjust the durations in the editing prefs panel so you just get the frame number to start a next full frame. For a NTSC project a still length of 14.982 seconds is a perfect 449 frames and won't glitch. Next would be 15.015 seconds for 450 frames. Anything between those numbers can cause a glitch because the event will have a partial frame duration. Same goes for cut to overlap conversion. 4.972 seconds is a perfect 149 frames, next up would be 5.005 for 150 frames.
Sony really needs to address this issue with a tweak of the prefs/edit interface. It should be restricted to only adjusting for full frame durations based on the project properties. For now, use the CTRL key while you click/ drag the duration so you have micro control of the adjustment and you can roll it to JUST start a new frame number. Hope that helps.

Craig H.
smhontz wrote on 7/30/2004, 11:18 AM
Thanks, Craig! Setting the still length of 15.015 and the overlap to 5.005 worked perfectly. I agree, it would be nice if it would round it to the nearest frame or at least give you an option...
smhontz wrote on 8/13/2004, 6:17 PM
Just an update: Sony was able to duplicate this and has added it to their bug list. They have no immediate solution, but the suggestion Craig gave is a good work-around.