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 data is also > impossible to parallelize without significantly changing the api.
why was this approach used? The API design seems to me not very smart because it's not flexible and you're stuck in the future (like now for multiple core support) I don't see any reason why you wouldn't make it all based on files and not on streams :s It's just a major disavantage in my opinion it would take a specialty file-based encoder using an independent > frame encoder to do and even that is not trivial. so we can assume that those API changes will never come and the flac encoder will never have multiple core support? thx --- Harry Sack <[EMAIL PROTECTED]> wrote: > > > 2007/9/7, Avuton Olrich <[EMAIL PROTECTED]>: > > > > > > On 9/6/07, Harry Sack <[EMAIL PROTECTED]> wrote: > > > > it's really not complicated I think: only api changes to write on > > any > > > > > > Please get started writing a patch, immediately. > > > > > > > > I'm just an IT student and I have no time for that :) > > I also didn't study the flac API in detail but I know it's perfectly > > possible because I made a avi encoder running on multiple threads > > once and > > it's exactly the same for audio data. > > > > -- > > > avuton > > > -- > > > Anyone who quotes me in their sig is an idiot. -- Rusty Russell. > > > > > > _______________________________________________ > > Flac-dev mailing list > > Flacemail@example.com > > http://lists.xiph.org/mailman/listinfo/flac-dev > > > > > > > > ____________________________________________________________________________________ > Building a website is a piece of cake. Yahoo! Small Business gives you all > the tools to get online. > http://smallbusiness.yahoo.com/webhosting > _______________________________________________ > Flac-dev mailing list > Flacfirstname.lastname@example.org > http://lists.xiph.org/mailman/listinfo/flac-dev >
_______________________________________________ Flac-dev mailing list Flacemail@example.com http://lists.xiph.org/mailman/listinfo/flac-dev