Controller editor komplete kontrol mk2 how to#
Controller editor komplete kontrol mk2 install#

Although part of the ini that comes with the installation these actions do not even appear if people do not have the extensions installed.

Controller editor komplete kontrol mk2 how to#

The same is true if people have no interest or idea how to take advantage of those customized actions & scripts that do not come natively with Reaper. However, recognizing that some user already encountered issues with the single file installation I think the switch to a slightly more involved philosophy justifies a message at startup if the installation was not completed successfully. Now, admittedly, the message at startup is 'rubbing it in' because we still have the warning once you invoke custom actions.

Controller editor komplete kontrol mk2 install#

could also happen with a portable install when moving stuff around) rather than replace it with a default dummy. I want the user to know if the config file is missing (e.g. With ReaKontrol v1.0 the philosophy changes a little from 'no user interaction necessary' (single file install, behind the scene csurf without any need for extra control surface config) to 'user involvement encouraged' (additional file installation which is user editable). 'nag' message at startup if installation is not complete and another message on the keyboard's display once the function gets invoked 'config file not found'. Creating the ini if not found came in on 2nd place, but in the end I deliberately settled on the current implementation: i.e. I went through exactly those ideas too (incl supplying an installer). The ReaStash entry is updated to reaKontrol (OSX) v1.00 Note to myself/TODO: i have to support you on the manual regarding OSX as previously offered. Therefore a suggestion: If there is no reakontrol.ini in the user preferences folder: why don't we create one with the default settings? Other idea: why don't we just ignore the file if it's not there? Third idea: if there is no file, why don't we just set the default actions without a configuration file? Leads to the same situation - zero config. I don't like messages which are nagging me that i have to provide some data first before using something with basic functionality. Personally i like the concept of zero-config. Do you want to provide a general Win/OSX release at We can *maybe* synchronize the release and create one 'release' pack at your central repository the next time? Just an offer. Some general questions about the release and the future: What should i do? Add it here? But it's not an API or control surface? Or is it a control surface? Do you have a link to the Windows-Entry so i can shamelessly copy it? Regarding ReaPack: I NEED HELP! Can't get into the magic. Yes but f4b7d introduced a small regression. What about publishing those also via ReaPack? I guess it's your turn now to build the OSX binaries.