<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'>
> Since people usually are using Jack by a package, when thy use real-time<br>> audio apps IMO it's ok to include it to a Jack package, anyway, IMO<br>> there should be a dependency setting without nice and with memlock.<br><br>Neither jack, ardour or any other app actually uses the 'nice' option simply<br>because it is in the limits file. The file just says that if applications/users want<br>to use a value this is what they are allowed to configure themselves without<br>having to have root permissions and thereby invalidate a otherwise reasonable<br>security policy. That is why having a 'nice' value in the file is useful: users can<br>tune the system without needing the recourse of having the root password.<br><br>> FWIW very often there are recommendations to _avoid_ a kernel-rt, since<br>> a distros 'default', 'desktop', 'generic' kernel should have the same<br>> capabilities and the kernel-rt should have disadvantages. The resume<br>> then could be, that people wonder, that they can't use Linux for complex<br>> audio sessions.<br><br>The issue is bigger than Linux. I was talking to Stings pianist, Kipper, on this<br>subject a while ago now. He had just bought the biggest FO Mac for his studio. <br>After a few days he pretty much took it back to the store and dumped it on them <br>as it did not do what was written on the tin, demanding that they make it work.<br>They had to tune it. OK, it finally did what he needs but the only difference is <br>that either you have to do the work or somebody else does. Linux in itself is not <br>the issue.<br><br>> IMO it doesn't make sense to package audio and MIDI applications without<br>> packaging the environment to use those apps.<br><br>Again, this is not limited to Linux and the PAM limits file is not in itself the solution. <br>The limits file only enables the possibility that applications can ask for what devos<br>think is optimal for their function and that somebody can configure an optimised <br>system without having to be root. That means the limits.conf should give that user <br>or group sufficient access to all the resources that they might need. That includes<br>negative 'nice' values for the cases where it might be useful.<br><br>Regards, ninck.<br> </body>
</html>