You have a project to play live and you save 10 different presets on ReaEQ for different moments of the gig (I´m talking about Reaper´s own preset system). Dealing with Absynth´s patches is as easy as it can get, so let´s focus on ReaEQ. We´ll now forget about Kontakt suppose you have a track with Absynth and an instance of ReaEQ. IMHO for using multiple sound in parallel in such a "live" situation, it's more appropriate to use a single track and do "parallel FX chains" by making use of assigning the "pins" of the plugins to the appropriate channels (up to 64) within an FX "chain" (than is more like a "net" then).įine, thanks for the tips and the code! Now, while that is clear as crystal, let´s put another example to clarify the topic. I use multiple pages assigned each to a masterkeyboard to independently switch the patches (unmute the appropriate track and push presets to the plugins there) of either. I understand that this is possible by using multiple pages "Configs" (that of course can be handled in the way described). I did not yet use LiveCoinfigs to activate multiple tracks at the same time. Now when selecting a line in LiveConfigs, both Kontakt and ReaEQ will switch to the desired setting. set four "lines" in SWS LiveConfigs" to each load the appropriate presets of "Slider to Midi PS" and ReaEQ. do same for the other two sound(patches save a preset (by "+") of both "Slider to Midi PS" and ReaEQ wirh appropriate names. set Kontakt to the first sound ("instrument in bank") by moving the slider of "Slider to Midi PS" and tweak the EQ Add my little "Slider to Midi PS" plugin before Kontakt to process the Midi Stream
So if you have a track containing Kontakt and RaeEQ and want four sounds/patches, You can do the following: Same will contain the settings of all parameters of that plugin. You can save a preset of any plugin with a name.
Free absynth presets Pc#
Now I save multiple Reaper presets for this plugin (and not for the one that creates the sounds) and when loading the preset, simply a Midi PC is sent, that again selects the appropriate patch/instrument in the sound plugin. That is way I made a JSFX that features a slider with the PC-No to be sent. (I did not research if there is a "bank position" or similar plugin parameter that might be able to be automated by Reaper, as I searched for a method that can be used with any plugin that internally features multiple patches to be be selected.) So (AFAIK) the only fast way to switch instruments in Kontakt is to organize the instruments in a bank and send a Midi PC message to Kontakt. And not (especially not with Kontakt) by loading a Reaper "preset", which is a collection of all published parameters of the plugin and in Kontakt will result in reloading all samples. Sorry but I don't really understand what you mean.Ī "preset" in a plugin (also known as "program", "patch", or "instrument in a bank" in Kontakt speak) is selected by sending a program change message to the plugin. I also don´t know if this section of the forum is attended at all, but I can´t help suggesting this since it would be of great help with, for example, something like Live Configs from the SWS Extensions. Please, correct me if I´m wrong in some of my statements, but I haven´t found an easy way to handle presets per FX instance. RPL libraries should have the possibility to be saved/recall per instance, in my opinion. Deletion of user presets seems to be done one by one, if I´m not mistaken. RPL library, for example, the imported presets are added to the existing list, so you end up with a massive list of all prresets for all projects. Now, if we could just have a way to manage presets more flexibly, with options to have global and/or per instance user libraries, it would be remarkably more useful.
Regarding this, Native Instruments´synths (mainly FM8, Absynth and Massive come to mind right now, which are the ones I use most) are, in my opinion, exemplary.you can activate/deactivate a bank of 128 programs per instance in which you can load anything that is included in the global database : internal, third party and user presets are easily arranged in the bank and you can have a dedicated list per instance. ini files and all of that, which in itself would be a total mess for many of us). There seems to be no easy way to have a dedicated bank of presets for every instance of a FX (I mean, at least without having to deal with. You can only save/recall presets in a global fashion (that is, user presets appear on every instance of the plug). Native preset management, as it stands, is not precisely what I would call "flexible". First of all, excuse me if this has already been requested.I haven´t found a proper request such as this but I might be wrong.
0 kommentar(er)
