Don't assume requested latency was provided #33

Closed
opened 2025-06-17 19:24:27 +01:00 by Ghost · 1 comment
Ghost commented 2025-06-17 19:24:27 +01:00 (Migrated from codeberg.org)

Even though we request a specific buffer size from Pipewire, it might not agree to it, for example due to system-wide configuration. Instead of hardcoding the value, the actual buffer size should be retrieved via the event queue the same way as the sampling rate.

Even though we request a specific buffer size from Pipewire, it might not agree to it, for example due to system-wide configuration. Instead of hardcoding the value, the actual buffer size should be retrieved via the event queue the same way as the sampling rate.
Ghost commented 2025-08-14 09:56:57 +01:00 (Migrated from codeberg.org)

Not a bug. Requesting a specific latency overrides user configuration, even when going under the minimum quantum value. As far as I can tell from my investigation, the requested latency is guaranteed from the audio server.

Not a bug. Requesting a specific latency overrides user configuration, even when going under the minimum quantum value. As far as I can tell from my investigation, the requested latency is guaranteed from the audio server.
Sign in to join this conversation.
No milestone
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
Tearnote/Playnote#33
No description provided.