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 <[email protected]>:
It appears it was a systemd config issue, rather than an issue with
pulse. In addition to updating /etc/security/limits.conf, I also
needed to add the following to the [Service] stanza in my pulseaudio
service file:
LimitRTPRIO=95
LimitNICE=-19
But I still cannot get realtime (fifo) scheduling to work. I
additionally have this in my Service stanza:
CPUSchedulingPolicy=fifo
And this in /etc/pulse/daemon.conf:
realtime-scheduling = yes
But still not getting realtime priority:
# chrt -p `pgrep pulseaudio`
pid 1203's current scheduling policy: SCHED_OTHER
pid 1203's current scheduling priority: 0
Thanks!
On Fri, Oct 30, 2020 at 5:35 PM Matt Garman <[email protected]> wrote:
On Fri, Oct 30, 2020 at 5:17 PM Jürgen Herrmann <[email protected]> wrote:
> Look here:
https://t-5.eu/hp/Software/Pulseaudio%20Crossover%20Rack/OnlineHelp/#scheduling
Hi Jürgen, thank you for the quick reply. But either I'm missing
something, 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 from
systemd, setting the realtime priority fails (setrlimit() operation
not permitted).
Thanks again,
Matt
_______________________________________________
pulseaudio-discuss mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss
Mit Aqua Mail Android
https://www.mobisystems.com/aqua-mail
_______________________________________________
pulseaudio-discuss mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss
