16-bit mono plays at wrong rate about oboe HOT 2 CLOSED

Additional note: I am using a mutex in my audio callback. I lock it, read from a stream, then unlock. In the main thread, the mutex is locked, data is copied into the stream, and then it's unlocked. Time spent with the mutex locked in either thread (the main thread or the audio callback thread) is extremely minimal (i.e., as tight as I can make it.) All the same, is this bad? Is it bad because a mutex can "preempt" a thread? Does that mean, if the mutex blocks, the thread schedular will let some other thread run (for well over the time limit the audio callback had) before getting back to it?

I could try switching over to a lock-free queue and try that. However, this doesn't sound (pun intended) like a latency problem, because the audio is not being interrupted. It's just playing in slow motion. Or could slow-motion audio playback also be a symptom of using mutexes in the audio callback?

from oboe.

Never mind. I fixed the bug, and it was in my code. The audio now plays as expected.

from oboe.