Home/ Questions/Q 6555263
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-25T12:47:54+00:00

I use Audio Queue Services in my application. When allocating the buffer, I set

  • 0

I use Audio Queue Services in my application. When allocating the buffer, I set the buffer size to 30000 samples:

AudioQueueAllocateBuffer(mQueue, 30000, &mBuffers[i]);

But the subsequent calls of the callback are made with the following inNumberPacketDescriptions:

30000
30000
30000
26928
30000
30000

They aren’t always equal to 30000. Why?

Record format configuration (using CAStreamBasicDescription):

mRecordFormat.mSampleRate = kSampleRate;    
mRecordFormat.mChannelsPerFrame = 1;
mRecordFormat.mFormatID = kAudioFormatLinearPCM;
mRecordFormat.mFormatFlags = kLinearPCMFormatFlagIsSignedInteger | kLinearPCMFormatFlagIsPacked;
mRecordFormat.mBitsPerChannel = 16;
mRecordFormat.mBytesPerPacket = mRecordFormat.mBytesPerFrame = (mRecordFormat.mBitsPerChannel / 8) * mRecordFormat.mChannelsPerFrame;
mRecordFormat.mFramesPerPacket = 1;

3 buffers are used.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Edit: I’ve seen iOS freak out and spontaneously change buffer sizes when presented with a non-power-of-two audio buffer. (Another SO question references this) Anyway,

    30000 is

    (a) a HUGE buffer size, and

    (b) a weird number to use for a buffer. Usually they’re in powers of 2— i.e. *=2 from 64, i.e. 64, 128, 256, 512, 1024, 2048, 4096. I’ve never seen one higher than 4096, and I do a lot of audio work.

    If you have a specialized reason to use unusually-large buffers, you could use a nextPowerOfTwo convenience function or just hard-code the math yourself.

    • 0