> > Furthermore it is a requirement that the same Audio object can be played simultaneously through the mixer with different playbackRates, amplitudes and mixdown parameters -- this is how a typical instrumental wavetable synth works. Will the approach of piping Audio objects through a mixer stream play nice with that requirement? Does captureStream() always return the same object for a given Audio being captured? If so, that might be a problem. > > To play the same media element multiple times, you'll have to clone it. This isn't much code --- var e = element.clone(); var stream = e.captureStream(); e.play(); --- and we can make it less code. Browsers would need to make sure that's efficient. (Making element.clone().play() efficient is a good idea anyway, since it's the simplest API for applications that simply want to play preloaded sounds in response to events.) > My question doesn't so much pertain to the API, which can be changed -- it has more to do with whether a streams implementation optimized for N-way telecommunication sessions of duration M (where N typically < 10 and M > 1 minute) is going to perform well with 100s of tiny little streams (N > 100 and M < 1 sec). ... . . . Joe Joe Berkovitz President Noteflight LLC 84 Hamilton St, Cambridge, MA 02139 phone: +1 978 314 6271 www.noteflight.com
Received on Tuesday, 18 October 2011 12:41:01 UTC