Closed actondev closed 3 years ago
This can already be done by implementing your own caching layer above the data callback. The fixed_sized_buffer example will allow you to process audio data in fixed sizes (defined by a compile-time constant).
Thanks for the pointer! Had missed this.
In my application I'm using libpd (embedded puredata) and I want to use miniaudio for the audio in/out. Puredata is configured to process chunks of 64 frames at a time (in puredata lingo this is called
ticks
).As it is, in my
dataCallback
I'm writingframeCount - frameCount%/64
frames, resulting in bad audio (under pulseaudio)As I see it this situation could be solved be either
dataCallback
to which the users can write how many frames they actually wrote.