Updated Martin 518 profile not working properly

ckaiserca said:

PS  We found the method of getting to the rotation for gobos just after posting this. Holding down the encoder and pressing mode.  But it seems to me that this is tons more difficult than just having the one encoder scroll through the various gobos and rotations as this is what we have been doing since Express.

Was there a reason to make the profile more complicated?

One of the goals of our fixture library is to standardize the interface to fixtures. The fixture library is re-mapping the DMX ranges on the gobo parameter to expose a more consistent interface. The console is attempting to make this single DMX channel look like two parameters: a mode selection and a gobo selection. This allows a show to contain data that manipulates one parameter without affecting the other. Users can write palettes that select each specific gobo without effecting the rotation, and other palettes that change from static to CW to CCW rotation without affecting the gobo selected. This also allows users to re-patch one fixture type in place of another. If the exposed parameters are the same between the fixtures, then there should be little modification to the show required in the re-patch.

The further a fixture's design is from the "standard" fixture the weirder it may respond to console control. For fixtures where this model breaks and we will create an exception (e.g. the CXI is never going to look like any other CMY fixture)

I hope this background help you understand what we are trying to accomplish.

Ray

ckaiserca said:

PS  We found the method of getting to the rotation for gobos just after posting this. Holding down the encoder and pressing mode.  But it seems to me that this is tons more difficult than just having the one encoder scroll through the various gobos and rotations as this is what we have been doing since Express.

Was there a reason to make the profile more complicated?

One of the goals of our fixture library is to standardize the interface to fixtures. The fixture library is re-mapping the DMX ranges on the gobo parameter to expose a more consistent interface. The console is attempting to make this single DMX channel look like two parameters: a mode selection and a gobo selection. This allows a show to contain data that manipulates one parameter without affecting the other. Users can write palettes that select each specific gobo without effecting the rotation, and other palettes that change from static to CW to CCW rotation without affecting the gobo selected. This also allows users to re-patch one fixture type in place of another. If the exposed parameters are the same between the fixtures, then there should be little modification to the show required in the re-patch.

The further a fixture's design is from the "standard" fixture the weirder it may respond to console control. For fixtures where this model breaks and we will create an exception (e.g. the CXI is never going to look like any other CMY fixture)

I hope this background help you understand what we are trying to accomplish.

Ray

Could this separate mode control be on a different encoder then? 

And could the "static" control issue be fixed? 

As it is now, it's very difficult to select the static gobo as any movement of the encoder causes the gobo to skip to the last position and to select a different pattern you have to carefully move the encoder click by click.