-
Notifications
You must be signed in to change notification settings - Fork 202
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
Add profile for Behringer UMC204HD #128
Conversation
Also, it seems when using this profile the auto-configured profiles for the device (eg. "Pro Audio") become unavailable. Is this a feature or a bug? |
If I change the inputs as you suggested, the configuration breaks; Here's the relevant parts as I modified them:
edit: and yeah, that's my alsa-info output. I also attached it in the pull request. |
I tried adding the volume controls using
Am I correct in assuming these volume controls would be the ones that show up in alsamixer, and the |
You can copy the config in the LibraryConfig to your ~/.asoundrc file and test the PCM using
Use |
Alright, this is strange. When I do it like that (though I had to replace
I tried defining them like this, but nothing seemed to change. What should I be looking for to begin with? Also, these volume controls also need to be "split"; the "UMC204HD 192k Output" control has 4 channels (FL FR RL RR) when physically the device has two stereo outputs. Is that possible?
|
We need pipewire logs - it seems that pw does not like S32_LE / mono combination.
Remove
Add lines `PlaybackCTL "umc204hd:${CardId}"' to the appropriate devices. |
OK, I attempted to add the volume controls (the changes are now in the PR), but I think they still aren't working correctly. I'm not observing any actual effect from adding them, but maybe I'm just not looking in the right places. What does describing the volume controls actually do? What can I do to verify that I've configured them correctly?
EDIT: The actual error seems to have been elsewhere in the output: EDIT2: Oh, about the |
Just check, if the stereo control maps correctly to the 'UMC204HD 192k Output Volume' and switch:
The stereo (value 2) is the default. It should be omitted (the functionality should be equivalent).
I don't think that there's a mapping scheme for this key. It should be just unique in the whole system. |
Alright, I think the controls should be right on paper now. Putting the config in However, I still can't actually find the remapped controls I have created (eg.
Could this be a PipeWire-related issue, since amixer is parsing the configuration just fine when it's in Thanks for the help :) |
Thanks for the feedback. The This config is not exported as the default alsa-lib configuration for now (so amixer do not see it). It's a private configuration for UCM applications only. I'll propose a solution soon. Pipewire: What does say |
Yeah, this is just something I tried in desperation and didn't undo.
`spa-acp-tool -c 0 -vvvv info` output (click)
|
Thanks, please, try to replace |
Also, EDIT: The second patch should resolve amixer / alsamixer controls visibility: |
Link: alsa-project#128 Signed-off-by: Peter Wedder <burneddi@gmail.com>
Link: alsa-project#128 Signed-off-by: Jaroslav Kysela <perex@perex.cz>
The second patch seems to work! I had to reboot after applying it ( alsamixer.mp4amixer -c U192k controls
I would never have figured that out on my own, thanks. |
Thanks, could you verify both patches so I can apply this to the main repo ? |
I did try both patches, in that I pulled the HEAD of the ucm204 branch. I did also try the first patch on its own, but it did not seem to work by itself; the controls remained invisible in alsamixer/amixer. |
The first patch should be just a cleanup for your work (merged all changes into one and add missing stuff). Could you show |
Alright, I tried the first commit by itself again, this time rebooting after applying it, and it seems to work too; the controls appear in alsamixer like they should. I believe I may have forgotten to reboot after trying it before, and clearly that (or restarting some component which I haven't discovered yet) is necessary for the controls to show up. In other words, I think the second patch (perexg@9723a9b) is not actually necessary; the controls show up in amixer/alsamixer even without it. HEAD of ucm204 branch (second patch on top of first patch):
The first patch (this commit: perexg@bed9728) by itself:
|
You are seeing the cached values and configs. The full state cleanup:
You may try to remove any additional changes for the UCM config and test, if you there are no new mixer controls. Then apply my two patches, reboot and check if there are controls and they are functional (changes the mute / volume). |
OK. I cleared the cache as you suggested and applied the two patches, and the controls work fine. Here's the output of
|
Link: #128 Signed-off-by: Peter Wedder <burneddi@gmail.com>
Link: #128 Signed-off-by: Jaroslav Kysela <perex@perex.cz>
Link: alsa-project#128 Signed-off-by: Peter Wedder <burneddi@gmail.com>
Link: alsa-project#128 Signed-off-by: Jaroslav Kysela <perex@perex.cz>
Adds a profile for the Behringer UMC204HD to split a 4-channel output into two outputs, and a 2-channel input into two inputs, as per the physical layout of the device. I have very little idea what I'm doing, so let me know if something looks incorrect (there's one thing that looks incorrect even to me which I shall point out in a comment below). The config does at least work, though.
alsa-info.txt