This is my first attempt at a cplusplus CHOP for the Enttec DMX usb pro. The .zip attached containes the enttec.dll + a .toe with some sliders attached to channels. Just enter the desired channel number and use the slider to set the value. It won’t work in FTE because it’s cplusplus.
Let me know if it works for you.
enttec.dll deets.
CHOP inputs
Input 1 = DMX channels (limit of 512)
Input 2 = DMX values (corresponding to the DMX channels)
floats page (first row)
value 1 = the device number (usually 0)
value 2 = turn the device on and off (there should be a little pause when you turn it on) enttec_dmx_usb_pro_touch.zip (29.4 KB)
Just updated a few things to make it way less buggy.
It’s all the same except you currently need to specify how many channels you are sending.
warning: If you specifiy more channels than you are actually sending then it will crash.
CHOP inputs
Input 1 = DMX channels (limit of 512)
Input 2 = DMX values (corresponding to the DMX channels)
floats page (1st row)
value 1 = the device number (usually 0)
value 2 = turn the device on and off (there should be a little pause when you turn it on)
floats page (2nd row)
value 1 = the number of channels you are sending.
In the cplusplus1 node, the dll path points to a file called “CPlusPlusCHOPExample.dll”, But there is only one dll file in the attached zip called “enttec_v1.dll”.
If i change it to the “enttec_v1.dll”, touch says “the program cant start because MSVCR100D.dll is missing from your system…” and the cplusplus1 node says “failed to load dll file”.
While I don’t want to take away from any of the hard work Adam has done here, there is a little easter egg for you guys in the latest experimental build 17220. I recommend you guys try the new DMX In and Out CHOPs! They were implemented using Enttec USB Pro boxes, so anyone who has these boxes we appreciate hearing your feedback.
Please note that we haven’t officially announced these additions yet since they are in the development and testing stage. Report any issues you have with them with the understanding that these CHOPs are still being tested and may change at any time. We can’t guarantee support turnaround time at this stage either.
Tada!
Works like a charm!
Some delay with the input node, maybe on the out too, I will check the performance window later.
And i also tried the Artnet setting with great results.
Wow that was fast. Nice to hear.
You can try reducing the ‘queue size’ in the DMX In CHOP to see if that helps with the latency.
It may produce slightly jaggier ramps though.
We still need to address buffering and smoothing of the data in future releases.
Make sure you’re using the default ‘FTDI Serial’ interface on both DMX In + Out,
and not ‘Generic Serial’.
Hi.
From what I understand the ip address is derived from the Universe/Net/Subnet addresses parameters, which you can modify.
The CHOP simply broadcasts messages with this address encoded in the message.
