Soft Key – Current Scene persistent indicator

Forums Forums Qu Forums Qu feature suggestions Soft Key – Current Scene persistent indicator

This topic contains 3 replies, has 3 voices, and was last updated by Profile photo of SteffenR SteffenR 1 week, 3 days ago.

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #102407
    Profile photo of ehud42
    ehud42
    Participant

    First question: The current QU firmware (1.95) is a few years old (July 2018). https://www.allen-heath.com/qu-series/qu-24/#software

    What is the honest likelihood of a feature request today being implemented in the next few months?

    Second question/point: The Feature Request

    Noted in the SQ forum (https://community.allen-heath.com/forums/topic/better-use-of-led-of-current-scenes-soft-key)

    When a Soft Key is assigned to a scene, then when that scene is selected (by soft key or menu)
    * Have the Soft Key light up and stay lit as long as that scene is active
    * Have the Soft Key blink when a change is made on the console that differs from the configuration stored in that scene.

    (I rented a Zoom L-12 earlier this year before purchasing a QU-24 and that’s how their Scene buttons work – very easy to see at a glance where you are and if you’ve deviated)

    #102418
    Profile photo of SteffenR
    SteffenR
    Participant

    * Have the Soft Key light up and stay lit as long as that scene is active

    You change one parameter and the scene is not active any more.
    Free your mind from this scene oriented thinking…

    You can change all parameters (from the console and from all possible remote systems) and the last recalled scene (that’s actually the scene you are “working on”) will still be the same

    #102419
    Profile photo of Mfk0815
    Mfk0815
    Participant

    Hmm, maybe its time to free yourself from the narrow mind that what A&H has implemented and you voted for the best solution ever, is also the best for others. Imagine that some of us, me too, will use scenes like a document, as you will use on your PC at home. You can load that document/scene into the processor/mixing console and manipulate that document. Then you want to simply save that changes with the same name on the same place in the storage. Thats why applications on your PC knows where the document is loaded from an also present that information to the user. If the document is modified in the application this might be shown too. You can delete or rewrite the whole content of the document, then name remains the same. So, why do you ever think that the same behaviour is not handy or needed on a mixing device? What are the great benefits to loose that information right after loading the scene? Why should it be not ok that A user can load a scene, modify some few parameters and is able to save it to the same place of the storage without the need to „remember“ that scene name and location outside of the console? And why you always think your way of thinking is the only right one?

    #102423
    Profile photo of SteffenR
    SteffenR
    Participant

    If you are used to a scene oriented show you should be able to see the scene you are “in”
    but I think this is not needed at every screen or with blinking lights.

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.