W3C home > Mailing lists > Public > public-audio@w3.org > July to September 2012

[Bug 17390] (Joe Berkovitz): Loop start/stop points

From: <bugzilla@jessica.w3.org>
Date: Mon, 30 Jul 2012 19:32:01 +0000
Message-Id: <E1SvvhB-00011g-Ni@jessica.w3.org>
To: public-audio@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17390

Chris Rogers <crogers@google.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |crogers@google.com

--- Comment #3 from Chris Rogers <crogers@google.com> 2012-07-30 19:32:01 UTC ---
(In reply to comment #2)
> 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).

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Monday, 30 July 2012 19:32:03 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 30 July 2012 19:32:03 GMT