Limited fast motioning with ctrl-drag

Flyarbo wrote on 2/10/2010, 5:14 PM
Why is the control-drag method of accomplishing fast motion on a video event so limited?

I'm familiar with the rigmarole of rendering -- recompressing -- rendering -- recompressing to achieve the desired amount of compression, but you also lose a little definition every time you do that; never mind the fact it's a goofy, clunky workaround and something we shouldn't have to do.

Why is it this way? Am I missing something? Why are we not allowed to time-compress all we want with a simple, single motion?

tracking: 10BAF9BA-15F7-4A2C-9E89-2F19A5E405BA

Comments

rs170a wrote on 2/10/2010, 5:38 PM
Why are we not allowed to time-compress all we want with a simple, single motion?

Because that's not the way Vegas does it.
The simple (i.e. free) way is to do a 12x increase, save that as a veg file, drop that veg file on the timeline and repeat as necessary.
No recompression necessary or required.
The other way ($80 U.S.) is to buy Veggie Toolkit.
One of it's many features is Time Bandit which allows you to speed it up or slow it done as much as you want in a single operation.
The choice is yours.

Mike
Flyarbo wrote on 2/10/2010, 6:08 PM
Mike:

A. Thanks for the Veggie Toolkit tip. Worth looking at.
B. Never would have thought of dropping a veg on a timeline. That's pretty cool, too.
C. Can't agree with your relaxed attitude on this subject. Why give us a feature that only kinda-sorta does something well?
D. My question was a user-interface purist kinda thing. Usually I combine a velocity envelope AND ctrl-drag to get screaming fast speedups. Works well, but still shouldn't have to do it.

Apparently there are lotsa ways to do fast motion.

:)
rs170a wrote on 2/10/2010, 6:21 PM
Why give us a feature that only kinda-sorta does something well?

Vegas started off as an audio only app.
Video was introduced in version 2 or 3 and that was at least 10 years ago and, back then, a 12X increase was a lot.
For whatever reason, the developers have seen no reason to change it.
Feel free to suggest it as an improvement.

Mike
Chienworks wrote on 2/11/2010, 2:50 AM
As a programmer and UI designer i can certainly understand a feature having limits. What i don't understand in this case is why the limit is 4x and not 40x, or 400x, or 4000x.

Shuttle speed used to be limited to 4x. Somewhere along the way an option was added to allow 20x. That's a big improvement, but once again i wonder why only 20?
bill-kranz wrote on 2/14/2010, 7:08 AM
"...dropping a veg on a timeline"

I thought this was how all the native video (veg) projects worked. I assume
someone was having a bit of humor in their reply.
As a newbie what is the exact reasoning for using the fast motion process? Don' t
you use the various file formats when rendering to get different levels of compression or
even use other methods to package and a send a movie clip?

Thanks,
Bill
Chienworks wrote on 2/14/2010, 12:29 PM
Bill, that refers to project nesting. You can drop an entire project into another project as it it was a media event. By doing this you can apply multiple levels of speed adjustment without any intermediate rendering.

The exact reason for using the "fast motion" process is to get faster motion. No more, no less. It doesn't have anything to do with file formats or compression.
bill-kranz wrote on 2/14/2010, 8:10 PM
Chienworks:

Hi. Thanks for those tips. I have not got into project nesting or media events yet but I have added one veg clip to the back end of the first one on the same timeline.

If I make a avant-garde piece I may add some "fast motion" but otherwise I am making straight documentaries.

Thanks,
Bill