[vorbis-dev] Re: UCI Project Announcement

[shatty]

Hi Monty,

None of the APIs that UCI plans to work on will be of
use to you as an external API for the Ogg mux/demux
platform.  The reason why you don't see anything in
the spec about mux/demux plugins is that mux/demux is
not a target for the UCI project.  UCI consists of two
APIs, one of which is implemented by a codec writer,
and the other which is utilized by an application that
wants to use one (or more) of the codecs provided.

So, UCI could possibly be of use to you as the
internal API for the vorbis/theora codecs.  In this
situation, the Ogg mux/demux framework would use the
UCI application API to access the codecs.  Vorbis
and theora would implement the internal codec API.

The result would be that Ogg could also store any
other codecs that supply an UCI interface.  And also
that any other container (such as MCF) could use the
UCI application interface to access the vorbis or 
theora codecs.

It's true that there's only a partial implementation
of the API so far. (AFAIK)  As such, I can understand
if you feel it is desirable to proceed with your own
solution for this API.  (especially seeing as you
already have one worked out for ogg/vorbis and clearly
have plans for its extension)

Still, I hope that you can find some time to
contribute your wisdom directly to the project,
especially to the extent that you find that UCI is
incapable of providing the necessary interface
between the Ogg framework and the vorbis/theora 
codecs.  I know your time is limited (as is all of
ours :-) ) and if this isn't possible then you can
still rest assured that we will examine your design
choices to ensure that UCI will be able to ultimately
serve your need.

Thanks for taking the time to look over the specs so far.

Andrew Bachmann

-----Original Message-----
From: xiphmont at xiph.org (Monty)
Date: Wed, 16 Oct 2002 20:40:05 -0400

[snip]

I'm building an Ogg mux/demux platform.  It has no other goal in mind
than turning Ogg into a framework that uses multiple internal codecs
seamlessly and presents a very easy to use encode/decode interface for
any and all Ogg transport streams and their contents.  This neither
duplicates nor works against UCI's goals.

[snip]

I'm going to continue working on seamless Ogg mux/demux.  The designed
API, both externally exposed to the application and internally exposed
to the codecs, is somewhat beyond what you're proposing, but it should
be perfectly useable within a well-designed UCI frame.

[snip]

Monty

<p>--- >8 ----
List archives:  http://www.xiph.org/archives/
Ogg project homepage: http://www.xiph.org/ogg/
To unsubscribe from this list, send a message to 'vorbis-dev-request at xiph.org'
containing only the word 'unsubscribe' in the body.  No subject is needed.
Unsubscribe messages sent to the list will be ignored/filtered.