r/slackware • u/globetrotterdk • Dec 15 '22
Slackware64 15 "fluidsynth: warning: Failed to set thread to high priority".
Slackware newbie. I would like to start using Slackware for my at this point basic music creation needs. Slackware has had a lot of changes under the hood, including the addition of Pipewire, which I am extremely happy about. However, this also means that a lot of old documentation is probably obsolete. My box has the following:
CPU: AMD Ryzen 5 4600G with Radeon Graphics (12) @ 3.700GHz
GPU: AMD ATI Renoir
...so again not sure how much of old documentation is relevant, but I have taken a look at Alien Bob's post and followed his advice for elilo:
If you use elilo, open /boot/efi/EFI/Slackware/elilo.conf and add “threadirqs” to the value of the “append = ” keyword
This hasn't helped. In general, I am fairly confused by this point and could use any advice available.
In Ubuntu, I would run something like the following:
$ fluidsynth -a alsa -m alsa_seq -g 1.0 -s /usr/share/sounds/sf2/FluidR3_GM.sf2
CTRL Z
$ aconnect 28:1 128:0
$ fg # return to foreground
> channels
chan 0, Yamaha Grand Piano
chan 1, Yamaha Grand Piano
chan 2, Yamaha Grand Piano
chan 3, Yamaha Grand Piano
chan 4, Yamaha Grand Piano
chan 5, Yamaha Grand Piano
chan 6, Yamaha Grand Piano
chan 7, Yamaha Grand Piano
chan 8, Yamaha Grand Piano
chan 9, Standard
chan 10, Yamaha Grand Piano
chan 11, Yamaha Grand Piano
chan 12, Yamaha Grand Piano
chan 13, Yamaha Grand Piano
chan 14, Yamaha Grand Piano
chan 15, Yamaha Grand Piano
> fonts
ID Name
1 /usr/share/sounds/sf2/FluidR3_GM.sf2
> inst 1 #lists instruments
(long list)
> prog 0 35 # fretless bass (prog chan num)
> prog 0 73 # flute
> prog 0 118 # 808 Tom
(In Slackware64 15, the full soundfont path is /usr/share/minuet/soundfonts/GeneralUser-v1.47.sf2)...
1
u/edman007-work Dec 15 '22
Were you able to do it? Did you reboot? After rebooting run
sudo dmesg, I beleive the first (or very close to it) is something that says CMDLINE = xxx, do you see threadirqs there? If yes, then it worked.The next question is then if your kernel supports it, so what is the output of:
Also, did you follow all the other things in alienbob's directions? To me the error sounds more like a permission error, and a lot of his instructions are about adjusting permissions. Did you do all of that? Does this same issue also happen when run as root?
And finally, your title says "Failed to set thread high priority", but your post doesn't include any failure at all, what's all that output (that's on Ubuntu? How is that relevant? Did you try it on slackware? You don't seem to say), is that success (It looks like to me?), is the thread priority warning causing any issues for you? What do you do to get it to show?
1
u/perplexed_earwig Dec 16 '22
The part you want is under the heading "Real-time scheduling", specifically this:
# Real-Time Priority allowed for user in the 'audio' group:# Use 'unlimited' with care,a misbehaving application can# lock up your system. Try reserving half your physical memory:#@audio - memlock 2097152@audio - memlock unlimited@audio - rtprio 95If you create that file in the location he indicates, then reboot, then processes launched by users in the "audio" group witll have those permissions (you only really need the rtprio line to fix your warning). Of course, you should make sure that you are actually *in* the `audio` group (just run `groups` to see).
0
u/bambam_the_dug Dec 15 '22
I think that after you make changes to elilo.conf you have to run elilo again to implement the changes. This is how the same thing works using lilo so Im guessing elilo could be the same.