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

  • Show Update Target in Command History

    Taylor C Jensen
    • Submitted on
    • 0 Comments
    Showing "Update" in the command history is not very useful, I would love to see what targets were actually updated. I want to know *what I updated*, to make sure I didn't update the wrong thing, and the only way to do that (after the fact), is to undo...

  • Patch Cleanup

    Jackmill
    • Submitted on
    • 0 Comments
    I spend an awful lot of time hunting down blank, useless channels in Patch and deleting them. It would be great to have a cleanup function that automatically gets rid of channels in patch with no address, no profile, and no data in the show file.

  • CopyTo multiple targets

    ChrDuda
    • Submitted on
    • 0 Comments
    It would be great if it was possible to copy to multiple targets. For example [Cue 1] [CopyTo] [5]+[8] All to often I find myself having to go to a cue and record to multiple targets, because CopyTo does not work in that regard.

  • Disable Macro

    kshih
    • Submitted on
    • 1 Comment
    Option to disable macro without having to delete contents or delete full macro. Helpful for organizing show file workflow - if you have magic sheets already made but want to disable functionality of a macro button without ruining the work of all the reference...

  • add icons to cues (like many other record targets) to show up in PSD

    ueliriegg
    • Submitted on
    • 1 Comment
    now that we have icons for many of the record targets, it would be helpful to allow them to cues as well. i'm aware that currently those icons are meant to show up in direct selects and cues don't exist there, but those icons could be a way how to add...

  • Auto-mark mode, Default Mark Earliest

    Jessica Drayton
    • Submitted on
    • 0 Comments
    Changing the default in automark to mark earliest instead of mark latest.

  • Restoring Rem Dim should follow Manual Time

    bev-fr
    • Submitted on
    • 0 Comments
    Currently, Rem Dim follows manual time when applied, but pressing Rem Dim again to restore the previous state happens in a snap.

  • Notes Columns for all Record Target Types

    stevendjlighting
    • Submitted on
    • 1 Comment
    It would be very helpful to have a Notes Column, as we have in the PSD, for all Record Target Types. Presets, Palettes, Macros, Effects, Snapshots, Magic Sheets. If we have a unique tab to manage a Record Target Type, it would be great to have a Notes...

  • Tab 99 > More clear indication of what triggered a specific cue or macro

    jolson
    • Submitted on
    • 0 Comments
    For example, was cue 2/2 triggered by a user pressing go, show control via list 1/ or 2/, OSC input, etc. It might be encoded in the data itself, but it isn't human readable.

  • Lay-Out SW keyboard should be a choice (apex or legacy)

    Theatermachine
    • Submitted on
    • 0 Comments
    The keyboard lay-out changed with the introduction of Apex. The software keyboard layout (as used in a tab or in the pop-up) should be mirroring the lay-out of the console or programming wing that you are actually using. If you are using the software...

www.etcconnect.com