Default scene startup

[volounteer]

@garyh

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

[mixsit]

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.

[barberousse]

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:

sudo systemctl enable qu-init-scene.service

Attachments:

You must be logged in to view attached files.

[soundfancy]

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.

[KeithJ A&H]

@soundfancy

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.

Thanks,
Keith.

[Author]

Posts