-
Notifications
You must be signed in to change notification settings - Fork 151
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: OpenRV 2.1.0 getting wrong framerate for movie files #600
Comments
I have a fix for this issue, I just haven't had time to report or submit a PR. The issue is due to ffmpeg version update. For mov containers, using the streams time_base as the frame rate for timecode is not correct. OpenRV/src/lib/image/MovieFFMpeg/MovieFFMpeg.cpp Line 1341 in 6226c5a
Using AVStream.avg_frame_rate should be the correct thing to use as that is what ffmpeg is using to encode the timecode for mov container files. This issue can be easily replicated using the Alab trailer media. The start frames are incorrect for the mov media in OpenRV. |
Hey @markreidvfx Thanks for the pointer in the right direction!
did the trick and OpenRV now is getting the correct framerate for mov containers. However we still get the console log: this is coming from ffmpeg: which is called here in openrv: OpenRV/src/lib/image/MovieFFMpeg/MovieFFMpeg.cpp Line 1364 in e551a0d
and So it seems it's calculating the framerate wrong somewhere else too. |
I believe it needs to be fixed in two spots. OpenRV/src/lib/image/MovieFFMpeg/MovieFFMpeg.cpp Line 3611 in 6226c5a
Maybe that will fix your audio issue. I also removed those weird hack about wrong framerates here OpenRV/src/lib/image/MovieFFMpeg/MovieFFMpeg.cpp Line 3615 in 6226c5a
I'm not really sure what that is all about, it seems very incorrect to me. I also only limited using |
for mxf you are right, but I think mp4 needs the same adjustment as mov have you tested with mp4 files? |
MOV and MP4 are essentially the same format, they use the same demuxer in ffmpeg. It's used for all these formats. (It's also used for cr3 raw files)
|
MKV and other containers are another issue entirely... If there is no metadata telling us what the timecode rate its impossible to know the start_frame exactly. moov Atom (mov) and MXF formats actually store the timecode as the number of frames, not a string, it would be nicer if ffmpeg exposed that, or the tc rate. |
how are you exactly checking if the list contains Before I was thinking about checking it like mircotornow@cb27612#diff-f87f8f114f0b9c97fdc4c1c6b87698cf860d0e01d0ae5bafdd55bfa24dffcfc7R706 |
I'm currently doing the same thing. |
What happened?
Hi all.
We noticed a very strange behaviour with our newest rv build (2.1.0 Head: f9e45c7)
When opening movie files (.mov, codec doesn't seem to matter, happens in prores, h264, dnxhd) rv is somehow getting a wrong framerate. (2 instead of 24)
It's also printing following to the console:
WARNING: Using non-standard frame rate 2400/1000
It was working fine in previous versions (openrv1.0 and openrv2.0 (our latest working head: f3066e7)
Here openrv2.0 on the left and 2.1.0 on the right
The FPS is set to 24 for both.
The different framerate results in wrong frame numbers, which is very annoying and makes it unusable in production.
Can anyone confirm that this is happening for them too?
Cheers
List all the operating systems versions where this is happening
CentOS7, Windows10
On what computer hardware is this happening?
any
Relevant console log output
Environment variables
No response
Extra information
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: