jasonhou Posted March 21, 2020 Share Posted March 21, 2020 Hello, I encountered this strange problem - the A3 key on the NI M32 keyboard triggers the Solo Button on a track (not the record armed track but a random track). Keyboard is automatically installed as a control surface in Logic and the firmware is the latest. What could cause this kind of problem? Thanks for your help. Quote Link to comment Share on other sites More sharing options...
Jordi Torres Posted March 21, 2020 Share Posted March 21, 2020 Hi, Incoming MIDI CC#3 will toggle the solo button on audio channel strips (whose track is selected though, not random), unless "Control Change 7/10 controls Volume/Pan of channel strip objects" is unchecked in Project Settings > MIDI > General > Miscellaneous. Although that setting only mentions volume and pan, other channel strip parameters (such as solo, mute and send level) also respond to specific MIDI CC's: CC3 = Solo CC9 = Mute CC28 and up = Send level J. Quote Link to comment Share on other sites More sharing options...
jasonhou Posted March 21, 2020 Author Share Posted March 21, 2020 Hi, Incoming MIDI CC#3 will toggle the solo button on audio channel strips (whose track is selected though, not random), unless "Control Change 7/10 controls Volume/Pan of channel strip objects" is unchecked in Project Settings > MIDI > General > Miscellaneous. Although that setting only mentions volume and pan, other channel strip parameters (such as solo, mute and send level) also respond to specific MIDI CC's: CC3 = Solo CC9 = Mute CC28 and up = Send level J. Thanks for the info! But the event triggers the Solo button is the Note-On of "A3". It doesn't triggers the focused track but another track which doesn't seem to have any relation with the focused track. I checked A3 is not used as a MIDI key command either, very strange. Quote Link to comment Share on other sites More sharing options...
Solution Jordi Torres Posted March 21, 2020 Solution Share Posted March 21, 2020 In that case have a look in your Controller Assignments Window, Expert View (Logic Pro X > Control Surfaces > Controller Assignments). You must have an assignment there causing this behavior. If you want to quickly verify this is the case, you can temporarily disable all control surfaces (Logic Pro X > Control Surfaces > Bypass All Control Surfaces). J. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.