- From: Alistair MacDonald <al@signedon.com>
- Date: Fri, 27 Jul 2012 23:10:10 -0400
- To: r baxter <baxrob@gmail.com>
- Cc: olivier Thereaux <olivier.thereaux@bbc.co.uk>, public-audio@w3.org
- Message-ID: <CAJX8r2mgkU4OuGCt-NbJA6h8x1PJyfPnFywozOV4YKN_hNwMEQ@mail.gmail.com>
Love this! You should set len to 16 by default, as that syncs with your typical 4/4 time sig. Beverly Hill's Cop anyone? :) http://proto.blandhand.net/patr/#rate:400;len:64;seq:8,0,0,0,11,0,0,8,0,8,13,0,8,0,6,0,8,0,0,0,15,0,0,8,0,8,16,0,15,0,11,0,8,0,15,0,20,0,8,6,0,6,3,0,10,0,8,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 ; On Fri, Jul 27, 2012 at 10:37 PM, r baxter <baxrob@gmail.com> wrote: > On Fri, Jul 27, 2012 at 3:51 AM, olivier Thereaux > <olivier.thereaux@bbc.co.uk> wrote: > > Very nice Roby. I like how intuitive the keyboard controls are. > > > > Thanks Olivier. Nice to know the controls seems intuitive, indeed! > > > You might want to limit the pace value set by the user: anywhere beyond > 1000 gets me clicks, and eventually the app slows down to near-halt on a > reasonably modern laptop + Chrome canary. > > > > Aye, good point. I'd mostly been working/testing with "pace" values > under 1000. > > I wonder how much this is a machine/cpu capacity issue... I realized, > after experimenting and reflecting a bit, that my code is guaranteed > to break with "pace" > 1406, as everything occurs within the jsNode > buffer-frame of 2048 samples, and I'm only handling one note > transition per buffer (so, if my math-brain is working rightly, > 60/(bufferSize/sampleRate) is the fastest that my code will reliably > handle note/step transitions). > > I think I should update it to limit the "pace" value to such. Where > you say "clicks, and eventually the app slows down to near-halt", is > definitely what I get with values above 1500 or so. > > Thanks much, > Rb > > -- Alistair MacDonald SignedOn, Inc - W3C Audio WG Boston, MA, (707) 701-3730 al@signedon.com - http://signedon.com
Received on Saturday, 28 July 2012 03:10:38 UTC