HandBrake

Description of problem or question:

After encoding my video with a consntant frame rate (form a variable fr source) Medialinfo specifies that the output video has a constant FR but, when I import that video into Premiere Pro, the properties of the video says "Variable Frame Rate Detected" and again, the audio gets out of sync.
Any suggestions?
Thank you in advance.


Steps to reproduce the problem (If Applicable):



HandBrake version (e.g., 1.0.0):

Version 20181213145711-e5f4a5e-master (2018121401)
Nighty



Operating system and version (e.g., Ubuntu 16.04 LTS, macOS 10.13 High Sierra, Windows 10 Creators Update):

macOs High Sierra 10.13.3


HandBrake Activity Log ***required*** (see How-to get an activity log)

https://pastebin.com/Pg0jEA48

You didn't post an encode log, so I can't say for sure there isn't a problem, but it's extremely common for 3rd party software to mis-detect framerate type with HandBrake content. This is due to the 90Khz clock base we use which sometimes leads to 1 tick jitter that confuses a lot of software when reporting this.

Assuming nothing else is wrong, your content is CFR. Otherwise we'd need an encode log to double check.

Funny thing is, it's usually MediaInfo that reports our CFR as VFR

Hi, thanks for your reply.
So if I understand correctly, what you are saying is that the file is CFR (as Medialinfo indicates), and not VFR (as Premiere Pro indicates)? The thing is, that when playing the file in Premiere Pro, the audio is out of sync, which is what Premiere usually does when importing a VFR video.
I've attached the activity log here: https://pastebin.com/Pg0jEA48

The log you provided is of a scan, not the actual encode itself.

There should be one of the encode as well. https://handbrake.fr/docs/en/1.1.0/help ... y-log.html

Ups, sorry about that.
Here: https://pastebin.com/fuEkLXsM

The output is CFR, subject to the timebased imposed jitter.

It's amazing that in 2018 editors like Premiere are so broken they can't support VFR content, much less practically CFR content.

mduell wrote: ↑Sun Dec 16, 2018 8:19 pmThe output is CFR, subject to the timebased imposed jitter.

Which is zero since it's 24 fps, not 24000/1001. Not sure what's throwing Premiere off.

24.000/90000 gives an irrational quotient, if those numbers are correct.
So it is defaulting to its two nearest rational neighbors, I think.

It's 90,000/24 i.e. 3,750 ticks per frame.

musicvid wrote: ↑Mon Dec 17, 2018 12:49 am an irrational quotient

Is that like a positive negative number?

Rodeo wrote: ↑Mon Dec 17, 2018 11:55 am It's 90,000/24 i.e. 3,750 ticks per frame.

And of course that's correct.