[FFmpeg-user] retain timecode stream when transcoding v210 to FFV1/MKV

BloodMan bloodman at gmail.com
Sat May 3 13:57:57 EEST 2025


Hello Christian,

OK. right.
But in general you have answer in error description: " Only audio, 
video, and subtitles are supported for Matroska." This means that 
timecodes was not supported by matroska.

In RFC you have confirmation: https://datatracker.ietf.org/doc/rfc9559/
"11.  Timestamps - Historically, timestamps in Matroska were mistakenly 
called timecodes."

So, or at least that's how I understand it, Matroska doesn't have 
timecode support, only timestamp support - which is not the same and 
apparently "doesn't convert" - or at least that's not the role of the 
encoder.




W dniu 2025-05-03 o 12:01, Christian Sievers via ffmpeg-user pisze:
> Thanks!
> 
> @BloodMan Yes I had seen that hint.
> 
> @John Curtis
> 
> Both commands throw up the same error message:
> 
> [matroska @ 0x7fdaabf0a2c0] Only audio, video, and subtitles are supported for Matroska.
> [out#0/matroska @ 0x7fdaabf07340] Could not write header (incorrect codec parameters ?): Invalid argument
> [af#0:1 @ 0x7fdaabf0fec0] Error sending frames to consumers: Invalid argument
> [af#0:1 @ 0x7fdaabf0fec0] Task finished with error code: -22 (Invalid argument)
> [af#0:1 @ 0x7fdaabf0fec0] Terminating thread with return code -22 (Invalid argument)
> [out#0/matroska @ 0x7fdaabf07340] Nothing was written into output file, because at least one of its streams received no packets.
> 
> I can’t post a link to an example file here because I don’t have the rights to do that, and I can’t make an excerpt that still has the timecode track … it’s a catch 22 :)


-- 
Pozdrawiam,
bloodman at gmail.com


More information about the ffmpeg-user mailing list