59,94 video on a 50fps timeline

relaxvideo wrote on 10/16/2014, 12:43 AM

How can I use it perfectly, without frame dropping, etc?
Slower playback is not a problem, it's only nature shots.
I know i have to set disable resample.
But how do i set the playback speed exactly to 50/59,9400599400599 ?

I can set 0,834 at event propertie playback rate, but that's not
exactly 0,834166666, so sometimes it will double or drop a frame. Vegas need an interpret footage dialog finally.

Any advice? And also the opposite: 50fps video on a NTSC timeline..
thanks

Comments

PeterDuke wrote on 10/16/2014, 2:35 AM

Set project Properties to old frame rate. Change the timeline ruler to Absolute Frames. Note exactly how many frames long your movie is. Change Properties to the new frame rate. Ctl+Drag the end of the movie so it is now the exact same number of frames long.

PeterDuke wrote on 10/16/2014, 2:40 AM

Note that 59.94 etc is an exact rational number, viz, 60x1000/1001

relaxvideo wrote on 10/16/2014, 5:02 AM

Peterduke:
So if i use this method, it will be 100% accurate? Even for a long project? I mean when i do your method, at event properties i see that playback speed is changed to 0,834. But is it 0,834 exactly or more precise just Vegas cannot show here the value? This would be good.

Let's do the math and say i have a 5 minutes NTSC footage,
that's 300 second.

When i set playback speed manually to 0,834 i get 359,71223 sec playback on a 50fps timeline.

But in reality i should have 300 / (50/59,94) = 359,6403 sec!
The difference here is almost 4 frames in a 5 minutes video.

If we use only 0.834 that's will produce sometimes doubled frames, right? Hope your method is perfect, and hope Vegas will support interpret footage (just like AE) in the future..

farss wrote on 10/16/2014, 6:00 AM

Yes this method is 100% accurate.

1) It was recommended by the developers many years ago, they did not recommend any other method.

2) It's working with absolute frames. You're telling Vegas to playback x frames in y time. It'll internally do the calculations to give exactly that outcome.

3) The indicated playback rate is limited to a certain precision probably so it doesn't become a distraction with insignificant errors causing it to display things like 23.97600000001

Bob.

Chienworks wrote on 10/16/2014, 1:52 PM

Would be nice if the dialog boxes weren't limited to 3 decimal places.

PeterDuke wrote on 10/16/2014, 8:03 PM

I should have acknowledged Bob (farss) as my source. I now do so.

farss wrote on 10/17/2014, 4:20 AM

[I]"I should have acknowledged Bob (farss) as my source. I now do so."[/I]

I'm humbled but it's not my invention. My only claim to fame is having a long memory helped by me having used that technique several times to great advantage.
SCS should make more mention of this capability of Vegas.

Bob.

Chienworks wrote on 10/17/2014, 11:12 AM

I once suggested that Vegas should have a media properties option that does this automatically: play back file at project frame rate. The developer's objection was that this could mess up the audio. Well, perhaps it should then have options for "stretch audio to match, don't stretch audio, or ignore audio".

PeterDuke wrote on 10/17/2014, 6:00 PM

I think audio is always stretched/shrunk to match, is it not? I don't think there is a way to prevent it in Vegas.

Chienworks wrote on 10/17/2014, 7:23 PM

If it's grouped, it is. If ungrouped, it's not.

For that matter, almost all of the files i might wish to use this feature on are video-only.

PeterDuke wrote on 10/18/2014, 7:51 AM

Ah, good to know. Thanks.