Tfive,
You have no idea how happy that makes me.
I did receive a PM from RAndyB who gave me some assistance but I've been too busy with house repairs to do anything about it (replacing weatherboards that were put up badly and incorrectly is an 'interesting' and perplexing exercise).
Would you be so kind as to post the code and I will adapt to my situation, hopefully with some luck and success? I am trying to install Logitech Media Server on my FreeNAS and if that works, I will use a RaPi as a Squeezelite client with PaXover Rack installed on it as well. One less big box, less energy used, more WAF, and centralised control.
You have no idea how happy that makes me.
I did receive a PM from RAndyB who gave me some assistance but I've been too busy with house repairs to do anything about it (replacing weatherboards that were put up badly and incorrectly is an 'interesting' and perplexing exercise).
Would you be so kind as to post the code and I will adapt to my situation, hopefully with some luck and success? I am trying to install Logitech Media Server on my FreeNAS and if that works, I will use a RaPi as a Squeezelite client with PaXover Rack installed on it as well. One less big box, less energy used, more WAF, and centralised control.
Last edited:
For anyone reading this thread and wondering:
Here is the thread that I started when exploring ALSA to replace MiniDSP:
asoundrc and ladspa
There is now enough information on the web to get started, as Tromperie has shown in his original post. It's difficult to work through the ALSA documentation: even the syntax of asoundrc file seems inconsistent, which adds to the frustration. As I have said before; great software, shame about the user manual.
Tromperie: It's the equivalent of Britain's January with you, if I calculate correctly? Just checked the weather in Melbourne - looks ideal for the outside work, unlike January here.
Andy
PS after a decade or so, I realised that the User Manual was the starting point for software projects. Actual people with cheque books focusses the mind in that direction.
Here is the thread that I started when exploring ALSA to replace MiniDSP:
asoundrc and ladspa
There is now enough information on the web to get started, as Tromperie has shown in his original post. It's difficult to work through the ALSA documentation: even the syntax of asoundrc file seems inconsistent, which adds to the frustration. As I have said before; great software, shame about the user manual.
Tromperie: It's the equivalent of Britain's January with you, if I calculate correctly? Just checked the weather in Melbourne - looks ideal for the outside work, unlike January here.
Andy
PS after a decade or so, I realised that the User Manual was the starting point for software projects. Actual people with cheque books focusses the mind in that direction.
Last edited:
That's why besides linking two soundcards at the ALSA layer (did it way back when with two M-Audio Delta 1010s in our home studio to have 16 tracks) I have never tinkered with .asoundrc and ALSA before. It's like using assembler compared to python if that makes sense, ALSA is completely at the hardware level.
Tromperie has to do it though as he has a kind of a special case setup with one soundcard delivering all the left channel audio and one soundcard all the right channel audio. As he succeeded in creating a multi-device though everything else should now be handled one layer up, eg. by pulseaudio.
In the end all the fussing about with config files by hand is not user friendly at all and that's why i created this wonderful piece of software - Pulseaudio Crossover Rack. A little bit of self-praisal can never hurt, can it? Let's get serious again, at the end of the day I'm not a coder but a user too and I want things to "just work (TM)".
Tromperie has to do it though as he has a kind of a special case setup with one soundcard delivering all the left channel audio and one soundcard all the right channel audio. As he succeeded in creating a multi-device though everything else should now be handled one layer up, eg. by pulseaudio.
In the end all the fussing about with config files by hand is not user friendly at all and that's why i created this wonderful piece of software - Pulseaudio Crossover Rack. A little bit of self-praisal can never hurt, can it?
Let's get serious again, at the end of the day I'm not a coder but a user too and I want things to "just work (TM)".
Do you have the original, unmodified version of /etc/pulse/default.pa in place? If not, grab a backup or reinstall the original version first. If not yet done, make a backup. Then, comment the following section:
Then uncomment and modifiy the line containing "load-module module-alsa-sink" to read:
After that, restart pulseaudio by issueing "pulseaudio -k" from a console. Then pulseaudio should now come up with only one device with 12 channels.
If it doesn't, well, then we have to investigate further. Pro tip: always go step by step, even if you think this is piecemeal. But this is good practice and the basis to debugging a problem. And if you change multiple things at once, how should we know exactly what is the state of your system and how to fix it? So if you want people to help you, you should heed their advice
Code:
### Automatically load driver modules depending on the hardware available
.ifexists module-udev-detect.so
load-module module-udev-detect
.else
### Use the static hardware detection module (for systems that lack udev support)
load-module module-detect
.endif
Code:
load-module module-alsa-sink device=multidevIf it doesn't, well, then we have to investigate further. Pro tip: always go step by step, even if you think this is piecemeal. But this is good practice and the basis to debugging a problem. And if you change multiple things at once, how should we know exactly what is the state of your system and how to fix it? So if you want people to help you, you should heed their advice
Default config files are installed by their corresponding package. /etc/pulse/default.pa is in package pulseaudio Debian -- File list of package pulseaudio/buster/armhf
Either extract the file from the dpkg package (e.g. midnight commander mc is great for that), or reinstall the package (apt-get install --reinstall pulseaudio) and the orig config will be copied to your directory with .dpkg-dist suffix linux - Duplicate config files with .dpkg-dist extension - Server Fault
- Status
- This old topic is closed. If you want to reopen this topic, contact a moderator using the "Report Post" button.