Understanding soft keys and making a soft key persistent across all scenes?

SQ SQ General Discussions
1

Understanding soft keys and making a soft key persistent across all scenes created after soft key created?

First, we tend to create scenes based on a previous scene, we very rarely create a scene from scratch. However, there are exceptions.

Second, I want to setup 2 soft keys, say 15 and 16 on SQ7, that will be driven my MIDI notes from an external device, to start and stop multitrack recording via sqdrive.

Here is the rub, once I create the recording soft keys, i.e. 15 and 16, that are explicit start and stop of recording, how do I make sure those keys are in every scene created after they are defined?

Can I save a scene that only has those soft keys defined, and they tell the engineers, when you create a new scene, also load the ‘recording key scene’ to reapply soft keys 15 and 16 but not completely over writing the scene just created?

2

The simplest way is ‘scene management’ as you have detailed. “Use this scene as your starting point for …”.

This sometimes works, but sometimes not. Just this Sunday, I lost a change I made a couple of weeks ago to our ‘default’ scene for the keyboard player who is trialling our ME-1 IEMs. Someone made a change for the drummer on Friday and assumed that the copy of the default scene that they took previously was still valid. Nope… OK, it was a simple fix once identified…

The other way is to look at global filters and/or scene filters. These permit changes to the soft keys to be ignored on a scene load.

This is different to user permissions that prevent the soft keys to be modified.

Dave

3

Yes, you outlined the specific key (sorry for the pun) concern I have, that someone will use the ‘wrong’ scene as a starting point, or create a scene from scratch, such that defined soft keys are lost/missing from that point on.

Below are the scenarios I see typical in scene development:

  1. Create scene 1, includes defined keys

  2. Create scene 2, from scratch, keys lost, since never created

  3. Create scene 3, based on scene 1, keys retained

  4. Create scene 4, based on scene 1, filter set, keys lost

I do not recall seeing the user permissions in the documentation per se, but will look again. As I see it, there is no way to protect the soft keys, if they are never there, such as in scenario 2 above. Is my understand correct? Or are user permissions global to all scenes? Soft keys can be made global to all scenes?

4

Go to Scenes / Global Filters / Other. You can block the soft keys and rotaries from changing.

It’s in the manual.

5

Don’t confuse user permissions with filters.

We have an administrator account (with a password) that has access to everything.

We then have an AV user (with a password) with slightly more limited features (e.g. our default scene is outside the range of scenes that they are able to modify). We have limited access to a few other things that we don’t want people playing with.

We then have a GUEST user (no password) with a different default scene to the AV user and extremely limited features. This is a ‘plug and play’ scene (for example) with a keyboard, guitar, a couple of singer microphone a background music channel, handheld microphones and a headset microphones.

User permissions stop the logged on user from doing things, not making things global.

Filters (scene and global) stop things from being recalled over the top of a previously loaded scene or whatever you have set on the mixer currently.

Filters can’t ‘magic’ a soft key configuration out of thin air for example.

Dave

6

Thanks for the qualifications and clarifications.