Remove requirement for application side double-buffering
At one time it was thought that application side double-buffering was
required for fast tracks to work reliably. It now appears that this
was overly conservative, and that fast tracks work just fine with
single buffers on application side. This is because the moment after
FastMixer pulls the data from the fast track, it synchronously signals
the application's callback thread to wake up, which will then run the
buffer completion callback handler to re-fill the buffer. So disabling
this check now.
Bug: 9276275
Change-Id: I2c74a8c6d752140ccc7d285c5c5c1f7fcd792650
diff --git a/src/android/AudioPlayer_to_android.cpp b/src/android/AudioPlayer_to_android.cpp
index 43a9353..d72cf4b 100644
--- a/src/android/AudioPlayer_to_android.cpp
+++ b/src/android/AudioPlayer_to_android.cpp
@@ -1332,9 +1332,9 @@
static bool canUseFastTrack(CAudioPlayer *pAudioPlayer)
{
assert(pAudioPlayer->mAndroidObjType == AUDIOPLAYER_FROM_PCM_BUFFERQUEUE);
- if (pAudioPlayer->mBufferQueue.mNumBuffers < 2) {
- return false;
- }
+
+ // no need to check the buffer queue size, application side
+ // double-buffering (and more) is not a requirement for using fast tracks
// Check a blacklist of interfaces that are incompatible with fast tracks.
// The alternative, to check a whitelist of compatible interfaces, is
