We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
onAudioReady()
I found modules/juce_audio_devices/native/juce_Oboe_android.cpp involves pthread_mutex_lock(), which is not realtime safe:
modules/juce_audio_devices/native/juce_Oboe_android.cpp
pthread_mutex_lock()
JUCE/modules/juce_audio_devices/native/juce_Oboe_android.cpp
Line 1367 in db60c1d
Some folks are facing weird Oboe audio latency problem with tracktion_engine. Probably this is the cause of the issue.
Oboe driver should not involve mutex lock (at least the default Bionic libc implementation is no-go).
Android
Android 14 (any version after Android 8.0 should be affected)
x86_64, ARM, 64-bit, 32-bit
No response
develop
The bug is present on the develop branch
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Detailed steps on how to reproduce the bug
I found
modules/juce_audio_devices/native/juce_Oboe_android.cpp
involvespthread_mutex_lock()
, which is not realtime safe:JUCE/modules/juce_audio_devices/native/juce_Oboe_android.cpp
Line 1367 in db60c1d
Some folks are facing weird Oboe audio latency problem with tracktion_engine. Probably this is the cause of the issue.
What is the expected behaviour?
Oboe driver should not involve mutex lock (at least the default Bionic libc implementation is no-go).
Operating systems
Android
What versions of the operating systems?
Android 14 (any version after Android 8.0 should be affected)
Architectures
x86_64, ARM, 64-bit, 32-bit
Stacktrace
No response
Plug-in formats (if applicable)
No response
Plug-in host applications (DAWs) (if applicable)
No response
Testing on the
develop
branchThe bug is present on the
develop
branchCode of Conduct
The text was updated successfully, but these errors were encountered: