Cannot mux a H264 with AAC on .TS with Maximum overall bitrate of 8,000

[dogmydog]

It seems that something is wrong with your encoder.
I have made some attempts; try the following:
Re-encode your mov original with the following command line:

ffmpeg -i "4000283-original.mov" -c:v libx264 -crf 21 -r 29.97 -profile:v main -level:v 4.0 -c:a copy "4000283-original.ts"

Dear @Prowo, thanks for the help! I am happy to say that the client has accepted my encode.
Is there a way to do this in batch?

This forum is incredible

[dogmydog]

Hey guys, sorry to reopen this thread, but I'm having a very weird but with ffmpeg and Frame Rate.

When I run this line on my Windows 10 x64 PC with Geforce GTX 1660
ffmpeg -i "%%i" -i "curtaon.png" -filter_complex "overlay=(main_w-overlay_w)/2main_h-overlay_h)/2" -c:v h264_nvenc -preset slow -r 29.97 -g 90 -strict_gop 1 -profile:v main -level:v 4.0 -cbr true -b:v 6M -minrate 6M -maxrate 6M -bufsize 8M -muxrate 8M -c:a copy "E:\VOD\netnow\%%~ni.ts"

I get the correct frame rate my client wants
Frame rate : 29.970 (30000/1001) FPS

However, when I run a similar lin on a Windows Server 2012 (with no GPU)
ffmpeg -y -i "%%i" -i curtaon.png -filter_complex "overlay=(main_w-overlay_w)/2main_h-overlay_h)/2" -c:v libx264 -preset veryfast -r 29.97 -g 90 -strict_gop 1 -profile:v main -level:v 4.0 -cbr true -b:v 6M -minrate 6M -maxrate 6M -bufsize 8M -muxrate 8M -c:a copy "E:\VOD\netnow\%%~ni.ts"

I get a different frame rate:
Frame rate : 29.970 (29970/1000) FPS

I tried adding the argument (-x264opts force-cfr), but it didn't solve the problem.
Can anyone help me understand why I am gettin different results?

Thank you so much!

[poisondeathray]

-r 30000/1001

[dogmydog]

-r 30000/1001

Fantastic! Thank you so much for the quick reply.
But, for the sake of solving the mistery, why does NVENC and libx264 generate different results?

[poisondeathray]

why does NVENC and x264 generate different results?

In terms of framerate ?

Not sure, but the nvenc result is technicallly wrong, or there are some errors with reading. Something is making some assumptions or rounding errors with the timestamps

-r 29.97 is literally 29970/1000. (ie. it's 29.970000000000000...)

-r 30000/1001 is literally 30000/1001 (ie. it's 29.97002997003...)

These are not the same thing

[dogmydog]

why does NVENC and x264 generate different results?

In terms of framerate ?

Not sure, but the nvenc result is technicallly wrong, or there are some errors with reading. Something is making some assumptions or rounding errors with the timestamps

-r 29.97 is literally 29970/1000. (ie. it's 29.970000000000000...)

-r 30000/1001 is literally 30000/1001 (ie. it's 29.97002997003...)

These are not the same thing

I see. I am going to try the -r 30000/1001.
Thanks again and best regards from Rio!

[dogmydog]

why does NVENC and x264 generate different results?

In terms of framerate ?

Not sure, but the nvenc result is technicallly wrong, or there are some errors with reading. Something is making some assumptions or rounding errors with the timestamps

-r 29.97 is literally 29970/1000. (ie. it's 29.970000000000000...)

-r 30000/1001 is literally 30000/1001 (ie. it's 29.97002997003...)

These are not the same thing

I see. I am going to try the -r 30000/1001.
Thanks again and best regards from Rio!

Client has accepted the encode! Thanks @poisondeathray!