Could you possibly explain the priority levels for items on the command line when busking a show, it seems to be that if you put a manual intensity on a group of fixtures, say "Group 1 @ 10%" then as you would expect you get those fixtures to stay at 10% including when releasing any active playbacks which also contain intensity information. The programmer / syntax is acting as priority.
However if you use a pallet for an attribute then whilst it initially works and you get the look wanted, if you happen to release an underlying playback which also had that attribute information on it then it seems to release the fixture back to default values for that attribute. Should it not be that the syntax / programmer is still priority and when you release a playback any attributes would refer to anything on the command line as the intensity does but it only seems to control intensity nothing else...
Example -
MFF1 = Intensity only for group 1 at Full.
MFF2 = Group 1 in red
push both faders up - fixtures are at full in red - as expected
then manually change the intensity to 10% and change the colour to blue on the command line - again as expected fixtures are in blue at 10%
however if I then release MFF2 the colour reverts back to the fixture default value but the intensity remains at 10%, is there a way to make sure that all information still in the programmer stays as priority until it is cleared so I could release the colour MFF but the colour would stay at the value sat on the command line?
(coming from a chamsys background where the manual values in the programmer would be priority unless you set a playback to be a higher priority for example a white strobe set to bump over everything)