Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WASAPI EVENT audio channel does not respond to volume change in EarTrumpet #197

Closed
philipdharris1 opened this issue Jun 6, 2018 · 6 comments
Labels
type: third-party-bug A bug in a third-party app or component that impacts EarTrumpet

Comments

@philipdharris1
Copy link

I use Foobar2000 as my music source
I have the output device to be WASAPI
image
However, the volume control for the WASPI channel doesn't affect anything. I can still receive sound from foobar2k
image

OS: Win 10 Pro
Build: 14393.2189

@philipdharris1
Copy link
Author

On further inspection, it appear that Windows itself grabs WASAPI as the program.
Probably not a fault with EarTumpet

image

@5HT2
Copy link

5HT2 commented Jun 7, 2018 via email

@philipdharris1
Copy link
Author

The EarTrumpet control should still get a list of all the programs running and adjust them individually. If anything, both Foobar2k AND the WASAPI service should be shown. For example, I can go into Foobar and manually change the volume.

how does EarTrumpet get a list of running programs?

@GoldenTao
Copy link
Contributor

@riverar will be able to answer this better, but EarTrumpet doesn't retrieve a list of running programs, we access the list of current audio devices and the audio sessions for those devices.

I took a look at Foobar2000 with that custom component installed and it appears to cause a bunch of other issues (at least, on my system, including crashing YouTube in Chrome when I started trying to play audio from Foobar) but it does appear the volume for Foobar is not controllable when using WASAPI as it seems to partially bypass the Windows Audio Service and talks directly to your audio driver.

The built in Foobar outputs appear to work fine with EarTrumpet 2.0.

@philipdharris1
Copy link
Author

I can control foobar volume within the program itself when in WASAPI mode
image
when you say built in, do you mean DirectSound to the windows controller?

@riverar riverar added the type: third-party-bug A bug in a third-party app or component that impacts EarTrumpet label Jun 9, 2018
@riverar
Copy link
Contributor

riverar commented Jun 9, 2018

@philipdharris1 This plugin configures foobar2000 to play in exclusive mode. That is, it takes over the playback device and prevents other apps from playing audio and disables all controls.

You may want to email the plugin author. There's nothing for us to fix here, sorry!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: third-party-bug A bug in a third-party app or component that impacts EarTrumpet
Projects
None yet
Development

No branches or pull requests

4 participants