Re: [Cellar] matroska and side data vs timecode

[Tobias Rapp <[e-mail]>]

On 03.11.2019 11:29, Steve Lhomme wrote:
> [...]
> 
> If you want something that will survive this scenario you have to tie
> this value to the first timestamp. When remuxing, if timestamps are
> altered of portions at the beginning of the file are removed, you need
> to edit the first timecode. It may be better to store in the TrackInfo
> with both the first timestamp and timecode values. It may not work
> when stripping the audio (as Tobias pointed out). So it may even be
> put in the SegmentInfo instead of the TrackInfo.

It looks tempting to put timecode information inside the video track as 
they share the framerate as a common property. But in my opinion it 
would be cleaner to just copy that framerate info into the timecode 
value structure. For storing a single TC offset using an element in 
SegmentInfo sounds good.

> You may also set the value in Chapters (which are not tied to a
> track). There's already a start timestamp. You could add the timecode
> for this timestamp. That works for NLE sources as well, each
> non-linear part would be a chapter with its timestamp translation. A
> good NLE system would also tag this chapter with all kinds of data
> about the source. (Matroska was also designed for this case in mind).

Setting up a timestamp/timecode mapping via Chapters for non-continuous 
timecode situations looks like an even better solution than using a 
dedicated timecode track as this structure should represent the timeline 
for players.

Best regards,
Tobias