Re: [web-audio-api] Loop start/stop points (#157)

> [Original comment](https://www.w3.org/Bugs/Public/show_bug.cgi?id=17390#2) by Chris Rogers on W3C Bugzilla. Mon, 30 Jul 2012 19:32:01 GMT

(In reply to [comment #2](#issuecomment-24244548))
> We're looking to make some progress on porting our synth architecture to the
> audio API and the lack of loop start/stop points is a gating problem for us.
> 
> My understanding from past discussion has always been that this issue was in
> scope for v1 since it is a basic feature of wavetable synthesis and is
> documented in our WG use cases.

Joe, I agree this is important for implementing sample-playback synths (SoundFonts, etc.).  The one point I'd like to make sure we figure out is how to deal with the sample data *after* the loopEnd attribute.  For example, in SoundFonts the loopEnd is often (but not always) set to end of the total sample data.  But when it's not, upon receiving a note-off command, the loop is expected to "exit" and proceed with sample playback all the way through to the end of the sample data (finally playing the sample data after the loopEnd).

---
Reply to this email directly or view it on GitHub:
https://github.com/WebAudio/web-audio-api/issues/157#issuecomment-24244567