Can't seem to control dmx lights via lighting desk

2 questions

1: Q light software...

I have a Showtec Showmaster 24 which is a DMX controller with 24 channels. I have plugged it's MIDI input into my PC using a USB/MIDI cable. QLC picks up the MIDI connection and I have assigned the MIDI channel as 2. The light desk tells me how to set up the MIDI input channel which is done, it tells me how to set it to wait for download dumps from the PC.

When it is waiting, it expects a single byte value of 85 as the beginning of the data block followed by the filename DC1224.BIN followed by a space. Then a file dump follows.

Bytes 22 to 69, notes that switch on/off the 48 chasers. The velocity is the program master.

Bytes 70 to 93, notes activate channels 1 to 24. Velocity controls the intensity.

Anyway to finish off the scenario I also have 4 LED cans which match perfectly to the StarVille LED PAR 56 built in fixture in QLC.

Anyway, when I set the lighting desk to listen to MIDI channel 2, route the QLC output to MIDI 2 using note velocity mode, setup a set of sliders that are mapped to one of the cans DMX address nothing see开发者_Python百科ms to change when I raise or lower the slider for any colour.

Is there a plugin for this desk or is there a way to make it work?

---

Question 2:

---

Following on from QLC I am writing my own software with source for MIDI in/out control. So assuming that I can output to the lighting desk, send the same sequence - byte 85, the filename and space, what follows?

I have the standard MIDI API for lighting which I have browsed does every command sent to the desk follow the same header?

TIA

Andrew Sprott

---

I think you are misreading the manual. The one I found doesn't have anything about the format of the data dump. What you are calling byte numbers are actually MIDI note numbers. e.g. sending a MIDI Note On message with note number 22 will turn on or off program 1.

It's very unclear what they mean by:

During receiving and sending file dump, the controller will automatically search for or send Device ID of 55H (85), a file named DC1224 with an extension of "BIN (SPACE)".

The 55H would need to be preceded by some command, otherwise it's just a data byte whose meaning would depend on the most recent command byte.

If there isn't better documentation, the best way to figure out the data dump format will probably be to send it to your PC and look at it there. I'd suggest MIDI-OX. I used to use that a lot when I was supporting Windows.

---

It seems that the dump is actually done via SysEx. I suspect this, since they have given you a device ID, which is passed with SysEx data. It is also the standard way to do a dump like this.

As @SSTeve pointed out, you should use MIDI-OX to receive and look at this data.

It seems that the actual format isn't provided to you, but I bet it will be obvious when you look at the data returned.

---

OK, solved the problem, the solution is to use the following sequence of bytes as a header for each packet sent to the desk :

$55+'DC1224.BIN '

The filename is used by the desk for communicating with other desks when synchronising.

What follows is a MIDI show control message with note on, pitch and velocity parameters. The device id is whatever the connection is to the lighting desk, a usb/midi cable for example.

The note on instruction uses the midi channel as it's lower 4 bits. The pitch is the colour channel in the DMX universe added to the base 70 - 24 channels 70 to 93 - and the velocity is the intensity, but remember you need to scale it from 8 bits to 7, in other words, new_colour=old_colour/255*127.

But anyway, It works.