Replies: 4 comments 16 replies
-
What version of miniaudio are you using at the moment? I am so sure I fixed that assert. Maybe there's still an edge case there that I missed... If you're not using the latest version, can you update and try again? |
Beta Was this translation helpful? Give feedback.
-
I can confirm that the latest version I understand this is vague description of a problem, but was there anything updated around |
Beta Was this translation helpful? Give feedback.
-
Here's the debug output:
|
Beta Was this translation helpful? Give feedback.
-
I just tested v0.11.12 and the same timing problem is there. This is the version where the output change crash issue was fixed so I can't even just stick to that version and have solid timing and no crashes when changing output. On the Samsung A10s, I tested v0.11.12 and immediately after went back to v.0.11.11 and it's like night and day. v.0.11.11 has the solid playback timing. |
Beta Was this translation helpful? Give feedback.
-
With the audio engine running, unplugging or plugging in headphones on Android devices causes miniaudio to crash. I think that Android sends a message when audio sources change: https://developer.android.com/reference/android/media/AudioManager#ACTION_AUDIO_BECOMING_NOISY, but that's using the Java-based audioManager.
As seen in the logs below, miniaudio crashes because an assertion has failed, I guess the pInputChache ends up pointing to an invalid memory location:
Is there a best practice in dealing with this on Android AAudio? On iOS, this problem does not occur.
Plugging in:
Unplugging
Beta Was this translation helpful? Give feedback.
All reactions