Help with Ardour DAW

When I install Ardour I get warning with the following message:

“The current user can not execute realtime processes. This will adversely affect audio latency. This system has an audio group and the user is a member. Check /etc/security/limits.conf”

The next warning is "Your system seems to use frequency scaling. This can have a serious impact on audio latency. For best results turn it off, e.g. by choosing the ‘performance’ governor.

can anyone tell me what this application is wanting?

my /etc/security/limits.conf file is

john@localhost:~> cat /etc/security/limits.conf
# /etc/security/limits.conf
#
#Each line describes a limit for a user in the form:
#
#<domain>        <type>  <item>  <value>
#
#Where:
#<domain> can be:
#        - a user name
#        - a group name, with @group syntax
#        - the wildcard *, for default entry
#        - the wildcard %, can be also used with %group syntax,
#                 for maxlogin limit
#
#<type> can have the two values:
#        - "soft" for enforcing the soft limits
#        - "hard" for enforcing hard limits
#
#<item> can be one of the following:
#        - core - limits the core file size (KB)
#        - data - max data size (KB)
#        - fsize - maximum filesize (KB)
#        - memlock - max locked-in-memory address space (KB)
#        - nofile - max number of open file descriptors
#        - rss - max resident set size (KB)
#        - stack - max stack size (KB)
#        - cpu - max CPU time (MIN)
#        - nproc - max number of processes
#        - as - address space limit (KB)
#        - maxlogins - max number of logins for this user
#        - maxsyslogins - max number of logins on the system
#        - priority - the priority to run user process with
#        - locks - max number of file locks the user can hold
#        - sigpending - max number of pending signals
#        - msgqueue - max memory used by POSIX message queues (bytes)
#        - nice - max nice priority allowed to raise to values: [-20, 19]
#        - rtprio - max realtime priority
#
#<domain>      <type>  <item>         <value>
#

#*               soft    core            0
#*               hard    rss             10000
#@student        hard    nproc           20
#@faculty        soft    nproc           20
#@faculty        hard    nproc           50
#ftp             hard    nproc           0
#@student        -       maxlogins       4
@users hard memlock unlimited
@users soft memlock unlimited
john soft memlock unlimited

# End of file

john@localhost:~> 


I solved the problem by deleteing @user lines, adding john hard memlock unlimited, and adding john - rtprio 95

@jdcart15:

Maybe, the application was confused by a single group being configured by 2 identical statements for the types “hard” and “soft” –

  • AFAICS, the correct syntax is to specify the item and value once only with the type “-” which implies both types “hard” and “soft” – combined …
    The syntax is explained in the “limits.conf” (5) man page.

I’m thinking that the rtprio 95 was important. The current file that is working has both hard and soft designations. i.e. both “john hard memlock unlimited” and “john soft memlock unlimited”