On 3/29/2018 2:13 AM, Michael Niedermayer wrote: > Well, no unless we want a single unified API that represents information > about timespans. > We can use completely unrelated systems to handle the virtual timeline, > the codec and related changes, chapters, ...
Personal opinion time: From design and use perspective, an single unified API to handle all of those things an their edge cases sounds like a nightmare to use and write. - Derek _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
