Avidemux Forum

Quote from: wokoxe2060 on June 30, 2021, 02:50:17 PMThat's interesting idea, but VP9 itsn't supported in M2TS officialy.

I had purely H.264 streams in mind like the one available for the ID I used for testing. I wonder what format Google uses to stream VP9 (for H.264, the video is split in short MPEG-TS chunks which actually just need to be concatenated). Of course, my recommendation applies to H.264 only (it would apply to HEVC if YouTube would use HEVC).

Quote from: eumagga0x2a on June 30, 2021, 09:06:24 PM

Quote from: wokoxe2060 on June 30, 2021, 02:50:17 PMThat's interesting idea, but VP9 itsn't supported in M2TS officialy.

I had purely H.264 streams in mind like the one available for the ID I used for testing. I wonder what format Google uses to stream VP9 (for H.264, the video is split in short MPEG-TS chunks which actually just need to be concatenated). Of course, my recommendation applies to H.264 only (it would apply to HEVC if YouTube would use HEVC).

Yeah, it should apply to av1, because it's supported in mp4... Anyway it's a good advice, because now we can record streams from beginning, unlike hls. But it's interesting how to extact vp9 stream from m2ts. Maybe it's possible to add support in ffmpeg itself...

In my unserstanding, "private stream" means the user of libavformat needs to know how to handle it, the data is entirely opaque for the demuxer.

Ok, the dev told me how to extract that private stream:
ffmpeg -i 1.m2ts -c copy -map 0:0 -f data raw.binAnd by next week, it should be possible in git master to force a suitable codec
I'll try recording more than 2 hours into m2ts, maybe it will work. I just hoped that you could fix that issue in ffmpeg itself, because you have much more expirence in coding than me.

hahah m2ts is not working, it just stop recording after 4 hours

[dash @ 000001b34a54dc80] DTS 1625 < 14400348 out of order39 bitrate=2330.8kbits/s speed=5.94x
[mpegts @ 000001b34be9ed80] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 1296031320 >= 146250
av_interleaved_write_frame(): Invalid argument
frame=863153 fps=355 q=-1.0 Lsize= 4096212kB time=04:00:00.38 bitrate=2330.2kbits/s speed=5.92x
video:3545012kB audio:225006kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 8.652330%
Conversion failed!

Quote from: wokoxe2060 on July 02, 2021, 07:31:26 PMI just hoped that you could fix that issue in ffmpeg itself, because you have much more expirence in coding than me.

FFmpeg is a beast at a completely different level of complexity and sophistication.

Quote from: wokoxe2060 on July 27, 2021, 06:56:18 PM

Code Select Expand

[dash @ 000001b34a54dc80] DTS 1625 < 14400348 out of order39 bitrate=2330.8kbits/s speed=5.94x
[mpegts @ 000001b34be9ed80] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 1296031320 >= 146250
av_interleaved_write_frame(): Invalid argument

As I wrote, it would be better to sidestep FFmpeg entirely. An application just needs to concatenate MPEG-TS chunks and start a new file on timestamp reset.