First of all, let me say that I don't know the current library very well. But what I would like to see libraries all support the same interface for dealing with packets taken from an ogg file. So, you could look into the ogg file, see what type of packets it has. Using only that information, try to load a plugin to handle them, which will make use of one interface. In this way, all players that use speex, vorbis, flac, theora.... can look into the ogg, get the type of that packet, load the decoder plugin, and start sending that plugin packets. I know Monty is supposedly working on a more unified framework. Perhaps this is what he is doing now? Oscar. On Thu, Jan 30, 2003 at 03:46:46PM +0100, Csillag Krist?f wrote:> Now that FLAC has officionally joined the Xiph family, > there are three different free audio codecs, which can be > stored/transported using the ogg container. > > Would it be possible to create an API and/or a library that > would cover them all? > > If my understanding of the situation is correct, if an application wants > to support vorbis, speex and flac, it has to use three different > interfaces. (That's what Stan Seibert is doing right now with ogg123.) > > If a unifying library would exist, application developers should only > code one interface. This would make things a lot more simple. > > This could also help to spread speex and flac more quickly, because if > vorbis-aware applications start to use the new, unified library, they > get very near to speex and flac support... > > What do you think, does this make sense? > > -- > Csillag Krist?f <fenwick@freemail.hu> > > --- >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@xiph.org' > containing only the word 'unsubscribe' in the body. No subject is needed. > Unsubscribe messages sent to the list will be ignored/filtered.-- boykin@pobox.com http://pobox.com/~boykin jabber: johnynek@jabber.org fingerprint=159A FA02 DF12 E72F B68F 5B2D C368 3BCA 36D7 CF28 fix copyright: http://lessig.org/content/standard/0,1902,16071,00.html -------------- next part -------------- A non-text attachment was scrubbed... Name: part Type: application/pgp-signature Size: 233 bytes Desc: not available Url : http://lists.xiph.org/pipermail/vorbis-dev/attachments/20030130/343a9e7b/part-0001.pgp
I am open to doing an adapter layer around the current libOggFLAC interface to implement a common one. Josh --- Drew Hess <dhess@bothan.net> wrote:> > I was just asking Josh about this. It sounds like the plan for now > for > FLAC, at least, is to keep the OggFLAC interface. But I agree, it > would be > nice to have a common interface for ogg formats. > > > -dwh- > > > On 30 Jan 2003, Csillag Kristóf wrote: > > > Now that FLAC has officionally joined the Xiph family, > > there are three different free audio codecs, which can be > > stored/transported using the ogg container. > > > > Would it be possible to create an API and/or a library that > > would cover them all? > > > > If my understanding of the situation is correct, if an application > wants > > to support vorbis, speex and flac, it has to use three different > > interfaces. (That's what Stan Seibert is doing right now with > ogg123.) > > > > If a unifying library would exist, application developers should > only > > code one interface. This would make things a lot more simple. > > > > This could also help to spread speex and flac more quickly, because > if > > vorbis-aware applications start to use the new, unified library, > they > > get very near to speex and flac support... > > > > What do you think, does this make sense? > > > > -- > > Csillag Kristóf <fenwick@freemail.hu> > > > > > > > > ------------------------------------------------------- > > This SF.NET email is sponsored by: > > SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 > See! > > http://www.vasoftware.com > > _______________________________________________ > > Flac-dev mailing list > > Flac-dev@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/flac-dev > > > > > --- >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@xiph.org' > containing only the word 'unsubscribe' in the body. No subject is > needed. > Unsubscribe messages sent to the list will be ignored/filtered.<p>__________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com --- >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@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
Now that FLAC has officionally joined the Xiph family, there are three different free audio codecs, which can be stored/transported using the ogg container. Would it be possible to create an API and/or a library that would cover them all? If my understanding of the situation is correct, if an application wants to support vorbis, speex and flac, it has to use three different interfaces. (That's what Stan Seibert is doing right now with ogg123.) If a unifying library would exist, application developers should only code one interface. This would make things a lot more simple. This could also help to spread speex and flac more quickly, because if vorbis-aware applications start to use the new, unified library, they get very near to speex and flac support... What do you think, does this make sense? -- Csillag Krist?f <fenwick@freemail.hu>
I was just asking Josh about this. It sounds like the plan for now for FLAC, at least, is to keep the OggFLAC interface. But I agree, it would be nice to have a common interface for ogg formats. -dwh- On 30 Jan 2003, Csillag Krist?f wrote:> Now that FLAC has officionally joined the Xiph family, > there are three different free audio codecs, which can be > stored/transported using the ogg container. > > Would it be possible to create an API and/or a library that > would cover them all? > > If my understanding of the situation is correct, if an application wants > to support vorbis, speex and flac, it has to use three different > interfaces. (That's what Stan Seibert is doing right now with ogg123.) > > If a unifying library would exist, application developers should only > code one interface. This would make things a lot more simple. > > This could also help to spread speex and flac more quickly, because if > vorbis-aware applications start to use the new, unified library, they > get very near to speex and flac support... > > What do you think, does this make sense? > > -- > Csillag Krist?f <fenwick@freemail.hu> > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: > SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! > http://www.vasoftware.com > _______________________________________________ > Flac-dev mailing list > Flac-dev@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/flac-dev >