[quote=snowmaniac153]On hog 2 --you could grab a mover-- press green---them BAM it was green .... then Press -Pig- Green-- and Away the green would go.
Is there a way on hog 3 to release the color...without pressing open???
Well, there is... . + Wheel puts value to default and backspace + Wheel removes the value. You get idea when you do this Programmer window open. The difference is important when you think what is recorded.
[quote=BenJourno]What is the different between . + Wheel and backspace + Wheel (knockout)? Don't understand the english manual at this point.
Greetings
(.) plus (wheel) is actually very different from (backspace) plus (wheel).
Using the point (.) key while turning and encoder wheel forces that attribute to its default value- specifically, it is putting a hard value of the attribute's default into the Programmer.
Using the Backspace key while turning and encoder wheel will act as a knockout: essentially erasing that parameter from the Programmer. This does not force the attribute to it's default. Whether the attribute goes to it's default at that point depends on what else may have control of that attribute.
This is easily confused if you have nothing else controlling the fixtures beyond the Programmer. In that situation, using the knockout shortcut will revert the parameter to it's default. However, if you have a cue or scene playing at the same time that also has control of the parameter, then knockout will not put the parameter at it's default (rather it will revert control back to whatever has the next priority). All knockout does is "erase" value(s) from the Programmer: removing the Programmer's control of the attribute(s).
A hard value (whether it is a default or not) is a hard value: this is information in your Programmer that can be recorded. A cell that is empty (not touched) will not be recorded.
The easiest way to see the difference is to simply look at the attribute in the Programmer window. Then, try both of the shortcuts. The difference in the cell should be very clear.
And since we're talking about this, the (.) + (0) + (wheel) is very similiar to (.) plus (wheel). The difference is if you are using a parameter with multiple "modes." For example, if you had a value for continuous Gobo rotation in RPMs and held (.) + (wheel), that would force a hard value of "0 RPM" into the Programmer. If, instead, you held (0) + (.) + (wheel), this would force a hard value of "0 degrees" into the Programmer. "0 Degrees" represents the default value of "Indexed Rotation." Indexed Rotation is the default "mode" of the Gobo Rotation wheel, so not only does this force a hard value of the default for the attribute, but- more specifically- it is the default for the attribute's default mode. There are times where you would use one over the other: it just depends on what you need.
I know this is a lot of information: the best way to understand this is to try these shortcuts while watching the values in the Programmer window. Unfortunately, simply looking at the stage will not tell you the whole story. It's all about control of the attributes, and knowing what has it.
ahh thank you for the detailed and helpful post CatWest. I think I understand it now. Just for recapitulation: (.)+Wheel sets the value back, so it is a bit like touching an unused fixture (when no cue is using the fixture), right?
Yes: Sort of. :147: The (.) + (wheel) is a little more specific. It doesn't matter what the attribute's current Output is (like it does for "Touch"). When you use this shortcut, it will force the attribute to it's default in the Programmer. The attribute may already be at it's default in the Output, or it could be be at a totally different value because a cue or scene has control... even if the Programmer already has the attribute at a different value, when you use (.) + (wheel), the value in the programmer will be forced to the default value.
