1. You have found a bug in the documentation. “size” is the number of bytes.
2. You could, I suppose, continue to use std::vector and friends, as long as
you use a custom allocator that uses AERT_Allocate under the hood. It’s very
important that all the calls to std::vector::push_back and friends happen
before streaming starts – you can’t call anything that might block in
APOProcess, or you will glitch, and memory allocation sometimes blocks.
From: wdmaudiodev-bounce@xxxxxxxxxxxxx <wdmaudiodev-bounce@xxxxxxxxxxxxx> on
behalf of Culann mac Cabe <culann@xxxxxxxxxx>
Sent: Wednesday, October 24, 2018 2:09:58 AM
Subject: [wdmaudiodev] AERT_Allocate "size" parameter & how to use AERT_x with
Hello wdmaudiodev people.
I am developing an APO and am doing some cleaning up work, including
implementing AERT_Allocate for all my memory allocation. I have a compound
1. The doc
defines the "size" parameter as " The number of input connections." Is this
correct? It seems to me to be incomplete, as in without other info (eg audio
sample data format) this can't evaluate to a byte size... so can someone please
clarify what this paremeter should really mean? (I'm guessing Bytes?)
2. I am currently using std:vector and std:queue for convenience to manage
IO buffering. Now that I am converting everything to use AERT_Allocate, can
someone please provide guidance/code snippet as to how I can use AERT_Allocate
in conjunction with eg std::vector - or do I have to revert to pure C arrays in