Comment # 6 on bug 1222755 from Edgar Aichinger

The pipewire wiki recommends to use a group "pipewire" to raise RLIMITS just
the same way it was done for JACK via group "audio" (or "realtime" on Debian
systems, I think). As a Linux audio user, contributer and packager, I have to
admit that I had no clear understanding how all this should be set up properly.
So I might be the culprit for this whole discussion popping up.

The whole thing started because of a warning message from Yabridge popping up
when instantiating Windows Plugins in Reaper or Ardour. The warning looked like
an error and confused people a lot, also because successfully running Windows
VSTs highly depends on the Wine version being used, and we didn't always
provide the "good" one. I'm not using Windows plugin binaries myself which
makes it even harder to have a clear picture.

Only recently, someone posted a comment in an Ardour forum thread that made
clear that it's only important to have a group for raising privileges via PAM
limits.conf.d snippet, possibly the group ownership of /dev/rtc0 and /dev/hpet,
and add the user to that group, but as long as such a group exists, its name
doesn't matter.

As it is, I think we should simply leave things as they have always been, and
use the audio group for low latency configuration.