This means that you set Master Keyboard Input to a track in the sequencer to route the control surface(s) to the track’s device in the rack. You can bypass this functionality by locking a control surface to a specific device - see “Locking a surface to a device”. Or you can simply use Remote Override mapping (see “Remote Override” for specific parameters - these will then be mapped to the selected controls regardless of Master Keyboard Input.E.g. if a Subtractor has Master Keyboard Input, your control surface will control the most important Subtractor parameters. If you set Master Keyboard Input to a track connected to an NN-XT, the control surface will now control parameters on the NN-XT device, and so on for each device. There are standard mapping variations for most devices as well - see “About mapping variations”.If you do not have transport controls on your control surface you can still map transport controls to controllers using Remote Override mapping - see “Remote Override mapping”.If you use Remote Override mapping (see “Remote Override”), the overrides will be saved with the current song, but won’t be there if you create a new song.The “Control Surface Details” document contains some information about the standard mappings of the different control surface models. But you can also activate Remote Override Edit mode to see which parameters for each device are mapped to your control surface(s) - see “Remote Override”.This is not a conflict of any kind, but simply a consequence that stems from the fact that all control surfaces by default follow Master Keyboard Input. By using Surface Locking (see below) or Remote Override (see “Remote Override”) you have full control over your control surfaces.
Locked devices (see “Locking a surface to a device”) can also be locked to a specific mapping variation.