-
Notifications
You must be signed in to change notification settings - Fork 222
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
ASUS ROG Zenith II Extreme UCM2 profile #197
base: master
Are you sure you want to change the base?
Conversation
…ut working. No mic, no jack control, no SPDIF
…hen unplugging/plugging while playing
For the Mic input issue, here is something interesting:
So my mic device is 48.
If I read this correctly, it finds the alsa mic as
Is it jumping back to device 0 ? |
You can test the UCM profile using two tools:
Please, attach the |
… messing about with spa-acp-tool
Progress! I tried this:
As the output was very long, I commented out my As I didn't see anything weird in there, I added Then I tried
And lo and behold, my devices appear in pavucontrol. After a reboot, it still seems to be working. If I change the code to reactivate the I don't know how those SectionUseCase interfere, but it looks like I should just get rid of the ProAudio SectionUseCase test. So looks like it's a step forward. I'll test further and play around to tweak the config. |
So here is what I'm still missing now:
|
…DIF for hw:0,3 (works when hw:0,1 is commented)
Hi,
I'm trying to get sound working on my ASUS ROG Zenith II Extreme motherboard. There is a kernel patch that I'm using for a while, that seems to get most ALSA stuff working. It kinda also works with the default ProAudio ACP profile (minus some case where it seems to loose synch after a while. But recording works).
Now, I'm trying to get it to work correctly with my Debian unstable desktop, using PipeWire with the PA tools (mostly pavucontrol).
Mostly, the routing of the inputs for capture seem to not work. It's always routing the input from
hw:0,0
, which isLine In
.I tried making a UCM2 profile, and got some basic stuff working. but there are some things where I'm stuck.
What I do is edit the UCM files, and then reload PW and WP with
systemctl --user restart pipewire pipewire-pulse wireplumber
. Then, I check withpavucontrol
what devices appear. If there is a syntax error, it falls back toOff
profile, orProAudio
profile, which was an experiment from me to see if I could just have the same pass-through behaviour as the ACP pass-through. I don't know if there is a better way to debug UCM2 profile loading, this approach leaves me pretty blind on what failed.Here are the issues I currently have:
speaker-test
output, sound goes to wrong outputs with pw.hw:0,0
instead ofhw:0,1
I don't know if the issue is still on the ALSA driver side or on the PW/PA config. I'm not a kernel programmer and don't know much about ALSA and PW, so any pointer here is welcome.