Aaargh! Why does it remove fade at end of clip?!?

smhontz wrote on 12/4/2012, 9:26 PM

This has bugged me since Vegas 3. I have a piece of video (Event A) with a nice one-second fade-out of the the video and audio at the end. I have another piece of video (Event B) further down on the same track with a nice fade-up at the beginning. When I slide Event B to the left up against Event A, Vegas removes my fades and makes it a cut. If I pull the pieces back apart, the fades reappear. Push them together, and they disappear. In fact, I then can't find the handle on the end of Event A to add the fade back in. So, I have to resort to having them 1 frame apart.

This doesn't always happen. Many times I push the clips together and it leaves my fades alone. I can't see a rhyme nor reason for this behavior.

Comments

john_dennis wrote on 12/4/2012, 9:35 PM

Drag one of the events to a different track and you can keep any fade-in / fade-out behaviour you want.

Tom Pauncz wrote on 12/4/2012, 9:38 PM

Make sure you have "Quantize to Frames" set on.
Tom

smhontz wrote on 12/5/2012, 9:13 AM

I do have Quantize to Frames set on. It's just so random. The vast majority of the time it leaves my fades alone and then once in a while I'll get this weird behavior.

Former user wrote on 12/5/2012, 9:18 AM

I have ran into this occasionally as well. I haven't figured out what makes the difference, but I wonder if Ripple is related?

Dave T2

Tom Pauncz wrote on 12/5/2012, 9:27 AM

I've also seen it occasionally. I am thinking that the end of one of the clips is not on a frame boundary.

What usually gets me around it is dragging the end of the clip(s) slightly.

Tom

Former user wrote on 12/5/2012, 9:31 AM

Tom, that could be, but I keep the boudary warning on and have had this happen without a warning of the frame boundary being off.

Dave T2

riredale wrote on 12/5/2012, 9:33 AM

This has always bugged me as well, ever since Vegas3. Sometimes they butt properly, other times not.

I mitigate the issue for the most part by reducing the magnetic effect. Years ago I discovered one could go into the secret Internal tab, search for "snap" at the bottom, then reduce the snap width from 7 down to 3. Clips then snap together appropriately but over a shorter distance, and I can move them much closer together on the timeline if I wish without having to zoom in to the frame level.

Former user wrote on 12/5/2012, 9:34 AM

Riredale, thanks for the tip. I need to check that out.

Dave T2

Tom Pauncz wrote on 12/5/2012, 9:34 AM

Me too Dave, but that's the only thing that makes any kind of sense. It's very unpredictable.

I usually zoom in on the timeline and that makes it easier to drag the ends back and forth. I typically don't lengthen or shorten the clips when this happens and it seems to fix it.

Tom

Former user wrote on 12/5/2012, 9:38 AM

If somebody could write some kind of debugging script that tracks everything you and Vegas do and logs it, some of these things could probably be figured out easily. But I don't know if such a script can run.

Just thinking out loud.

Dave T2

Mrkrng wrote on 12/6/2012, 12:50 PM

I too have had this problem in all versions of Vegas and on 3 different computers, and I'm surprised there hasn't been more mention of this. I often have drag the end of one or both clips back and forth and then reapply the fade. Many times I have missed this happening and ended up without a fade in my render. This can slow down editing considerably.

Tech Diver wrote on 12/6/2012, 1:25 PM

In every case that I have seen this issue, it was due to the end(s) of the clip not being on the frame boundary. Assuming you have snapping turned on, you can easily fix this by merely grabbing the end of the clip, moving it some finite amount, letting go of it, then moving it back to the desired location. Note that just moving the clip end to another location and back again, without letting go of the mouse ,will not fix the problem.

Peter