Version
menu_open

Handling Conflicts in Control Surface Sessions

Multiple active bindings can conflict with their Controller Assignments. It is not possible to load multiple bindings to the same key simultaneously.

[Note]Note

Bindings from a Control Surface Session are loaded from top to bottom. When a conflict occurs, the first binding takes priority and only the first conflicting binding is loaded.

When a conflict is found:

  • A yellow triangle appears beside the group name in the Control Surface toolbar.

  • A yellow message appears beside the binding in the Control Surface Session view.

There are multiple ways to handle conflicts:

  • Reorder the bindings in the Control Surface Session view to change priority.

  • Use the shortcut menu on the binding entries to resolve the conflict.

  • Change the controller assignment for one of the conflicting bindings.

[Tip]Tip

In some scenarios, it might be useful to use the same controller assignment with different bindings in the same group. For example, you could create an Effect View Group that binds properties of different effects. Because the Effect Editor can only load one effect at the time, the bindings would never conflict.

Was this page helpful?

Need Support?

Questions? Problems? Need more info? Contact us, and we can help!

Visit our Support page

Tell us about your project. We're here to help.

Register your project and we'll help you get started with no strings attached!

Get started with Wwise