Chrome exclusive audio mode

[Gordon Chan]

Hi all,

I cannot get Chrome working as the captioned mode by the command switch --enable-exclusive-audio,can anybody help with me please. Thanks!

[Henrik Andreasson]

Can you please elaborate? What exactly is it that fails? 

Please note that exclusive audio support only exists for Windows.

On Mon, Jun 5, 2017 at 1:46 PM, Gordon Chan <gordonc...@gmail.com> wrote:

Hi all,

I cannot get Chrome working as the captioned mode by the command switch --enable-exclusive-audio,can anybody help with me please. Thanks!

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/d735af57-4b0e-48f9-95dc-7ccfb7ca1ca1%40chromium.org.

[Gordon Chan]

Yes, i'm using windows7 64bit, to my understanding, exclusive audio means WASAPI mode in which it will bypass the windows mixer and the streamer in chrome will gain exclusive access that other audio cannot jam in. But i still can get other audio jam in when listen to an audio stream in chrome. 

Gordon Chan於 2017年6月5日星期一 UTC+8下午7時46分18秒寫道：

[Henrik Andreasson]

I think you have to do manual operations on your actual device as well to allow the app (Chrome in this case) to run in exclusive mode.

You should also check chrome://version/ to ensure that your command-line flags is really utilized.

To change the exclusive-mode settings of a playback or recording device

1. Right-click the speaker icon in the notification area, which is located on the right side of the taskbar, and select Playback Devices or Recording Devices. (As an alternative, run the Windows multimedia control panel, Mmsys.cpl, from a Command Prompt window. 
2. After the Sound window appears, select Playback or Recording. Next, select an entry in the list of device names, and click Properties.
3. After the Properties window appears, click Advanced.
4. To enable applications to use the device in exclusive mode, check the box labeled Allow applications to take exclusive control of this device. To disable exclusive-mode use of the device, clear the check box.
5. If exclusive-mode use of the device is enabled, you can specify whether a request for exclusive control of the device will succeed if the device is currently playing or recording shared-mode streams. To give exclusive-mode applications priority over shared-mode applications, check the box labeled Give exclusive mode applications priority. To deny exclusive-mode applications priority over shared-mode applications, clear the check box.

--

--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/64d5b465-fbc6-43f1-8ba7-75adec3b4267%40chromium.org.

[Gordon Chan]

Hi Henrika,

Below is the version output, it seems the flag is not recognize in chrome. Any thoughts? 

-------------------------------------------

Google Chrome	58.0.3029.110 (Official Build) (64-bit)
Revision	691bdb490962d4e6ae7f25c6ab1fdd0faaf19cd0-refs/branch-heads/3029@{#830}
OS	Windows
JavaScript	V8 5.8.283.38
Flash	25.0.0.171 C:\Users\User\AppData\Local\Google\Chrome\User Data\PepperFlash\25.0.0.171\pepflashplayer.dll
User Agent	Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36
Command Line	"C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --flag-switches-begin --flag-switches-end
Executable Path	C:\Program Files (x86)\Google\Chrome\Application\chrome.exe
Profile Path	C:\Users\User\AppData\Local\Google\Chrome\User Data\Default
Variations	241fff6c-dd772b49 3095aa95-3f4a17df 7c1bc906-f55a7974 1c752ce9-33c3eba5 ba3f87da-45bda656 cf558fa6-48a16532 f3499283-7711d854 349d561b-969ce2d0 9e201a2b-ecdd092e 6eb432aa-ca7d8d80 5274eb09-3f4a17df b684f56f-4d2fac87 b791c1b8-ca7d8d80 9773d3bd-ca7d8d80 b22b3d54-1c15b2e9 2e109477-ca7d8d80 99144bc3-3cc2175e 9e5c75f1-ee841e81 f79cb77b-3d47f4f4 b7786474-d93a0620 23a898eb-3d47f4f4 4ea303a6-ecbb250e 7aa46da5-669a04e0 69bf80fa-91c810ef b2f0086-93053e47 f11cb941-11910166 6844d8aa-669a04e0 494d8760-f23d1dea f47ae82a-86f22ee5 3ac60855-486e2a9c f296190c-116bbed1 4442aae2-6e597ede ed1d377-e1cc0f14 75f0f0a0-d7f6b13c e2b18481-4c073154 e7e71889-4ad60575 288c530e-803f8fc4 828a5926-ca7d8d80
Compiler	MSVC 2015 (PGO)

Gordon Chan於 2017年6月5日星期一 UTC+8下午7時46分18秒寫道：

[Gordon Chan]

Sorry, below is the updated one.

-------------------------------------

Google Chrome	59.0.3071.86 (Official Build) (64-bit) (cohort: 59_86_Win)
Revision	fcbc16eadeff40b48fbd6b4694fb8487aededbc2-refs/branch-heads/3071@{#740}
OS	Windows
JavaScript	V8 5.9.211.31

Flash

25.0.0.171 C:\Users\User\AppData\Local\Google\Chrome\User Data\PepperFlash\25.0.0.171\pepflashplayer.dll

User Agent	Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.86 Safari/537.36
Command Line	"C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --enable-exclusive-audio --flag-switches-begin --flag-switches-end

Executable Path	C:\Program Files (x86)\Google\Chrome\Application\chrome.exe
Profile Path	C:\Users\User\AppData\Local\Google\Chrome\User Data\Default

Variations

ca7e5485-3f4a17df

241fff6c-dd772b49 3095aa95-3f4a17df 7c1bc906-f55a7974 1c752ce9-33c3eba5 ba3f87da-45bda656 cf558fa6-48a16532 f3499283-7711d854

9e201a2b-ecdd092e 5274eb09-3f4a17df

9773d3bd-ca7d8d80 b22b3d54-1c15b2e9 2e109477-ca7d8d80 99144bc3-3cc2175e 9e5c75f1-ee841e81 f79cb77b-3d47f4f4 b7786474-d93a0620

27219e67-b2047178 23a898eb-3d47f4f4 4ea303a6-ecbb250e 7aa46da5-669a04e0 2697ea25-ca7d8d80 b2f0086-93053e47 81fca794-19eaf52c 6844d8aa-669a04e0 494d8760-3f4a17df

f47ae82a-86f22ee5 3ac60855-486e2a9c f296190c-116bbed1 4442aae2-6e597ede ed1d377-e1cc0f14 75f0f0a0-d7f6b13c e2b18481-4c073154 e7e71889-4ad60575 288c530e-803f8fc4

61b920c1-ca7d8d80 828a5926-ca7d8d80
Compiler	MSVC 2015 (PGO)

Gordon Chan於 2017年6月5日星期一 UTC+8下午7時46分18秒寫道：

Hi all,

[Henrik Andreasson]

The flag seems active but I can't say for sure what the full effect or running in exclusive mode is.

Did you do the manual steps I listed for your device? I am not convinced that "still can get other audio jam in when listen to an audio stream in chrome"

means that exclusive mode is not working. The main consequence is that the latency should be reduced.

Please note that the code under this flag is experimental and not being actively improved. Performance might have degraded over time since

it was added originally. 

--

--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/197dd667-ddc7-43c7-a5d9-e059caf56424%40chromium.org.

[Gordon Chan]

Did you have an experience using Jriver running in exclusive audio mode? It simply does not allow someone to adjust the volume and when Jriver is singing then there is no audio jam in when you play a stream in chrome.

Hope it explains.

Gordon Chan於 2017年6月5日星期一 UTC+8下午7時46分18秒寫道：

[Martin Blazek]

I know for a fact that the --enable-exclusive-audio switch does not work, as of Chrome version 62.0.3202.94.

One of the ways of knowing that the output is accessed in Exclusive Mode is to play some audio to it in Exclusive Mode (i.e. exactly what the --enable-exclusive-audio switch should accomplish) and then attempt to play audio from some OTHER application to the SAME output - it should fail to play (and will typically throw some error message).  As far as Chrome is concerned, the --enable-exclusive-audio makes no difference - the output is accessible from some other player with or without the switch.

The Windows OS setting to allow applications take exclusive control over the device is enabled, by the way (see attachment), and playback from other applications (used foobar2000 with WASAPI plugin) can successfully play audio to the output preventing other apps from accessing the output (which is exactly how Exclusive Mode works).

Any chance the bug in Chrome will get fixed eventually?

Google Chrome	62.0.3202.94 (Official Build) (64-bit) (cohort: Stable)
Revision	4fd852a98d66564c88736c017b0a0b0478e885ad-refs/branch-heads/3202@{#789}
OS	Windows
JavaScript	V8 6.2.414.42
Flash	27.0.0.187 C:\Users\bls128\AppData\Local\Google\Chrome\User Data\PepperFlash\27.0.0.187\pepflashplayer.dll
User Agent	Mozilla/5.0 (Windows NT 6.2; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36
Command Line	"C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --enable-exclusive-audio --flag-switches-begin --disable-smooth-scrolling --flag-switches-end

Executable Path

C:\Program Files (x86)\Google\Chrome\Application\chrome.exe

Profile Path

C:\Users\bls128\AppData\Local\Google\Chrome\User Data\Default