I'm processing Vuo clips in the latest beta VDMX and driving published parameters via OSC data.
I notice sometimes it appears VDMX does not process all the OSC data and sliders fail to move in VDMX. Other times its fine.
Some ports process data correctly and others fail to respond.
I checked the data coming out of the sending programme using a OSC Data Monitor tool and I can confirm the data is sent to the correct port and name space.
As a unit test I also created a version of the Vuo composition and added some nodes to process the OSC data directly and this works as expected.
I then added the clip into VDMX and processed the same data and the clip in VDMX doesn’t seem to process the OSC data as expected.
It would appear that VDMX has problems processing OSC data in Vuo composition, with a separate port for VDMX and Vuo. In Vuo V1.2.8 and the non beta version of VDMX worked ok with processing OSC data directly in Vuo and not via a published parameter.
It would also appear that VDMX has problems processing all OSC data values on occasions.
I have logged these with VDMX but also reaching out to the Vuo community to see if anyone has had any similar experiences as the suggestion from VDMX is it’s a Vuo issue and not a VDMX one.
The unit testing I did when processing directly in Vuo works as expected.