Vegas has problems cutting accurately

StormMarc wrote on 3/10/2004, 1:47 AM

I recall reading others complaints on this forum about the problem when cutting and trimming with the split frames overlapping (creating a two cut flash frame). I've had the problem with Qauntisize to frames both on and off. No other NLE I've used has ever exibited this problem and it a real pain to deal with. I suspect it has something to do with the ripple tool and I've experienced this on both of my computer systems.

Has Sony acknowledged this is a problem? I love Vegas but this really needs to be fixed in version 5.

Marc

Comments

farss wrote on 3/10/2004, 2:06 AM

I've never had precisely the same problem, so long as I've got QTF on, no sub frames but I'd add that Ripple seems to produce some annoying behaviour, mostly linked to the way Vegas forgets which bits of audio are meant to be in sync with which bits of video.

This behaviour is incedibly easy to reproduce and yet I've never seen it acknowledged as a 'bug'.

craftech wrote on 3/10/2004, 5:23 AM

I don't like the ripple edit feature either because it doesn't always work properly. I usually drag stuff around instead. Stretch out the timeline so you can see better (By the way: For the life of me I don't understand why the slider bar has to grow or shrink when you do that).

Try unchecking automatic crossfades. I did that a long time ago so I can't remember what type of problem it used to cause, but I remember that I didn't like them for some reason.

John

cyanide149 wrote on 3/10/2004, 5:41 AM

I also only use the ripple tool if I've got to insert/delete on an extremely busy timeline. Even then, I occasionally get those "phantom frames" scattered about...

JJKizak wrote on 3/10/2004, 5:52 AM

I have found that it varies with how much expansion or contraction that has been applied to the timeline. I will uncheck quantize to frames, make the clips merge or separate, then recheck quantize to frames. This is with guidelines not visable. With the ripple edit on it seems to work most of the time but I use ripple edit sparingly and usually shut it off after only one edit. Sometimes I will have to expand the timeline a whole bunch to get the clips to merge properly. The shift "B" sometimes doesn't work when you try to use it over a clip junction, one clip being bare bones the other having a speed change or FX applied. The shift "B" will stop when it hits the second clip. But I am really not complaining even when the multilple sound tracks (17) decide to change their volume settings by maybe .1 or .2db. for no reason from day to day.

JJK

rmack350 wrote on 3/10/2004, 9:58 AM

My experience with "Quantize to frames" lately is that it only works when the wind is just right. Using 4.0e.

BTW, for still frame duration in a 29.97 project-a 1 second duration creates an event that is 29.970 frames long. Obviously not "Quantized to frames". You need to adjust this in prefs to a number that makes whole frames-like 1.001 seconds.

Generated Media also does this. It's a 10 second default but this yeilds fractional frames. Unfortunately the Media generator tool rounds the duration display down to whole frames while creating an event with fractional frames.

I think "Quantize" is broken. Fractionally, of course.

Rob Mack

StormMarc wrote on 3/10/2004, 11:19 AM

I should note that on my recent project I was using the trimmer alot and insert editing from the trimmer. Many of the problems seemed to happen in relation to ripple editing beng on. Glad to hear I'm not the only one having problems. I'm confident the programming staff who brought such a great product must be working on this.

Marc