<br><br><div><span class="gmail_quote">2007/9/8, Josh Coalson <<a href="mailto:xflac@yahoo.com">xflac@yahoo.com</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
it actually is complicated. the libFLAC api is not suited to a<br>multithreaded design because the i/o is stream-based, not file-<br>based. flac(.exe) is the file-based wrapper around libFLAC that<br>allows it to work on files. the way libFLAC buffers data is also
<br>impossible to parallelize without significantly changing the api.</blockquote><div><br>
<br>
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)<br>
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<br>
</div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">it would take a specialty file-based encoder using an independent<br>frame encoder to do and even that is not trivial.
</blockquote><div><br>
<br>
so we can assume that those API changes will never come and the flac encoder will never have multiple core support?<br>
<br>
thx<br>
</div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">--- Harry Sack <<a href="mailto:tranzedude@gmail.com">tranzedude@gmail.com</a>
> wrote:<br><br>> 2007/9/7, Avuton Olrich <<a href="mailto:avuton@gmail.com">avuton@gmail.com</a>>:<br>> ><br>> > On 9/6/07, Harry Sack <<a href="mailto:tranzedude@gmail.com">tranzedude@gmail.com
</a>> wrote:<br>> > > it's really not complicated I think: only api changes to write on<br>> any<br>> ><br>> > Please get started writing a patch, immediately.<br>><br>><br>><br>> I'm just an IT student and I have no time for that :)
<br>> I also didn't study the flac API in detail but I know it's perfectly<br>> possible because I made a avi encoder running on multiple threads<br>> once and<br>> it's exactly the same for audio data.
<br>><br>> --<br>> > avuton<br>> > --<br>> > Anyone who quotes me in their sig is an idiot. -- Rusty Russell.<br>> ><br>> > _______________________________________________<br>> Flac-dev mailing list
<br>> <a href="mailto:Flac-dev@xiph.org">Flac-dev@xiph.org</a><br>> <a href="http://lists.xiph.org/mailman/listinfo/flac-dev">http://lists.xiph.org/mailman/listinfo/flac-dev</a><br>><br><br><br><br><br>____________________________________________________________________________________
<br>Building a website is a piece of cake. Yahoo! Small Business gives you all the tools to get online.<br><a href="http://smallbusiness.yahoo.com/webhosting">http://smallbusiness.yahoo.com/webhosting</a><br>_______________________________________________
<br>Flac-dev mailing list<br><a href="mailto:Flac-dev@xiph.org">Flac-dev@xiph.org</a><br><a href="http://lists.xiph.org/mailman/listinfo/flac-dev">http://lists.xiph.org/mailman/listinfo/flac-dev</a><br></blockquote></div>