Begin with Default

The Default profile holds the assignments you want as your baseline. Put broadly useful actions here, such as volume or a frequently opened application.

An app profile changes only the controls that need a different behavior for that app. Unchanged controls continue to use Default.

Create an app profile

Open the Studio Pad editor and use the profile controls to add a profile for an installed application. Select that profile before assigning the actions you want to override.

For example, one key can run a writing action in your text editor while retaining its Default action in other applications. Choose shortcuts that are supported by the target app and test them there.

Understand inheritance

When a control is marked as inherited, its action comes from Default. Editing the Default assignment also changes what that control inherits.

A custom assignment in an app profile takes precedence for that control. Use Use Default to remove the override. Knob directions and the press action can inherit independently.

Edited and active are different

The editor stays on the profile you selected so you can finish configuring it. The active profile can follow the app in front when automatic switching is enabled.

After editing, focus the target app and check which profile is active. Leave the configuration view before testing a physical press.

If a key runs the right action in the wrong app, check automatic switching, the selected application, and whether the action is inherited or overridden.

Keep profiles manageable

Start with a small number of overrides. You do not need to duplicate every Default assignment into each app profile. This makes later changes easier to understand.

Before deleting a profile, review its custom assignments. Deleting it removes those overrides; it is different from clearing one control.