One question (sorry I missed the call last week) - are we not considering release segments in looping, or presuming that would be handled by a different node? (e.g. a sampled piano sound will frequently have a release segment that records the "clunk" of the damper hitting the strings again.) FWIW (remember I was not involved in the design of the WA API, and came to it fairly recently), I initially found noteOn/noteOff a bit confusing as well; however, in this context it begins to make a lot more sense. As Chris just said, those implementors who use webkitAudioContext already will have to fix up their content anyway (although probably only to alias audioContext). On Mon, May 7, 2012 at 11:16 AM, Tony Ross <tross@microsoft.com> wrote: > > From: Tony Ross [mailto:tross@microsoft.com] > > Sent: Monday, May 07, 2012 11:14 AM > > > > Thanks Oliver. > > Apologies for misspelling your name, Olivier (clearly I'm typing my > replies too quickly). > > > > From: Olivier Thereaux [mailto:olivier.thereaux@bbc.co.uk] > > > Sent: Monday, May 07, 2012 11:00 AM > > > > > AFAIK there is one (or 2 depending on how you count) implementation(s) > > > of the API in browsers, but Chris was worried about the number of > > > content pages using the feature. I suspect many of those are demos. > > > > I suspect most existing content is already tied to a single > > implementation regardless since the WebKit version of the API is vendor- > > prefixed. > > > > -Tony > >
Received on Monday, 7 May 2012 18:39:28 UTC