New issue
Advanced search Search tips

Issue 753428 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Aug 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 3
Type: Bug



Sign in to add a comment

When Windows 10 is configured for spatial audio Chrome may take several seconds to render sound.

Project Member Reported by dalecur...@chromium.org, Aug 8 2017

Issue description

I.e. if you start Chrome and play something like:

http://storage.googleapis.com/dalecurtis/buck720.webm

You won't hear sound for a few seconds. While in Edge the sound will start instantly. More interestingly, if you keep Edge running in the background and then retest in Chrome, Chrome will also play the sound instantly.

Looking at my receiver the reason seems to be that Edge keeps the audio rendering to your selected spatial setting (Dolby Atmos in my case), while Chrome alone ends up rendering 8-channel PCM. This triggers a mode switch on the receiver which is partially (possibly even largely) responsible for the audio gap.

It'd be nice to figure out what settings we need to apply to the audio endpoint to achieve audio playback without any gaps; since the delay is long enough that short sounds are completely missed.

Possibly we need to create a ISpatialAudioClient instead of an IAudioClient?

https://github.com/Microsoft/Xbox-ATG-Samples/tree/master/Samples/Audio
https://msdn.microsoft.com/en-us/library/windows/desktop/mt807491(v=vs.85).aspx
 
Status: WontFix (was: Assigned)
Actually, Edge has the same issue when I retested later. It seems this is just typical mode switching issues. The only way around this might be to keep a stream open, but that wastes power, so not much to do here. We already lazily close streams after a few seconds, so track switches and the like don't incur this penalty.

Sign in to add a comment