I have set up a pretty basic HUE Checkerboard composition to run in VDMX and it is reacting very slowly when loaded into a layer.
I built the test comp after Jaymie’s example: https://community.vuo.org/t/-/5061
When I drag the slider around the hue reacts slowly and is choppy.
When I create an audio analysis plugin, it runs fine without the Vuo comp loaded, but when I load the Vuo comp, I can see the audio reactivity peaks also getting choppy / freezing etc.
Running 2011 MBP 16GB Ram, SSD drive…
Has been pretty good running visuals before!
Running at 720p
Edit: When I run the comp in Vuo itself, and play with the HUE slider in the Protocol-Input area, it runs smooth and awesome :)
Edit Edit: When I run a regular, and much more advanced Quartz.qtz patch it also runs flawlessly / as expected.
As well, I have tried with “Run Vuo files in Separate Processes?” both checked and unchecked (and after restarting VDMX).
The .vuo file has been tested both installed on the same drive,- SSD, in Documents/Vuo Projects/
As well as on a 2nd internal HDD, in Documents/Vuo Projects/
When I connect the Audio Freq 1 Data Source to the HUE Slider, the lag seems to become intermittent, rather than constant; I can snap fingers and see the Frequency Visualizer, Slider and hue itself in the output all change gracefully, but they still lag/lock up, every two seconds or so.
When the Freq Visualizer and Hue ‘output’ lock up, the Slider still remains fluid; this leads me to believe it’s something in the graphical output locking up, despite all the info and inner-workings still functioning? And by that I mean, I really still have no idea ;)
Ok ! @jstrecker thank you! I think you’ve solved something larger here :)
Your comp with the Twirl node worked great. So that got me looking at the differences: Time input.
I guess without having Time input driving a node (in my original comp) in the Image Generator, it isn’t constantly listening, so it seems.
I created a new Comp, replacing the Multiply with a Subtract node that just subtracts Time from itself (because I don’t want to have a Twirl effect all the time ;)
Attached comp for reference.
Let me know if you think there is a great issue here with VDMX or how Vuo comps are run- I wouldn’t think I should Have to input Time in order to get updates every frame, but it seems like something is up to that effect.
Also this isn’t the place for it, but when I ‘Add new comment’ to reply in these forums, it would be great to see the previous replies to better make reference to them :)
[mstjean] I guess without having Time input driving a node (in my original comp) in the Image Generator, it isn’t constantly listening, so it seems.
[me] Not sure what’s going on here. There should be events coming in through all published input ports, not just time.
Oh! The “event into any published input goes through all” behavior was added in Vuo 1.2. VDMX is still using Vuo 1.1. Presumably VDMX is only sending events regularly through the time port. For now, you can work around it by hooking up an event-only cable from the time port to the nodes that need events.
To save me some potential time, can you clarify what you mean by event-only cable? If my comp is, as above, just “Make HSL Color” → “Make Checkerboard Image” nodes, where would I send time? Should I cancel it out with a Subtract node and send to the Center input on “Make Checkerboard Image”, for example?
Thanks. Hopefully the awesome lads at Vidvox will implement 1.2 soon!
Event-only cables are the thin cables. They don’t carry any data, so there’s nothing you have to cancel out. You can draw one by connecting a cable to a triangular (event-only) port, as in the composition below, or by holding down Option while dragging a cable.