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

  • Edit attributes visible in real time on Augument3d..

    • Under Review on
    • 0 Comments
    Hi Currently when you edit attributes, in patch, to fixture, the fixture go to home position ... in the case of edit pan and tilt I think it would be more immediate to choose the edit if you could immediately see the result on Augument3d... currently...
  • Magic sheet color selection

    • Under Review on
    • 2 Comments
    Make it easier to change colors in the magic sheet. Two suggestions: Change the top row of color selection to be "white," "blacK" and the last six colors I chose manually. Use the ML color picker to choose a color (including the swatch books, so...
  • Implementation of QR-Codes in aRFR/iRFR.

    • 0 Comments
    i work in a theater with a lot of guest performances. I´m use my rfr app for focusing. I think to be quicker, it would be nice to scan the QR Code of a circuit (installad for the TPSR App) to select circuits to Highlight or ML-Control for the device....
  • Order Fixture along as in a3d

    • Under Review on
    • 2 Comments
    You could add in option in the offset tool that says "order all the fixtures as they are ordered in argument3d". I think that´d be one of my favourite options in eos.
  • Pull gobo and shutter information as a raster from a camera in real time

    • Under Review on
    • 1 Comment
    If the user put a piece of paper behind the shutter assembly of a leko at their desk and backlit the paper from where the lamp would go, perhaps a camera or webcam could be pointed at the 3" aperture of the shutter assembly and, with the contrast boosted...
  • PixelMap Layers - include "stacking order" property

    • Planned for Future on
    • 1 Comment
    Hello It would be great if I could change the stacking order of a layer on the fly - I often have the need to fade between a number of different images, and since I am limited to 12 layers I have to do some messy trickery once I get past image 11 to...
  • Magic Sheet tombstone

    • Planned for Future on
    • 1 Comment
    The Magic Sheet tombstone should be modified so that it matches the Live Summary tombstone. In particular: Color swatch should not go behind the intensity value (so intensity colors still work - green, blue, white, magenta, etc) Same thing for...
  • 2.9.1 and 3.+ on Same Machine issue

    • Planned for Future on
    • 4 Comments
    So this is an interesting problem that isn't really a bug, but just something that I think will need to be dealt with eventually. With 2.9.1 and 3.0 on the same machine (Nomad on PC), if 2.9.1 is accidentally (or sometimes purposefully) opened in client...
  • [request]{Query} [at] # should return all instances of that level

    • Planned for Future on
    • 2 Comments
    {Query} [at] # should return all instances of that level even if that level comes from a palette or preset.
  • Add an option to allow cue playback to override whatever is captured in the command line

    • 0 Comments
    I was thinking primarily of a busking scenario where I could use direct selects to select groups and apply palettes but would still want a go command to take me to a known state. Another might be to ensure a blackout is always able to take full control...