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

  • VMS Update

    • 0 Comments
    The advancement of integrated graphics on the new Intel and AMD chips seems like a great opportunity to add some features to the VMS. I would love to see 3D pixel maps built within Eos in addition to complex shapes much like what Enttec ELM can do.
  • Feature Request: Outlined Font for Magic Sheet Text.

    • 0 Comments
    Feature Request: Outlines for Magic Sheet Fields. Reasoning: Outlines help me see better, I like magic sheets. I made a sample picture. Thanks!
  • Storing rate and size values modified by faders

    • 1 Comment
    Hi, I would like to able to store in the cues the size or rate of an effect while modifying them by a fader
  • Feature Request A3D - Conventional Focus Input Method

    • 2 Comments
    It is possible to get a way to key in the focus point of conventional lamps XYZ in patch, rather than mouse clicking.
  • OSC Fader Improvments

    • 0 Comments
    It would helpful also to get some configuration data from the Faders, e.g. labels of the "Fire" and "Stop" button and also the "Fader Type" like Master, Effect Size, Effect Rate ... Maybe something like: /eos/out/fader/<index>/<fader index>/config which...
  • [Load] + [Go]/[Back] to load pending cues

    • 0 Comments
    This would essentially be a Go/Back-Shortcut for the pending cue. Allowing us to quickly skip to a cue without having to type it in first. Sometimes you have to skip one or more cues quickly, but you still want the marks to happen for example.
  • DS Millennial Button Labels respect || for carriage return.

    • 0 Comments
    I would like it if millennial button labels displayed text the same way DS tiles do when double pipes (||) are added to labels.
  • focus traditionnal fixtures as moving lights in augmented

    • 2 Comments
    hello, as it seems very fastidious to focus trad incrementing datas, would it be possible to focus them same as in wyg, as if they were moving lights? using rotations makes it really too long and imperfect, so i don t waste time on it, but would be a...
  • Order Fixture along as in a3d

    • Under Review on
    • 2 Comments
    You could add in option in the offset tool that says "order all the fixtures as they are ordered in argument3d". I think that´d be one of my favourite options in eos.
  • MSC TX ID per Cue List

    • 0 Comments
    Assign an MSC TX ID on a Cue List Basis so that a cue list can be dedicated to a particular destination rather than having to set it globally for all MSC sends.