Understanding AudioTrack Assertion in Android

Question

In my Android app, I\'m using the AudioTrack API to output audio bytes that I receive from a RFCOMM Bluetooth connection. The audio plays as expected and is very clear. Howe

Answer 1

Make AudioTrack buffer size the same you get from minBufferSize. That could fix your issue.

Answer 2

Hidden Bug

The error is not directly related to the audioBuffer size vs. minBufferSize. Assuming that these two must be identical is an API misunderstanding, if not misuse. (†)

The reason behind this apparent fix is that having identical sizes ensures that the audioBuffer is copied in full during mAudioPlayer.write(audioBuffer, 0, audioBuffer.length), each time, every time.

The actual reason for the crash is that audioBuffer, when larger than minBufferSize, may not have been copied in full, then discarded before mAudioPlayer.write(audioBuffer, 0, audioBuffer.length) had a chance to complete.

Solutions

• Check audioBuffer allocations and deallocations
• In a multi-threaded or async environment, ensure that audioBuffer has been consumed in between allocations.

(†)

1. AudioTrack buffer size > audioBuffer size:
   you may have many small packets arriving irregularly and can take advantage of the AudioTrack buffering system to compensate for these irregularities

2. AudioTrack buffer size == audioBuffer size:
   1 to 1 match ; mAudioPlayer.write is pretty much guaranteed to have copied audioBuffer exactly into AudioTrack buffer when returning

3. AudioTrack buffer size < audioBuffer size:
   the track will iterate through the audioBuffer as needed ; audioBuffer life cycle better lasts long enough

In all cases, audioBuffer must remain allocated until consumed, and a new buffer presented to mAudioPlayer.write before it runs out of data to avoid gaps in playback.