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

  • Pixel Mapping- Intensity only

    • 3 Comments
    I've had a few projects now, where I would like the pixel map to only affect the intensity, so I can use colour palettes to mix the colour- the reason being, that for fixtures that have more colour parameters then RGBW, I can't achieve the same depth...
  • Alert times triggered by external Q triggers

    • 1 Comment
    Hello, This is a request from a trainee. They are running a show where cues are triggered by a mixture of manual Go presses, and OSC triggers from automation, and are finding it irritating that their alert times are only running if the cue is triggered...
  • If you submit say 20 new bug reports that get an EOS number you get a free TK10

    • 1 Comment
    Just an encouragement to submit reports
  • Apply Alert TIme as Follow Time

    • 0 Comments
    Since Alert Time finally made it's way from Cobalt to EOS, it would be great if a related feature would too: On Cobalt you can apply the recorded Alert Time as the Follow Time for the Cue. (Or multiple Cues at once). This would be handy on EOS as...
  • Alert Timing OSC Support

    • 0 Comments
    Hello, It would be a huge help for Nomad users and Companion users to have Alert Timing sent over OSC. For productions that want the structure of a Time-code show but need the flexibility of manual cue control, Alert Timing is amazing. Adding the ability...
  • Emergency marks that happen in a cue part with an existing Mark flag should show as "M+"

    • 0 Comments
    It's very easy to miss broken marks when their emergency marking happens in a cue that already has a mark flag on it. It would be great if emergency marks could always be attention grabbing in the cue list, instead of only when there isn't already a mark...
  • Cue Part Label Copy To/Move To

    • 2 Comments
    The following different syntaxes don't do anything or don't do what we intend them to do [Cue] [1] [Part] [1] [Copy To] [Cue] [2] [Part] [1] {Labels Only} [Enter] - does not copy the Part 1 label from Cue 1 to Cue 2 Part 1, instead copies the Cue 1...
  • 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.
  • Channel Lists should focus to most recent channel or not at all until [Enter]

    • 1 Comment
    Maybe this could be a user-level setting rather than a global change, but I struggle with the channel views changing focus while I'm building a channel selection. Usually (with some exceptions) while building a channel selection when [+] or [Thru] is...
  • Discrete timing: Fan percentages

    • 0 Comments
    Its great we can have percentages on time and delay but being able to fan say, [Group] [1] [Delay] [/] [100] [Thru] [0] [Enter]. At the moment obviously you can fan absolute delay and time but we cant on percentage. This'll make discrete timing revolutionary...