Please explain how this edit feature is useful?

GordyHinky wrote on 4/25/2004, 2:39 AM
I'm trying to figure out how "insert" and "overlay" in Vegas compares to other NLE's. Here is what I have determined.

These three methods seem to be very useful.

1. "Ripple" on + "Add Media From Cursor" = "Normal Insert"
2. "Ripple" off + "Add Media From Cursor" = "Normal Overlay"
3. "Ripple" off + "Add Media To Cursor" = "Backwards Overlay"

However this 4th method (which completes the above) doesn't seem very useful. Please explain what purpose it serves.

4. "Ripple" on + "Add Media To Cursor" = "Backwards Overlay" but the timeline ripples leaving a big gap between the new overlayed clip and the next subsequent clip.

Doesn't seem very useful to have the timeline ripple after this "Backwards overlay", does it?

On a side note, one thing I really like about Vegas is when you "overlay" media it doesn't delete the original clip beneath. This is a really nice feature. Although the way the clips on the left slide beneath clips on the right can be confusing to work with sometimes. I wish there was a modifier key to allow the left clip to slide on top of the right clip.

Comments

GordyHinky wrote on 4/25/2004, 12:02 PM
Somehow this droppted to #29. Anyone having any comments on this?
ibliss wrote on 4/25/2004, 12:09 PM
If you turn off automatic crossfading, this will get rid of the 'overlay' you are taking about. Not sure about the gap at the end of the inserted media file though (that happens either way).

Anyone else?
ibliss wrote on 4/25/2004, 12:15 PM
Okay, got the hang of it.

lets say you have a 10 second event A and another event, B.
then you add event C, dropping it halfway along event A.
you will end up with 5 secs of A, then C, then a 5 second gap, then clip B.

If you add event C 8 seconds into event A you will get
Event A, Event C, 2 second gap, Event B

If you drop Event B directly at the end of A, you will have
Event A, Event C, Event B (no gap)

So what's happening is that ripple edit is adding the remainder of Event A to the length of event C and moving Event B along the timeline by this value. Basically not a bug but a flaw in the logic of the ripple edit system. Sony, can you tweak this for us please?

I will go and fill in a bug/feature request thing.

At least we can work around it by spliting at the cursor befor adding the new media.
Spot|DSE wrote on 4/25/2004, 1:08 PM
GordyHinky, I just GOTTA ask what your screen name comes from?

This is not a flaw in the ripple edit system, but rather a flaw in how it's used. The ripple will always maintain the integrity of the time relationship of a track, all tracks, or all tracks and markers depending on what's selected in the ripple dropdown menu. It will place new media at the cursor point, regardless of where it's at. So, to make this properly effective, turn on snapping (F8) then put your cursor where you want to insert new event. Then insert new event. The timeline will move to the right for the length of the new event. By the same concept, it will move the timeline to the left when you delete an event.
ibliss wrote on 4/25/2004, 1:13 PM
But surely it's wrong to have the section of the existing event that crossfades or that gets 'overwritten' by dropping the new media ontop of it calculated into the amount the remaining media is moved along the timeline - there shouldn't really be that gap after the media that has been inserted?

Actually playing with it a bit more I think I've got my head round the logic - the gap created is the length of the inserted media that overlaps the existing media to the LEFT of the end of event A in the examples above.

This litt Veg file I've made demonstrates what I'm trying to say (I'm sure you understand anyway). Drop the media 'Event C' from the media pool onto the timeline at the marker posistion on track 1 and then on track 2.

Do you think it would be wise to have an option not to have track 1 behave like track 2 without having to split evet a?

hope I'm making sense :)
GordyHinky wrote on 4/25/2004, 2:06 PM
It's my name. You're not the first to make fun of it. Oh well, so is life. Do you have any comments about my side notes above? Specifically a modifier key for the way the heads and tails of clips interact on the timeline?
skibumm101 wrote on 4/25/2004, 5:02 PM
Spot, I know why you were asking!
GordyHinky wrote on 4/25/2004, 6:31 PM
What was Spot asking? Anybody else have comments?
Spot|DSE wrote on 4/25/2004, 8:27 PM
GordyHinky, it LOOKS like an abbreviation of a fairly famous person's name in Utah who is getting a lot of press. Not making fun at all, just had to ask because it's a pop-culture version of that person's name. Nothing more to add.
Regarding your problem, I'm just not understanding what part of ripple you aren't getting. Ripple doesn't add nor remove relative space from your project, it merely allows you to move either entire project length or entire track length in either direction, keeping all relevant events together.
I use Delete and Ripple religiously, it's such a great functionality for me.
GordyHinky wrote on 4/25/2004, 8:47 PM
What specific person?

I understand ripple. I don't understand why someone would use "Ripple" on + "Add Media To Cursor" = "Backwards Overlay". The timeline ripples leaving a big gap between the new overlayed clip and the next subsequent clip. Is there a real reason to use this feature or is it just an effect of the ripple function (kind of like being able to floor my car while it's in neutral but it will destroy my engine).

More importantly I was wondering if anyone had specific comments on hot the heads and tails of events work together (specifically how the left clip goes "under" the right clip). and if there is in fact a modifier key to change the relationship.
Spot|DSE wrote on 4/25/2004, 9:12 PM
In preferences, you can specify how the right/left crossfade relationship works, in terms of length of time. There is no shortcut key modifier.
I assume you are laying multiple pieces of media at once, and therefore getting automatic crossfades. you can also turn crossfades off.
Beyond that, I'm not understanding the specific of how you are destroying/creating backwards overlays.