• State Not Answered
  • Date
    JTBettis
  • Date
  • Replies 3 replies
  • Subscribers 185 subscribers
  • Views 3091 views
  • Users 0 members are here

Flexi Encoder Screen Bug?

Hello All,

I just upgraded my Eos Ti to 2.5.

I noticed an issue with the encoder pages, on the Encoder screen, when they're in Flexi mode.

When I select a group or channel, I need to terminate the command line before the encoder screen will 'refresh' to flexi mode. I may be wrong, but up through 2.4.1 all I had to do was type in a group or channel. I didn't need to hit <enter> after the selection.

An Example:

In my show file, I have ETC D-60s in channels 1-10 & generic RGBW fixtures in channels 11-20.

When nothing selected, the color encoders, spread over several pages, show all possible color options inactive.

In 2.4.1, I believe when I typed '1', the Color encoder pages showed the 7 colors & Hue & Sat. But when I typed '11' all I saw was R, G, B, W, and H&S.

Now, in 2.5, when I type '11', I see the R, G, B, W, and H&S encoders active, but they're spread out over several pages along with inactive encoders with the remaining colors from the D-60s. It isn't until I type '11 <enter>' (terminating the command line) that the encoder screen shows the active R, G, B, W encoders on one page and H&S on another page with nothing else and no other pages.

This happens across several different types of fixtures & whether I'm selecting channels or groups. I didn't notice if this happens with other encoder types, but will be in front of my console to check tomorrow.

Not sure if this is a bug or a purposeful change. I first noticed it when I selected a fixture from a Magic Sheet & went to adjust it's color. Having to tap the Magic Sheet button then hit <Enter> just to see the encoder screen pages in flexi like they should be seem awkward.

Thanks

Jeff

Parents
  • 0
    Hello Jeff,

    I just checked this out across a couple of versions, and I'm not seeing what you describe either in v2.3.3, or v2.4.1, or in v2.5.0. The console needs to have some concept of what you're selecting in order to show the ML controls and encoders you can use. It is expecting the syntax to be "Thing, type of action, value". Typing in '1' isn't enough to declare the 'thing' because the console is waiting to see if I want just '1', or '11', or something else.

    However, if I do something to specifically pick a channel (click on its tile, press a channel Direct Select, or use '+', '-', or 'thru' for instance), then the ML tab and Encoder pages reflect the options of the first thing selected, and continue to expand as my selection expands. That includes clicking the channel's target image on a Magic sheet.

    Have you checked to see if the issue is show-file specific? If you created a quick new show with a couple of different fixture types and a magic sheet, can you get it to behave the same way?
Reply
  • 0
    Hello Jeff,

    I just checked this out across a couple of versions, and I'm not seeing what you describe either in v2.3.3, or v2.4.1, or in v2.5.0. The console needs to have some concept of what you're selecting in order to show the ML controls and encoders you can use. It is expecting the syntax to be "Thing, type of action, value". Typing in '1' isn't enough to declare the 'thing' because the console is waiting to see if I want just '1', or '11', or something else.

    However, if I do something to specifically pick a channel (click on its tile, press a channel Direct Select, or use '+', '-', or 'thru' for instance), then the ML tab and Encoder pages reflect the options of the first thing selected, and continue to expand as my selection expands. That includes clicking the channel's target image on a Magic sheet.

    Have you checked to see if the issue is show-file specific? If you created a quick new show with a couple of different fixture types and a magic sheet, can you get it to behave the same way?
Children
No Data
Related

www.etcconnect.com