-
Track Motion (conceptually)
I’ve finally gotten comfortable with Vegas (thank you John Rofrano and Mike Kujbida, in particular) to the point of having output several TV spots now and having totally cut the cord from my prior system of ten years (thanks again, Mike K… you were so right).
What I’m wondering, though, is if I’m missing something about Track Motion: I get how it works, and have been able to produce with it, but what I’m not understanding is why somebody thought it would be a better idea to assign keyframes for position and motion and such to an entire track (only) instead of just to the individual events on a track.
Point being, it just seems so cumbersome and counter-intuitive (to me… Mike, please be nice) to have separated events on a single track– each with their individual static positions and movement characteristics– all dictated by the keyframe information of the track and not contained within the events themselves. Meaning, if I have several events on a track, each with their own specific keyframe instructions, it seems so much more intuitive if there existed “Event Motion” instead of (or in addition to) “Track Motion” when it comes to sliding stuff around on a track after initial placement.
I pose this because I just keep running into so many situations where, when I’ve made an initial composition of things together with holds and moves and such, when I move them to new places the keyframes (on the “track” level) don’t necessarily move with them and I wind up with a big mess I have to go back and fix (and fix again if I make additional changes).
Granted, I’ve noticed that many times when I slide an event earlier or later the first keyframe will go with it, but subsequent keyframes won’t, for some reason (maybe someone can enlighten me as to why). Maybe I’m ignorant as to how to move an event and guarantee that all its track motion keyframe information go with it (?)
So… here’s where I ask you to help me change my paradigm if I’m the only one thinking that Track Motion is “crude” in its structure.
Thank you (and I’m really not a bad person),
–Kelly
-
1 Reply
-
Kelly, congratulations on the “divorce”.
I know that it was a tough break initially but I’m glad to see that you’re happy with your decision.Now back to the issue at hand.
For each time that I use Track Motion, I use Pan/Crop at least 100 times.
Pan/Crop works at the event level and there are few options that Track Motion offers me that I can’t do in Pan/Crop.
Other times I create something (for example, a show opening that uses Track Motion) in a separate instance of Vegas, save it and then import that veg file (i.e. “nesting”) into my current project.
Reply to this Discussion! Login or Sign Up