Feature and improvement suggestions

Feedback from users like you help us shape and improve Eos for all productions. We receive a large number of feature requests and suggestions from many sources, including this forum. Your comments and votes help us understand which features you’re passionate about, but there are many additional factors which inform development prioritization for any given release.

The most helpful information you can provide us when commenting on issues is how a particular suggestion would help you. If you describe your use-case and how the suggested change would benefit your work, it lets us gain a much deeper understanding of the need behind the suggestion. Suggestions often have an impact on what we work on, even if we ultimately choose not to implement a suggestion exactly as it’s described. Our ultimate goal is to understand what you and all users need and to create solutions that meet those needs. Occasionally, that’ll mean implementing a suggestion as described, but it usually means working to understand the need behind the suggestion and how we can meet that need for as many users as possible.

While we endeavor to update and respond to popular suggestions, the volume we receive means there will be occasions when we can’t provide an update or response in a timely manner. For bugs and show-critical issues, please use our standard forums and support structures: https://www.etcconnect.com/Contact/Technical-Support.aspx

  • Linear Effect Scale Data

    • 1 Comment
    It would be great to be able to enter (+)#% or /# values in the scale box for linear effects. This would assist in creating linear effects that are relative to the intensity. That way we could change a channels intensity on the fly without having to adjust...
  • Delete cue with show control

    • 0 Comments
    An additional delete cue parameter that will delete both the cue and it's associated show control event(s). This could take the form of a CIA command modifier/softkey [Delete] [Cue] 10 {with events} and/or a setup defined default. In my workflow...
  • Having the Intensity, focus, colour, Beam and Soft Keys on the Touch Bar.

    • Planned for Future on
    • 1 Comment
    Hi, Very Similar to this https://community.etcconnect.com/control_consoles/eos-family-consoles/f/eos-family/23447/macbook-pro-touch-bar-custom-configuration but just moving the bottom row of buttons as above to the Touch Bar on relevant models.
  • Custom Augment 3D Fixture Models VIA GDTF/ User changable models for augment 3d.

    • 1 Comment
    Allow users to change the fixture model in augment 3d. Therefore the user can correct the incorrect models that exist within the library.
  • Custom Direct Selects Label in Tab

    • 0 Comments
    When I check "Use Select" in the custom direct select tab settings, I'd like the label to appear on that button. Currently it says "Custom # ".
  • AutoMark delay

    • 0 Comments
    Hello Please could you add the possibility to set a default delay to the AutoMark in the setup menu ? Thank you
  • Bigger Input box for Show Archive Box in Shell

    • Planned for Future on
    • 1 Comment
    When you go to edit the Show Archive Path (or Media/Model Archive Path) in the Shell, the box to edit the text above the keyboard has never been wide enough to show the whole file name. Can it at least be as wide as the keyboard? I think since I've...
  • Feature Request: Option to make auto mark mark earliest

    • 2 Comments
    In most cases, moving lights could move to its position, but automark forces it to the cue before the change happens. It would be great to have the option to make the move as early as possible.
  • Improved Design for Multi-Cell Lighting Fixtures within Magic Sheets

    • 1 Comment
    Magic Sheets are great but one aspect I have always struggled with is how to represent a multi-cell fixture that still enables direct control of the parameters I want to see when designing/controlling such fixtures. The problem: If you have a lineal...
  • OSC Custom DS

    • 0 Comments
    Custom DS should also available over OSC. There is a need to return also the DS type of the button.