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

  • Fade Area at the edge of Zones in Augment3d

    • 2 Comments
    A 'fade out area' for Augment3d-Zones would be great. You could set it to a specific distance, so a beam that touches the zone fades from it's current intensity to zero as it moves further into the zone.
  • Add "Field Angle" as an MVR option

    • 0 Comments
    When importing from an MVR file (specifically from Vectorworks) you are locked into Beam Angle as the field that aligns to the Augment3d Beam Angle. But in Vectorworks language, that should really be field angle. Would love the option to choose either...
  • Constants in absolute effects

    • 0 Comments
    Currently I can assign a variable as a timing for an absolute effect but if I do so I can no longer adjust the cycle time of the effect. I would like to propose the idea of a constant for timing that can be defined and is unchanged if I change the cycle...
  • Add in patch copying to part channels

    • 0 Comments
    In patch chan 82 part 1 <copy to > chan 82 <part> gives Error: Syntax error I would have expected to be able to duplicate a fixture on a channel.
  • 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...
  • At Boot NPs Should Go To Home Position

    • 0 Comments
    At boot the console sends all NPs to library default, instead of the home preset. You have to sneak enter with no manual data to get them to be in the correct position, they should automatically be here when the console launches. If I wanted the profile...
  • Query for Fixture Selection in A3D Edit

    • Under Review on
    • 2 Comments
    Hi there, Is it possible when in A3D Edit mode to query fixtures by type? If not, could it be so? Thanks!
  • Raw data values and Palettes both work in a single command line

    • 0 Comments
    [Group] (31) [Focus Palette] (3) {Intensity} (0) [Sneak] (6) [Enter] will not work. [Group] (31) [Focus Palette] (4) {Zoom} (100) [Sneak] (1) [Enter] will not work. Only the raw data will execute. All data needs to be contained in a palette for the...
  • Prohibit user from advanced merging past target limits

    • 2 Comments
    My venue had a crash of the console caused when doing an advanced merge. The merge was passed the bounds of the target limits. In this case it was: Submasters: Start 900, End 999, Target 1000 When a user attempts to merge past a targets limit...
  • Implicit OSC Timecode Output

    • 0 Comments
    As part of the implicit OSC output, include the timecode of the cue, if applicable