A large part of my work is writing about and sharing the Vuo story. We believe there are all kinds of people who will embrace Vuo once they discover it’s out there. So, my efforts include helping create the Vuo website, writing press releases, submitting conference proposals and generally figuring out how to create excitement and how to spread the word about Vuo. I occasionally help out with Vuo e-mail support and I'm part of the think-tank called "Team Vuo."
When exactly the problem happens — when VDMX rapidly sends a series of changing parameters into several published input ports in a Vuo composition, such as when using LFOs.
It's unrelated to Vuo's Send/Receive OSC Messages nodes.
Why it happens — unnecessary work is being done in the communication between VDMX and Vuo.
Actions Team Vuo is taking — We will make communication on Vuo's end more efficient in the next Vuo release, and have contacted the VDMX developers to suggest how they can make it more efficient on their end.
Work around — Move the LFO performance into Vuo using Wave or Curve nodes. Then set up your published ports to select the Wave node, Curve node, or constant value you want to use. You can also used published ports to control the input values to the Wave or Curve nodes. I've included an example that runs at 60fps on my system.
We haven't tested the composition, but one of my colleagues suggested hooking up the time port. VDMX seems to work better when the width, height, and time ports are all connected to nodes in the composition. Generally, it's also not a good practice to use nodes that create their own events within an image generator composition. So, you can use a cable from the time port to an "Allow First Event" node, where the output event would then go to the "Make Wireframe Shader" and perhaps the "Make 3D Point" nodes. Let us know if that helps.