Parameter Lock and Shortcut buttons

[richkeys]

The Parameter Lock feature in Utility does not have an option to lock in Assignable Button and Live Control Knob settings system wide? I am finding when I load in a different registration that didn't include my shortcut settings I am frequently having to re-assign the short cut buttons again and hopefully remember to save them into the registration. Is there a way around this? For now I don't need my shortcuts to be part of Registrations, I want it to be system wide.

Rich

[Fred Smith]

The Parameter Lock feature in Utility does not have an option to lock in Assignable Button and Live Control Knob settings system wide? I am finding when I load in a different registration that didn't include my shortcut settings I am frequently having to re-assign the short cut buttons again and hopefully remember to save them into the registration. Is there a way around this? For now I don't need my shortcuts to be part of Registrations, I want it to be system wide.

Sadly, no. The best you can do is create a setup registration that sets the keyboard the way you want.

When you find a registration that changes your assignments, re-memorize it unchecking the Assignable box. Then load your setup registration to restore your assignments.

Eventually, you'll have your registrations trained to do what you want.

Cheers,
Fred

[richkeys]

Sadly, no. The best you can do is create a setup registration that sets the keyboard the way you want.

When you find a registration that changes your assignments, re-memorize it unchecking the Assignable box. Then load your setup registration to restore your assignments.

Fred,
Yes, just watched your setup registration video. Since I am at the very beginning of building registrations it makes sense then to do that first, then save new ones off that setup registration always checking the Assignables I guess.

I'm not sure I understand your second comment. What does unchecking the Assignable box do when re-memorizing? And then wouldn't loading in the setup registration delete the contents (styles, voices, mixer) of the current registration I was on?

Rich

[Fred Smith]

I'm not sure I understand your second comment. What does unchecking the Assignable box do when re-memorizing? And then wouldn't loading in the setup registration delete the contents (styles, voices, mixer) of the current registration I was on?

Rich,

Next time you press the Memory button, stop and look at the screen. Take 5 minutes to check it out.

Each box represents a group that will be memorized, or not, depending on whether the box is checked. If the Style box is checked, the style will be memorized, and loaded when you load this reg. If it's not checked, the style won't be memorized, meaning that when you load this reg, the currently loaded style will not be changed.

Same thing with the Assignment buttons. If the Assignment box us not checked when you memorize the reg, then it won't make any changes to your "shortcuts".

Cheers,
Fred

[richkeys]

Fred,

I understand what the Memory check boxes are and what they memorize. I need to understand the specific procedure you stated. "Re-memorize a registration with the Assignable unchecked." Understand that part. The next step "load the setup registration to restore the Assignables" is not clear to me. That will pull up the generic registration I made with the correct Assignables that I want, but how does that bring those Assignable settings into the previous registration that had the incorrect Assignable settings? Am I misinterpreting this? If you can't explain further, I will just play around with it.

Rich

[Fred Smith]

Fred,

I understand what the Memory check boxes are and what they memorize. I need to understand the specific procedure you stated. "Re-memorize a registration with the Assignable unchecked." Understand that part. The next step "load the setup registration to restore the Assignables" is not clear to me. That will pull up the generic registration I made with the correct Assignables that I want, but how does that bring those Assignable settings into the previous registration that had the incorrect Assignable settings? Am I misinterpreting this? If you can't explain further, I will just play around with it.

Rich,

It doesn't "bring those Assignable settings into the previous registration". It will simply, as you say, load the "correct Assignables that I want". And once they're loaded, they won't change because you re-memorized the offending registration to tell it not to.

Cheers,
Fred

[richkeys]

Thanks, Fred. I understand the concept now and the knowledge will help before I start building registrations. The way the registrations work takes a little getting used to.

Rich