MIDI commands to DMX problems

Anakin

Dear Peter,

I'm trying to automate my stage lights, using the DOREMIDI MTD-1024 device, which converts MIDI signals to DMX.
I then incorporated the MIDI commands to send to the lights into the lyrics and individually they all work.
The problem is when I press play. If I send too many commands in close succession (with timesync), such as turning some pars on and off on a quick drum cut, some of the lights execute the command, others leave it out, or execute it partially. I saw that something changes if I change the buffering (but it doesn't solve the problem).
Could it be a Mac memory problem? I'll paste the commands below, where you can see the timesync. These are commands given to 2 types of lights, on 2 different MIDI channels:

[midi@01:56.97: CC1.127@1, CC2.0@1, CC3.0@1, CC4.0@1, CC5.0@1, CC6.0@1, CC7.0@1, CC8.127@1]
[midi@01:57.07: CC1.0@1, CC2.0@1, CC3.0@1, CC4.0@1, CC5.0@1, CC6.0@1, CC7.0@1, CC8.0@1]
[midi@01:56.97: CC1.0@2, CC2.0@21, CC3.0@2, CC4.35@2, CC5.0@2, CC6.0@2, CC7.127@2]
[midi@01:57.07: CC1.0@2, CC2.0@21, CC3.0@2, CC4.0@2, CC5.0@2, CC6.0@2, CC7.0@2]

[midi@01:58.79: CC1.127@1, CC2.0@1, CC3.0@1, CC4.0@1, CC5.0@1, CC6.0@1, CC7.0@1, CC8.127@1]
[midi@01:58.90: CC1.0@1, CC2.0@1, CC3.0@1, CC4.0@1, CC5.0@1, CC6.0@1, CC7.0@1, CC8.0@1]
[midi@01:58:79: CC1.0@2, CC2.0@21, CC3.0@2, CC4.35@2, CC5.0@2, CC6.0@2, CC7.127@2]
[midi@01:58:90: CC1.0@2, CC2.0@21, CC3.0@2, CC4.0@2, CC5.0@2, CC6.0@2, CC7.0@2]

[midi@01:59.07: CC1.127@1, CC2.0@1, CC3.0@1, CC4.0@1, CC5.0@1, CC6.0@1, CC7.0@1, CC8.127@1]
[midi@01:59.18: CC1.0@1, CC2.0@1, CC3.0@1, CC4.0@1, CC5.0@1, CC6.0@1, CC7.0@1, CC8.0@1]
[midi@01:59:07: CC1.0@2, CC2.0@21, CC3.0@2, CC4.35@2, CC5.0@2, CC6.0@2, CC7.127@2]
[midi@01:59:18: CC1.0@2, CC2.0@21, CC3.0@2, CC4.0@2, CC5.0@2, CC6.0@2, CC7.0@2]

[midi@02:00:82: CC1.127@1, CC2.0@1, CC3.0@1, CC4.0@1, CC5.0@1, CC6.0@1, CC7.0@1, CC8.127@1]
[midi@02:00.93: CC1.0@1, CC2.0@1, CC3.0@1, CC4.0@1, CC5.0@1, CC6.0@1, CC7.0@1, CC8.0@1]
[midi@02:00:82: CC1.0@2, CC2.0@21, CC3.0@2, CC4.35@2, CC5.0@2, CC6.0@2, CC7.127@2]
[midi@02:00:93: CC1.0@2, CC2.0@21, CC3.0@2, CC4.0@2, CC5.0@2, CC6.0@2, CC7.0@2]

[midi@02:01:12: CC1.127@1, CC2.0@1, CC3.0@1, CC4.0@1, CC5.0@1, CC6.0@1, CC7.0@1, CC8.127@1]
[midi@02:01:23: CC1.0@1, CC2.0@1, CC3.0@1, CC4.0@1, CC5.0@1, CC6.0@1, CC7.0@1, CC8.0@1]
[midi@02:01:12: CC1.0@2, CC2.0@21, CC3.0@2, CC4.35@2, CC5.0@2, CC6.0@2, CC7.127@2]
[midi@02:01:23: CC1.0@2, CC2.0@21, CC3.0@2, CC4.0@2, CC5.0@2, CC6.0@2, CC7.0@2]

[midi@02:02:97: CC1.127@1, CC2.0@1, CC3.0@1, CC4.0@1, CC5.0@1, CC6.0@1, CC7.0@1, CC8.127@1]
[midi@02:03:08: CC1.0@1, CC2.0@1, CC3.0@1, CC4.0@1, CC5.0@1, CC6.0@1, CC7.0@1, CC8.0@1]
[midi@02:02:97 CC1.0@2, CC2.0@21, CC3.0@2, CC4.35@2, CC5.0@2, CC6.0@2, CC7.127@2]
[midi@02:03:08: CC1.0@2, CC2.0@21, CC3.0@2, CC4.0@2, CC5.0@2, CC6.0@2, CC7.0@2]

[midi@02:03:29: CC1.127@1, CC2.0@1, CC3.0@1, CC4.0@1, CC5.0@1, CC6.0@1, CC7.0@1, CC8.127@1]
[midi@02:03:40: CC1.0@1, CC2.0@1, CC3.0@1, CC4.0@1, CC5.0@1, CC6.0@1, CC7.0@1, CC8.0@1]
[midi@02:03:29: CC1.0@2, CC2.0@21, CC3.0@2, CC4.35@2, CC5.0@2, CC6.0@2, CC7.127@2]
[midi@02:03:40: CC1.0@2, CC2.0@21, CC3.0@2, CC4.0@2, CC5.0@2, CC6.0@2, CC7.0@2]

[midi@02:05:05: CC1.127@1, CC2.0@1, CC3.0@1, CC4.0@1, CC5.0@1, CC6.0@1, CC7.0@1, CC8.127@1]
[midi@02:05:16: CC1.0@1, CC2.0@1, CC3.0@1, CC4.0@1, CC5.0@1, CC6.0@1, CC7.0@1, CC8.0@1]
[midi@02:05:05: CC1.0@2, CC2.0@21, CC3.0@2, CC4.35@2, CC5.0@2, CC6.0@2, CC7.127@2]
[midi@02:05:16: CC1.0@2, CC2.0@21, CC3.0@2, CC4.0@2, CC5.0@2, CC6.0@2, CC7.0@2]

Thank you for your help,
Marco

Lishy

Anakin you say they’re sent to 2 midi channels but can see @‘s for channels 1, 2 and 21 in your syntax? Midi only has 16 channels too…

Anakin

Lishy hi Lishy, you are right. I wrote 21 instead of 2.
Tonight I will correct that wrong number and see if everything will work.. I will let you know.

Thank you

peter

The syntax seems correct. It is possible that the receiver is overwhelmed with the number of commands it receives directly one after the other. We have seen these problems with some guitar pedals that just skip some commands when sent directly one after the other.

In your case I would do the light programming differently. You do the programming in ST3 which is very uncomfortable, error prone and hard to change if you want to change something. Instead setup different light scenes in your DMX controller app (or hardware) and use midi only to trigger the preprogrammed scenes.

Anakin

peter Thank you.

Do you have some suggestions?

I would like to have an app or a hardware capable of recording light shows of an sentire song. In that manner I would only trigger a show from ST3 and sync them with music..

Lishy

Anakin I used to use the adj operator 384 and created my lighting scenes on the there and triggered it via Bluetooth midi from ST3.
I also bought the doremidi device you have but it didn’t seemed to be able to do what I wanted it to so I sent it back. I’m currently in the process of setting up my lighting scenes using the photon 2 app so I can get rid of the dmx controller which was limited in what it could do midi wise. With the app I can use an expression pedal to fade the lights in and out manually when needed.

peter

No, I run all my lights in standalone mode. Setting up the wiring for lighting takes up too much time. I have switched over to ApeLights which have some excellent sound to light synchronized over wifi so that all lights run in sync and the rest is static lighting.

Anakin

Lishy Thank you Lishy.
Now doremidi has a firmware update for adding fading..

But I will follow your advices.. I will update this thread.

Thank you