BUG REPORT v3a

MixNut wrote on 5/15/2002, 8:40 AM

Hello,

I'm having a *really* annoying problem...Is this a known bug?:

Whenever I use the numpad arrow key to move selected clips on track 1 [as example] to track 3 and the audio temporarily crosses/overlays edited audio on track 2, some of the crossfades and edits on track 2 are CHANGED/BROKEN [i.e. moved, gone, fades over the entire clip duration, multiple copies of the same clip on top of itself, etc.].

Are there plans to fix this problem in the next update? Is there any way to avoid this now?

TIA

MixNut

Comments

SonyIMC wrote on 5/15/2002, 10:41 AM

Thanks we have a repro and will add this to our bug database.

MixNut wrote on 7/3/2002, 3:38 PM

Did this one get fixed in 3b or 3c? I see no mention of it in the 3c bug fix list.

TIA

SonyEPM wrote on 7/5/2002, 9:22 AM

If you click and drag the event between track 1 and track 3 (mouse operation), the crossfade on track 2 will not get "broken", since you are not dropping the event on track 2. Numpad move will break the crossfade on track 2 (turns it into a punch-in).

We'll try to come up with a cleaner behavior in a future version of Vegas.

MixNut wrote on 7/7/2002, 11:59 AM

This is not an acceptable alternative!!! Moving the clips with a mouse does not guarantee same placement in timeline and is slower than with numpad.

THIS SHOULD BE CONSIDERED A BUG AND REPORTED AS SUCH. THIS NEW "BEHAVIOUR" HAS COST ME HOURS OF WORK IN FRONT OF CLIENTS.

PLEASE FIX THIS!!!

David

DougHamm wrote on 7/7/2002, 2:01 PM

I haven't tried to reproduce this so take my advice with a grain of salt - but what if you temporarily reordered your audio track before using the arrow keys, and then moved it back after? In other words, getting it out of the way? It would add a second or two to the process but perhaps it would allow you to do what you need to do?

CDM wrote on 7/9/2002, 3:51 PM

you can turn snapping on and move the event with the mouse. It WILL snap to its original location.