hudiy.eu

Just played around, starting hudiy after each command in terminal, it’s the last one that breaks it, “set default source”

The routing looks correct when loading the modules manually. The error after starting Hudiy is not related to PipeWire. It seems that the system didn’t close the sockets on time. In such cases, try shutting down Hudiy with the command pkill -9 hudiy (Step 3) - this will force the system to clean up all resources.

There also appears to be an access/permissions issue with the /run path, but it shouldn’t cause problems (didn't you edit some files with sudo?).

Restart your Raspberry Pi to clear PipeWire (the modules in the config should remain commented out with #), then carefully repeat the same steps to load the modules again and let us know how the audio behaves.

Hi I’ll try that in a moment, however prior to tonight every time i’ve closed hudiy with alt F4 and never had an issue getting it to start again. What was the file I may have edited? I can check if i’ve done anything.

alex124.rh wrote: Sat Sep 06, 2025 10:28 pm Hi I’ll try that in a moment, however prior to tonight every time i’ve closed hudiy with alt F4 and never had an issue getting it to start again. What was the file I may have edited? I can check if i’ve done anything.

If you see similar errors with bind or if Hudiy fails to start after close, just in case, run the command pkill -9 hudiy each time. The /run permissions can be ignored for now. We’ll still be available for some time today, so for now let’s focus on the PipeWire modules.

Hey,

Thanks for the prompt response. everything’s okay now, except some weird behaviour with the subwoofer dial.

It’s affecting the front and rear channels whenever it’s turned above 0 it seems. I’m not sure what effect it’s having on the sub channel itself.

see attached video, apologies it’s not great but i have no tripod.

https://share.icloud.com/photos/041XCmx ... Jl0ikwPhAg

hudiy wrote: Sat Sep 06, 2025 10:33 pm

alex124.rh wrote: Sat Sep 06, 2025 10:28 pm Hi I’ll try that in a moment, however prior to tonight every time i’ve closed hudiy with alt F4 and never had an issue getting it to start again. What was the file I may have edited? I can check if i’ve done anything.

If you see similar errors with bind or if Hudiy fails to start after close, just in case, run the command pkill -9 hudiy each time. The /run permissions can be ignored for now. We’ll still be available for some time today, so for now let’s focus on the PipeWire modules.

also if you need to address the latest issue first that’s fine, but any guidance on getting this new patch to run from boot that would be great, maybe a service, or an autostart script, or the hudiy run script, with a 10 sec wait in front? let me know what you thinks best

The Subwoofer dial behavior is expected in this case. It will work incorrectly because PipeWire has mixed up the sound card channels (hence the need to load the remap-sink module to map them correctly). In the new version of Hudiy, we’ve added a configuration option so that the Subwoofer dial simply controls the LFE channel volume (as it typically works in amplifiers) instead of balance. With this option enabled, everything should work correctly in the new version.

You can add the commands for loading the modules to $HOME/.hudiy/share/hudiy_run.sh (before start of the Hudiy) and include a sleep x (where x is the number of seconds) at the beginning of the script to wait until the card is detected (1-2 seconds of sleep should be enough).

This is, admittedly, a workaround, but PipeWire currently doesn’t have any mechanism to solve the problem of late card detection (at least it’s not described in any available documentation).

It is indeed a workaround but it’s a solution nonetheless and I am very grateful for you help. it may not be the ideal way but it’s better than having no sub controls.

in the next version will the sub volume still increase proportionally with the main volume? can you clarify how it will work, thanks.

also third point, i’m having trouble with siri audio being crackly and muffled. same with texts and calls in CarPlay. I can open a new thread if needed.

hate to say it, but another issue, now when ever i boot the carplay keeps hanging and crashing, wont connect without me first disconnecting it and reconnecting it physically https://share.icloud.com/photos/0b0vOSq ... _0vkFKcand then when i try again. the whole thing crashed, not even alt f4 working.
https://share.icloud.com/photos/0222obv ... 76ijrH6alA
then next time, it goes into carplay but now touch doesn’t work, it’s not the screen because if i jump into terminal that works fine with touch. then i unplug the carlinkit, and touch is fine, so my conclusion is an issue with carplay here.

i will say i had encounter this maybe 1 in 10 or 20 boots previously when hudiy was untouched but never was bothered but its more common now.