search for: multicoder

OPTICODE As "Optimum Code" or "Optimized Code". Or OPTCODE as before, but also recall the "OpCodes" of processors and the web name is free. Or OPTCODER / OPTICODER as "Optimizing Coder" Alberto -------------- next part -------------- An HTML attachment was scrubbed... URL:

--- Harry Sack <tranzedude@gmail.com> wrote: > 2007/9/8, Josh Coalson <xflac@yahoo.com>: > > > > 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

2007/9/9, Josh Coalson <xflac@yahoo.com>: > > --- Harry Sack <tranzedude@gmail.com> wrote: > > 2007/9/8, Josh Coalson <xflac@yahoo.com>: > > > > > > 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

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. it would take a specialty file-based encoder using an independent frame