Paul Adenot (:padenot) Reporter
	Description • 9 years ago

This is what Chrome does, and seems like it could be worth it, creating and destroying system audio streams is expensive (and can be super super super _super_ long on some platforms, we've seen 8 seconds on OSX).

	Matthew Gregan [:kinetik]
	Comment 1 • 9 years ago

Yeah, this also allows us to do nice stuff like quickly fade the volume in and out during the seek so there's no harsh pop between sample transitions.

I think the only reason we have the current behaviour is that there's no API-level distinction between pause/resume (where we likely want to stop the audio stream for power/resource savings) and the type of short stream transition caused by a seek.  Maybe we need something slightly fancy, like a timeout on the stream where we only kill it after it has been paused/idle for more than N seconds.

	Luke
	Comment 2 • 9 years ago

Please add whiteboard:  [games]