- From: Jukka Jylänki <jujjyl@gmail.com>
- Date: Mon, 17 Jun 2013 16:36:43 +0300
- To: public-audio@w3.org
- Message-ID: <CA+6sJ-3cUhdqfARHGFcqaDo=4AS1i-OMKt3TY_x7Tpqq5pLZvA@mail.gmail.com>
Thanks for the reply! With the start()-scheduled approach, In Firefox nightly, the audio stutters on all sampling rates. In Chrome, audio does not give glitches on 48kHz or 96kHz. This sample https://dl.dropboxusercontent.com/u/40949268/emcc/bugs/webaudio_only_sdl_beep.htmlruns through the various sampling rates to allow you to test as well. 2013/6/17 Robert O'Callahan <robert@ocallahan.org> > On Mon, Jun 17, 2013 at 8:16 PM, Jukka Jylänki <jujjyl@gmail.com> wrote: > >> Currently I create an AudioBufferSourceNode for each buffer, fill it, and >> schedule it to be played back in appropriate time with >> AudioBufferSourceNode.start(when) call. This is problematic and produces >> glitching audio in both Firefox nightly and Chrome: >> > > If you use this approach with 48KHz buffers, does it work without > glitching? > > 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 Monday, 17 June 2013 13:37:15 UTC