Yes, we are working on a fix for this…
Great. Thanks for keeping me updated.
FYI, this seemed to work in version 4.3. My current app shows a native buffer of 240, an active one of 1440, yet runs without any glitches.
OK. A fix for this is now on develop with commit 0fae934.
This commit now checks if Sapa is supported and takes this as an indication that it supports realtime audio (“Pro Audio”). If it is a Pro Audio device, it now makes sure that it will always use the realtime audio priority thread if the sample rate matches the native sample rate (the default sample rate).
1 Like
Oh, wow, that was fast!
I can’t thank you enough for your time and efforts to solve this. Great support!