-
Notifications
You must be signed in to change notification settings - Fork 211
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
UCM for Behringer UMC204HD broken #177
Comments
I tested using the newest ALSA UCM from master branch and everything went back to normal. I guess the issue is fixed in this commit 2cc5a68 |
Hello, I seem to have the same issue but in my case using the master branch does not solve the issue. While it fixed the error mentioned above I now get no mixer for this device and init fails. I am running libasound version 1.2.7 and ucm HEAD from git. The error I get is the following..
amixer also does not show any mixer device |
alsaucm dump text seems to show the mixer though...
|
Could you attach stderr output from `strace amixer -D hw:U192k contents' ? |
Here is the output, hope it helps. |
please note this is with the ucm2 profile enabled |
Please note I use pipewire and wireplumber in my setup here. |
Ok, I think I found something... When opening without ucm2
In this case controlC1 gets opened.. with ucm
In this case controlC1 is not even tried it is starting from C2 which obviously does not exist. |
Could you show the full strace ? |
Hi, |
Ok, I guess that's not the issue, there is something else happening in the UCM case. |
This is the issue. Could you attach the |
Here the ctl_remap file that's generated for the device |
It seems that the driver offers different control names:
Could you change those names in configuration ( |
I am not finding this in the conf file, could you explain this in more detail? |
Ok, I made the change to the file and the ctl file now looks like this.... but I still get the same error |
I do not understand this...
So yes "PCM Playback" is correct, but for whatever reason this still does not work |
Ok, I made it work by switching around the SRC and DST in the file. I can now select between the outputs and inputs. Please see the attached file as an example. Why do I need to switch this around though? |
The Dst and Src macro arguments were improperly used. Switch them. BugLink: #177 Signed-off-by: Jaroslav Kysela <perex@perex.cz>
The USB driver has two variants for the PCM control names: UMC204HD 192k Output Playback Switch / Volume and PCM Playback Switch / Volume BugLink: #177 Signed-off-by: Jaroslav Kysela <perex@perex.cz>
Oops, it's my fault. I switched the argument use in common/ctl/remap.conf macro. Thank you for tests. Could you retest with the current master tree (above two commits) ? |
Hello, I tested it with this and it works better. alsamixer now no longer fails, BUT I have a different issue now. When I initially connect the device I see the following errors...
As a result I am not seeing the outputs. If I then change the profile of the card in pavucontrol to "off" and back to "default" the outputs and inputs appear. Could this be a race during init? |
I haven't got to test it with my own UMC204HD but I did a while back at times see 41 clock source is not valid error, which seems to be a USB issue, as the device is not recognized as audio device. I did some unplug and plugging though (or replacing the USB cable) and it went away. I will see after this if I see those errors with these new commits. |
@gregory112 That's a different issue and is driver related, the clock source error is just a warning, but there have been fixes released yesterday for some other issues. |
The hw_params issue seems that the driver does not allow to set the requested parameters by the dshare alsa-lib plugin. Could you get some debug logs (more verbose) from pipewire to check which params cannot be installed ? |
I am not seeing this issue, the problem apparently seems that pipewire is trying to open the device but then fails for some reason...
|
@maru-sama Yes, just like you, I cannot suspend my laptop if the sound card is still connected. |
@maru-sama I actually did see your issue for a while, in which plugging the interface result in output being not detected, which I thought was related with the clock errors. I thought it was related to the USB connection, as I don't really see this issue anymore. I did actually change my USB cable, and try to just plug and unplug the interface. I really haven't seen this issue for a while, plugging the interface directly I can use it immediately without having to change profiles. I haven't updated my UCM to the latest commits created by this issue though, did this issue happen after the latest commit, or happen even before? |
@gregory112 I just got my device this friday so I never tried with an older version. That said my firmware is more recent than yours so I am also facing other issues. My main pet peeve is that I cannot turn the device OFF and with my setup (cabling) and the notebook not sleeping with it connected I have to find an alternative for now. |
Any way to look for the current version of the firmware that I am using? I haven't used this for a long time actually, few months only, so I cannot say that this one is particularly new or old. I wonder what "No such device" error mean. I also see it often in pipewire. |
Never mind I think it's the
|
Yep correct, I was about the reply that as well. I have a new version of the firmware which requires some usb quirks for proper playback but the sleeping issue is there as well. Your firmware should not have any issues with playback cutting out.
I will test this some more this evening, but could this really be a timing/interaction issue? |
You are using the 1.35 then? The patch for that has not been merged to upstream it seems, it is tracked in this issue, no? https://bugzilla.kernel.org/show_bug.cgi?id=215934. |
Correct, I applied it myself for my current kernel. |
I cannot judge anything without logs. Maybe |
@perexg I forgot to update the issue here. I tried this command two days ago WITHOUT pipewire or wireplumber running and the result was different every time. I saw either one profile or three profiles. In the end I changed the audio interface to a motu m4 and I do not have any issues, so I guess it is a driver/firmware related issue with this device. |
@maru-sama The patches there did not help you then? Do you have any issues with the 204 in Windows? |
The quirks For the Poppinga worked fine. The Others For the click source did Not. |
As this seems to be driver/firmware issue should we close this issue then? |
From my Site yes since the Last commits fixes the ucm Case. |
@perexg Hi. Is it possible the fix could be included in Fedora? The latest release 1.2.7.1 has the UMC204HD broken. |
@perexg You submitted two fixes, the direct card name and the mixer, and the direct card name one I think affects multiple soundcards. This might justify creating release 1.2.7.2? |
This is related: #128.
I came from this issue I filed in Pipewire: https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2471.
So previously a while back, Behringer UMC204HD was detected as a single stereo input channel. This sound card has two inputs. However, just recently, the channel was separated into two mono channels, which was perfect. However, with the most recent update (I don't know if it's pipewire, pipewire-alsa, alsa-card-profiles, or alsa-ucm), it reverted back into the stereo single input (left/right) mode. What can I do to bring back the previous correct settings (apart from the bugs I filed in Pipewire)? I did not modify any ALSA UCM files.
Previously, a while back: it is detected as UMC204HD 192k (stereo input).
Then: UMC204HD 192k Line 1 (mono) and UMC204HD 192k Line 2 (mono) (this is how it's supposed to be, I think it's from the pull request above).
Now: Back to UMC204HD 192k (stereo input).
Might also be helpful but I am using pipewire. This is the output of
alsaucm listcards
:There is an error for hw:2, which I assume is the Behringer. Here is the result of
alsaucm -chw:2 dump text
.The text was updated successfully, but these errors were encountered: