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

alsactl store restore overrides #14

Closed
flatmax opened this issue Jul 29, 2017 · 5 comments

Comments

Projects
None yet
2 participants
@flatmax
Copy link

commented Jul 29, 2017

Hi there,

I am wondering whether lxpanel is also overriding the standard alsactl file store/restore methodologies ?

I am cross linking this problem which we have known exists, but haven't been sure where to find information about :
http://forum.audioinjector.net/viewtopic.php?f=5&t=3003&p=4836#p4832

I suspect that this problem and the following problem are coming from lxpanel ?
#13

By the way, can we leave problems open until they are addressed in software fixes ?

thanks
Matt

@spl237

This comment has been minimized.

Copy link
Contributor

commented Jul 29, 2017

As in the previous issue - the volumealsa plugin only overrides asoundrc if the selected device has no simple audio controls. The solution is to either provide at least one ALSA simple control in the device, or to uninstall the volume plugin.

Modifying the plugin to work with devices which do not support the ALSA simple control interface is a lot of work, and isn't required for 99% of Pi use cases, so it's not something I'm planning to do. (However, if you feel like modifying the plugin to properly support non-simple ALSA controls, feel free to submit a PR!)

@spl237 spl237 closed this Jul 29, 2017

@flatmax

This comment has been minimized.

Copy link
Author

commented Jul 30, 2017

@flatmax

This comment has been minimized.

Copy link
Author

commented Jul 30, 2017

@flatmax

This comment has been minimized.

Copy link
Author

commented Jul 30, 2017

Can you please open this and #13 until they are fixed ?

thanks
Matt

@spl237

This comment has been minimized.

Copy link
Contributor

commented Jul 30, 2017

Due to the way the designers of ALSA have chosen to differentiate between controls, simple controls are identified with text strings. The plugin looks for known text strings in the names of simple controls which map onto main volume - the names used are Master, Front, PCM, LineOut, Digital, Speaker and Headphone. The audio injector octo does not offer a control with any of these names, so it is not controllable via the plugin. Further, it would appear that your device has multiple output channels anyway, while the plugin maps its volume control onto a single (stereo) control - it would require major changes for the plugin to simultaneously control 8 output channels. The plugin is therefore never going to be compatible with this device.

The stereo audio injector does offer a "Master" control, so that should be valid for the plugin. There is therefore some other issue which is causing it to be rejected - but without access to the hardware, I cannot debug it. If you want to send me an example of the hardware in question, I can investigate, although I cannot guarantee that I will be able to fix the problem if there is some fundamental incompatibility with the way the plugin works.

Unless you want to send me an audio injector to test, both issues will remain closed, as I cannot work on them. As before - the workaround if you do not want asoundrc changed by the plugin is to uninstall the plugin. If the plugin is changing asoundrc, it is unable to control your device, so you lose nothing by uninstalling it. The plugin fallback to default device by overwriting asoundrc is intended behaviour to ensure that there is always a valid audio device and will not be changed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.