-
Notifications
You must be signed in to change notification settings - Fork 225
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hint for buffer delay setting is inaccurate if pipewire is used #2347
Comments
Thanks for the report. Would like to submit a PR? Note: This will likely not make it into 3.8.2 anymore as we are in translation freeze phase (beta) already. But future versions would certainly benefit from that clarification. |
I would better pass than on to those with better level of English than me 😄
Yes, I can confirm that (no need to start with |
The audio controls that are specific to one audio subsystem should only be being shown for that audio subsystem. JACK isn't OS-specific, of course. However, plenty of non-OS-specific controls may have OS-specific niggles - these are generally dealt with at compile time. |
Sorry for the maintenance noise here. To me it seems a bit difficult to proceed here. @gilgongo @jose1711 @mulyaj do you have any other suggestion on how to move this forward? I think
Could be reworded to
**Note: ** I 've unsubscribed from this issue to keep notifications down. If you need me, please ping me. |
I think this is good. |
Hopefully, #2645 will close this. |
Describe the bug
Hint for Settings/Buffer Delay shows:
.. On Linux, use the JACK configuration tool to change the buffer size.
If a user is using Pipewire this text does not help much - changing the buffer size in - say QjackCtl has no effect. Instead jamulus needs to be started like this (for 128 samples):
As Pipewire is being adopted by more and more Linux distribution, hint should be improved.
Operating system
Arch Linux, x86_64
The text was updated successfully, but these errors were encountered: