spride Posted May 11, 2022 Share Posted May 11, 2022 In Logic 10.7.3 (and maybe below but I've only been using Ableton for the last year or so), if I have a plugin window open and then try to perform keyboard actions within it, for example, searching for a preset using the plugin's search feature, or naming a new preset as I save it, the keystrokes are not sent to the plugin window but to Logic itself, thereby triggering unwanted actions such as play/stop and even deleting regions. I've checked a number of plugins from different mainstream manufacturers (Arturia, Cherry Audio etc) and they all behave similarly. Is anyone else seeing this behavior? MacBook Pro M1Pro / macOS 12.3.1 / 32GB RAM / Logic 10.7.3 / all plugins up to date. Quote Link to comment Share on other sites More sharing options...
des99 Posted May 11, 2022 Share Posted May 11, 2022 Can you give some specific examples of plugins that do this? (Rather than listing manufacturers with many plugins). Usually keyboard handling when a plugin window is focused is the responsibility of the plugin to handle (they usually "steal" the key presses that they handle, and then pass the unrecognised key presses on to the host). I have the Arturia stuff, and a couple of Cherry stuff like the Quadra, and I've not noticed this behaviour as such, so if you can give me one or two to check out, I'll take a look... 1 Quote Link to comment Share on other sites More sharing options...
Solution spride Posted May 11, 2022 Author Solution Share Posted May 11, 2022 Well, I don't know why I didn't try this earlier, given I work in IT - I rebooted and now it works properly. Of course. Gonna leave this here in case anyone else has the same issue. 1 Quote Link to comment Share on other sites More sharing options...
spride Posted May 11, 2022 Author Share Posted May 11, 2022 Hi Des99 - see my update before I saw your reply, which says that a reboot fixed it (for how long?) but: Cherry Audio MiniMode Arturia SEM-V 2 Arturia Analog Lab 5 Arturia SQ80 V Arturia Jup-8 V 4 Quote Link to comment Share on other sites More sharing options...
des99 Posted May 11, 2022 Share Posted May 11, 2022 (edited) It's possible the plugin window wasn't focused (white outline), so while it looks like the plugin has an open text input field, your key presses were not going to the plugin at all... Edited May 11, 2022 by des99 1 Quote Link to comment Share on other sites More sharing options...
spride Posted May 11, 2022 Author Share Posted May 11, 2022 Thanks, it is possible. If it happens again I will check for the focus line. 1 Quote Link to comment Share on other sites More sharing options...
spride Posted May 11, 2022 Author Share Posted May 11, 2022 (edited) So I have some more information which may be useful. This seems to occur when you have the plugin window on a different display than Logic. Steps to reproduce: Open the Plugin window Move it to a different display from the one where Logic is running Try to enter text and the keystrokes go to Logic, not the plugin window, despite the fact that the plugin window has the white focus outline Steps to resolve: Move the plugin window back to the same display as Logic Close the plugin window Open the plugin window Text entry behaves as normal Can anyone with two displays or more confirm what I'm seeing? Edited May 11, 2022 by spride Quote Link to comment Share on other sites More sharing options...
des99 Posted May 11, 2022 Share Posted May 11, 2022 (edited) I'll check shortly... Edit: I couldn't reproduce this, and I tried both ways. Regardless of which display Logic was on (MBP screen, or external monitor), with the plugin on the other one, the plugin always received my text input when it was focused. Edited May 11, 2022 by des99 Quote Link to comment Share on other sites More sharing options...
spride Posted May 14, 2022 Author Share Posted May 14, 2022 That's weird. It's very consistent here. I am on a M1Pro running Monterey. Is that in any way similar to your platform? Quote Link to comment Share on other sites More sharing options...
des99 Posted May 14, 2022 Share Posted May 14, 2022 I’m running an M1pro on Monterey, yes. Quote Link to comment Share on other sites More sharing options...
spride Posted May 15, 2022 Author Share Posted May 15, 2022 Curiouser and curiouser. I'll try to make a video to show the effect. Quote Link to comment Share on other sites More sharing options...
spride Posted May 15, 2022 Author Share Posted May 15, 2022 and of course I can't reproduce it now Quote Link to comment Share on other sites More sharing options...
des99 Posted May 15, 2022 Share Posted May 15, 2022 15 minutes ago, spride said: Curiouser and curiouser. I'll try to make a video to show the effect. I'm not doubting you're seeing this, btw. 11 minutes ago, spride said: and of course I can't reproduce it now Which suggests this issue is not a simple, easily reproducible one that affects everybody, but is some bug where Logic, or some plugin, gets into a weird state that causes this issue - which makes it a lot harder to track down, and find a way to 100% repeatably reproduce it. Quote Link to comment Share on other sites More sharing options...
spride Posted May 17, 2022 Author Share Posted May 17, 2022 Yes. I will continue to observe and see if there is a unique set of circumstances under which it occurs. Luckily I am trained in Kepner-Tregoe problem analysis :-) 1 Quote Link to comment Share on other sites More sharing options...
des99 Posted May 17, 2022 Share Posted May 17, 2022 I don't know what that is, but it sounds *cool*... 😎 Quote Link to comment Share on other sites More sharing options...
spride Posted May 17, 2022 Author Share Posted May 17, 2022 It's a popular framework in service management and related disciplines for determining root causes of problems when there's no obvious one. It asks questions like: Where is it happening? Where is it not happening? Where could it be happening but isn't? When is it happening? When is it not happening? When could it be happening but isn't? etc The idea is to force you to look at all aspects of the problem rather than yielding to your biases and habits. 2 Quote Link to comment Share on other sites More sharing options...
james__gregory Posted January 29, 2023 Share Posted January 29, 2023 Having the same problem, but with Komplete Kontrol / Kontakt 7 for the search feature when using within Logic. It activates Logic commands and nothing gets typed in the search bar. This doesn't happen when launching either Komplete Kontrol or Kontakt software as standalone apps. It works fine then. Have rebooted a few times to no avail. Quote Link to comment Share on other sites More sharing options...
des99 Posted January 29, 2023 Share Posted January 29, 2023 Yes, Kontakt 7 for sure behaves like this. You should report it to NI as a bug... 1 Quote Link to comment Share on other sites More sharing options...
james__gregory Posted January 29, 2023 Share Posted January 29, 2023 3 minutes ago, des99 said: Yes, Kontakt 7 for sure behaves like this. You should report it to NI as a bug... Funny...that's where I started...on the NI forum. There is a post there about it as well. But thank you. I will definitely trying to contact them. 1 Quote Link to comment Share on other sites More sharing options...
james__gregory Posted January 30, 2023 Share Posted January 30, 2023 I emailed support at NI and they responded that it's a known issue and that developers are currently working on it. They recommended closing and reopening either the Browser or Kontakt window and that it would restore focus. That hasn't been the case so I suppose it's up to them at this point. 2 Quote Link to comment Share on other sites More sharing options...
james__gregory Posted February 1, 2023 Share Posted February 1, 2023 Update from Native Instruments regarding this... Niall (Native Instruments) Jan 31, 2023, 11:48 GMT+1 Hi James, when we were able to reproduce this here, the first search would function, but the next search would trigger the transport controls. But closing and reopening the Kontakt window would allow us to make a search again. If I understand you correctly, you are saying that you cannot complete even one search. I'll certainly pass on this info to the devs. I don't have a time-frame for a possible fix but it is a high priority topic so shouldn't be too long. Best regards, Niall 1 Quote Link to comment Share on other sites More sharing options...
HoraceWimp Posted April 1, 2023 Share Posted April 1, 2023 (edited) I have the same problem here with Kontakt 7.2 and Logic 10.7.7. First input to search field works, after that keyboard input is forwarded to Logic. Does anyone know any workaround or solution in the meantime ? (except closing the kontakt window and reopening it). Edited April 1, 2023 by HoraceWimp correction Quote Link to comment Share on other sites More sharing options...
seagate Posted June 2, 2023 Share Posted June 2, 2023 Well it's the 2nd of June 2023 and the problem is still there in multiple plug ins. Kontakt 6 & 7 Arturia Pigments and Analog Lab but not in Jupiter V (haven't tried them all) All of Cherry Audio are working fine, so are all of the U-he plugs. Haven't checked all my plug ins but it's bizarre it happens in some and not in others especially from the same manufacturer. And no fix inside or even acknowledgment from the mothership. On a side note, I'm glad we now have Logic for iPad, because we all love working with tiny screens.... 🤪 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.