search for: vasoftware

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.

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.

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.

...it will! > > > > > -- > 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 >

On Wednesday, January 8, 2003, at 12:56 PM, Josh Coalson wrote: > 'touch doc/FLAC.tag' and run make again I did and got: gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I../.. -I./include -I../../include -g -O2 -O3 -DNDEBUG -Dunix -fomit-frame-pointer -funroll-loops -finline-functions -Wall -W -Winline -DFLaC__INLINE=__inline__ -c `test -f 'encode.c' || echo

Here is what I imagined (just vague thoughts, nothing polished): Let's suppose we have a hypotetical library called "Free Universal Codec Kit" - ..um...well.. Frunick for short :) (Of course I am not proposing this name, I'm sure the suits in the industry would not like it...but for my example its OK ;) Now, an application should do something like this: #include

Here is what I imagined (just vague thoughts, nothing polished): Let's suppose we have a hypotetical library called "Free Universal Codec Kit" - ..um...well.. Frunick for short :) (Of course I am not proposing this name, I'm sure the suits in the industry would not like it...but for my example its OK ;) Now, an application should do something like this: #include