emanuel_froes Posted March 22 Share Posted March 22 Does any one knows this? Quote Link to comment Share on other sites More sharing options...
David Nahmani Posted March 23 Share Posted March 23 What are you doing exactly when this window pops up? Quote Link to comment Share on other sites More sharing options...
emanuel_froes Posted March 28 Author Share Posted March 28 hi David! sorry for the late reply i was doing what ever, editing, recoring, all. Nothing especial. The peroblem disappeared then came back for a while andd now it is good again. No key command is set wrongly for this Quote Link to comment Share on other sites More sharing options...
David Nahmani Posted March 28 Share Posted March 28 It looks like your control surface window is in learn mode when you click a button or fader in Logic. You can choose Logic Pro > Control Surfaces > Controller Assignments and make sure the "Learn Mode" button at the bottom right is not enabled (gray and not blue). Now when you click something in Logic you shouldn't get that pop-up window. Quote Link to comment Share on other sites More sharing options...
Solution JakobP Posted March 28 Solution Share Posted March 28 (edited) Seems you're trying to learn a plugin parameter from a midi fx plugin, e.g. the Modulator, and then tweaking parameters that aren't automatable... Edited March 28 by JakobP 1 Quote Link to comment Share on other sites More sharing options...
David Nahmani Posted March 28 Share Posted March 28 3 minutes ago, JakobP said: Seems you're trying to learn a plugin parameter from a midi plugin, e.g. the Modulator, and then tweaking parameters that aren't automatable... Oh now you're getting somewhere! 😄 So it could be that the parameter is not automatable, OR that the parameter is one from a plug-in that is before the plug-in that is in learn mode. So scratch what I was saying @emanuel_froes - this issue is due to a MIDI plug-in that is in learn mode. For example: 2 Quote Link to comment Share on other sites More sharing options...
emanuel_froes Posted April 5 Author Share Posted April 5 On 3/28/2023 at 1:53 PM, David Nahmani said: Oh now you're getting somewhere! 😄 So it could be that the parameter is not automatable, OR that the parameter is one from a plug-in that is before the plug-in that is in learn mode. So scratch what I was saying @emanuel_froes - this issue is due to a MIDI plug-in that is in learn mode. For example: Thx DAvid! Yes, what happened was that i left this "open" and somehow the project file of template saved this. Since the template is big, i could not find the cause of the mistake. I forgot to mention, now i remember , i was doing that modulation trick 😉 1 Quote Link to comment Share on other sites More sharing options...
David Nahmani Posted April 6 Share Posted April 6 Great! It's really @JakobP we should thank for that one though! 😄 Quote Link to comment Share on other sites More sharing options...
emanuel_froes Posted April 13 Author Share Posted April 13 On 3/28/2023 at 1:53 PM, David Nahmani said: Oh now you're getting somewhere! 😄 So it could be that the parameter is not automatable, OR that the parameter is one from a plug-in that is before the plug-in that is in learn mode. So scratch what I was saying @emanuel_froes - this issue is due to a MIDI plug-in that is in learn mode. For example: yes, was exactly this, i was playing this thic cool thing 😉 template is too big then maybe something left forgotten. BUt now works well 1 Quote Link to comment Share on other sites More sharing options...
David Nahmani Posted April 13 Share Posted April 13 Ok good to hear! 🙂 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.