Hey,
Been a debian user for ages (debian sid most of the time), maintained various machines, PCs, etc over the years.
Lately, I got something strange from my mate install: whenever I plug my old MBox 2 USB soundcard to a USB port, even though it works out of the box when I explicitly use it (for example with mplayer: mplayer -ao alsa:device=plughw=M2 some_sound_file), it is flagged as "disabled" in the mate sound preferences and can't be used as the default output via the GUI. It is a load of rubbish because the device works, I can also use it with jackd without any problem (whether as the main device or via zita-a2j).
I have another USB sound gizmo which works as expected via the MATE sound pref GUI, a USB to optical gizmo which I use as the default sound card for the desktop's audio outputs. It is linked via ADAT to an RME Multiface II which also works out of the box either via pure ALSA or jackd (and even when selected in the mate sound pref GUI). In this way, whether I use jackd or not with the RME system, I always hear audio coming from any s/w sources such as the web browser or other which I do not want to redirect explicitly to the RME soundcard.
I do not use pipewire, I do not use pulseaudio. I have always used either pure ALSA or jackd. My question is: what does "device disabled" mean in this GUI ? What makes mate think that the device is "disabled" ?? I remember it used to work some months ago, I could select the MBox2 via this GUI, etc.
I had in the mean time updated my PC with the latest mate available via the debian unstable package system, + various other things. I am not sitting in front of the PC so I can't tell you exactly what version of mate / alsa / etc it is currently running.
Been a debian user for ages (debian sid most of the time), maintained various machines, PCs, etc over the years.
Lately, I got something strange from my mate install: whenever I plug my old MBox 2 USB soundcard to a USB port, even though it works out of the box when I explicitly use it (for example with mplayer: mplayer -ao alsa:device=plughw=M2 some_sound_file), it is flagged as "disabled" in the mate sound preferences and can't be used as the default output via the GUI. It is a load of rubbish because the device works, I can also use it with jackd without any problem (whether as the main device or via zita-a2j).
I have another USB sound gizmo which works as expected via the MATE sound pref GUI, a USB to optical gizmo which I use as the default sound card for the desktop's audio outputs. It is linked via ADAT to an RME Multiface II which also works out of the box either via pure ALSA or jackd (and even when selected in the mate sound pref GUI). In this way, whether I use jackd or not with the RME system, I always hear audio coming from any s/w sources such as the web browser or other which I do not want to redirect explicitly to the RME soundcard.
I do not use pipewire, I do not use pulseaudio. I have always used either pure ALSA or jackd. My question is: what does "device disabled" mean in this GUI ? What makes mate think that the device is "disabled" ?? I remember it used to work some months ago, I could select the MBox2 via this GUI, etc.
I had in the mean time updated my PC with the latest mate available via the debian unstable package system, + various other things. I am not sitting in front of the PC so I can't tell you exactly what version of mate / alsa / etc it is currently running.
Statistics: Posted by thorgal — 2025-01-28 10:24 — Replies 1 — Views 58