Hello everyone,
I am currently setting up QLab to run cues on an Ion. For this show (doors open tonight at 5!), the cues on the Ion are set up in groups of hundreds, with the first act starting at cue 100, the fifth act starting at cue 500, etc, so the cue numbers get quite high.
All the MSC cues in QLab are set up as Lighting (General), GO, Device ID: 0, Q Number: [the cue number], Q List: 1, Q Path: [blank]. During our run through, we noticed that our cues numbered 2200 and above do not play on the Ion after being triggered from QLab. We went back and created cues intermediate between 2004 (the last one that worked) and 2200--the highest one that works is 2147; 2148 and above do not.
If QLab settings are changed to just a GO with no Q Number, the high number cues play fine. Is this a known issue with QLab or the Ion software or is this a limitation of the strange "hexadecimal" encoding used by MSC? Does anyone know of a solution to this problem besides changing all the cues to plain GO's without Q numbers?
I am currently setting up QLab to run cues on an Ion. For this show (doors open tonight at 5!), the cues on the Ion are set up in groups of hundreds, with the first act starting at cue 100, the fifth act starting at cue 500, etc, so the cue numbers get quite high.
All the MSC cues in QLab are set up as Lighting (General), GO, Device ID: 0, Q Number: [the cue number], Q List: 1, Q Path: [blank]. During our run through, we noticed that our cues numbered 2200 and above do not play on the Ion after being triggered from QLab. We went back and created cues intermediate between 2004 (the last one that worked) and 2200--the highest one that works is 2147; 2148 and above do not.
If QLab settings are changed to just a GO with no Q Number, the high number cues play fine. Is this a known issue with QLab or the Ion software or is this a limitation of the strange "hexadecimal" encoding used by MSC? Does anyone know of a solution to this problem besides changing all the cues to plain GO's without Q numbers?
