Converting GH2's Variable 80% to 100% @ 29.97

pdxalex wrote on 9/26/2012, 4:19 PM
Greetings,

I've done a lot of googling, to no avail...

I have some footage recorded with the GH2 in variable mode at 80% (of real-time speed) at 23.976 fps. I need to speed up the footage to real-time 100% (ie 1.25x) and render as 29.97.

Total noob in this regard. How can I speed up the footage exactly 1.25x with best results? I've used the velocity envelope in other projects but can't set it to exactly 125% and speeding up playback rate while experimenting with switches (disable, force, smart resample) doesn't seem to affect output. I still end up with a slow motion (80%) clip rendered at 29.97.

Thanks, any help much appreciated.

Edit: I'm on Vegas 11

Comments

JasonATL wrote on 9/26/2012, 5:14 PM
I'm assuming you are in a project with a framerate of 29.97. With the media on the timeline, right click on it and select Properties... Now change the Playback rate to 1.25. I suggest that you also set "Disable Resample".

Edit: Also, to set a velocity envelope to a specific number, right click on the envelope node and select "Set to".
john_dennis wrote on 9/26/2012, 6:08 PM
A brute force method would be to export a still image sequence from the 23.976 project timeline. Then, import the still image sequence into a 29.97 project.
pdxalex wrote on 9/26/2012, 6:18 PM
Thanks for your reply.

Jason, I tried this and it seems output is correct - but Vegas then "fills" the "missing time" from original clip by looping the beginning part.

For example, my original test footage is 1min in actual time but being recorded at 80% it shows up as roughly 1min 13s. So I select "disable resample" and set playback to 1.25. Result is a clip at 100% realtime... all good... but the length should be only 1min. Instead the rendered video is still 1min 13s... the first 1min is fine, but then vegas fills in another 13s by playing part of the beginning again.

I think this is the cause for my confusion... I hadn't noticed it was doing this before :(

I hope that made sense. How can I just end up with the 1min rendered video?
john_dennis wrote on 9/26/2012, 6:27 PM
Drop the video on the 23.976 project timeline.

Zoom out so you can see the end of the 1 minute 13 second clip.

Hold down the Control key and drag the right end of the clip back to 1 minute.

Render to a 29.97 output.

Disable resample if it looks better.
pdxalex wrote on 9/26/2012, 6:40 PM
Thanks John, but 'dragging' the clip to change velocity isn't really precise.

I noticed using Jason's aforementioned method though that Vegas inserts a "notch" in the timeline and I can just manually trim the clip afterwards.

Thanks for everyone's help.
john_dennis wrote on 9/26/2012, 7:34 PM
I gave you the most precise answer first.
JasonATL wrote on 9/26/2012, 7:44 PM
I don't quite understand your issue.

You seem to want to speed up a 1:13 clip and have it still last 1:13. It won't. Time goes by faster. My method works fine (at least you seemed to indicate that it did), except the clip on your timeline is still 1:13. Now, just cut the clip at 60 seconds: notice the notch on the top of the clip? That's the end of the clip.

Alternatively, use John's method (either one of them).
pdxalex wrote on 9/26/2012, 7:53 PM
Jason, sorry if I wasn't clear. I *don't* want it to still last 1:13... I know it should be shorter, as it plays back faster. But that's the point... the rendered clip wasn't short - which resulted in some confusion. I initially didn't realize part of the (nature) clip was being looped. After trimming before rendering, the result is correct speed and shorter - which is all good - thank you.

John, and I really appreciate it. It's just somewhat of an indirect method / work-around. I've actually never tried it before and it's great info... gave it a try and it worked like a charm. Definitely something to keep in mind, thanks!
Chienworks wrote on 9/26/2012, 10:10 PM
Actually, Calculating the correct endpoint and Ctrl-dragging to it is the ONLY guaranteed accurate method. The difference in speed between two frame rates may not always be three or fewer decimal places and you can't type more than three in either the clip properties or the velocity envelope. Ctrl-drag will accurately frame-align the speed change. So, when i need it to be right,