Tutorial: Realtime (RT) Audio on Linux: The Basics (for Laymen)
Uploader Comments (jkymarsh)
All Comments (21)
-
I'm afraid all it does is just allows a non-root user to renice processes. In order to get hard real-time perfomance one needs to run patched kernel. I tried doing things adviced in this video but got no perfomance increase (comared to same thing ran with root). After patching a kernel I can run JACK with under 1ms latency with no Xrun's. Cheers
-
This video is a nice tutorial to optimize the standard linux for realtime audio, but it's still using soft real-time kernel, which has nothing to do with hard real time does it?
-
I can run my nord rack2 with hydrogen drum machine cortoled by seq24 now. thank you.
-
@1:48 Finally! Somebody making a sane statement about linux-rt kernel. Thank you, friend.
-
Great way of explaining and teaching us, thank you for your kind work,
-
tahnk you thank you =) =)
-
I'm in MEPIS, so I had to log into the actual root login to make these changes.
I couldn't save the changes from my user account with root privileges.
But it worked fine after changing it in the actual root account of MEPIS.
Not sure about setting your limits at the user level. Would be better to use the @audio group so only those processes get the increased privs. Otherwise, any old user process (gnome panel, notifications, browsers, etc) can steal resources during the middle of your recording sessions!
jaaxxone 1 year ago
@jaaxxone This is untrue. First off, placing users within in Audio group doesn't have anything to do with determining what programs use RT priorities; it's simply a naming system used to keep things straight if a lot of users use your system. Programs don't know (or care) what user group you're a member of. Secondly, programs don't inherently use unbounded amounts of system resources; they have to specifically be configured to do so.
jkymarsh 1 year ago
Changed file permissions:
sudo chmod limits.conf -rwxrwxrwx
but got this message:
"Could not save the file /etc/security/limits.conf.
You are trying to save the file on a read-only disk. Please check that you typed the location correctly and try again."
Ejacka 1 year ago
@Ejacka Try actually logging in as root rather than using sudo. If that doesn't work, you may want to alter your chmod tactic... Using chmod ugo=rwx (or some variation thereof) has always been more reliable and straightforward for me. (Also, doesn't a hyphen before the permissions arguments remove from a file/directory?)
jkymarsh 1 year ago
INteresting, but one thing I don't understand is what's the difference between soft and hard limits and the "-" ?
fatsterfatster 1 year ago
@fatsterfatster A soft limit is a default value when a user logs in, and this value can be increased using the terminal "ulimit" command. However, we're not interested in either a soft limit or a hard maximum limit, nor using "ulimit" to manually change anything, so we don't have to bother with hard or soft at all.
jkymarsh 1 year ago