Request - Cue as reference

I've just been thinking of the same idea recently. After doing a couple quick shows with a very repetitive sequence of scenes/looks, This feature would be amazing.

The way I've been doing it is creating a Preset for all the channel. Each scene I just Select All and apply the Preset that I want to reference to.

This works fine the only annoyance is it looks messy, I'd rather see my intensity as absolute data and see the palettes and presets used within with their labels.

I was thinking if you could Record a "Look"

[Record][Look][1]Enter]

And then you would apply the look to the cue to be referenced to.

[Cue 1][Execute][Look][1].

The Cue would automatically place a Full Block on itself so that any tracking data wouldn't rove into it. But things could track downstream from the referenced look. So it would be useful for those top of a scene occasions.

I would think that any changes made to that cue would update into the look and change throughout the show where the look has been applied. I realise though that there may be an occasion where someone may want only part of a cue (only a select amount of channels) references to a look, 

I suppose it would be useful to apply a "look" on a Channel level as well.

It would eliminate all those time when you have to remember the cue number of the scenes you want to copy to from, and at a later date if you want to change your "Pug in a Forest" Scene throughout the whole show with changes made on a Cue level not just a Preset & Palette at a Channel Level.

Hey Sam,

If you do Recall From Preset X that will bring the levels and references in as they are stored.

D

But wouldn't allow me to change a "Scene" / "Look" throughout the show by just updating the cue.

I would have to go into each cue that is that kind of look and make the same changes, or record or update to those cues that require the changes.

Sure, absolutely, but it would be cleaner for recalling a 'look'.

D

You're right. I would much prefer to see the Presets/Palettes.

It's just that I find the referencing of cues (by using a massive Preset) really useful, there's just really that one disadvantages of it being really messy.

The feature is obviously only useful for certain situations but if you've got that Hire that walk in and tell you they want 5 different states but in a cue list with over 100 cues in random orders it would be brilliant. Or to be honest I would have loved this for Love & Information here at the Court. Anything that is repetitive really.

You're right. I would much prefer to see the Presets/Palettes.

It's just that I find the referencing of cues (by using a massive Preset) really useful, there's just really that one disadvantages of it being really messy.

The feature is obviously only useful for certain situations but if you've got that Hire that walk in and tell you they want 5 different states but in a cue list with over 100 cues in random orders it would be brilliant. Or to be honest I would have loved this for Love & Information here at the Court. Anything that is repetitive really.

I sometimes build a secondary Q list with my base looks in it - like 5 Q's.  Then in my main Q list (300 Q's) I execute the secondary Q list - so I'm basically referencing an external Q.

There are a couple little hiccups - The execute line fires a tad slow so if you want to have data override the referenced Q you'll need to have an auto-follow Q that waits 1/2 second before firing.   The other issue is the execute can draw focus to that Q-list.   Executing a little macro "Cue 1/ Enter" in the same line fixes this problem.   

The upsides are you can add unlimited fixtures long after the Q list is built with ease.  

You are essentially using referenced timing which can be super useful.  

You are referencing effects and their overrides as well - which can't be stored in a preset (yet)

You can also leave the INT information as hard values and have all other information showing the labels.

To get past that Macro "Cue 1/ Enter" you could lock the PSD top left of your tab.

I'll have a play, seems a nice work around, with the correct Assert/Blocks put in place.

locking the PSD with the padlock has nothing to do with what cuelist becomes active in the command line, methinks...

No, it wouldn't. But when playing back the show, you may not want the cue lists flicking between each other. I would only want to be seeing the cue list with the 300 Q's in. The cue list that is showing me the numbers the DSM is calling and I'm pressing Go on.

There would be no need to change focus on either the command line or the PSD during a show would there?

no there wouldn't. but while programming and making changes it might be unfortunate, if you think you're recording to cuelist 1 (which is what you're seeing on the PSD) but in reality you're recording to cuelist 2 because executing a cue pulled focus to that cuelist...