|
Bugzilla – Full Text Bug Listing |
| Summary: | Pipewire, missing pipewire group | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | Daniele Tombolini <kailed> |
| Component: | Sound | Assignee: | Takashi Iwai <tiwai> |
| Status: | NEW --- | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | alarrosa, edogawa, kailed, tiwai |
| Version: | Current | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Daniele Tombolini
2024-04-14 09:47:56 UTC
What's the exact requirement here? Do you mean it's needed for establishing a higher RT priority? Or any other reason? Yes, for RT priority as documented here: https://gitlab.freedesktop.org/pipewire/pipewire/-/wikis/Performance-tuning#rlimits Better to have that group already available. AFAIK some distros have already added it. Thnaks. Isn't it better to use rtkit instead? (In reply to Takashi Iwai from comment #3) > Isn't it better to use rtkit instead? To be honest, I don't know for sure but it seems that everybody are using rt limits. At the end it's just a group, it doesn't hurt to have it :) Some more info: https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/thread/3ALY7DNUFGXGJQT7QFBOADAXGPV6HLGF/ I forgot to mention that there are also some problems with Yabridge and RTKIT. 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. |