Personally I don’t like “restore on power on” in most cases.
We use it at church - the Roland boots into scene 00, which is locked (so it doesn’t get accidentally overwritten)
Scene 01 is the “scratch space” - this is where we all save the working state of the desk as we build the weekends setup.
If we need to save a setup off for a future event then there are hundreds of available scenes to use.
When I’m out gigging I load a scene, and want it to stay as set in the event of power glitches.
If I had a QU at church I would have a softkey set to “load scene 0” or similar.
if you touch a fader the scene content is already altered so the state has from now on nothing to do with the scene content
so it makes no sense to show last recalled scene after a reboot
if you need to start with a defined state then recall a scene at startup
Potentially then the “recalled scene” should be greyed out or something the moment anything is changed. Then you would recall with a greyed out 1 there (or, better still, nothing)
This has gotten way too complicated verses my original intent in mentioning it.
All I am saying is this. I think it would be better if the console booted up displaying in the scene window the last scene it was on at shutdown and that scene also displaying in the lower part of the screen. Whether or not any changes have been made. Sure last state can remain. It’s not recalling only displaying. If the operator knows that he can choose to recall the previous saved version of that scene or proceed from that point.
How hard is that? It’s just a logical thing that I left on scene 10. Boot up. My display shows scene 1. Makes no sense to me.
This has gotten way too complicated verses my original intent in mentioning it.
All I am saying is this. I think it would be better if the console booted up displaying in the scene window the last scene it was on at shutdown and that scene also displaying in the lower part of the screen. Whether or not any changes have been made. Sure last state can remain. It’s not recalling only displaying. If the operator knows that he can choose to recall the previous saved version of that scene or proceed from that point.
How hard is that? It’s just a logical thing that I left on scene 10. Boot up. My display shows scene 1. Makes no sense to me.
Dug this thread up searching if there was a solution -for whatever reason- wanting the source of 'Scene 1' available upon start up.
Between two QU's, several varieties of scene setups -live gigs, live record templates, in home studio templates etc and sometimes flipping through track layouts or names to ID the template (scene).
I agree a simple asterisk or such on the 'source would be plenty. But as I presume there will be no further updates on the QU(?).. I think I found a solution.
To bad we're restricted to six digits names in the mixer but a next best workaround;
Name 'Mix LR' with with the template's scene number.
It comes up in two button pushes, 'select LR' and either Processing or the Routing pages.
At our gig last night I was using my ‘Default indoor’ scene (scene 4) for our band. Everything seemed fine, however we tripped the noise limiter (which had an absurdly low limit, it was a family party at a social club and we’re not loud!). When power was restored we had weird issues, there was feedback/ringing even though all channels and all mixes were muted (including LR). Anything with a compressor ‘ON’ gradually went into max compression (red vertical bar) one channel at a time over a minute or so. It seemed to have some internal feedback going on. I first switched off all compressors then in a panic I decided to reset and did a controlled shutdown. We got going again and managed fine (very quietly). Only later I went to the mixer intending to save the scene as a new ‘indoor quiet’ scene did I realise that the mixer ‘current scene’ field was blank (I had forgotten to re-select a scene) and the ‘next scene’ field was set to scene 1 (default outdoor).
So a couple of questions…
After a power interruption where, according to other comments, it should have reverted to the previous scene, why did I get those weird issues which weren’t there before? (I can’t recall what scene was ‘current’, if any, at that point.
After the controlled shutdown, power-up doesn’t result in any scene being selected, and I forgot to select one, so what ‘state’ would the mixer have been in if ‘current scene’ was blank?
The QU normally always starts up in its last state that it was shut down in previously. I have had instances were power has suddenly been lost, but my QU has always restarted in its last state regardless of whether I had saved it or not. It might not necessarily show the correct scene name, but it is always as I last left it.
our church seems to get the last scene with any tweaks that were in use when the Qu was powered off through the correct sequence on the screen in the upper right
our MD has instructed us to sign and then ALWAYS select scenes and recall the one that we are supposed to use that day/night
which resets to the master default that he and the dealer set up to avoid problems and simplify use for volounteers
I think that what ever tweaks the last operator had used would come up with the scene that they had been using so we need to restart fresh to be sure
That makes sense, particularly to avoid a lot of [perhaps] 'unwanted drift (as opposed to ‘work in progress refinements’…) once you’ve established your good working templates.
I use the Qu-Pac at my church, with a Raspberry PI and a Unifi AP plugged on the same network. The Raspberry Pi and the Qu-Pac are turned ON at the same time. I attach a script I made to force scene 1 reload at each startup using MIDI over TCP commands.
qu-init-scene.service is to be copied in /etc/systemd/system
qu-init-scene.py is to be copied in /home/pi/bin (create the bin directory if missing)
Then login to the Raspberry and enter this command:
If you turn on qu16 the next day after rehearsing the show, it is difficult to know which scene is based now. Sometimes I try not to remember which scene I used during rehearsals. If you press the scene button while the power is on, I hope that the screen is focused around the last scene used, and even if I press scene after turning it off and on, I hope that you will show the surroundings of the scene you used at the end, and that the scene you are currently using will somehow be displayed.
You are never ‘in’ a scene, or working directly on a scene.
There is only one current state of the mixer and storing a scene stores all the settings from this current state into a scene slot.
Recalling a scene replaces all the current settings with the settings from the scene slot (depending on filters of course).
So you are always only ever in the current state, and it’s this state which is remembered when turning off and later powering on the mixer too.
The mixer doesn’t know after a restart what the last scene you recalled was, and as soon as you make any changes the current state will no longer match the stored state either, so it could be very misleading to tell the user the last scene recalled prior to shut down.