(For most other/older NI controllers the Midi templates are edited in Controller Editor instead.) Best to edit these from the KK software as per NI manual. Templates are stored in "Komplete Kontrol MK2 Settings.dat" and are evaluated through NIHIA. All other variations of using MIDI messages from the keyboard to learn/link to Reaper actions, plugin controls etc are possible just like with any other keyboard incl more advanced concepts like using MIDItoReaControlPath.Īnd the NI software allows you to create Midi templates to modify the Midi CCs, add names, create keybed zones, colors etc. map an action to one of the top row buttons. Maybe you simply forgot to enable control messages for your normal KOMPLETE KONTROL Midi Device in the Reaper options? You would do the latter if you want to have your MIDI CC buttons and knobs on the keyboard to act globally within Reaper, e.g. And you can do that on top of ReaKontrol, it coexists happily together with all the Reaper standard stuff. You can do exactly what you would do with any other MIDI controller. There are no limitations in regards to mapping actions to the S88, MIDI learn, MIDI link etc. I can't even map an action to a midi controller.unless I'm missing something. It is also the reason why - at least at this stage with the very simple structure we have - I do not see a reason for a dedicated installer. It takes care of the whole point of installing all required files properly. This leads me to installation in general: I am a huge fan of ReaPack! It should be the default way to install. However, once the dust has settled we might remove the message at startup and just leave the one when you invoke the function. Most people will not ever encounter the message anyway. In a nutshell: I stand by my decision to create these messages and "gently force" the user to do a proper installation. Although part of the ini that comes with the installation these actions do not even appear if people do not have the extensions installed. 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. 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |