On 4/5/2018 8:14 PM, Rostislav Pehlivanov wrote: > I think it makes sense to have it in AVStream rather than as side data. > I don't have an opinion on whether codec switches should be indicated. It > would be nice for them to be a separate segment if that's possible and > reliable, since it would allow users to init all they would at startup. If > not then they can just handle them as they come like a stream and reinit if > they have to.
The consensus so far seems to be AVStream members, so I will switch to that approach. For codec changes, not all formats indicate codec changes up front, such as MPEG-TS which we may be streaming, so I think it has to be handled as it comes anyway. > After all this API only concerns complete files rather than > streams. 'Streaming' should actually be possible in the same sense you can stream a progressive MP4 of Matroska file, since this data is located in the same place as the index, which will be upfront (or at least, all in one place). - Derek _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
