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

  • PSD User data fields

    • 0 Comments
    PSD User data fields would be super useful, sometimes I would like to have a field/column labelled "Trigger" that would tell an operator where a trigger is coming from - OSC, MIDI, GO on Eos, analog input... Other fields could be labelled "Busk", as...
  • Allow FX values to be recorded into Palettes

    • 0 Comments
    Right now this is only possible with a workaround, having the FX stopped and with its exit being a stop and hold and stopping the effect. But this has issues in and of itself, and we should be able to just record the "pink" or light yellow value (from...
  • Bring MH gobo icons in to beam palettes

    • 0 Comments
    When you populate beam palettes with gobos from moving heads, can the icons that already exist in the head file be applied to the palette? Automatically or via button somewhere.
  • suggestion

    • 0 Comments
    i have some Q and suggestion on the magicsheet we can link to color or use color swatch on field like this. i hope to gobo also link or use goboswatch on feild. grand ma layout can do this. and etc also can develop easily.. or already have solution...
  • selective merge in A3D

    • 0 Comments
    I see there are questions popping up here and there, including mine about selective A3D merge as we have in patch. This would be extremely useful for merging objects from one model to another. Thank You
  • Keyboard shortcuts for camera views

    • 0 Comments
    In most 3D softwares, there's keyboard shortcuts for switching from top, side, right, etc. views. It's clumsy trying to navigate around when I can't quickly access the top view. Check out the Blender keyboard shortcuts. Maybe they need to be CTRL+[#]...
  • Save As Shortcut

    • 0 Comments
    Proposing an addition to the CIA's File menu. Below the " Save (D:\*file path*) " adding a " Save As (D:\*file path*) " targeting the folder the showfile is currently saved to. This would ease the process of saving iterations of your file without...
  • Sending OSC command to designated ports

    • 1 Comment
    It should possible to send an OSC command, e.g. of a Magic Sheet to a designated and configured ports. Some examples: udp:8001:/opta/relay=1 tcp:4707:/opta/relay=0 It would helpful to it with magic sheet command buttons also with String execution...
  • Keyboard shortcut or macro command to show/hide pop up ML controls

    • 1 Comment
    A quick way to show and hide the pop up ML controls menu for those who struggle to find the mouse cursor on our non touch screen monitors like myself.
  • Query Query

    • 0 Comments
    What if Query Query acted like select active, so it would filter to non-sub channels. IE: Query Query @ full would grab all chans at full filtering out the chans getting their value from a submaster.