[ogg-dev] chaining support

Conrad Parker conrad at metadecks.org
Fri Jun 19 17:52:23 PDT 2009


An issue that's been cropping up recently is chaining support. We
discussed this a bit at FOMS 2008, and there are some open issues.
There was talk of making some skeleton-like metadata that spans chain
boundaries (or perhaps putting into skeleton a "chain identifier").
Other things that need to be specced out:

 * edits vs. playlists: how to distinguish between chains that have
come about by removing part of an existing file, vs. a sequence of
completely separate files
 * how to present a seek bar to the user for each kind of chain, ie.
one timeline for the entire sequence?

Perhaps all we need is a field in skeleton (could be a text
message-header field) for "sequence identifier", which identifies
chain sections which are part of the same edit.

Chain sections which are just a concatenation of files to play (eg.
output from icecast) would be distinguished by not having the same
sequence id, either by explicitly having different sequence ids or by
not having a sequence id at all (the current case).


More information about the ogg-dev mailing list