VVVV.Audio icon indicating copy to clipboard operation
VVVV.Audio copied to clipboard

rethinking buffers

Open zeos opened this issue 5 years ago • 0 comments

Hey, VAudio freaks!

How about rethinking the concept of Buffers in VAudio, in a way that is closer to the Supercollider's Buffers and the related UGens (PlayBuf, BufRd, BufWr, OSC, BufGrain....)?

For example: Filestream, Wavetable, Granulator etc. should be taking a Buffer for their audio input argument, instead of a Filename.

Buffers can be loaded from a file or an audio signal can be sent to them or spread of values can be simply written at once.... (I know there is an issue already on that) I think there is a lot in common between V4 and SC, mainly about the channels expansion concept and the node graph structure strategy of execution, just an idea, may be there is something there... Also sometimes there are duplicate pins (Audiorate and V4(frame) rate), this is not very coherent. I know there are ton of things also that are different from SC, however, the test of the time related to SC, shows that it is really a great language and fantastic concept for Audio-Programming, may be we can learn from it, instead of re-inventing the vaudio concept from scratch.

-- I found myself in the past 3-4 years doing SC more and more and linking it with V4 over OSC, sometimes I really wonder, why I can't just stay in V4, VAudio is so close to something I can really use for more experimental sound synthesis and processing, and not only for routing audio signals and using VST-s... however, sample interpolation, buffers, noise generators, triggers.... and some other fundamental nodes (UGens) are crucial to get there...

http://doc.sccode.org/Classes/Buffer.html

Your thoughts on that? Do you have any experience with SC? If not, take a look at it, it is fantastic

best, --zeos

zeos avatar Feb 07 '19 13:02 zeos