What happens if you start the pulseaudio daemon in the console? Do you get rt scheduling then? I would check that first to see if pulsesudio is configured correctly. If that works you're probably better off asking the question in the systemd list then...
Best regards, Jürgen
Am 31. Oktober 2020 01:33:05 schrieb Matt Garman <matthew.garman@xxxxxxxxx>:
It appears it was a systemd config issue, rather than an issue withpulse. In addition to updating /etc/security/limits.conf, I alsoneeded to add the following to the [Service] stanza in my pulseaudioservice file:LimitRTPRIO=95LimitNICE=-19But I still cannot get realtime (fifo) scheduling to work. Iadditionally have this in my Service stanza:CPUSchedulingPolicy=fifoAnd this in /etc/pulse/daemon.conf:realtime-scheduling = yesBut still not getting realtime priority:# chrt -p `pgrep pulseaudio`pid 1203's current scheduling policy: SCHED_OTHERpid 1203's current scheduling priority: 0Thanks!On Fri, Oct 30, 2020 at 5:35 PM Matt Garman <matthew.garman@xxxxxxxxx> wrote:On Fri, Oct 30, 2020 at 5:17 PM Jürgen Herrmann <t-5@xxxxxx> wrote:Look here: https://t-5.eu/hp/Software/Pulseaudio%20Crossover%20Rack/OnlineHelp/#schedulingHi Jürgen, thank you for the quick reply. But either I'm missingsomething, or that says to do exactly what I've already done..Realtime scheduling works when run from the commandline using"runuser" (i.e. so I don't run as root). But when launched fromsystemd, setting the realtime priority fails (setrlimit() operationnot permitted).Thanks again,Matt_______________________________________________pulseaudio-discuss mailing listpulseaudio-discuss@xxxxxxxxxxxxxxxxxxxxxhttps://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss
_______________________________________________ pulseaudio-discuss mailing list pulseaudio-discuss@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss
