Bug?? Goto Cue Out kills NiP in subs

This is intentional behavior, but it can be confusing.

The non-intensity parameters are LTP - latest takes precedence. The Go to Cue Out instruction tells everything to go to their background value, which is now the latest instruction for the channel. (If the sub was LTP, you would also see the intensity fade out with the Go to Cue Out command).

There are a few workarounds that come to mind:
- You could make the submaster Independent (at a higher priority) - this is probably the best option
- You can use Go to Cue 0 or Go to Cue <List Number> / Out to specifically target intensity or a particular cue list
- You can use Release or Off on the playbacks you wish to take out

If you get into that state, you could also Assert the submasters to restore their NPs.

Thanks for the response. Some times I wonder that I'm not the only EOS programmer in the world that has these issues. Its my biggest problem spending 50% of my time on an EOS and the other 50% on the MA2: Jack of All Trades, Master of None.

The Independant change was what I needed, I think. I don't understand the benefit of a submaster not protecting NiPs as a default. If I wanted them to react to commands, I would not have put them into a submaster.

I wish there were a way to set submaster defaults. Some shows I work on need all of the subs to be exclusive while you are building the show, other projects need the subs to not be exclusive since they are used in the actual cue creation.

I haven't spent much time with the new software so maybe this has been fixed but I have never had any luck with Goto Q #/0, Release, and Off doing what they are supposed to do. Either they don't fully release (i.e. you see grey background values but if you Sneak or Goto Q Out, they change to different grey background values) or they affect channels that are not in the targeted cue list (i.e. sending the conventional checkout list to 0 or Release or Off also kills the NiPs from the completely separate moving light checkout list.) It makes me wonder what the benefit of building an "ownership" cue - a 0.01 cue with all default values stored in it - is when the console treats any cue or list as a whole stage look and does not focus on only those channels that are contained in the specific cue or list.

Thanks again!

TH

Thanks for the feedback. I checked around with a few people and found out we will be adjusting this behavior in a future version (which actually might be pretty soon). The behavior will be changed such that LTP parameters on a sub won't be stolen by a Go to Cue Out. Other LTP actions will still affect it.