Random Glitches in DMX Output
Posted: Tue Sep 10, 2013 12:02 pm
Using both the most recent Official Release of Suite 2, and the September Beta release I get random glitches in the DMX Output. I have a few Elation Event Bar's connected. The Event Bars have four pin spot moving heads. Every 5-10 seconds or so they rapidly move from their set position, and then move right back again. The movement lasts less than a second or so.
I don't believe it's a drop of the DMX signal, because I have the units set to remain in their last known state in the event of a signal loss. So for them to move randomly, the controller must be sending information to do so.
I'm using a laptop with Windows 8 on it. I noticed this at my first event using Suite 2, where the laptop was connected to DJ hardware too. So I brought it in and connected a single Event Bar, with no other USB devices hooked up, no other software running, etc. The glitch still happens. I guess the good news is that it rules out lots of cables and other possible issues, and means the problem is repeatable.
Bad news is, I have no clue how to fix it. Does anyone know if this is a known bug that's being addressed. Or could I have a defective hardware unit?
I'm going to try a few more tests, like using another computer, different OS, etc. But if you see this and know more I'd appreciate any help.
Thanks.
I don't believe it's a drop of the DMX signal, because I have the units set to remain in their last known state in the event of a signal loss. So for them to move randomly, the controller must be sending information to do so.
I'm using a laptop with Windows 8 on it. I noticed this at my first event using Suite 2, where the laptop was connected to DJ hardware too. So I brought it in and connected a single Event Bar, with no other USB devices hooked up, no other software running, etc. The glitch still happens. I guess the good news is that it rules out lots of cables and other possible issues, and means the problem is repeatable.
Bad news is, I have no clue how to fix it. Does anyone know if this is a known bug that's being addressed. Or could I have a defective hardware unit?
I'm going to try a few more tests, like using another computer, different OS, etc. But if you see this and know more I'd appreciate any help.
Thanks.