Cue List Widget Customizations

[flyingGoatBoy]

Hi, I've been using QLC+ for the small community theatre I volunteer at for 4+ years.

My typical workflow is to create all of the scenes for the play or performance, and then put them all into a cue so I can basically have anyone "run lights" for the show.

That being said, it would be really great if the Cue List widget supported some additional customization.

Please forgive me if there are other ways to accomplish this.

Wish list items:

• The ability to remove (hide) columns. - Operators don't need to know how long the cue item trasition is (for example)

• Custom Font selection per row/column - Typically I make the Scene notes in ALL CAPS so the operator notices them, but i would be great if the "notes" column had a different font, or if a row has an important action, we could change the color or make it bold so that the operator knows it is important

• Separators for the cue - basically a blank item the allows the operator to know where they are in the list (i.e: Act 1, Scene 2) Right now I create blank functions that have zero hold time that accomplish this, but it would be nice if there were something less "hacky" to do this.

• ability to hide certain rows - we have multiple moving head fixtures that we use during our performances, and occasionally I need to put zero length scenes in place to move them to the correct location. This confuses the operator because from their perspective, it does 2 cue jumps per 1 "next" button push. This then causes them to push "back" which might load the wrong lighting scene. If I could hide the row, it would prevent some confusion

[GGGss]

Separators for the cue - basically a blank item the allows the operator to know where they are in the list (i.e: Act 1, Scene 2) Right now I create blank functions that have zero hold time that accomplish this, but it would be nice if there were something less "hacky" to do this.

A dummy scene is generally accepted throughout the world, so that will stay.

ability to hide certain rows - we have multiple moving head fixtures that we use during our performances, and occasionally I need to put zero length scenes in place to move them to the correct location. This confuses the operator because from their perspective, it does 2 cue jumps per 1 "next" button push. This then causes them to push "back" which might load the wrong lighting scene. If I could hide the row, it would prevent some confusion

Did you already study the concept of a collection? This solves the above problem. With a collection, you can fire a lot of functions at once.

To the other ideas: in a theatre concept, this could be a nice to have feature.
Well before I got to know QLC+, I misused a home automatisation system to give cue's and go's to backstage, efx, orchestra and the like. This was a play with 120 actors and 45 musicians. And that was 'pfieuw' to get everything in pace.

[flyingGoatBoy]

Separators for the cue - basically a blank item the allows the operator to know where they are in the list (i.e: Act 1, Scene 2) Right now I create blank functions that have zero hold time that accomplish this, but it would be nice if there were something less "hacky" to do this.

A dummy scene is generally accepted throughout the world, so that will stay.

Fine by me. Just thought that while I was requesting, I may as well give it a shot. We use a sound cue app called "Multiplay" that allows separator elements in the cue and it helps the operators, who usually are not tech savvy at all.

ability to hide certain rows - we have multiple moving head fixtures that we use during our performances, and occasionally I need to put zero length scenes in place to move them to the correct location. This confuses the operator because from their perspective, it does 2 cue jumps per 1 "next" button push. This then causes them to push "back" which might load the wrong lighting scene. If I could hide the row, it would prevent some confusion

Did you already study the concept of a collection? This solves the above problem. With a collection, you can fire a lot of functions at once.

Yeah I already use collections, and I could technically just add the "position" scene to the previous collection in the cue to accomplish the same thing. The issue I have with that is then I get a ton of collections that are the same except for the addition or removal of the position scene. (i.e. "Forward Stage bright w/ scene 2 position".)

While It's not terrible, it's a replication of basically the same thing over and over with one minor variation. By Breaking out the "position" element (which is a collection also,) I can keep my collections general enough that I don't need to sort through a ton of them.

Thinking a bit more about it, this might also be helped by the other item in this request: per row font or styling. At least then I could tell the operators to ignore "red" rows or whatever.

Thanks for taking the time for a response.

[JimJoiner2]

We use qlcplus for the same thing (Cue Lists called "Chasers" with infinite Times) in a Theatre setting. We would like the ability to renumber the Cues. Better yet, keep the same numbers but add Cues in between Cues without re-numbering the whole List. Right now, we put the numbers in the Script and the Director "Calls" the lighting cues based on the numbers in the Script. We would like the ability to add/subtract additional cues in between the numbered cues such as cues for the Follow Spot operators.

[GGGss]

Jim, Welcome to the forum.

Adding / renumbering / change the sequence of ... I make use of a text editor and open the show file there. It looks like an XML structure. You can quickly alter its content now. Make sure you make a backup though! If you break the structure of the file, you break your project.

[SPS]

Jim, Welcome to the forum.

Adding / renumbering / change the sequence of ... I make use of a text editor and open the show file there. It looks like an XML structure. You can quickly alter its content now. Make sure you make a backup though! If you break the structure of the file, you break your project.

I 'll join this Cuelist widget Customizations because I also uses them in a play session.
I tried to alter the chaser in the XML file, but unfortunately the numbering in the chaser is not used for the numbering in the widget.
Altering the "stepnumber" in the chaser does not change the widget. Pity

Paul

[kittyrobbins]

This is an old topic so maybe a solution has been found?

Adding / renumbering / change the sequence of ... I make use of a text editor and open the show file there....

Does this still work? It has no effect when I try it.

Example:

<Step Number="4" FadeIn="5000" Hold="4294967294" FadeOut="5000">3</Step>
<Step Number="4.1" FadeIn="2000" Hold="4294967294" FadeOut="2000">1</Step>
<Step Number="5" FadeIn="2000" Hold="4294967294" FadeOut="2000">3</Step>

This does not change the step numbers when I save and then load the file in QLC+. Still sequential - 4, 5, 6.

Also, how do you set the step column width to zero? I can adjust column widths using the slider on every column EXCEPT Step #.

[GGGss]

Example:

<Step Number="4" FadeIn="5000" Hold="4294967294" FadeOut="5000">3</Step>
<Step Number="4.1" FadeIn="2000" Hold="4294967294" FadeOut="2000">1</Step>
<Step Number="5" FadeIn="2000" Hold="4294967294" FadeOut="2000">3</Step>

Contrary to other light desks, QLC+ does not like decimals in the chaser's steps. This is because you can bind the steps to an external control, and possible values are 0-255 (like a DMX channel).
Solutions: Quickly copy that section to a spreadsheet and let it renumber your steps. If a director decides to add an intermediate step, you will need another approach. I'd suggest using a chaser within a chaser, but now fade times will become a little more difficult.

[kittyrobbins]

I see, thank you again.

I guess I'll stick to using the NOTES column for cue numbers, as once all the cues are in my script or in the stage manager's book, re-numbering is a nightmare. Thus, point cues.

Is there really a way to hide the step number column?

[edogawa]

Here in Linux/Plasma6, I can drag the column separator to the very left so that the Number column vanishes, but only in Operate mode. In Design mode it's insensitive to mouse.

[kittyrobbins]

Here in Linux/Plasma6, I can drag the column separator to the very left so that the Number column vanishes, but only in Operate mode. In Design mode it's insensitive to mouse.

Ah, that works! Too bad it doesn't save that way, but at least it's something.

Seriously, the confusion at the top of shows with new people running lights is a regular thing. I've considered placing a piece of spike tape on the monitor over that spot.

[flyingGoatBoy]

Here in Linux/Plasma6, I can drag the column separator to the very left so that the Number column vanishes, but only in Operate mode. In Design mode it's insensitive to mouse.

You can do that in windows also, but if you change the chaser at all and then switch back to operate mode, you'll have to "hide" all of the columns again.