Hi,
I tried -fps 30000 1001
It is still 29.75.
BTW, why should be -fps 29970 1000 rounded to 29.75?
Thanks.
Hi,
I tried -fps 30000 1001
It is still 29.75.
BTW, why should be -fps 29970 1000 rounded to 29.75?
Thanks.
Hi,
Do you have any news regarding the issue?
For backwards compatibility with our older H264 products it is really important for us to have correct VUI timing parameters.
Thanks.
Hi,
The accuracy is 0.25fps like 29.25, 29.5, 29.75. So it has to be exact 29.97 in your product? Do you also use NVIDIA platforms in older products?
Hi,
Yes, we have to be exact. Otherwise the elementary stream is incorrect.
And with this accuracy there are standard framerates which cannot be set correctly, e.g. 29.97, 59.94. Moreover, in our product we have the option for framerate decimation - in those cases it gets even worse. Due to the incorrect framerate parameter handling the resulting encoder bitrate is quite off from the input paramerter we set.
The older products does not use NVIDIA platform, but the VUI framerate issue is general: it can be seen on every playback platform, e.g. all PC decoders I tried (including ffmpeg, VLC, MPC-HC) displays incorrect elementary stream FPS because the VUI is incorrect.
Regards.
Hi,
Could you please give me an info which version is the most probable?
Thanks.
Hi,
I really need an answer to be able to decide how to go on with our development. It is really urgent, please respond.
Thanks.
Hello,
We are checking it. If you need to prioritize the issue, please contact us to have further cooperation.
Please try attachment. It is verified by running following commands:
$ ./video_encode a.yuv 1920 1080 H264 out.h264 --insert-aud --insert-spspps-idr --insert-vui -fps 29970 1000
$ ffprobe ./out.h264
Would like to reiterate that you can always contact us to seek for direct technical support.
r32_1_libtegrav4l2.zip (71.5 KB)
Hi DaneLLL,
Thank you very much for the fast fix. My results:
As you advised, I will contact directly using the above link.