Using the Pan/Crop feature allows motion on individual events, just no 3D moves as this requires Track Motion which, as j razz suggested, can also be used.

What is the reason that Vegas will not do motion to individual events?

It does. SImply click on the pan/crop icon on any event and then move or re-size the pan/crop window.

Are you having difficulty with achieving individual track motion for an invidivual event then place THAT event on its own track. OR are you asking a reasoning behind the whole TM thing? Hmmm.. I guess it maybe because Vegas comes from a linear stable that was Audio and that relies on tracks? And each element is regarded as a separate piece of media?

Damn fine question . . but as I say, if you want to TM an idividual event - as above. But of course you can ALSO Parent/Child whole groups of individual Events in individual tracks and have this PARENT track TM the whole family with its siblings . .and even THAT parent you could make a child to its OWN Parent and so on and so forth . . The possibilities are almost endless.

So, asking the question may get you an historical reply BUT it wont get you any further in delving into some of the more spectacular options and possibilities THAT is Vegas.

TM, within Vegas, is extraordinarily spectacular.

Grazie

I would want to do it just for completeness sake. We can have event pan/crop, so why not event motion? For that matter, why don't we have track pan/crop too? Yes, we can put an event on a separate track, but that gets messy. We can keyframe the motion so that it only affects one event, but that gets messy.

Yes, Kelly, I appreciate your and my wish for "completeness" I'd call it a type of mirroring ( there IS another word, it escapes me at present ), but I was attempting to respond to the question.

Hey, while we are on completeness how about synching GenMed and GenText to the Timeline?

Grazie

I know that you can add several events to atrac and use keyframes to control motion. But as Cienworks said, it can get messy. Also too many tracks with just one event makes no sence. So, yeah, what's the history behind "Track Motion". Why can't it work like pan and crop?

The old 3d plugins from debugmode.com were a solution to event based motion that did not use the pan/crop tool They were subsequently rolled into Wax. So you can still find them in there.

Another argument in favor of event-based motion (which you can sort of accomplish with Pan/Crop) is that using an entire track for 3D will significantly slow down render. It's much better now than it was earlier, but it still makes for a slower render. This is where the old Debugmode tools come in very handy.

OK, I'm getting a hang of this now.

What we have here is a list of that which WE know we are being affected by:

#1 - Messy to have single Event Motion - We all agree

#2 - If something works in one way, then it should work in another way - Kelly's point - I'm assuming we all agree? I do!

#3 - Render times in Track based motion are significantly increased, this is a bad thing - I hope we all agree with this - I do!

So getting back to the original, excellent, observation, how, "In all that was Mr Ford" ( quality testing etc etc . ) do we get Madison to hear this? Not necessarily just in the detail, but our awareness of just why this needs to be surmounted?

Douglas? Might it be possible for Vegas just to "see" the area that needs to be rendered rather than the whole shebang? A kind of "Mute" track until you hit IN-point-#1 > OUT-point-#1? Now THAT would be neat anyway! A selective vertical muting option!! Just mute the areas that are "vacant" of events? A kinda Event-Aware Envelope!!!


Grazie