Vegas 18 detects wrong FPS, then re-conforms frame rate based on that

FPSproblem wrote on 9/17/2020, 11:26 AM

I was working on a 23.976 project in Vegas 15.

I open it in Vegas 18, and now there's resampling all over the place because suddenly Vegas has decided that all my 23.976 video files are 25fps for literally no reason. There is nothing in the metadata to suggest this should ever be the frame rate. Even within Vegas in the stream info it says 23.976. Despite that, it decides 25fps, and the "option" to change that is permanently greyed out. Disabling resampling does not fix it because Vegas is still mistakenly trying to conform the video, so there are duplicate and missing frames now.

How do I tell Vegas to stop being stupid?

Comments

VEGASDerek wrote on 9/17/2020, 12:21 PM

@FPSproblem: could you provide a MediaInfo printout of the media you are experiencing this problem with?

FPSproblem wrote on 9/17/2020, 12:28 PM

@FPSproblem: could you provide a MediaInfo printout of the media you are experiencing this problem with?

https://pastebin.com/gM8E11rC

It's [a file that looks exactly like, but isn't] a blu ray put through handbrake to get Vegas to recognise it. [It would appear to some who didn't know this that] I'm cutting down the movie Grand Prix (1966) to a more reasonable length by getting rid of some bad acting and subplots. Also editing the sound of the ending for less of a whimsical feel :)

michael-harrison wrote on 9/17/2020, 12:32 PM

I don't know if 18 still has this problem but with previous versions, the common recommendation is to convert VFR video to CFR. Yours only varies from 23.974 to 23.981 but still, I'd try re-handbraking the original and setting your frame rate to 23.976 if that's what you need

Also, you could have just pasted the mediainfo into your forum post

System 1:

Windows 10
i9-10850K 10 Core
128.0G RAM
Nvidia RTX 3060 Studio driver [most likely latest]
Resolution        3840 x 2160 x 60 hertz
Video Memory 12G GDDR5

 

System 2:

Lenovo Yoga 720
Core i7-7700 2.8Ghz quad core, 8 logical
16G ram
Intel HD 630 gpu 1G vram
Nvidia GTX 1050 gpu 2G vram

 

vkmast wrote on 9/17/2020, 12:37 PM

Copyrighted material?

FPSproblem wrote on 9/17/2020, 12:44 PM

Copyrighted material?

Edit3: It's not Grand Prix (1966), it just happens to look like the Blu Ray copy of my own disc which I own in media info. I made the film which coincidentally has the same running time and it has nothing to do with anyone if it makes you stop wetting your bed.

I don't know if 18 still has this problem but with previous versions, the common recommendation is to convert VFR video to CFR. Yours only varies from 23.974 to 23.981 but still, I'd try re-handbraking the original and setting your frame rate to 23.976 if that's what you need

Also, you could have just pasted the mediainfo into your forum post


Noted, will paste directly next time. I'll try that. I hope the frames stay the same so my edits still work! I just wish I could remember the settings I used the first time - I did it a couple of years ago now. On that note, is there a better way to get Vegas to accept MKV files without transcoding/diminishing quality now?

EDIT: don't need the handbrake conversion - there's an mkv reader in the file I/O options in preferences. Going to see if that gets it right.

EDIT2: Nah, Vegas crashes when I so much as hover over the mkv file lol

Musicvid wrote on 9/17/2020, 1:22 PM

Regardless of its age, if you downloaded a ripped MKV of your movie, it is piracy. Ripping a disc you purchased is not strictly illegal in the U.S.

Normal practice on this forum is to not discuss these issues publicly, as many of our contributors make all or a portion of their livelihoods from the production and distribution of commercial copyrighted media content, and are bound by professional association requirements.

What you got from your previously ripped Handbrake file is probably encoded wrong; we call them "frankenfiles." There is no help for that, sorry.

 

FPSproblem wrote on 9/17/2020, 2:18 PM

What you got from your previously ripped Handbrake file is probably encoded wrong; we call them "frankenfiles." There is no help for that, sorry.

I mean, it works in Vegas 15. I'm not sure Vegas seeing a self-declared 23.976fps file and going "YES THAT OF COURSE MEANS 25fps! And no you can never change my mind." is a fault of an encoder, but okay. Looks like I'm delving into handbrake settings again.

Musicvid wrote on 9/17/2020, 2:30 PM

If you delve into the topic of "soft telecine" vs. "hard telecine" in optical disc production, the discrepancy will make more sense to you. The legal movie disc specifications are 25 PAL and 29.97 NTSC.

24p (23.976) film source is often flagged 25i or 29.97i for conformity with the standards. I give you 99.97% certainty it is not a Vegas issue, since I have done dozens of MakeMKV->Handbrake conversions of my own discs for my own use. The correct Handbrake setting is "Constant Frame Rate, Same as Source." If your source is hard telecine (scan lines), you need to take care of that in Handbrake, not Vegas. Hope this helps.

Here is the opening flyover from Avatar done correctly at 24p (23.976):

And here it is done incorrectly at 29.97 NTSC. See the difference?

FPSproblem wrote on 9/17/2020, 3:41 PM

24p (23.976) film source is often flagged 25i or 29.97i for conformity with the standards. I give you 99.97% certainty it is not a Vegas issue, since I have done dozens of MakeMKV->Handbrake conversions of my own discs for my own use. The correct Handbrake setting is "Constant Frame Rate, Same as Source." If your source is hard telecine (scan lines), you need to take care of that in Handbrake, not Vegas. Hope this helps.

Yes, I see the difference, but I'm afraid your example does not apply here.

It's flagged 23.976p everywhere I can find it outside of Vegas (and INSIDE Vegas!). All programs other than Vegas see 23.976p. Vegas sets it to 25p, not 25i. There is no automatic de-intelacing going on, nor is it necessary; Vegas 18 is handling it incorrectly - the file is not, nor was it ever interlaced, and is 23.976p in literally every sense, and moreover Vegas 15 already handles it 100% correctly!

Musicvid wrote on 9/17/2020, 3:51 PM

[EDITED]

Ok, best of luck.

FPSproblem wrote on 9/17/2020, 6:18 PM

I re-encoded in handbrake with a definitely non-variable frame rate (I think I did before anyway), and Vegas 18 still incorrectly processes it as 25fps. Vegas 15 still interprets it correctly.

john_dennis wrote on 9/17/2020, 6:49 PM

In the trade, this is known as a non-problem.

FPSproblem wrote on 9/17/2020, 9:39 PM

In the trade, this is known as a non-problem.

Interesting. So I would assume duplicated and missing frames/shoddy resampling artifacts are present in abundance in your professional work?

Vegas 18 processing a 23.976fps file as if it were 25fps in a 23.976 project and breaking said project due to this is not a non-problem. It's an issue not present in Vegas 15.

Can I give you the opposite of a "thank you"?

Musicvid wrote on 9/17/2020, 10:03 PM

Interesting. So I would assume duplicated and missing frames/shoddy resampling artifacts are present in abundance in your professional work?

Vegas 18 processing a 23.976fps file as if it were 25fps in a 23.976 project and breaking said project due to this is not a non-problem. It's an issue not present in Vegas 15.

Can I give you the opposite of a "thank you"?

Ok, that's enough. You are addressing an Engineer with nearly a half-century of experience as if he were a streetcorner punk. And I quite agree, your third generation copyrighted material is not a player in anyone's game. Forum rules are here, suggest you practice mutual respect, or else find yourself a new sandlot.

Pay particular attention to Sections 1, 2, 3, and 5.

https://www.vegascreativesoftware.info/us/community-rules/

If you wish to pursue this further, the official Support link is at the top of this page. Don't bother us.

And by all means,

 

EricLNZ wrote on 9/17/2020, 10:50 PM

@FPSproblem Please post your mediainfo here on the forum, not to an external site. There is an upload button for this purpose

michael-harrison wrote on 9/18/2020, 8:19 AM

@EricLNZ copy and paste works even better.

@FPSproblem post media info for the latest file

 

System 1:

Windows 10
i9-10850K 10 Core
128.0G RAM
Nvidia RTX 3060 Studio driver [most likely latest]
Resolution        3840 x 2160 x 60 hertz
Video Memory 12G GDDR5

 

System 2:

Lenovo Yoga 720
Core i7-7700 2.8Ghz quad core, 8 logical
16G ram
Intel HD 630 gpu 1G vram
Nvidia GTX 1050 gpu 2G vram

 

FPSproblem wrote on 9/18/2020, 2:30 PM
Pay particular attention to Sections 1, 2, 3, and 5.

https://www.vegascreativesoftware.info/us/community-rules/

Okay.

1. I would suggest that John keep his comments factual and objective by not suggesting that my issue does not exist - otherwise why would I even be here? Kind of breaking rule 3 there as well.

2. I was very clear on what my issue was, and it was not "unfriendly". What could be considered unfriendly, perhaps, is wandering into a forum topic and chastising someone for owning a blu-ray, then heroically coming to the aid of someone else who arrives and declares that their issue doesn't exist.

3. This is not a repeat, nor meaningless topic. I would suggest you read this rule also before bringing up something only tangentially related like interlacing etc.

5. At no point during any post have I requested, promoted, advertised or linked to any copyrighted material.

Bye.

I'm re-re encoding in handbrake. I don't think there's a combination of settings that Vegas 18 won't commit this error with. I'll paste the mediainfo here when it's done - the last two encodes still say VFR even though I have constant frame rate applied, so at this point both V18 and handbrake could be at fault (though bear in mind V15 STILL interprets it correctly!).

michael-harrison wrote on 9/18/2020, 3:46 PM

Not that my voice carries much weight here but I'm with FPSP on the copyright "issue."

1. It should never have been brought up ( @vkmast) and became a distraction.

2. The legality of ripping discs is country dependent and in many (most), doing so for personal use is perfectly legal. Even in countries where doing so for personal reasons *isn't* legal, I.E. the U.S., because you have to break encryption to do it, it's not remotely morally wrong.

3. He never once said or implied he was going to something illegal with the resulting rip.

IMO this thread should be locked and @FPSproblem should be encouraged to start a new thread, focusing on the technical issue he's facing.

Last changed by michael-harrison on 9/18/2020, 3:51 PM, changed a total of 1 times.

System 1:

Windows 10
i9-10850K 10 Core
128.0G RAM
Nvidia RTX 3060 Studio driver [most likely latest]
Resolution        3840 x 2160 x 60 hertz
Video Memory 12G GDDR5

 

System 2:

Lenovo Yoga 720
Core i7-7700 2.8Ghz quad core, 8 logical
16G ram
Intel HD 630 gpu 1G vram
Nvidia GTX 1050 gpu 2G vram

 

FPSproblem wrote on 9/18/2020, 6:33 PM
IMO this thread should be locked and @FPSproblem should be encouraged to start a new thread, focusing on the technical issue he's facing.

Excellent idea. I need to either work out why handbrake won't generate a constant frame rate file no matter what I do (in order to repel further hordes of people willing to make excuses based on that single fact as to why Vegas 18 is somehow designed to intentionally incorrectly determine the frame rate), or give up entirely and re-install Vegas 15.

I'm leaning toward the latter.

michael-harrison wrote on 9/19/2020, 3:18 AM

fwiw, I've never had HB fail to create a FFR file when I converted from VFR.

Make sure you're choosing "Constant Framerate" and not just selecting the rate in the dropdown on the video tab.

Also make sure you're using the latest version.

System 1:

Windows 10
i9-10850K 10 Core
128.0G RAM
Nvidia RTX 3060 Studio driver [most likely latest]
Resolution        3840 x 2160 x 60 hertz
Video Memory 12G GDDR5

 

System 2:

Lenovo Yoga 720
Core i7-7700 2.8Ghz quad core, 8 logical
16G ram
Intel HD 630 gpu 1G vram
Nvidia GTX 1050 gpu 2G vram

 

FPSproblem wrote on 9/19/2020, 10:21 AM

I am doing that, and I updated handbrake just to make sure. Still does it.

 

Anyway, in the meantime I found a solution that will solve this issue for anyone who runs into it:

Use Davinci Resolve instead.

It can even import the project (it does majorly ruin the audio edits, though!).