You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
console_callbacks.py requires a default mixer (alsa.mixers()[0]) to exist even if another mixer is explicitly specified with --mixer.
It's a problem at least in the following case: No HW mixer exists (The case for Hifiberry DAC), and a software mixer has been added to asound.conf and is specified with the --mixer option, but that mixer has never been used by anyone. (It seems - although I don't understand how alsa works - that it becomes visible with amixer as soon as some process has used it once)
The solution now is to edit console_callbacks.py, removing the dependency on alsa.mixers()[0], or to invoke the software mixer once with another program.
This could be solved by skipping the mandatory "default=alsa.mixers()[0])" assignment and only trying that assigment if there is no --mixer argument provided.
The text was updated successfully, but these errors were encountered:
console_callbacks.py requires a default mixer (alsa.mixers()[0]) to exist even if another mixer is explicitly specified with --mixer.
It's a problem at least in the following case: No HW mixer exists (The case for Hifiberry DAC), and a software mixer has been added to asound.conf and is specified with the --mixer option, but that mixer has never been used by anyone. (It seems - although I don't understand how alsa works - that it becomes visible with amixer as soon as some process has used it once)
The solution now is to edit console_callbacks.py, removing the dependency on alsa.mixers()[0], or to invoke the software mixer once with another program.
This could be solved by skipping the mandatory "default=alsa.mixers()[0])" assignment and only trying that assigment if there is no --mixer argument provided.
The text was updated successfully, but these errors were encountered: