Who tonfilm
When Sun, Jun 19th 2016 - 19:00 until Sun, Jun 19th 2016 - 21:00
vveekend vvorkshops is back again next Sunday with tonfilm introducing VVVV.Audio ;) So forget max/msp or even worse puredata, and learn how to use a fully capable audio pipeline right in vvvv!
Join us at 19. June 5PM CEST at https://youtu.be/I2nnyRkbllo
Subscribe to the vveekend vvorkshops channel to get direct updates: https://www.youtube.com/c/vveekendvvorkshops
anonymous user login
~13h ago
~13h ago
~1d ago
~3d ago
~14d ago
~23d ago
~28d ago
~1mth ago
~1mth ago
~1mth ago
Shortly after I wrote the article tonfilm noted he needs to postpone the workshop. So this sunday 5PM CEST we will dive into vpm, the new way of installing packs. see'y'all! https://youtu.be/85dqOxb6JcE
Thank you tonfilm and microdee for organizing!
Unfortunately I haven't been able to keep up with Vaudio but this was a good overview of the current state.
One design issue I have is having playback state (bpm/play/loop etc) be part of the same node as the audio driver and shared across the audio graph.
While the current design will probably be enough to satisfy a lot of people I think audio in vvvv should be free from such restrictions as having one global clock/timing state. One solution might be to keep the settings in the AudioEngine node but as a master/default clock, then for all nodes that rely on the timer/bpm/etc add an optional timer override pin that allows you to use multiple timers/playback states/BPMs.