In the domain of lighting we prefer to use Sacn than Artnet.
Why? Coz Sacn protocol use multicast and Artnet broadcast or unicast.
So when i use Sacn with Touchdesigner i got this (see picture)
My desk send no informations but i have values coming from i don’t know where it comes from.
Its like a rabbit coming out from a hat and it does randomly.
If u have answers of what it’s happening, it will be wellcom.
Also are thex really comming in or do they just appear on startup?
Also, what fixtures did you patch in Nomad? Maybe there are some fixtures with homevalues different then 0 (pan tilt for example).
I hit the clear output and nothing hapend.
I put the rate at 40 and now its sending evrey values second.
alphamoonbase
In artnet no problem. but when i start Sacn its sending a value to 100 every second.
i put a normal dimmer, 1 channel connected to 1 address dmx (0-255)
What is the start codes?
Sadly I do not have my nomad license key with me right now. I will have a look when I’m in my office the next time!
Can you please post a picture of your path in nomad and also one screenshot of your ACN viewer in nomad?
Yeah this is a known problem with ETC stuff. You have to filter out all start codes but “0” aka replace the asterisk in the DMX In CHOP’s “Start Code” parameter with a zero.
The image you posted of the errant DMX packet shows that the start code is 221, which in hex is 0xDD.
If you look at the DMX alternate start codes in the DMX spec (on esta website TSP ) you can see that “DDh” (aka DD hex) is reserved for ETC’s “per channel priority” feature which only ETC stuff outputs, and nothing in ETC’s infrastructure even utilizes that functionality yet. There’s not even a way to set per channel priority in Nomad / Eos / Ion software as far as I know.
I think I gave a longer explanation on this forum post if you wanted more info:
@snaut I would actually recommend, if you can maybe in the next release, making the default start code on the DMXin CHOP be zero instead of asterisk as the vast majority of the time, people are only going to want DMX data (start code 0) and this is the only time a non-zero start code actually shows up in the wild (ETC stuff spitting out per-channel priority). I’ve been dealing with DMX for 20 years and have never seen any use of alternate start codes (aka anything other than zero) in the wild, and I don’t know anybody who has.
If the need for an alternate start code ever comes up, whoever needs it will be knowledgeable enough to know that they need an alternate start code and they can then change it to something other than zero.
@Peeet Thanks for that insight, we will definitely look into that change (might be not the next build, but soon)
Thanks a lot, it works!!!
Default start code = 0 in builds 2020.22150+
