- From: Robert O'Callahan <robert@ocallahan.org>
- Date: Mon, 10 Mar 2014 18:35:16 +0800
- To: Joe Meadows <jam@jamspace.com>
- Cc: "public-audio@w3.org" <public-audio@w3.org>
Received on Monday, 10 March 2014 10:35:43 UTC
On Fri, Mar 7, 2014 at 9:18 AM, Joe Meadows <jam@jamspace.com> wrote: > *Example application* > I have a client/server audio synthesizer project. The server generates a > stream of Ogg/Vorbis audio that is rendered by the client (browser) using > an HTML audio tag. The client can change various parameters (e.g. pitch, > gain, pan, etc) and the server will immediately alter the output stream > accordingly. > > This arrangement if very nice because it requires nothing special on the > client side. However, in the browsers that I've tried the audio element > buffers very aggressively, literally several minute's worth of data. So > when the user tweaks a setting it will not be heard in the browser for a > long time, even though the server immediately reflected the change. > Can you modify the server so that it doesn't deliver data faster than real time? 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, 10 March 2014 10:35:43 UTC