![]() 8 different sounds playing 8 different parts from a single instance of Omnisphere. My typical process is to create an Instrument track with Omnisphere (for example) and then create 8 MIDI tracks to send to the MIDI channels 1-8 of Omnisphere. it's easier when mixing, I just thought each separate instance of a VI automatically starts eating away at resources, even if it's doing nothing. I do appreciate the (in my view) better organization of having 8 instrument tracks. If you personally had 8 sounds in Omnisphere doing different parts, would you create eight separate instrument tracks, each with an instance of Omnisphere with one sound, or one instrument track with one instance of Omnisphere and 8 MIDI tracks sending to it? However, Omnisphere is not that intensive. Technically incorrect to say Omnisphere will run in one thread (because the plugin could be multi-threaded) but it is limited when only running one instance vs many. So they can't be processed completely independently. That's because the DAW has no idea what you are doing so dependencies are serial - ie if you trigger notes on 3 MIDI tracks going to the same Omnisphere, and if you were using the Omnisphere mixer/sends/aux (which the DAW has no clue on if you are or aren't), it needs to output those together at the same time. Omnisphere (as a multitambral instrument) will run in more limited threads than if you had more than one instance of Omnisphere. The DAW manages multcore processing for plugins.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |