[Flac-dev] Compile problems on OSX

2007-09-08 Thread Erik de Castro Lopo
Hi all, I've got two problems compiling the current CVS FLAC sources on OSX. Firstly, the configure script can't find the OGG libraries which were installed from MacPorts. I have tried: ./configure --with-ogg-includes=/opt/local/include \ --with-ogg-lib=/opt/local/lib but they ar

Re: [Flac-dev] Re: multiple core support

2007-09-08 Thread Brian Willoughby
Harry, You assume that the only way to use FLAC is the way that you are using it, by converting one file format to another. That's not the only way to use FLAC. The most important uses of FLAC are for internet streaming radio or hand-held digital audio players. Both of these prominent

Re: [Flac-dev] Re: multiple core support

2007-09-08 Thread Ralph Giles
On Sat, Sep 08, 2007 at 03:05:32PM +0200, Harry Sack wrote: > But it's not clear to me why everything was based on streams... Streams, at least in the variety we seem to be describing, aren't seekable. This is a considerable simplification and allows for more flexibility in other areas, like net

RE: [Flac-dev] Re: multiple core support

2007-09-08 Thread Scot Thompson
No, streams should stay. Audio is NOT a file based process -- it's a stream. You can't listen to an entire song simultaneously. You organize it into files for later use, but you listen and record from a stream. Stream-based storage is practically REQUIRED for an audio codec. It's not random acc

Re: [Flac-dev] Re: multiple core support

2007-09-08 Thread Harry Sack
2007/9/8, Brian Willoughby <[EMAIL PROTECTED]>: > > Ralph, > > The problem is that there is no clear advantage, at least in terms of > multiple cores, to the approach you're asking about. In order to > allow each stage of the codec to overlap, you need smart buffering > between each stage. That a

Re: [Flac-dev] Re: multiple core support

2007-09-08 Thread Harry Sack
2007/9/8, Josh Coalson <[EMAIL PROTECTED]>: > > it actually is complicated. the libFLAC api is not suited to a > multithreaded design because the i/o is stream-based, not file- > based. flac(.exe) is the file-based wrapper around libFLAC that > allows it to work on files. the way libFLAC buffers