*#!*%##! Vegas!

Comments

DouglasClark wrote on 9/13/2004, 11:18 AM
Hey John, I experienced all of what you're talking about over the weekend. I was "learning" to do L-cuts and J-cuts, slipping media, etc., on an old project with multiple video and audio. What a mess! I thought I was really doing something dumb. There were crossfades appearing over entire events (which turned out to be events on top of events). And audio out of sync. Etc. etc. I'm glad to hear I'm not alone.

If this behaviour is a "feature" in Vegas, I sure would like to hear an explanation of the logic. Because it don't make no sense to me. I got a tip from another thread to leave auto-ripple off, and just hit post-edit ripple whenever needed. That sure seems to apply for J- and L-cutting.
jetdv wrote on 9/13/2004, 12:30 PM
There were crossfades appearing over entire events (which turned out to be events on top of events).

Sounds like an instance where you were holding donw the CTRL key and then slightly dragging the clip instead of simply clicking to select it. A CTRL-Crag will COPY the clip resulting in exactly what you were saying.
johnmeyer wrote on 9/13/2004, 1:04 PM
Sounds like an instance where you were holding donw the CTRL key and then slightly dragging the clip instead of simply clicking to select it. A CTRL-Crag will COPY the clip resulting in exactly what you were saying.

Ed, I wish it were so, but if you follow my "chaos" instructions and then start playing around with combinations of selections, you will very quickly end up with exactly what he describes. No need to hold the Ctrl key. While it is true that some of these selection combinations you might create are what an engineer would call "pathalogical cases," most of them are not. It is actually quite easy to end up with discontiguous events selected. If you then start playing around with grouping -- which as I showed ends up ungrouping the audio events -- then will quickly end up with all sorts of overlapping events, which automatically crossfade and give you the effect that Douglas describes.
riredale wrote on 9/13/2004, 8:04 PM
I don't profess to be a Vegas guru, but in my experience the ripple tool is very logical, very effective, and very dangerous. I can screw up a project in no time if I forget when the ripple button is on.

If I leave it off and turn it on only when really needed, and then immediately turn it off again, I don't have any problems with ripple editing. But perhaps that's because I'm not doing sophisticated stuff.
PhilinCT wrote on 9/13/2004, 8:16 PM
Amen! I do the same, ripple has caused me much rework. I have also had the multi copying of events described earlier due to my control dragging habit.

They all fit into the do it once, never again folder. Each is very useful when needed, but must be watched!

Phil
JJKizak wrote on 9/14/2004, 5:46 AM
The ripple button should be a blinking type as I go back and forth with it and sometimes forget that its on and thank God for the undo. Or it could be blinking text or blinking time frames. The fader problem has been with Vegas from day one. Now also when I open Forge within Vegas on a long clip the external monitor will not come back on when going back to Vegas and I have to re-click the external monitor to come back on. This only happens on a long clip but on a short clip it's OK. It also happens with DVDA-2.

JJK
BrianStanding wrote on 9/14/2004, 2:20 PM
Lessons learned from Vegas, the hard way:
1. Never use the Auto-Ripple on the tool bar. Use shortcut keys or the menu to manually ripple instead.

2. Never use "grouping" for anything other than maintaining Audio/Video sync.

3. Never turn on "Snap to Grid Marks."

4. Always leave "Quantize to Frames" turned on, unless you're syncing "wild" audio (say, from a MiniDisk) with audio recorded on your DV camera.

5. Always "Save As" and give your VEG file a new name, to maintain backup copies.

6. If you change any of these settings, change them back IMMEDIATELY.
Randy Brown wrote on 9/14/2004, 4:51 PM
"The ripple button should be a blinking type..."
I don't feel quite so stupid now, I quit using it because I sometimes would forget to turn it off and wind up with such a mess that I had to take it off of my "handy buttons". I would prefer not only a blinking light but an audible "eeee-eeee-eeee!!!!" like you hear when a large construction vehicle is backing up : )
Randy
riredale wrote on 9/15/2004, 10:53 AM
Add to the blinking button and the truck-backup-noise the following: the computer should open and close it's CD and DVD trays continuously. Taken together, all these things would be hard to ignore...
Grazie wrote on 9/15/2004, 11:49 AM
. . . yeah ... know what yer mean . . I've set up one of those auto hammers that spring outta the cupboard on an extending wooden arm . . . Thwwack! . . yer only do it once . . or twice . . . works though .. .

Grazie