@neauoire I can write down the documentation for this, but there is no other uxn instance, it's the same, they use the same ram and zero page, it's just the stack that is added something like this:
// Stacks.
u8 wst[256];
u8 rst[256];
u8 *w;
u8 *r;
u8 wst_audio[256];
u8 rst_audio[256];
u8 *w_audio;
u8 *r_audio;
For avoiding data races, writing to ram or zero-page from the audio vector should be discouraged unless you implement some form of mutex
@bd This is kind of messy, it create device specific scaffolding in uxn, could we spawn a new uxn instead, and kill it at the end of the vector? It would have its own stacks, and device page, and share access to the RAM