Manjaro 6.9.3.3 GNOME
Running Renoise 3.4.4 (purchased), I get the following message window on startup:
Failed to create a RealTime priority thread for ALSA. Will create a non RT thread instead…
It is highly recommended to use RealTime priority audio threads with ALSA AND Jack to get acceptable audio latencies, but you may need admin rights to create RT threads. Please see the Renoise for Linux FAQ on https://www.renoise.com for more details.
What I tried
Install from the install.sh script inside the renoise tarball download for Linux (demo version FYI).
<[Crackling sounds]>, removed Renoise using the uninstall.sh script…
The message from Renoise wants RealTime with both ALSA and Jack. Manjaro seems to be running PipeWire, as opposed to PuseAudio. So, I don’t want to start out-smarting either Manjaro or Renoise.
What is the right way to get this working?
What should I do now, if anything?
Should this be considered a “bug” to report somewhere?
Edit: This is partially solved, (viz RealTime). I’m continuing discussion here.
I did it just now (realtime-privileges and realtime group membership).
That removed the RealTime error message at application startup.
But, it still makes only crackly sounds just the same. Also tried reboot and remove-reinstall. So, I’m presuming there is more to be done with the audio stack, probably with PipeWire, but I don’t want to guess.
The message itself says it wants “RealTime priority… with ALSA and Jack”. So, probably that isn’t happening, even with proper realtime permissions.
I installed the linux66-rt kernel and it hasn’t solved it. The question is about how to properly configure the RealTime sound stack with ALSA, PipeWire, and Jack. Should this become a bug report?
less -N install.sh
(lists the install.sh file with line numbers in front - here is what I think is relevant and seems to fit your problem description)
204 echo "Checking audio configuration..."
205
206 if [ -f "/etc/security/limits.d/audio.conf" ] || \
207 `grep -E "^[^#]+(rtprio).*$" /etc/security/limits.conf > /dev/null`; then
208
209 echo " OK - PAM seems to be installed and configured for audio applications."
210 echo " If you nevertheless have problems with ALSA or Jack (such as crackles \
211 or too high latencies) take a look at 'https://wiki.linuxaudio.org/wiki/system_configuration#limitsconfaudioconf' \
212 for help please..."
213
214 else
215 echo " PAM seems not to be installed or not configured for audio applications."
216 echo " It's HIGHLY RECOMMENDED to tweak your system for realtime audio applications to \
217 get acceptable audio/MIDI latencies with Jack and ALSA. Please have a look at \
218 'https://wiki.linuxaudio.org/wiki/system_configuration#limitsconfaudioconf' for more information about this topic..."
It seems you don’t have this file - need to create it with the proper content
(of which I know nothing - I haven’t looked at the references given)
It looks like you have looked in the wrong place - and a -rt kernel is also not what is called for.
I didn’t realize that you got it from AUR - I just downloaded the installable file directly from their site and looked inside to find some clues.
The AUR uses the very same file.
I just tried to see what the installer does and found these comments and hints in there.
so:
no!
You could either look in your pamac cache (or yay or whatever you used) or download the file yourself once more, unpack it and you’ll find that file from which I got these lines and can look at it yourself.
I have seen that file and I did have it. It should have been used both in the simple install.sh use and the renoiseAUR package. Basically, the AUR package double checks some dependencies and allows it to be removed with yay -R renoise, rather than uninstall.sh…
I thought it would - because crackling was mentioned in the installer file - and I don’t have that directory nor any file in it.
I also don’t know what should be in there.
I had hoped that this would help you - sorry that it didn’t.
I know next to nothing when it comes to audio - I just found these hints but didn’t look at them myself.
Those actually were the “proper” troubleshooting steps, which I missed. Still, that page has some type-os and one of the links in that article is broken.
I’d definitely vote against this - but you can look at these files as examples and compare them with what you have.
For instance navigate (on that github site) to the modules/pipewire/pipewire directory and find what is in these sample files.
All of these can be installed in your $HOME, no need to potentially mess your system up by putting them into /etc - Manjaro or not, the Linux variant is largely irrelevant, Manjaro isn’t something special or exotic.
These are just configuration files - revert any changes and have the previous state again.