Qlab & Lanbox MIDI Show Control Help

[thestratocaster]

Hello,

 

I am trying to run my lighting desk via MSC.

 

My lighting desk is a Lanbox Lcx, running LCEdit software.

 

I have connected MIDI cables IN and OUT via usb to my Mac.

 

My Lanbox is connected via USB, and running the lights via DMX.

 

When I run a MSC cue via Qlab, I get no response from the Lanbox. The settings I am using are as follows:

 

Qlab (pro version)

 

Patch 1 - USB MIDI port 1

Patch 2 - USB MIDI port 2

 

LCEdit:

 

ID: A, MSC: 1

 

Any ideas on what im doing wrong? Screenshots below

 

 

 

http://s23.postimg.org/9np583wzb/Screen_Shot_2013_04_12_at_6_49_18_PM.png

 

http://s23.postimg.org/yi8n26htj/Screen_Shot_2013_04_12_at_6_49_51_PM.png

 

http://s23.postimg.org/ls4ep39vb/Screen_Shot_2013_04_12_at_6_50_10_PM.png

 

cheers

 

Kim

[alistermorton]

In the second shot the device ID is 0, but in the third it's A - I'd guess that is the problem. Change the device ID to A in the Go command?

[s0600204]

Change the device ID to A in the Go command?

Technically' date=' "A" is not a valid value for a Device ID (it must be numerical 'tween 0 and (if memory serves) 63). Typing "A" (or any other non-numerical value) into QLab in this input field will result in QLab rejecting it and replacing it with "0". That said, alister, I do believe you're onto something.

 

Kim, if you hover your cursor over the box captioned "MSC" in LCEdit, I believe you may get a popup that tells us that [I']this[/I] is the MSC Device ID that the "layer" will respond to. (The "ID" field here is apparently the name of the layer.) So could you try doing what alister suggests, but changing the "Device ID" field within QLab to "1" instead of "A" or "0"?

 

After that, I'd think it would be a case of determining the cuelist and cue number. From screenshot 3, it appears you're in cuelist 21 and you don't appear to have a cue 1.1 in that list.

 

Hope this helps.

[alistermorton]

Technically, "A" is not a valid value for a Device ID (it must be numerical 'tween 0 and (if memory serves) 63).

 

So used to thinking ion hex for device id's.

 

 

That's my excuse and I'm sticking to it ;-)