MIDI to DMX issue, VERY ODD. MIDI triggering error, triggering opposite?

Hey,
I have a very odd problem even a professional lighting engineer was baffled by.
Here's what we're using: 3 Par 64 LED cans, in 5 channel slave DMX mode. 1 Chauvet Obey 40 controller (midi compatible). Apple Macbook running logic pro with a midi track synced to a click(metronome) track and backing/FX tracks.
The Problem: I have programmed the scenes on the Obey 40 to correspond to the midi notes from logic. Everything triggers fine when you click the keyboard keys in the logic control window. Everything seemed to work fine for the first few measures. After programming midi to an entire song (click/backing tracks) we noticed the lights would mis-trigger, doing the opposite of what has been commanded. So if we programmed two 4 count notes, the light would be off during the notes and flash on between notes. If we programmed an 8th note, the light would stay off for that 8th note and come on in the gap between notes. After much trial and error, I started programming the midi notes in reverse, where they were messing up, until those too starting triggering opposite of intended.

The lights and controller were purchased new, proper DMX channels have been assigned, we're using a dmx terminator and the lights work fine standalone and with the controller. The problem is from the computer to the controller. The only other thing I could think of is that we aren't using "3 pin DMX" cables, but regular "3 pin XLR" cables. Again, the lights work fine in standalone (one light as a master, the other two as slaves) or working with the controller. We have tried using a USB to Midi cable to connect to the controller, as well as a firewire to external digidesign hardware with midi to connect to the controller. They both had the same errors, although the latter seemed to run smoother.

Anybody else have this problem? Seen it? Heard of it?
Can you help us solve it?

Thanks,
In Search of Sight
 
I doubt the lights nor the board are the problem. The scenes and chases I've programmed into the Obey 40 run fine...the problem is with midi control, most likely computer to controller related

Thanks for the response, I'll try to head down to a music store and plug all of our stuff into a different controller.
 
Follow Up: Issue Resolved!

Well, we fixed the issue ourselves. First and most importantly, DMX cables are underrated! We also took the macbook into the genius' and had them re-format our computer and re-install Logic Pro. Another difference is we built our own midi tracks from scratch (apparently the first ones were converted midi tracks from the metronome track? Psh, Drummers...). We also noticed that you can't run your midi commands too close together or they'll mis-trigger/trigger opposite of intended. However, since switching to proper DMX cables, the mis-triggering will correct itself after a few more notes. We are able to get pretty quick scene changes, but you have to leave some space between the different midi commands(scenes) you're triggering. If the light your triggering is not doing so accurately, go back and adjust the space between the last two midi commands. Also, while building your show, if your lights stay on or trigger wrong, just tap the keys on the virtual midi keyboard a few times to reset the midi.

All in all, we have one hell of a light show synced to every song and it's quite impressive!
Hope this will help others who are having the same kind of issues.

Here's how we do it!
Macbook Pro running Logic. Logic handles the following: Sending a metronome(click) track to the drummer's headphones, sending samples and backing tracks to the house P.A. and sending usb to midi signal to the Chauvet Obey 40 which controls our lights.

Thanks everybody
 

Users who are viewing this thread

Back