Right now, we have to learn every key of the Launchpad manually. It would be great if there would be a kind of Launchpad preset instantly available.
Comments (10)
-
-
reporter re
#20Read slot, scene and group MIDI triggers from JSON file, first draft→ <<cset ed28b959064a>>
-
reporter re
#20Before setting MIDI triggers, clear the old ones→ <<cset af00d6cc27c9>>
-
reporter re
#20Add possibility to change connected controller without overwriting modified MIDI triggers→ <<cset 91244a465dd0>>
-
reporter re
#20Add possibility to generate controller template based on current MIDI triggers (context menu on 'Connected controller' label)→ <<cset 134d0970d68d>>
-
reporter - changed status to resolved
-
reporter re
#20Fix group MIDI triggers→ <<cset e8966b158d5f>>
-
reporter re
#20Also read scene group MIDI trigger from controller configuration file→ <<cset 003b12667ad1>>
-
reporter re
#20Also include scene group MIDI trigger in conroller configuration file template generation→ <<cset 4fb40eea5bf7>>
-
reporter re
#20, re#28Add APC 40 controller configuration file, add Launchpad default MIDI triggers→ <<cset 58cc3e2be0d8>>
- Log in to comment
However, once a user maps it and saves a track template it is not an issue. Not a major priority, unless it is easy to fix. Maybe .ini file? Then others could edit .ini file with their controller, apc40... however - editing .ini files can get users into trouble.