Credits: Module based on: http://vvvv.org/contribution/interfacing-reaktor-vvvv-node15-workshop (thanks for sharing these files! I use a lot of resources directly from this contribution and it was really easy to get even when i was not present on the workshop) in combination with http://vvvv.org/contribution/vobjects
Modular, cable free system to send OSC messeages
DEATH TO CONS!
you need to have this:
in your packs folder in VVVV
Why should I want this?
First of all, reaktor is a great tool for sound, and when you want to build interface in vvvv that talks through UDP, it usually means a LOT of cables and cons nodes, this little module make them disappear, leaving you with modular system that does not needs cables, can access one OSC value from multiple places in VVVV just by using OSC name, and can be expanded with more functionality easily.
What is a Vobject?
Vobject is a system from microdee, that you always wanted in VVVV, but never knew about it. It could be system for distributing multiple S nodes to one R node, or it could be system for managing skeletons and other information from Kinect. These are just two examples and this module is built on the first one. This is a great place for learning Vobject, which has a huge pontential in data handling! (also featured on Emeshe, which was not yet featured in TV commercials unfortunately)
What is missing?
I took out few features out of first realease, specifically I found a way how to receive drum triggers from reaktor sequencer faster, when setting UDP to Spread queue mode. Its a bit tricky, I need to play a bit more with it so I know it really works. Right now the Discard mode is most accurate for knobs, faders, etc.
There are many possibilities what and how to control in Reaktor, particularly useful is snapshot switching, you can find that in original files from Reaktor workshop (link in credits).
I could have made the decision to distribute RAW data in VObject directly without changing it to string, but i did not (had some problems with crashing). This is probably more stable.
I have not tested this in huge application, but I am building a live performance on this system so updates are expected.
thought you will like it. I would like to expand this if you have any ideas bring them on! :)
thanks, it makes the life much easier,
microdee has changed how vojbects works (its a bit simpler now) so I had to update this little creature
Is this still supposed to work since microdee changed to VObject 2?
I get a lot of red objects (primitive objectm and formular)
not updated, I think messages have some example based around OSC, and would probably suggest try to look into them
@ofersmi: VObjects are a failed concept which were trying to do something vvvv was not designed for. messages are far superior alternative. if you'd need more fidelity you can utilise VL or even C# ;)
@stix and @microdee, thanks for the answers! I'll check messages... I wanted to get started with VL, but I still can't get my head around that. What would be the advantage of VL over messages? is it because its event based?
messages is a node pack for vvvv, VL is an entirely different and wider range programming language. judge for yourself
@microdee yes, I know now, I ment in respect to OSC reliability and timing...
but maybe I should just start a thread about this....
anonymous user login