- From: Maciej Stachowiak <mjs@apple.com>
- Date: Fri, 24 Oct 2008 08:26:25 -0700
On Oct 24, 2008, at 6:44 AM, timeless wrote: > Sounds like what you really want is an audio/video stiching api so > that you could concatenate a second sound track and achieve a smooth > transition. That might be useful in its own right but seems irrelevant to the use case of looping a single sound. (Probably the best way to do something like this (short of a realtime sound API) would be the ability to queue up an audio file (or range thereof) to play next when the current one finishes, because then the media framework can take care of ensuring a smooth transition.) - Maciej > > > On 10/23/08, Maciej Stachowiak <mjs at apple.com> wrote: >> >> On Oct 14, 2008, at 5:40 PM, Ian Hickson wrote: >> >>> >>> There is no way to say "loop forever" right now primarily because >>> doing so >>> would mean complicating the syntax of the playcount attribute to be >>> not >>> just a number. You can work around it with script (just add >>> onended="currentTime=0" to the <video> element). >> >> This would lead to perceptible glitches in looped audio, compared to >> being able to represent the looping to the media framework. >> >>> To be honest I'm not really convinced we need the looping feature at >>> all. >>> It seems like we should drop this from the current version. What >>> benefit >>> does it bring? Is looping really that common? If we got rid of it we >>> could >>> find better ways of picking the start time. >> >> For example: I think looped audio would be a common thing for games >> to >> want to do, and they wouldn't want it to glitch when it loops. >> >> Regards, >> Maciej >> >> > > -- > Sent from Gmail for mobile | mobile.google.com
Received on Friday, 24 October 2008 08:26:25 UTC