[gstreamer-bugs] [Bug 540890] Need generic way of handling multi-track/chapters files

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=540890
  GStreamer | gstreamer (core) | git

--- Comment #45 from Sebastian Dröge <slomo at circular-chaos.org> 2010-08-04 07:51:43 UTC ---
(In reply to comment #36)
> > > I suggest to add TOC query (which contains query mode - whether to get full TOC
> > > or to get position to insert other TOC entries), which will return UID of the
> > > parent GstTocEntry (where to insert another TOC elements) and the type (chapter
> > > or edition) of GstTocEntry which can be inserted in that parent entry (for
> > > example, we return 0 for UID and EDITION for the type, which means that other
> > > entries should be inserted right into the root TOC and these entries should be
> > > editions) in case of position request mode, and full TOC in case of TOC request
> > > mode.
> > 
> > Well, I'd probably use a single TOC query type and it will always return the
> > complete TOC but contains some kind of marker for the TOC Entry for the pad
> > over which the query was received. That's probably a bit easier.
> >
> 
> 
> Just to be sured that I understood all the things correctly: some element
> receives TOC query, then it checks the pad over which that query was received
> and decides which TOC entry to mark as "extendable" (or some kind of that) and
> returns UID of that TOC entry with the full TOC. Is that right?

Something like that, yes.

(In reply to comment #37)
> (In reply to comment #35)
> > 
> > Another thing we probably want is a "GstTocSetter" interface, similar to the
> > GstTagSetter interface. Which would then be used for muxers to set the TOC
> > properly on them. Sending events from the application to the element is not
> > really clean.
> 
> Is that to set the toc on the right element? I wonder if applications would
> know on which element the should set the toc if there are multimple TocSetter
> elements in a transcoding pipleine ...

It's also better to have an interface because sending events from app to
element is not very clean. And additionally it allows the elements to see a
difference between application set TOCs and TOCs sent by upstream elements.
Usually you want to prefer the former.

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.