Blu-ray frame rate of 48 & 24?

[clashradio]

Hello,

I'm working on a The Force Awakens Fan Edit using the 2016 Blu-ray as the source. When I rip the movie via DVDFab9Portable, it breaks the main movie into two files (00151 & 00153). When I checked the properties of the two files, I noticed file 00151 is at a frame rate of 47.952 and file 00153 is at the standard 23.976. I'm using Sony Vegas Pro 12 as my NLE. So when I "matched file properties to movie clip" (using the first file of 00151, since that's the first file I dropped into the timeline) does Vegas change the overall frame rate to 48?

I did a New Hope Fan Edit a few years ago and DVDFab split that up into two files as well, although I don't know if the first file was at the higher frame rate.

[_Al_]

You can set frame rate in project settings to whatever you like, 48 or 24 (simple numbers in reality they could be as you mentioned 23.976 and its double frame rate version). That match source is just newbie feature to set project properties when they do not know what to set.


Vegas just renders preview to a frame rate that is set in your project properties (if full preview is set) and if you generate new events it gives it that frame rate.
Otherwise any clip frame rate is converted only while exporting to whatever you set up export settings.

So if a clip is 48fps and you export 24, then it is resampled to that frame rate. It uses resample (if new frames are needed) or just skips frames or duplicate frames if you disable resample.

But anyway, hard to imagine different frame rates for the same BD title.

[jagabo]

And Blu-ray doesn't even support 47.952 or 48 fps.
https://www.videohelp.com/hd#tech

[clashradio]

So if a clip is 48fps and you export 24, then it is resampled to that frame rate. It uses resample (if new frames are needed) or just skips frames or duplicate frames if you disable resample.

So you're saying if I clicked the "disable resample" box in Properties, I don't have to worry the two different frame rates?

[_Al_]

No, that is just resample method.

You do not worry dropping 48fps and 24 fps on the same timeline.

Do you want to export 24p? Then export 24p, and Vegas would skip every other frame for 48p clip, with resample check or un-checked because frame ratio is exactly doubled, this is a special case. Might be wrong here, I think Vegas does that in this special case. If I'm wrong, then it just interpolates or blends (whatever is set in project properties) all frames to a new frame rate, but I think in this special case, it just drops frames.

Do you want to export 48p? Then export 48p but Vegas has to generate new frames for that 24p clip. If resample is checked, Vegas would calculate missing frames, if disabled, Vegas would just double each frame to to get 48p in this case.

[clashradio]

My goal is a BD25 @ 23.976fps. I selected "interplolate fields" as my Deinterlace method because I read if you have fast motion scenes, that's the best option.

[Cornucopia]

It's FILM sourced. It's not supposed to be interlaced, so you shouldn't be doing any deinterlacing to it.

Scott

[jagabo]

Once again: Blu-ray doesn't support 48 fps. So your 48 fps clips cannot really be 48 fps.

[_Al_]

Yes to above, but I messed up mentioning that interpolate and blend, that does not belong to re-sampling but for deinterlacing so I guess I was the cause for this confusion, you do not have interlace footage.

[clashradio]

Once again: Blu-ray doesn't support 48 fps. So your 48 fps clips cannot really be 48 fps.

Why does Vegas Properties show 48fps on that first clip?

As far as Deinterlace method goes, I should just select "none" and not "interpolate"

[jagabo]

Once again: Blu-ray doesn't support 48 fps. So your 48 fps clips cannot really be 48 fps.

Why does Vegas Properties show 48fps on that first clip?

Who knows but that's what you should be investigating, not deinterlacing or resampling methods.

[clashradio]

Once again: Blu-ray doesn't support 48 fps. So your 48 fps clips cannot really be 48 fps.

Why does Vegas Properties show 48fps on that first clip?

Who knows but that's what you should be investigating, not deinterlacing or resampling methods.

Thanks. There were (are) multiple issues I had so I listed a few of them to see which one I needed to tackle first.