Fixture Profile Request: Futurelight CC-200

Hi Aaron:

Yes, user min and max allows percentages to be shown instead of 00-255 if you desire, but it doesn't do the math for you as to what those percentages should be.

Ranges are the values selected by the buttons- then to move within those you would hold down shift while moving your encoder.

Thank you,

Additionally, your request has been submitted for when we start making profiles again the new year.

Thank you very much, Shasha. As I stated in my first message, strangely the CC-200 is identical to the Beam 250 XT produced by Robe. I would just use that fixture profile instead—both manuals have the exact same DMX chart—however there are a few slight problems with it anyway related to incorrect or missing ranges.

Could you possibly estimate how long it would take for the profile to be completed? How exactly are fixture profiles that have been requested by individuals such as myself released? Does EOS have some sort of facility to import individual fixture definition files?


Regarding parameter ranges, I am using Nomad in Element mode, as opposed to EOS, so I do not have encoders. Can I scroll within ranges in ML Controls somehow? I want to know how to do this for two reasons: so that, if desired, I can set the colour wheel to such a position where the beam produced is split between two adjacent colours, and for adjusting the strobe rate on the shutter channel.

When the button pertaining to each range specified for a particular parameter is selected in the ML Controls display, is the value outputted the lower bound of that range or its midpoint, or neither?

Thank you, Aaron.

As other responses have noted, the delay now is simply because of the holiday but our typical turnaround time for new profiles is two weeks. Once the holidays are over we will do our best to have a library patch released before 1/14/2017 that will include the CC-200.

Profile requests are release as Fixture Library Updates via our website. If you go to the same location as software downloads you will also find the most recent library patch. We are creating fixture definition files and then creating an installer to place them onto your console.

In ML Controls clicking the title of any parameter will give you a virtual encoder on the screen. You can use this to move within ranges.
The value output is the lower of the range when selecting buttons in ML controls.

Thank you,

Hi, Sasha.

Thanks for answering all of my questions so promptly.

I apologise for not posting a request sooner. I only discovered last week that no profile existed for this particular fixture. This is my first time using EOS for a show and posting in this community so I was not aware of the procedure to request the production of a profile. I would very much appreciate it if you are able to release the library patch in that time frame.

As for adjusting the value within a range, it never would have occurred to me that clicking on a parameter's title bar would reveal anything else. It really could not be any simpler! I shall remember to try clicking random objects next time I unable to locate something—you never know

Something which still confuses me, despite another user briefly explaining the matter, is this whole business of virtual parameters. How exactly does a virtual parameter affect the output of a parameter mapped to a DMX channel? Taking the Beam 250 XT fixture I have been discussing, why does the Shutter Strobe parameter associated with channel 3 only have one range specified but yet the virtual Strobe Mode parameter has all four ranges, as described in the manual? What actually connects the two together if there is no option to do so in the fixture editor? If I attempt to create the fixture from scratch I cannot replicate this configuration. Even more confusing is the fact that the minimum and maximum values of each range specified for the virtual parameter do not correspond with those in the manual, yet if I open the About display after selecting a button for this parameter, in ML Controls, the correct value (lowest in range) is registered as being outputted to the address mapped for Shutter Strobe. After now having the opportunity to play around with the virtual encoders for each of these parameters, I do notice another peculiarity: when I select the 1 to 8 Hz button under the parameter for strobe, if I then activate the encoder alongside and rotate it, the number above changes to between 01 and 08. Obviously this is more useful than just seeing the raw DMX value for determining the actual strobe rate, but what exactly instructs the value to be displayed in that form?

Is it all simply a case of there being a lot of values and settings which are hidden to the user and are beyond the realm of being modified in the fixture editor, or am I missing something?

Hi, Sasha.

Could you ensure that the DMX range values for the colour wheel are correct and that no ranges for channel 4 are missing? This is currently the case with the Beam 250 XT profile. As I will have very limited time once you have managed to successfully release the fixture in a library patch, I cannot afford to have errors in it which I am unable to correct myself in the fixture editor. I would suggest revising the existing Beam 250 profile in addition, although it is not particularly important for myself if you are producing a new profile specially for my fixture type.

Many thanks,
Aaron

I'm sorry to pester, but I really would like to know how this works. Could someone from ETC answer my questions?

Also, Sasha, could you confirm whether a fixture profile is in the process of being built?

Hello, Aaron:
I am sorry for the delay- I have been out of the office for a few days.
Your profile is being worked on and will be released as part of a patch for v2.5.0
When we make fixture profiles we are able to link parameters in background code so that one can affect the other. This isn’t really possible in the fixture editor on the board itself – so it is something we need to do here at the factory. What is happening is we are able to provide, through background coding, a way to give the user interface some buttons that allow you to jump between ranges.
The profile we are building will be based directly on the manual that Ueli found earlier and the DMX ranges provided by the manufacturer. They should be correct.

Thank you,

Thank you for your response, Sasha. I understand what is happening now. Are there any plans to improve the fixture editor to give users this capability?

I appreciate you agreeing to produce this in such a limited time frame, but do you have any idea when this will be available as I am concerned it wont be ready in sufficient time?

Hello, Aaron:

As of right now I know they are working on it and hope to have it completed before the initial deadline you mentioned earlier in this thread.

As I understand it we do not plan on making those background mechanisms available in the fixture editor as it is something in the code that needs to be done in the background.

Thank you,

When it has been completed, will
It be posted herein the forum or in the software section of the site?

Do I import the library using an option in ECU?

When it is completed the library will go into the software section of the website like other software. We usually also make a forum post to let people know it has been released.

You will run the library installer via the {Software Update} option in the ECU.

Thank you

Hi Sasha,

Have you seen my reply to your PM? It is becoming rather urgent that I have this sorted now.

Thanks,
Aaron

Hi Aaron:

Yes- I saw it and I have been working on a detailed response.

Thank you,