[Peter Kerr]

My newly compiled latest ffmpeg does indeed mux to .m2ts, but alas, I still get the same double speed video; but at least now I can post it as a bug in ffmpeg. Thanks for your help.

[Peter Kerr]

I thought someone might say my ffmpeg looked long in the tooth! I managed, eventually, to download and compile the latest ffmpeg and x264 sources, but I still get the same funny parameters, including r_frame_rate 100/2 and timebase 1/1,200,000.

Unfortunately the only tool I can find which will mux to .m2ts is tsMuxer. As far as I can see MP4Box does only do what its name says.

I’ve tried looking at x264 encoding guides but there don’t seem to be any options relating to the parameters I’m interested in except -r 50/1 which is still giving the same output as -r 50.

If I could find where in the .h264 file the r_frame_rate.num and .den values are stored I could try a hack and overwrite them with 50 and 1, but I can’t find X00640002 (2 byte int) or X0000006400000002 (4 byte int) in the file. I suppose I could eventually work it out from tracing the code in ffprobe.

All very frustrating. The key to this is no doubt understanding just why ffmpeg is choosing such strange values for r_frame_rate and timebase in the first place.