Low RTTIME limit detected after latest Manjaro Update

[hauiproductions]

Hello everyone, i hope you are doing well.
After applying the latest manjaro-gnome full update from few days ago, i experience a message "Low RTTIME limit detected" after starting any Musicmaking application (Reaper or Ardour, e.g.) and when a Windows-VST Plugin is loading via yabridge and wine-staging. All was working well for almost years before, and i checked twice all the usual realtime-settings (manual and via scripts). Also i tried different rollbacks of wine-staging versions. No success.

I reinstalled my 2 months old full system image, and everything is working out of the box. After applying the update (i even tried to not update the rt-kernel for testing) the message comes immediately by loading a windws-vst. I checked the usual how-tos and any hint in the internet and here in this forum.... but for now i am really out of ideas.....

ulimit -R -t

and

grep -H -e rtprio -e memlock /etc/security/limits.d/

is saying rtprio 98 and memlock unlimited…

rtcqs says all is ok/green.....

pulseaudio --dump-conf | grep rttime says rlimit-rttime = -1

I am not using Pipewire, i am using Jack2 with Cadence as GUI... seems Manjaro has changed some things here....
so if you got any hints or experience the same problem, maybe we find a solution together. Thanks a lot in advance!.
Haui

[hauiproductions]

So a litte update on here, i changed and searched manually (and via grep in my home folder) the whole machine for the rlimit-rttime = 200000 value, but it seems i cannot find it.

I also tried other Plugin Hosts like Carla (before it was yabridge), but the message also appears....... right now i downgraded my wine-staging to 7.20

No success at all..... i am a little bit lost right now

This value seems to be somewhere on the machine and is been read by the wine-vst plugin environment.....

[bluebell]

Is there a file in /etc/security/limits.d with

Code: Select all

@audio   -  rtprio     95
@audio   -  memlock    unlimited

and is your userid in the group audio?

[Impostor]

I am not using Pipewire, i am using Jack2

Are you sure? When I google "low rttime limit yabridge" I'm getting results pointing to a pipewire misconfiguration in~/.config/pipewire/jack.conf

[hauiproductions]

Thanks a lot for your help.

Yes, /etc/security/limits.d are all set and i have no pipewire config directories.....

Its really strange, it worked for over 2 years now, and this happened after the last (big) manjaro update.

I searched a lot and all configs are saying its all set the right way.

Seems to be that when the Windows-VST is starting up (even with carla or yabridge, and also in reaper or ardour) it gets the RTTIME Value from "another place"....

I also set wine back to 7.2 and to Windows 10... no change. I wonder no one else has this problem since last update.....

Starting the Windows VST Synth directly with wine makes no problem, just when the vst is started in the DAW (via .dll) the message appears.

[tseaver]

@hauiproductions

I wonder if your group memberships got reset when you upgraded. Can you post the output of the groups command from within a terminal? E.g., for me:

Code: Select all

$ tseaver lp dialout cdrom floppy sudo audio dip video plugdev users netdev lpadmin scanner sambashare vboxsf0

[hauiproductions]

Yes the output is:

network power rtkit realtime users storage lp input audio wheel

and my username.

Today i saw that the RTTIME message appears before even the dialogue "wine is updating" (i updated my downgraded version 7.2) for loading the VSTi is gone.

[hauiproductions]

I added myself now to all groups you mentioned (just for testing) and also installed for testing the liquorix-rt kernel...... no change

But with the liquorix-kernel, the WinVST plugins are loading and playing well.... The RTTIME Message still comes up after loading every Win VSTi ......

But it seems that they are working (still testing....)

With Manjaro-RT Kernel the VST plugins fail completely to load.

[hauiproductions]

So my - hopefully temporary - solution is:

Using the liquorix-rt-kernel when making music.

This kernel is right now the only option for me that my VST Instruments are loading. The error message still appears, but i can live with that.

All projects that i loaded were playing as before.

When i boot on exact the same machine with manjaro-rt kernel - the plugins fail.

I will keep an eye on it, and yes i will of course try to get someday rid of the Win-VST Plugins

When future Manjaro updates will not fix this error message / issue maybe it is time to make a new install from scratch... with Manjaro or another distro like AVLinux .....
So thanks everyone for helping, i will keep you updated in the future on this topic !

[Daniele71]

I've never heard of anyone with this problem with plain Jack (not pipewire implementation), you'r are very lucky
Also a rt-kernel is really not necessary but if it works for you...

[autostatic]

Did you test if your user can set realtime priorities? Quick test could be:

Code: Select all

$ xeyes & pid=$!; chrt -p 80 $pid; killall xeyes
[5] 1513259
chrt: failed to set pid 1513259's policy: Operation not permitted
[5]+  Terminated              xeyes

As you can see my current user is not allowed to set any realtime prio. Otherwise no error message should be shown.

[sunrat]

Using the liquorix-rt-kernel when making music.

Liquorix is a kernel with full pre-emption and a few other optimisations that make it good for audio, not strictly an RT kernel. In my testing a while back it worked as well as or better than RT kernels I tried.

I use it for everyday computing as well as audio but switch between ondemand and performance governor depending on current use. It works really well.

[novalix]

What is that README mentioned in that error message? Have you ever read that?

I don't know about Manjaro. Maybe they changed the jack configuration to gain rt privileges through the pipewire group.

[hauiproductions]

Did you test if your user can set realtime priorities? Quick test could be:

Code: Select all

$ xeyes & pid=$!; chrt -p 80 $pid; killall xeyes
[5] 1513259
chrt: failed to set pid 1513259's policy: Operation not permitted
[5]+  Terminated              xeyes

As you can see my current user is not allowed to set any realtime prio. Otherwise no error message should be shown.

Hi autostatic, thanks for helping,
my user is allowed and this command runs without error/fail.

[hauiproductions]

What is that README mentioned in that error message? Have you ever read that?

I don't know about Manjaro. Maybe they changed the jack configuration to gain rt privileges through the pipewire group.

Hi novalix, thanks for helping.
Yes i had been reading nearly every readme for this.... but found no hint...
I am sure, somewhere this value is set.... and can be changed ...... but i really dont know where to search anymore... i have been through every config file i know or others told me.....