So, the release of Logic 9 and some recent changes I've made to my workflow have got me thinking about key command sets again. So, let me explain my understanding of the state of the World, and you Logic experts correct me where I'm wrong: - Logic ships with >1,000 commands assignable to HID keys or MIDI events (CC#s or just notes?) in the Opt-K window - This is way more than a normal computer keyboard has keys for, even with modifiers, so large numbers of them are not assigned, allowing the user to customize and save these sets. - Logic DOES ship with a default set of assignments, but this depends on the region and computer keyboard, and it can be reset to blank. - People can create and share command sets and switch between them and so on. - By DEFAULT, some Logic key mappings in US/English mode conflict with default OS X global key commands - Major updates of Logic tend to introduce new assignable commands (e.g Flex Time transient marker manipulation tools) My personal setup has essentially evolved from two things: (1) Going through the Davids books and assigning keys when they came up and were relevant to something I do. (2) Searching for something in either the Opt-K window or Google and being like "oh yeah, I need a key for that." As I understand it, BT made a push to get people to standardize on an expanded set of default keys a few years back, which was discussed in various places but seems to have fallen by the wayside. I know there's an attitude, common amongst the sorts of incessant knob twiddlers that end up using programs like Logic (also common amongst the similarly-minded software developers) that this is great, actually, it would be better if Logic shipped with NO mapped commands and every user could create his own and store them in a text file and push it to github. That's cool, but I'm not really talking to you guys in this post, no offense. It seems to me eminently reasonable to try to converge on a baseline set of key commands. Users would be free to modify it to suit their perfect workflow, and extend it as not all commands would be able to be mapped, but why aren't more mapped by default than there are now? I don't particularly care _which_ key is mapped. Frankly, I don't want to sit down with Logic now and rethink my individual shortcuts. There are tons and tons I don't know at all. I have no muscle memory for them. I think the Apple experience in general though shows that there's a lot of value to be gained in agreeing on as much "reasonable default" as possible, as opposed to "hey, just make it an option." It reduces cognitive load on everybody, and I for one end up sitting down at other people's Logic rigs all the time. Having a sort of standard baseline of expanded KC's seems like it would make this easier. What is the current Logic Expert thinking on this? Are people adopting/using BT's set? Is there a L9 version? Is there another commandset that covers a wider range than the default, but is relatively well thought-out, commonly used, and available for download? I may very well be missing something big, but it seems to me that this should really be Apple's job. They aren't doing it. However, by making so much mappable and making the mappings easy to share and swap around, they've given us all the tools we need to do it. Thoughts?