admbmb Posted November 5, 2021 Share Posted November 5, 2021 Hi All, I seem to be having a funny issue after starting a new Logic Pro project. I use Superior Drummer 3 as an SI track, and I've never had this problem before, but my keyboard shortcuts when I'm in SD3 are randomly not working on SD3, they're defaulting to Logic. I am working with SD3 inside a Logic project, and I have the SD3 window highlighted. Universally in the past, when my SD3 window is highlighted, SD3 responds to all the keyboard shortcuts, ex. "P" for the Grid, "Ctrl + z" for undo, all that. However, no matter if I have the SD3 window highlighted, "P" brings up the Piano in Logic. "Ctrl + z" undos things in Logic. Even copy/paste shortcuts start doing things in Logic that I don't understand. This behavior is 90% of the time, and the other 10% of the time, the shortcuts work in SD3. But not all of them. I have "Enable Keyboard Shortcuts in DAWs" checked in my SD3 Settings, and none of my other settings seem off or have changed, nor could I find any setting particular to this issue. Anybody know what could be happening? I'm running Logic Pro [Trial] 10.7.0 on an Apple Silicon MacBook Pro. This has been my setup throughout this weird change. Quote Link to comment Share on other sites More sharing options...
admbmb Posted January 1 Author Share Posted January 1 I'm having this same issue, except NOTHING on my keyboard is working in SD3, even typing letters. Like I can't rename a track in my SD3 mixer. Going to try SD3 forums as well. Quote Link to comment Share on other sites More sharing options...
oscwilde Posted January 1 Share Posted January 1 Logic version and OS? I use Sonoma/10.8.1 and if SD/EZD3 has focus - "most" shortcuts work fine. There are some, like Create New Project, where the command is "passed thru" to Logic, but the majority of commands work within SD/EZD3. There was a similar problem with Kontakt up until recently, but NI updated the plug-in and this problem no longer happens. It appears that it's a combination of Logic, OS and plug-in that causes the behaviour, so make sure all are updated. It's possible the behaviour may also change - with some plug-ins - when running in Rosetta mode. 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.