![]() ![]() ![]() The Native Instruments ones all required “Whole bank”, as far as I could see. As it turned out, I think just about all my plugins worked fine with presets / pseudo-presets, and in fact many (eg Diva, ImpOscar2, VB3) continued sounding held notes after the patch change, rather than muting. I actually went through all my plugins and tested to see how well they worked using Cantabile’s preset / pseudo-preset drop-down, and whether they required “Whole bank” state behaviour for changes. For that reason, I don’t try to use presets, pseudo-presets, or banks because I don’t understand how they work with Omnisphere well enough to trust the process during a live show. But since Omnisphere uses significant computer resources, I would be interested in hearing from people who do.ĭespite Brad’s excellent reply to another post, I am often unsure what exactly gets saved when I saved the Rack, and understand that it is different for each plugin. And if I need Omnisphere in another Rack (regardless of whether it’s in the same Song or SetList, or not), I use a new instance of Omnispere.ĭespite Brad’s excellent reply to another post, I am often unsure what exactly gets saved when I saved the Rack, and understand that it is different for each plugin. I don’t use the plugin’s abilities for keyboard splits and mappings I prefer to have all of that in Cantabile. Go back to Cantabile and save the Rack, and use it within a song.Go into the Omnisphere plugin (from Cantabile), either select an existing patch or create a new one, edit as needed, add additional patches onto other Parts (up to 8 in the Multi) as needed, and finally save the Multi.Create a new rack to contain this new “sound”.I do use Omnisphere with Cantabile, but I am probably not using it in a very efficient way. I am also interested in the responses to this. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |