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

  • Select Manual "User" Modifier

    • 0 Comments
    Hi all, Suggesting the addition of user filtering to the [Select Manual] keyword. It would be useful in some environments to have the ability to select manual values generated by specific users. I could see this as the addition of {User} to the soft...
  • Custom ML Control Profiles

    • 0 Comments
    Hi! Now that modern moving lights and other LEDS have tons of attributes and us designers don't actually use most of them, I was thinking it might be cool to add some level of customization profiles to the ML controls. And these profiles could be different...
  • Magic Sheet, increase field items

    • 0 Comments
    It would helpful if you increase the number of field items. 6 items are less for using parameters and categories. May the field items could dynamically.
  • [Copy To] {Plus Show} Should Optionally Exclude By-Type Palettes

    • 0 Comments
    Hi! Currently (in Eos 3.2.5) in patch, using [Copy To] with the {Plus Show} modifier copies all data from the source - including referenced data that was not discrete, making a data discrete in palettes that are otherwise exclusively by-type. I believe...
  • sACN input not only to submasters but also to faders

    • 0 Comments
    Hey there, I'd like to map sACN to Faders. In our youth theatre ensemble we have got an old Element. It can't upgrade to EOS 3. But I'd like to use my nomad with Augment3d and all these new EOS 3.x features. Element has 40 faders I'd like to use. I...
  • Remove parenthesis in offset option.

    • 1 Comment
    If I have a lot of fixtures, I may want to select 4th fixture, then every 4th+1 fixture. This is useful in instances where you are fanning an array or grid of fixtures and want to create interesting curvy looking beams using pan/tilt, but do not want...
  • New Magic Sheet field to indicate source

    • 0 Comments
    Requesting the addition of ‘Source’ as a field in magic sheet symbols, as lifted straight from the ‘About’ channel CIA display. Really useful for studio and event contexts where we’re running shows off a mix of subs and cues and want to quickly read...
  • Add Meters/Feet Unit in X Y Z focus and "Meters/Feet per rev" option in manual control for encoders

    • 1 Comment
    Hi, i tried to change units of X per rev for encoders in user setup. Only way to achieve this is to edit X focus in Fixture editor and apply a "D" unit to X Focus. It would be better to have meters or feet by default for X Y Z parameters and resulting...
  • Tab Navigation for Macro Editing

    • 2 Comments
    In order to change tabs in a macro there needs to be a TAB_DOWN [#] TAB_UP but that can only be done when recording. It would be really great if it could be added after the fact, if forgotten. What brought this up for me was trying to make a patch macro...
  • "Only Merge Augment3d XYZ Location" - its without the Augment3d Data in CIA (Beam Angle, Beam Edge.....)??

    • 1 Comment
    Hi, the new function "Only Merge Augment3d XYZ Location" is great, but the Merge is without the useful self stored data in the Patch Augment3d CIA Tab ( Beam Angle, Shutters, Beam Edge..... and so on). Please include these things also in "Only Merge...