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.
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.
