- From: Matt Diamond <mdiamond@jhu.edu>
- Date: Fri, 7 Sep 2012 14:35:20 -0700
- To: Jory <me@jory.org>
- Cc: public-audio@w3.org
- Message-ID: <CADdpXtv_dk=STdd+sDGpAqWTO4Yy2mkAx_k3LLeTbaUSmZEbpA@mail.gmail.com>
Great, thanks for the link, definitely looks helpful. It seems like the strategy is to get a string-formatted, base-64 encoded representation of the audio and open a window with a data URI containing the audio string. I guess the question now is finding the best way to generate that audio string in the first place... perhaps I can use the RealtimeAnalyserNode's getByteTimeDomainData method to assemble it on the fly. On Fri, Sep 7, 2012 at 2:25 PM, Jory <me@jory.org> wrote: > Marcus posted this a number of weeks ago: > > http://mzl.la/R9GLQD > > It is a non-realtime synth/sequencer that can generate a WAVE file. So > it's certainly possible. I'm not sure if there's a recommended method, > though. > > Jory > > On Fri, 7 Sep 2012 14:11:00 -0700, Matt Diamond wrote: > > Apologies for the naive question (as I'm pretty sure it must have been > > discussed already) but is there a currently available method for > exporting > > the output of the Web Audio API to a downloadable file (e.g. WAV/MP3)? My > > first thought was the Media Capture/Streams API, but I'm not sure if the > > capability is there yet. > > > > Also it would be great if we could prompt the user to download a file via > > solely client-side processing, without having to stream the audio to a > > server and package the download there. Not sure if either of these are > > possible scenarios right now though. > > > > Matt > > Jory K. Prum > Sound Guy > > --------------------- studio.jory.org ----------------------- > | me@jory.org | > | http://www.jory.org http://studio.jory.org | > ------------------------------------------------------------- > | PO Box 775 | (415) 454-7937 | > | Fairfax, CA 94978-0775 | (415) 342-9349 Cel | > ------------------------------------------------------------- > > >
Received on Friday, 7 September 2012 21:35:48 UTC