Yeah, de-/encoding a stream would have a lot of advantages but there is no
streaming en-/ decoder I would be aware of and for the application I'd intend
to use it for, it might be sufficient to de-/ encode a file in whole. Dependent
of the time and efforts for creation and maintenance of a stream encoder, it
might not fit into the time budget. (Apart from that, as of now, it gives a
nice demo application that just runs quickly in every browser, independently
from any platform and has nearly zero maintenance cost.)
-- Rillke
> Subject: Re: [flac-dev] FW: flac (encoder, analyzer, decoder) tool now (also)
> available in JavaScript
> From: bri...@audiobanshee.com
> Date: Tue, 20 Jan 2015 10:25:31 -0800
> CC: flac-dev@xiph.org
> To: ril...@wikipedia.de
>
> I'm not sure that I understand your goal. In a browser setting, I would think
> that you want to decode a stream, not a file, because streaming should have
> less of a memory impact. The reference decoder is a file decoder, so you
> probably don't want to port that. I don't think that there is a reference
> streaming decoder, so you'd need to write your own using the libFLAC or
> libFLAC++ routines.
>
> Brian
>
> On Jan 20, 2015, at 10:14 AM, Rainer Rillke <ril...@wikipedia.de> wrote:
>>...
_______________________________________________
flac-dev mailing list
flac-dev@xiph.org
http://lists.xiph.org/mailman/listinfo/flac-dev
