![]() ![]() ![]() Unfortunately, I may lose that if I switch to a non-service. Clearly they’ll have worked through some of I agree that the reproducibility that NixOS brings is very attractive – that’s what I’m here for. But I saw your response before you edited it and I think your suggestion to try to contact those people is a good one. I think it’ll come in handy when I’ve solved these more fundamental problems. That’s why I’m considering abandoning that approach and trying to go back to jack1, which is familiar to Muznix is very interesting, but it’s specifically about kernel configuration. However many jack clients are unable to connect to it for some reason. Another advantage is that it’s a proper service and its config can be declared in configuration.nix, which I see as a big win. It seems the standard NixOS approach is to go with jack2/jackdbus and interop it with pulseaudio, which sounds like a great idea, in principle. There are still some wrinkles I need to iron out, but I’ve been really excited with it so far and I don’t regret the swap. I’ve happily used Nix as a secondary PM for a few years now, but I only recently switched from Debian to NixOS. Sometimes, I’d just remove it altogether if the machine was dedicated to audio production. I’ve not found it terribly inconvenient to simply kill pulseaudio when I wanted to do more serious, jack-related things. I’ve used jack1 successfully for many of those years, though jack1 doesn’t cooperate well with pulseaudio. I could retreat back to Debian and continue as I have. It’s more specifically NixOS and jackdbus that are new to me and with which I’m struggling. ![]() Matters are certainly much better now than when I started. I think I may not have been clear regarding my starting point.Īs far as audio production with linux (Debian, for the most part) and FOSS per se, I’ve been at it for at least 20 years and it has been very satisfying. 256 frames/period do work quite well for me, 1024 is a pretty safe value.Thanks for the replies. If you experience XRUNs, try increasing the "frames/period" value on your "net master" machine. Now you have two channels on your desktop/laptop that will be sent to your RPi via network and be played back there. Jack_connect system:capture_2 alsa_out:playback_2 Jack_connect system:capture_1 alsa_out:playback_1 Connect the two channels coming from your "net master" (=desktop/laptop) to your ALSA-output: Run jack using the "net"-driver without realtime: "jackd -r -p 8 -d net -C 2 -P 0" Load the "netmanager" on your desktop/laptop: "jack_load netmanager" I even went one step further and set-up a netjack-solution: The only drawback is that you have to connect your client manually to the output-ports since they are not named "system." That's about it! alsa_out will create two output-channels in jack that will be played back via ALSA to the RPi's analog jack or via HDMI. Run alsa_out with lowest possible quality-setting (keep CPU-usage low): alsa_out -q 0 -v Channel count doesn't really matter since we won't be using them! We limit the ports to 8 to limit memory-usage but feel free to increase this value. Run jack using the "dummy"-driver without realtime: "jackd -r -p 8 -d dummy". Install jack from "jack2"-branch (was jack-dmp) (for example jack-1.9.8) I got jack-audio-connection-kit running on the RPi! Argh, I feel a little dumb right now since it took me so long to get this idea. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |