Forum Discussion
Dev channel update to 79.0.309.11 is live
paulheu
Paul, do you have another machine, computer that you can see if you have audio in that environment? It has to be something preventing sound besides the Channels themselves. A 'bug' is not going to affect only just one 1 person.
Cheers,
Drew
paulheu as people have suspected, this is in fact a known Chromium bug that we're also tracking on our end where Chromium doesn't follow the default audio endpoint. In some cases, restarting the browser will fix it, but if that doesn't help you, you could also try opening a ticket with our support agents to see if they've got any other tricks for getting you working again until we can get a fix in for this issue.
Also Limyx826 the dual icons on the taskbar is a known issue, and we're working on a fix.
- Yeah i guess..
- That's really sad..
there are flags related to audio like:
Enable Hardware Audio Offload
Audio Focus Enforcement
Use realtime priority thread for Audio Worklet
in edge://flags/
that you could try but there is something in your Windows installation that is causing interference. of course you can get it fixed by refreshing your Windows but that's up to you. As I feared, with 79.x pused to beta I now have no sound enymore on this build.. So here ends my travels with Edge Insider.. It was fun while it lasted.
With this push, when using Edge and playing sound, it no longer shows up in sound settings for me either in Windows. Back to chrome I guess.. 😕
paulheu wrote:Actually a bug can affect a few or even a single person if it only happens in a specific situation.
Here's my setup:
3700X/RTX2080 32GB
RME HDSPe AIO audio
Synchronous Audio Router which provides virtual audio targets on top of the ASIO driver for the RME card
Current WIN10 version
Default audio target is a virtual device called "Applications"
Any browser works in this setup except Edge DEV and as now found Canary.
When I look at Sound settings, on playing audio using any working browser I see the browser show up in the list, on Edge DEV and Canary this does not happen.
I tried to specifically route the Canary and DEV applications to a target in SAR but this also did not work.
It may be unique to my environment, yes very likely in fact. IMO it is still a bug in the DEV channel though and my fear is that this will translate to the Beta channel once it is updated and that will mean I will no longer be able to use Edge.
Yes you're right, it is very possible that the issue will be shipped to the Beta channel soon.
and you said audio works in Chrome and other browsers which proves your setup is alright, but only Edge insider has problem.
I used to use a similar audio setup like you before, not everybody is supposed to use the default settings.
Actually a bug can affect a few or even a single person if it only happens in a specific situation.
Here's my setup:
3700X/RTX2080 32GB
RME HDSPe AIO audio
Synchronous Audio Router which provides virtual audio targets on top of the ASIO driver for the RME card
Current WIN10 version
Default audio target is a virtual device called "Applications"
Any browser works in this setup except Edge DEV and as now found Canary.
When I look at Sound settings, on playing audio using any working browser I see the browser show up in the list, on Edge DEV and Canary this does not happen.
I tried to specifically route the Canary and DEV applications to a target in SAR but this also did not work.
It may be unique to my environment, yes very likely in fact. IMO it is still a bug in the DEV channel though and my fear is that this will translate to the Beta channel once it is updated and that will mean I will no longer be able to use Edge.
