strange lights suddenly... midi file cues to dmx-controller

[Peter D]

I am busy starting midi file cues to a connected dmx-controller and had no trouble whatsoever.. But during technical run of theater play I was starting the cues in different order and pressing escape and starting another cue and so on.

Suddenly I saw some lights from one cue mixing with other lights of another midi file cue..

During showtime all went well.

I wish I knew what happened there.. I am new to qlab and my guess is that trouble arises in one or two midi file cues that are 3 minutes long (base file duration: 03:00.64) and the other 20 midi file cues I use in the workspace are only 00:00.06 long. 

So I start running this long midi file cue (complex light for dancing) , I press escape after 20 seconds or so, all lights go black, I start another 'normal' midi file cue and then behaviour of lights is strange, having for example one light from long file in the cue of normal file..

So my first guess is that the long midi file cue is still somewhat active in the dmx controller, not fully aborting by the escape button.... ?

Thanks for any advice..:-)

Peter

[Damien Figueras]

Question - What is the DMX controller that you are sending MIDI to? 

My guess is that while pressing escape will stop what's happening in QLab, that doesn't necessarily reset the DMX-controller. For example - if you're sending to a light board and there is a sequence of lights set to auto-follow from one command, killing the signal in QLab won't actually stop or reset what's happening on the lighting console. And if the MIDI triggers are really just GO cues and are not triggering specific cue numbers within the console, that could also create a mess when moving out of order. 

Since the MIDI is being used to trigger some other commands on a DMX-controller, the issue is likely on the DMX-Controller and not in QLab.

Thanks!
Damien

--
Contact support anytime: sup...@figure53.com
Follow QLab on Twitter: https://twitter.com/QLabApp
User Group Code of Conduct: https://qlab.app/code-of-conduct/
---
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/qlab/24310891-cc9e-40b9-8ec9-bc0fb9b4859dn%40googlegroups.com.

[Rich Walsh]

Also, if you're sending MIDI Note Ons as part of your MIDI File Cue pressing escape will not send MIDI Note Offs, so you'll be stuck with anything that had been turned on when you panicked. You need to send All Notes Off (Control Change 123) or possibly All Sound Off (Control Change 120) on every MIDI channel used after a panic to clear any "stuck notes". QLab's escape stops QLab: it doesn't issue commands for devices it has triggered to also stop…

Rich

[Peter D]

Thanks for the insights!

Dmx controller is: CDS Lanbox-LCX. It gets configured by its own ' LCedit ' software and during show it is used as a standalone.

(midi file cues are sent to Motu ultralite firewire soundcard connected to thunderbolt of the macbook, then the Lanbox is connected to soundcard by midi-cable)

Indeed (by monitoring the software while running Qlab and its midi file cues) I can see escape-button does not halt the 3 minutes auto-follow light sequence.

(midi files do trigger specific cue numbers in the console though).

Indeed I am 'stuck with what has been turned on'. For now, I'm good, knowing it only happens with not following the normal order of the show itself, and also I found the stop-button in the software of the console, which is runnign next to me on a different laptop...

Peter