can I supply my own buffer in remoteio render callback
can I supply my own buffer in remoteio render callback
- Subject: can I supply my own buffer in remoteio render callback
- From: 赵宇龙 <email@hidden>
- Date: Tue, 17 May 2011 10:56:40 +0800
typically, a render callback will like this:
static OSStatus PerformThru( void *inRefCon, AudioUnitRenderActionFlags *ioActionFlags, const AudioTimeStamp *inTimeStamp, UInt32 inBusNumber, UInt32 inNumberFrames, AudioBufferList *ioData) { AudioUnitRender(..., ioData); or memcpy(iodata->mBuffer[i].mData, ...);
}
both of them will perform a memory writing operation.
so can I avoid this write? for example:
iodata->mBuffer[i].mData = my_own_buffer; ?
the problem is I pass the my_own_buffer to framework, and I lose tracking of it: I don't know when to free it.
So, is there anyway to resolve this problem?
Br Zhao Yulong |
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden