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

EE does not autoload a virtual audio sink #3459

Open
PassiveLemon opened this issue Oct 17, 2024 · 1 comment
Open

EE does not autoload a virtual audio sink #3459

PassiveLemon opened this issue Oct 17, 2024 · 1 comment

Comments

@PassiveLemon
Copy link

EasyEffects Version

7.1.9

What package are you using?

NixOS

Distribution

NixOS 24.05

Describe the bug

The preset for a virtual audio sink does not autoload when it's set as the default.

Expected Behavior

When the virtual audio sink starts and becomes the default, autoload the profile for it.

Debug Log

easyeffects.log

Note that in the log, the profile for wivrn.sink was NOT autoloaded, I manually loaded it so that the information about it is printed. I then killed the server creating wivrn.sink to show that the profile for my headphones (Corsair) is autoloaded.

Additional Information

These are my autoload profiles
image

The problematic one is wivrn.sink. Once the WiVRn server is started, it creates wivrn.sink (which I already set to default) so it becomes the default audio sink until it gets removed when the WiVRn server is shut down.

@PassiveLemon PassiveLemon changed the title EE does not autoload virtual audio sinks EE does not autoload a virtual audio sink Oct 17, 2024
@wwmm
Copy link
Owner

wwmm commented Oct 17, 2024

Hum... The current autoload code relies on device routing signals because that is the only thing that can be used on some hardware. Specially in the cases here microphones are plugged in the onboard card jack. Virtual devices do not have routing signals. Probably because they do not have hardware profiles.

In order to deal with virtual devices some kind of solution based only in the node name would be required. But this may be a little annoying to implement considering that for real hardware we can't act based on node names most of the time =/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants