First off, thanks to RJ and everyone else who has contributed their time and effort to designing all of this. You're much smarter than I am, and give a tip of the ol' hat to all for your hard work.
For the last 4 years, I've used a couple Firegod (128 ch) controllers. I didn't want to re-sequence everything, so I added the ETD in Vixen starting at Ch 257. A DMX universe for the Freestyle (512 ch), and that left the pixels starting at ch 769 (128+128+512). The ETD plug-in is set to start at 257 to 4352. Hub is set to DMX and Pixelnet 1
Here's the problem: No matter what the Vixen plug-in start channel is set to, it appears the ETD wants to start at Channel 1. I couldn't figure out why the pixels were acting strangely, and finally deduced that the SSC's were programed 256 channels too high. If the SSC was supposed to start at 1000, it had to be programmed to start at ch 744. I changed the start/stop addresses in the Vixen plug-in, but it made no difference. The ETD still started at channel 1. I can't tell if the FG data is getting hosed. It's still in the attic.
I know, you'll say "Just program the SSC's 256 lower!". That's not the right way to do it, and sets-up channel conflicts in Vixen, which is a recipe for disaster.
Can anyone verify this condition? Any fixes?