Just fixed up the node as per your request. Please let me know if I have missed out something for next time, as I am still in a process of learning.
Personally I would like to only zero buffer if we need, but you suggested to make it mandatory. (I changed it to have it within the channel loop- but changed it back again). When you change the audio port functionality from retain to clear maybe we should have a look at it. Also zero-ing the buffer uses the size of default buffer (as there are no samples to get their buffer size).
Also all of the default audio headers are in the .pro file- but in the submission documentation you only want .c
I Alexander Mitchell understand and agree to the Vuo Contributor Agreement, and I intend for this code to be integrated into Vuo.
audiobuffer (set in Milliseconds- but converts that value to the nearest multiple of the blocksize)
blocksize (typically set to 64 samples)
The audiobuffer multiplies the blocksize buffer to accommodate system I/O, so the blocksize is the internal audio buffer size set typically to 64 samples.
This allows greater accuracy when control rate operations are interlacing with audio nodes. Such as controlling volume from midi slider etc. Currently Vuo's audiobuffer runs at 512 samples- and only allows maximum accuracy of 93.75 control events per second. It would be fantastic for Vuo to use this dual buffer approach to improve audio control accuracy. Settings for buffers can also be published in preference menu.
EDIT: fixed explanation about blocksize v's buffers to correct explanation that Steve mentioned below- otherwise confusing.
