InSearchOfSight
Member
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 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