AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Keycue for mac11/29/2023 ![]() ![]() ![]() I don't know if any of this tells you anything, it doesn't me at the moment.Did you know that the average Mac OS X application has 40 to 80 menu shortcuts? Menu shortcuts are supposed to provide quick access to frequently used menu commands. Here's that list:īelow are the results of that sequence + P and + T in Key Codes, but with the "Fn" key also pressed - as noted, it doesn't register those Key Commands without Fn included. There are eight total letters that don't register with Key Codes when combined with the Control-Option-Command sequence (all of them do if I add Fn). I noticed it doesn't show Fn visually next to the Keys section - is there a formal symbol to define the "Fn" key on a Mac? I don't know of any Logic key commands that use it or I'd check.Īlso of interest: It's not just T and P that combo doesn't work with. But Key Codes includes "NX_SECONDARYFNMASK / kCGEventFlagMaskSecondaryFn / NSFunctionKeyMask" when I press the "i" button to the right of the Modifiers codes, so it's indeed also registering the Fn key in those cases. If I add Fn, both register just like in Logic. ![]() First off, neither of the two key commands registers in Key Codes. Nice call facej - Key Codes didn't resolve it but did shed some light. Where are the Logic Prefs files I need to trash? I have not tried that yet. And for whatever reason, adding the Fn key makes it believe that sequence is being pressed. So up til now, Control-Option-Command-T and Control-Option-Command-P are the only key commands it should recognize, but doesn't. Both work perfectly well - without the Fn key needed - and that includes after rebooting my Mac, restarting Logic, etc. I found two shortcuts that use that same key combo (with a different letter) but aren't yet reserved by any commands, and assigned them: Control-Option-Command-G to Show/Hide Toolbar, and Control-Option-Command-H to (Toggle) Autopunch Mode. I then deleted what appears to be "Control-Option-Command-T" from the "Show/Hide Toolbar" Key Command, but in actuality includes the "Fn" key too - I have to press Fn to get it to jump to that in the Edit Key Commands screen as well it doesn't recognize Control-Option-Command-T without the Fn. Just the two I've mentioned have the problem (to date). Control-Option-Command-N creates a New Track Alternative, Control-Option-Command-D creates a Duplicate Track Alternative, and a few others I tried work fine as well. I first tried a few other combos that use the Control-Option-Command- sequence to see if they are all "stuck." Nope. I had a 2015 MBP 13" until very recently - it had the exact same issue.įar from a big deal but I'd just like to figure out what's going on. Gear: I use a Focusrite Clarett 8PreX (Thunderbolt 2) with a 2019 MacBook Pro 15" running Mojave 10.14.6 and Logic Pro X 10.4.6. Incidentally, my Fn is set for functions like brightness, volume, etc., not as a true F key. Yet sure enough, if I press Fn-Control-Option-Command-T (or P) they work every time.Īm I missing something? Feels like I'm overlooking something obvious like the "Fn" key's symbol, if it has one. "Fn" is not reflected in any documentation I've seen nor in my Key Commands Editor. ![]() Last night I discovered that adding the "Fn" key to these shortcuts makes them work. I also have the Ke圜ue app installed but it doesn't detect any conflicts either. Those key combos are reflected in my Key Commands Editor, and no conflicts exist. Their Key Commands are Control-Option-Command-T and Control-Option-Command-P, respectively. I have an issue that's stumped me for too long: Every Key Command (so far) works fine with the exception of two that are nearly identical: Show/Hide Toolbar and (Toggle) Autopunch Mode. I'm also on the final chapter of David's Logic Pro X 10.4 book - exactly the type of material I needed. I've been using Logic Pro X for a few years and have found more invaluable answers/info here than I can remember. First-time poster here, but far from a first-time visitor to this forum. ![]()
0 Comments
Read More
Leave a Reply. |