QLab+MSC+Lanbox LCX

[Erik Rietman]

So I'm struggling with sending a Go cue from Qlab by MSC to my Lanbox LCX. I've checked everything; Midi-channels, device-ID's etc. But I can't manage to get it work.

If I send a program change trigger to my Lanbox it will work. But with this I'm not able to fire a specific que step...

Anyone any ideas?

De inhoud van dit bericht is alleen bestemd voor de geadresseerde en kan vertrouwelijke of persoonlijke informatie bevatten. Als u dit bericht onbedoeld heeft ontvangen verzoeken wij u het te vernietigen en de afzender te informeren. Het is niet toegestaan om een bericht dat niet voor u bestemd is te vermenigvuldigen dan wel te verspreiden. Aan dit bericht inclusief de bijlagen kunnen geen rechten ontleend worden, tenzij schriftelijk anders wordt overeengekomen. De Leercompany aanvaardt geen enkele aansprakelijkheid voor schade en/of kosten die voortvloeien uit onvolledige en/of foutieve informatie in e-mailberichten.

[Frédéric]

Hi Erik,

First of all do you see the midi-recieve led (on the lanbox) flash when firing a Q-lab MSC-cue?

This is to know if your problem is "hardware"-midi related or MSC-related...

F

Op zondag 25 januari 2015 20:58:23 UTC+1 schreef Erik Rietman:

[Sander Loonen]

Hi Eric, 

I have succeeded in doing this many time, but I always forget how the settings are in Q-lab.

play around with he Device ID (maybe the 0 in Lanbox is 1 in Qlab)

or with the Q-path and stuff..

once it runs it is steady as a rock though….

grt

Sander

--
--
Change your preferences or unsubscribe here:
http://groups.google.com/group/qlab
 
Follow Figure 53 on Twitter: http://twitter.com/Figure53

---
You received this message because you are subscribed to the Google Groups "QLab" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qlab+uns...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
<Qlab.png>

[Erik Rietman]

Tried several things. When firing a MSC command to the lanbox the midi led flashes. I also can control it with a program change trigger

Do I have to fill in all the  msc boxes? (q Number, Q List, Q Path) 

Erik

[craig k]

You shouldn't need to have all boxes filled, I would even try just the cue number and see if that gets through. But it looks like you are assigning MSC id 0 to you LCX, and QLab (I believe) defaults to MSC id 0 as well. This could cause some conflict maybe?

A couple of thoughts from a first look.

Craig K.

[Samuel Thériault]

Hi,

I use this and this is how it's work for me.

Midi Cue: Select your device and Message type : MSC

I Use Commande Format: Lighting (but I think it's don't change anything)

Command: Go

Device ID: 1 (this setting is also a setting in your lanbox on the layer advance option I think)

Q Number: cuelist-number.cue-number (ex: I want to fire the cue 60 on the cue list 100. Q number = 111.90

Q List and Q path stay empty.

I can see on your picture that you are working in list 1 and you cues are 1-3 so you will put 1.1 to fire cue one in the Q Number box.

Hope that help. I use this setup in the summer for a show so it's not super fresh in my mind but if you need more info let me know. I will plug my Lanbox and take screen shot for you.

Good Luck

[Erik Rietman | KIRENTIS]

Hi Samuel,

Thanks for you input. I'll try you suggestion the coming days. One thing is not completely clear to me. You say if you want to fire cue number 60 in cue list 100 your Q number is 111.90. Can you explain that? In thought it should be 100.60 What am I thinking wrong here?

Erik

Hartelijke groet,

Erik Rietman

Maandagstraat 36

1335 LE  ALMERE
T + 31 (0) 36 844 69 22
M + 31 (0) 6 244 04 822
I www.kirentis.nl 
E er...@kirentis.nl

--

--
Change your preferences or unsubscribe here:
http://groups.google.com/group/qlab
 
Follow Figure 53 on Twitter: http://twitter.com/Figure53

---

You received this message because you are subscribed to a topic in the Google Groups "QLab" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/qlab/TdN_VI7wMXo/unsubscribe.
To unsubscribe from this group and all its topics, send an email to qlab+uns...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Samuel Thériault]

You are right. Mistype. 

Samuel Thériault

[Erik Rietman]

So, I'm still struggling with sending MSC cues form Qlab to my Lanbox. Checked all things over and over again but still with no luck. Normal midi cues to the Lanbox are working fine. What am I missing here??

My setup:

• Macbook Pro with Qlab 3.1.9
  
• Lanbox LCX connected through usb for editing purposes
  
• Macbook is connect with a midi cable to the Lanbox
  
• Midi out connector Lanbox not plugged in.
  
• Running midi monitor

I'm trying to fire cue step 87 from cue list 166

[Mike Post]

I guess I’m a bit confused here.  You say the Lanbox is hooked up by USB, but you had a MIDI cable from the Mac to the Lanbox.  How is the MIDI cable hooked up to the Mac?  Is there a driver to send MSC over USB?

I’ve never seen the MIDI port listed in your MIDI cue.  My guess is it’s not really connected to your Lanbox that way.  In the settings on QLab, click on the MIDI cue instead of MIDI controls and see how things are configured in there.  Maybe there’s something in there that looks more like your connection to the Lanbox you could try.  The MIDI controls section is about your local QLab responding to MIDI instead of the outboard box.

Also, try setting the Command Type to Lighting General.  All Types has proven problematic for me in the past.

Lastly, there was some discussion about needing to have a value in the Q List field.  This was in reference to ETC products, but you might try putting something in there.

Hope that helps!

Mike Post

mdp...@mac.com

http://mdpostdesign.com

(601) 307-8657

--
--
Change your preferences or unsubscribe here:
http://groups.google.com/group/qlab
 
Follow Figure 53 on Twitter: http://twitter.com/Figure53

---

You received this message because you are subscribed to the Google Groups "QLab" group.

To unsubscribe from this group and stop receiving emails from it, send an email to qlab+uns...@googlegroups.com.

[Samuel Thériault]

HI,

Ok my first question is: Do you have a license on the qLab? Because at the bottom it's written Demo. And the free version dosen't support midi cue according to the website.

After that, when the lanbox receive midi the first led on the box (midi i/o) should flash at lease once. If you don't get a flash, the lanbox might not receive data. What is the usb to midi interface you are using between the computer and the lanbox?

The only difference I have after that in my qlab session is the Command format. I'm set to Lighting (general).

For me it's work with nothing in the Q List field.

And like Mike say, the midi setting is in the other tab in teh setting pannel. Midi, not Midi Control

Let me know. I'm using this setup for 3 years now and everything is smooth and stable.

Thanks

Sam

[Sergio Sisques]

Q number 3.0

[Erik Rietman]

OK, let me clarify some things.

• The lanbox is hooked up to the macbook pro using an USB Cable. I'm using this to edit the cue lists with the appropriate software (LC edit)
  
• I also have connected a usb midi interface. So an USB cable is going to the interface and a midi cable is going from the interface to the lanbox
  
• On the midi cue in Qlab I've selected Message Type "Midi show control" 
  
• The midi destination is USB 2.0 midi port 1
• I also patched the correct setting in the Midi Settings tab (not the Midi Controls tab)

Normal midi cues ("voice messages type /program changes") are working fine and I can trigger a specified Cue list in the Lanbox. (Also in demo mode) But what I want to achieve is that I can trigger a specific Cue Step in the Lanbox through MSC

I hope this information helps a bit.

Erik

On Monday, March 9, 2015 at 2:55:14 PM UTC+1, Sergio Sisques wrote:

Q number 3.0

[Samuel Thériault]

Hi Erik,

You are probably really close to the working setup.

Everything look good. If you want to compare, I include picture of my setup and configuration. Everything is working here with that set-up.

When you hit Go on the midi (MSC) cue, does the midi green light on the lanbox flash at lease once?

Also, what is the configuration of the cue that can trigger a cue list? What you mean by that? You trigger a list that contain cue with auto follow?

Hope that help.

Thanks

[Erik Rietman | KIRENTIS]

Hi Samuel,

Thanks for your reply. I'll try to simulate your setup and see if that works. The green midi light on the Lanbox lights up when I give a cue, so i think it's something inside the lanbox. I'll let you know the outcome!

​Erik

--

--
Change your preferences or unsubscribe here:
http://groups.google.com/group/qlab
 
Follow Figure 53 on Twitter: http://twitter.com/Figure53

---

You received this message because you are subscribed to a topic in the Google Groups "QLab" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/qlab/TdN_VI7wMXo/unsubscribe.
To unsubscribe from this group and all its topics, send an email to qlab+uns...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Erik Rietman]

After struggling for some time now, it still doesn't work. It's driving me crazy.....:-)

So I've made a small screen recording to explain my problem. Maybe this helps...

https://youtu.be/qAt2cfCj9lg

Regards,

Erik

On Sunday, January 25, 2015 at 8:58:23 PM UTC+1, Erik Rietman wrote:

[Erik Rietman]

Samuel,

What are your midi settings in then Lanbox? And did you change the midi Sysex ID in LCedit?

Regards,

Erik

[Samuel Theriault]

Hi,

I looked at the video. The only thing I would say, in the Q List box there is no little line like in the Q Path. I'm will try this here and see if it's cause problems.

I don't remember changing settings in the lanbox.

I'm game to have a skype with you if you want. I'm in Montréal, Canada for time zone info.

Hope to get that fix with you

De inhoud van dit bericht is alleen bestemd voor de geadresseerde en kan vertrouwelijke of persoonlijke informatie bevatten. Als u dit bericht onbedoeld heeft ontvangen verzoeken wij u het te vernietigen en de afzender te informeren. Het is niet toegestaan om een bericht dat niet voor u bestemd is te vermenigvuldigen dan wel te verspreiden. Aan dit bericht inclusief de bijlagen kunnen geen rechten ontleend worden, tenzij schriftelijk anders wordt overeengekomen. De Leercompany aanvaardt geen enkele aansprakelijkheid voor schade en/of kosten die voortvloeien uit onvolledige en/of foutieve informatie in e-mailberichten. --

--
Change your preferences or unsubscribe here:
http://groups.google.com/group/qlab
 
Follow Figure 53 on Twitter: http://twitter.com/Figure53

---
You received this message because you are subscribed to a topic in the Google Groups "QLab" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/qlab/TdN_VI7wMXo/unsubscribe.
To unsubscribe from this group and all its topics, send an email to qlab+uns...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Samuel Thériault

cell.: +1.514.758.4177

[Samuel Theriault]

HI,

My setting on Lanbox Global setting - Comm - LanBox Serial/MINI settings
Is set to MIDI SysEX ID: 1

And your are at 9. Maybe this is the problem.

I'm returning on the midi usb adaptor thing. What is the cable and converter you are using? Mayby it's send wrong data when using MSC?

I tried the M-Audio Midi port and also midi out from a PreSonus audio card. Both work. Do you have anything else with what you can give a try?

I even tried to put something in the Q List box in Qlab and it's work. The lanbox ignore it.

I'm using this setup for 3 years now and I have no problems. At first it's was on Qlab 2 and when I switch to Qlab 3 I did not change anything in the Lanbox even.

I don't know if it's an option considering that the lanbox contain all the cues but maybe a reset could help.

At that point it's trouble shooting process.

Let me know

Le 2015-03-17 12:30, Erik Rietman a écrit :

De inhoud van dit bericht is alleen bestemd voor de geadresseerde en kan vertrouwelijke of persoonlijke informatie bevatten. Als u dit bericht onbedoeld heeft ontvangen verzoeken wij u het te vernietigen en de afzender te informeren. Het is niet toegestaan om een bericht dat niet voor u bestemd is te vermenigvuldigen dan wel te verspreiden. Aan dit bericht inclusief de bijlagen kunnen geen rechten ontleend worden, tenzij schriftelijk anders wordt overeengekomen. De Leercompany aanvaardt geen enkele aansprakelijkheid voor schade en/of kosten die voortvloeien uit onvolledige en/of foutieve informatie in e-mailberichten. --
--
Change your preferences or unsubscribe here:
http://groups.google.com/group/qlab
 
Follow Figure 53 on Twitter: http://twitter.com/Figure53

---
You received this message because you are subscribed to a topic in the Google Groups "QLab" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/qlab/TdN_VI7wMXo/unsubscribe.
To unsubscribe from this group and all its topics, send an email to qlab+uns...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Erik Rietman]

Hi Samuel,

I changed the midi sysex id to 1 several times with no luck. I'm beginning to think that the cable might me the problem as you suggested. It's a standard low end midi cable. Maybe that's the problem. I'll try to set it up with another device.

Thanks for all your responses.

[Charlie Richmond]

I have seen MIDI interfaces like that which have reversed the IN and OUT connections - try swapping them around.

Charlie

You received this message because you are subscribed to the Google Groups "QLab" group.

To unsubscribe from this group and stop receiving emails from it, send an email to qlab+uns...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

* Charlie Richmond - http://www.RichmondSoundDesign.com

* Viber: +16047159441 Skype, LinkedIn & Twitter: charlierichmond

* facebook: charlie.richmond

* facebook.com/pages/Richmond-Sound-Design-Ltd/130195960832

* google.com/+CharlieRichmond google.com/+Richmondsounddesign

[Rich Walsh]

SysEx ID should have nothing to do with MSC Device ID – completely different things. That interface looks like your problem. Have you tried connecting its OUT to its IN and seeing what MIDI Monitor gets back when you send an MSC message?

You know your connections are the right way round as other simpler MIDI commands are working.

Rich

[Frédéric]

Hi Eric,

I'll attach a screenshot of a cue, this way worked for me. Normally the midi device in this show was an Avid digi002.

Hope this helps. If you like you can PM me, but I have première next week here in Bruges, so I'm working day & night.

I can remember that it didn't work right away (2011), but I certainly got it to work within a day...

Regards

Frédéric

[Erik Rietman | KIRENTIS]

I'm getting more and more the idea that the midi interface is the problem. MSC cues are send out ok (as shown on midi monitor) but not properly processed through the interface I think. I'll try swapping it out for another one. I'll let you know!

​Erik

--
--
Change your preferences or unsubscribe here:
http://groups.google.com/group/qlab
 
Follow Figure 53 on Twitter: http://twitter.com/Figure53

---
You received this message because you are subscribed to a topic in the Google Groups "QLab" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/qlab/TdN_VI7wMXo/unsubscribe.
To unsubscribe from this group and all its topics, send an email to qlab+uns...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.