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

  • Focus for Conventionals in Augmented3D

    • 0 Comments
    There should be a way to focus conventonal light using XYZ coordinates because sometimes i found the point and move option makes it hard to get really accurate.
  • Feature Request - same timeformat as Timecode all over the board

    • 0 Comments
    Hello, i love to have the ability to notate time always in HH:MM:SS.MS For example in Cues... That will include to have more than 99min and 59sec as max cue-time and other max time values i don't know of jet. Thanks a lot. thilda
  • Feature Request - see rate/size /etc of FX altered via Global FX-Master

    • 1 Comment
    Hihi, i would love to see the current rate/size/etc of a running FX while using a Global FX-Master. Thanks you very much thilda
  • Type Focus Points for Conventional Fixtures in Patch

    • 0 Comments
    Hopefully not a duplication; Is it possible to create a way to type focus points for conventional lighting into patch? So that known focuses could be key-ed into the console? Thanks!
  • Settings request: number pad factor of 10x or not

    • 2 Comments
    Hi! I'm sure that this has been mentioned before, but for those of us who work in film and television and are regularly using extremely high-powered LED fixtures close to the action, being able to hit [channel 1] + [at] + [3] + [enter] and having the...
  • Shutters order and Augment3d

    • 4 Comments
    Hi Everybody A question about how to manage the shutters' order with Augment3d : I used to change the order to have the A one upstage, C one downstage, B one Stage Left and D one Stage Right. This system is really useful to play with shutters. The...
  • A3D - Ability to Ignore Addresses in VW Import

    • 0 Comments
    I might be missing something but it seems when you import into A3D from VW 2020 there is no way to ignore the addresses of the incoming VW file, which is mostly an issue because it will knock out the patch in EOS if you've made a mistake in VW and there...
  • Augmented Tab Options - Create Pixel Map from...

    • 1 Comment
    Probably on the list already but would be nice if the "create pixelmap from Magic Sheet" and "create magic sheet from pixelmap" were located on Tab 3/9 respectively... Super powerful tool though! They're going to save me hours of pixelmap layouts...
  • Feature Request: Ability to Customize CSV export of patch and correction for multicell fixtures in CSV

    • 1 Comment
    I use the CSV export of the patch to make fixture labels these days. It would be lovely to be able to choose which fields are exported in the CSV (for example, I only use Channel, Address, Type and Notes). Also, it would be useful to be able to export...
  • OSC get channel value

    • 0 Comments
    Please do it OSC command to get channel or address value from any cue by OSC command. Like: /eos/get/cue/<cuelistnumber>/<cuenumber>/<channel>/value response will back value of intensity, color, beam, ... I think it is basic function and it is frustrating...