How to set "Strobe Mode" to "Closed" / "Open" / "Strobe" ... ?

I would suggest making Beam Palettes with “By Type” fixtures for each fixture you will be using. That way it is always referencing Beam Palette “X” which would have each fixture’s strobe value. When you change type in patch, it would just reference the value for the new fixture type in that palette.

Thanks croaarj.

So, there is no way to directly access these Buttons ("Open", "Strobe" etc) other then clicking?!

Re Beam Palettes, I thought in a similar direction! Of Beam Palettes "By State", to be updated once every tour stop. "By Type" is an interesting alternative, will ponder.

Related issue is "Shutter Strobe" range. It also is not standardized (0..100%), instead has arbitrary ranges, sometimes representing Hz rates (i.e. with Robe Pointe, 0 .. 15Hz - ok, cool), sometimes based on raw values (i.e. Robe BMFL, 64..95 - seriously?).
Any suggestions how to work around this incoherence?

The only way around it would be to edit the fixture profile for yourself. Those ranges are all established by the 3rd party company that builds profiles for ETC. when you go into the fixture profile there are 2 columns: DMX Value and User Value. If the user manual provides a Hz range for the strobe, you can change the User Values Min and Max to match the provided range.

if you do “By Type” it would just save you a little bit of time because if you end up at another venue that has a fixture type you have already used, you would not need to update the palette again. 

This incoherence in the fixture library is maddening. I hope this will be addressed soon. The fixture library needs a big overhaul to ged rid of alle the inconsistencies.

We can only pass on the information provided by the manufacturer of the fixture.
The documentation we get varies from "four words scribbled on an envelope" to "detailed 50-page manual".

Some manufacturers send us or our 3rd party supplier (Carallon) a sample of each fixture so we can measure all the information that's missing or incorrect in the manual, and create the best possible personalities.

Most fixture manufacturers don't do that, and don't put information like stroke Hz in their manuals.
In many cases we don't even know which DMX value is "slowest strobe".

We can only improve these when users like yourself let us know the real numbers, and put pressure on fixture manufacturers to improve their documentation and send us sample fixtures.

Thanks for clarifying, Richard. I can totally see these issues esp with exotic fixtures.

However with the Robe BMFL (compared to Robe's Pointe) and also with the Clay Paky Axcor the issue rather seems that different contributors follow different "philosophies" how to translate the various value-ranges and capabilities of the fixture into faders/values in EOS. There are indeed inconsistencies that would be ace to get fixed. Shutter Strobe from 64 to 95 isn't really intuitive

This I've fixed to 0..10Hz (as per manual) as well as similar issues with Clay Paky Axcors - is there a way to commit edited profiles, so they can be reviewed and)added to the next library update?

mfo said:

is there a way to commit edited profiles, so they can be reviewed and)added to the next library update?

There are a lot of "Bug Fixes" in the Fixture request Forum.

mfo said:

is there a way to commit edited profiles, so they can be reviewed and)added to the next library update?

There are a lot of "Bug Fixes" in the Fixture request Forum.

That's the way then. Tho I can't figure out how to export a single fixture (in order to post it). Any leads?

Just save the showfile.

If you want to limit it to just that particular fixture, make a new blank show and Merge it in.

The Merge is the process because you'll often want to bring by-type palettes along and similar.