• State Suggested Answer
  • Date
    essentials
  • Date
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 185 subscribers
  • Views 909 views
  • Users 0 members are here

Robe CycBar 15 with color picker

I can't wrap my head over this:

1) White channel on Robe Cycbar 15 always stays at 100 when using color picker (all color spaces as well as pre-defined gel colors), rendering the color picker useless. It does respond only to its encoder.

Why does it not behave as any standard RGBW? Am I missing something?

Tested on M2 and M3 of built-in library profile. Eos v.2.7.4 and 2.8

2) Is there a reason for color picker cross-hair to snap back to background values when those are auto-blocked? (cross-hair only, not the actual output)

Thanks.

Parents
  • 0

    Hi there,

    Unless Eos know these color point of White it treats it as a separate parameter from the rest of the color fixing. You will want to follow up with Robe and ask them to send the appropriate fixture info for this parameter to Carallon to have it scanned into their system. This way Eos will be able to integrate this information and include White in the rest of the color mixing. 

    I'm not seeing the color picker cross-hair snapping issue you reported, unfortunately. Does this occur during cue or sub master playback? We can see in the channel's About information where the source of this color is coming from. 

    Best,

    Therese

  • 0 in reply to Therese

    Hi, thank you for your response. I am reaching out to Robe and awaiting their answer.

    I couldn't replicate the snapping issue on OLE and I wouldn't  be able to get to the desk for a few weeks, unfortunately. It occured numerous times during single cue list playback with a few subs recorded, but mostly inactive. It occured to me this might have been related to multiple LTP values being present, but the affected channels only had manual vales with background values provided by cue. It was a tightly scheduled job so I wasn't able to dig deeper on this on the spot and had to settle with the issue disappearing after deleting an earlier autoblock in the cue list. 

    What bugs me is that it wasn't exclusive for a single fixture type and occured on Clay Paky Alphaspots, DTS Nick Washes and Robe Cycbars. 

    With the mouse button pressed, the cross-hair moved as expected. On the mouse button release it didn't stay where left, but snapped back to the background value (however, the actual output did not). 

    So, I guess my question is - are there circumstances (that I might have accidentally created) under which is this behavior expected?

    Thanks.

Reply
  • 0 in reply to Therese

    Hi, thank you for your response. I am reaching out to Robe and awaiting their answer.

    I couldn't replicate the snapping issue on OLE and I wouldn't  be able to get to the desk for a few weeks, unfortunately. It occured numerous times during single cue list playback with a few subs recorded, but mostly inactive. It occured to me this might have been related to multiple LTP values being present, but the affected channels only had manual vales with background values provided by cue. It was a tightly scheduled job so I wasn't able to dig deeper on this on the spot and had to settle with the issue disappearing after deleting an earlier autoblock in the cue list. 

    What bugs me is that it wasn't exclusive for a single fixture type and occured on Clay Paky Alphaspots, DTS Nick Washes and Robe Cycbars. 

    With the mouse button pressed, the cross-hair moved as expected. On the mouse button release it didn't stay where left, but snapped back to the background value (however, the actual output did not). 

    So, I guess my question is - are there circumstances (that I might have accidentally created) under which is this behavior expected?

    Thanks.

Children
No Data
Related

www.etcconnect.com