On Mon, Oct 21, 2013 at 7:04 PM, Chris Wilson <cwilso@google.com> wrote: > Hmm, now I think I see basic gain control, so that was a poor example - > replace that with delay, or filtering, etc. As for the other built-in > effects - perhaps I misspoke. But I'd suggested that this was the major > issue - that you needed to do everything in libraries - and was never > corrected, > I did mention from the beginning that native effects were envisaged: http://lists.w3.org/Archives/Public/public-audio/2011OctDec/0009.html https://dvcs.w3.org/hg/audio/raw-file/tip/streams/StreamProcessing.html#mediastream-extensions If you said something incorrect and I failed to correct you, I apologize and promise to be more vigilant in the future :-). and I see in the examples inclusions like "effect.js" and > "audio-ducking.js". In the case where you have substantial built-in > libraries, I don't see a huge difference between where we are today and > MSP, then, other than the known problem of script nodes being in the main > thread. > There are a lot of other differences. But it's a bit of a waste of time to belabour this now. Rob -- Jtehsauts tshaei dS,o n" Wohfy Mdaon yhoaus eanuttehrotraiitny eovni le atrhtohu gthot sf oirng iyvoeu rs ihnesa.r"t sS?o Whhei csha iids teoa stiheer :p atroa lsyazye,d 'mYaonu,r "sGients uapr,e tfaokreg iyvoeunr, 'm aotr atnod sgaoy ,h o'mGee.t" uTph eann dt hwea lmka'n? gBoutt uIp waanndt wyeonut thoo mken.o w * *
Received on Tuesday, 22 October 2013 08:22:33 UTC