> On Mar 27, 2018, at 5:16 PM, wm4 <nfx...@googlemail.com> wrote: > > On Tue, 27 Mar 2018 16:45:23 -0400 > Dave Rice <d...@dericed.com <mailto:d...@dericed.com>> wrote: > >>> On Mar 27, 2018, at 4:33 PM, wm4 <nfx...@googlemail.com> wrote: >>> >>> On Tue, 27 Mar 2018 16:11:11 -0400 >>> Dave Rice <d...@dericed.com> wrote: >>> >>>>> On Mar 27, 2018, at 4:01 PM, Derek Buitenhuis >>>>> <derek.buitenh...@gmail.com> wrote: >>>>> >>>>> On 3/27/2018 8:52 PM, Rostislav Pehlivanov wrote: >>>>>> I think we should drop the internal crap if the tools and the API support >>>>>> it. Would also solve a lot of issues like ffmpeg.c not trimming the start >>>>>> frame (so people complain all the time about longer files). >>>>> >>>>> I personally agree, but I thought I'd be diplomatic about it, since it >>>>> would >>>>> technically be losing a 'feature', since it would no longer Just Work(ish) >>>>> and require user applications to apply timelines themselves - and I >>>>> figured >>>>> some would argue that point. >>>> >>>> +1 I’m willing to contribute what information or samples would be needed >>>> to help with Matroska support with virtual timelines. IMO, this would be a >>>> valuable feature to have in ffmpeg. >>>> Dave Rice >>> >>> Some explanations how this interacts with editions would be good. >> >> I put an example with two editions at >> https://archive.org/download/chapters_test/chapters_test.mkv which mimics a >> digitized video > > Also this file lacks a chapter end time in the second edition. How is > that valid?
You’re right. I moved this discussion to cellar, but when the Edition is Ordered then ChapterTimeEnd is required. Dave Rice _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
