[StonepianoParticipant]

One more detail- maybe someone knows if this is normal:

If I recall a scene, the bottom row shows the recalled scene twice, for it to be both “curr” and “next”. I need to give the scene recall go an extra push in order to get to a place where the actual next scene is queued.

[StonepianoParticipant]

I did it a while back, and it solved a couple of problems I had at that time. Thinking of doing it again, I have the show stored on a USB-key, but since I can´t trust the console, I´m a little bit hesitant to rely on a complete show to load correctly…

[StonepianoParticipant]

Let me give you an example of my console´s behaviour:

– I send FX2 return to mix 5-6 on a scene
– I move to the next scene, where no such setting has been made, but the FX-return fader is up there, in the same position as I put it in the previous scene. No Filtering, nothing safed. This can´t be right. Mind you, I most definitely know what scene I´m on, because they have a name and a number to go with it. Have no duplicate scenes. And I only have this one particular scene, where I´m sending the return to this particular mix. But it remains there, in all consecutive scenes- I have to remove it manually at every scene-change.

Perhaps another one: I send FX2 to an input channel, store it -by the book- move to the next scene, all other parameters, mutes and such, change with the scene, but the FX-send is sticking in there like a sore thumb. And it never was stored in that following scene.

[StonepianoParticipant]

The manual actually says: “RECALL- Touch this button to instantly recall a scene, overwriting the current settings.” What the Heck do they mean by this? Don´t want to overwrite anything by just recalling a different scene. There´s some “wording” right there…

But OK, am I really become so confused by all this, that when I press “scene recall go”, highlight the current scene, recall it once more at the touchscreen, press “store” and confirm the overwrite to a one specific number of a scene, I am actually working on something else? Is this really what you guys are trying to tell me? Come on…

[StonepianoParticipant]

Yes Dick, you are grossly mistaken if you think I don´t know how to recall a scene.

[StonepianoParticipant]

… and when I press that friggin´ “store”- button, the dialogue asks me to confirm the overwrite, and the scene number and name matches with the currently recalled scene. So there you have it.

[StonepianoParticipant]

There has been quite a lot of complaints about the confusing logic surrounding the scene memory logic in these forums. I´ll try once more to set this straight:

– I have my “scene next”-softkey set up to be “scene recall go/auto increment on”
– When I press next, recall/store/clear on the right side of screen for the queued next scene, bottom bar shows
current/next
– I now highlight the current scene from the list, and press “recall”, the right side now shows the name of the current scene
– I press “store”, thinking that I am now storing the scene which appears as “current” on both sides of the screen
– After “storing” bottom bar indicates both “next” and “current” to be the same, with same scene-number
– I now press the softkey again. and now bottom bar shows the current scene and the next
– The end result: some of the sends are not stored

I have read the manual inside & out, but it still won´t tell me, why all my eq, comp/gate, fx type/parameter- settings follow scene changes, but some fader sends do not? At the moment these include FX2 input channel sends (FX1,3 & 4 work), FX1 & 2 returns, FX1 & 2 returns to mix 5-6. All mono mixes follow scene changes, as do all master sends.

So just tell me this is not confusing! I have 50 more shows ahead of me, and there is just no way I´ll “start all over again”, 47 scenes with radical parameter changes…

P.S. It is still ridiculous, that softkey assignment “scene previous” cannot be “auto incremented”. You press previous, and you have to recall it from the touchscreen, obliterating the whole idea of a quick recall. If you need to go back to a previous scene, it´s usually in a situation where it needs to be done fast.

[StonepianoParticipant]

Well, as previously mentioned, I have my scene recalls on a softkey (10). Now, if I tweak settings on a particular scene, and highlight it from the list, it then appears as the current scene on the right-hand side of the screen, where you can then store the settings, supposedly. I press store, and the bottom bar indicates the same scene twice, don´t know why that is? So I press next once to actually queue the next scene. Sometimes, somehow my fx sends I made for the previous scene remain on the next recalled scene, among some other sends. Nothing else is filtered, but the softkeys, no safes on anything. When I return to the scene I originally wanted to adjust, the settings I made are not there.

So please shed some light on what am I doing wrong here?

[StonepianoParticipant]

Here in Europe we can order one ,made to measure, from Thomann, 229€. Has a little doghouse too for the AC-cord and the lamp.

[StonepianoParticipant]

All these irritations are a shame, the desk is very straightforward to do the actual mixing on, and it sounds nice, too. Fallen in love with the EMT- emulation. 480 not half-bad either.

[StonepianoParticipant]

It’s not just you- I’ll add in the utterly counterintuitive scene recall/store functionality, with excellent capability to overwrite the wrong scene. Workflow interrupted, because you have to remind yourself that the console is one step ahead of your current activity. Easily remedied, would suppose?

[StonepianoParticipant]

Anything & everything that makes better use of the screen real-estate. Could be prettier also… streamlining the scene recall-logic is high on my list.

[StonepianoParticipant]

Yep. There are reasons for an update. It is a bit irritating, that the customer has become a beta-tester… this applies to all things digital nowadays.

[StonepianoParticipant]

Thanks guys, I think I’ll postpone the update until my present gig is over. Especially when today, the USB- connection died. For both a key and the hard-drive, both formatted and not used for anything else but Qu. I’m pretty sure the connection will wake up tomorrow, when I boot the console, but nevertheless… the update shall wait until january.

P.S. I’ve gotten to terms with that scene recall- stuff, but it still sucks, Big Time. If someone really likes to work like that, I suggest he consult a doctor

[StonepianoParticipant]

@mervaka- I´m finally learning to live with the Qu logic, but I really do not understand why you would like to tweak something that´s going to happen in the future, and not the situation at hand? It is the storing-function that bugs me, I´d like to concentrate on what I´m actually hearing at the moment, not on thinking that I´m storing the settings on the “next” something…

P.S. I don´t particularly care about what you think.

[Author]

Posts