Avid Pro Audio Community

Avid Pro Audio Community

How to Join & Post  •  Community Terms of Use  •  Help Us Help You

Knowledge Base Search  •  Community Search  •  Learn & Support


Avid Home Page

Go Back   Avid Pro Audio Community > Legacy Products > Pro Tools 2018

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 10-16-2018, 02:42 PM
kirkbross's Avatar
kirkbross kirkbross is offline
Member
 
Join Date: Jul 2004
Location: Los Angeles
Posts: 372
Default Multiple Instnaces of VIs vs. multiple MIDI tracks targeting a single instance?

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. i.e. 8 different sounds playing 8 different parts from a single instance of Omnisphere.

Is this the best practice in terms of computer resources or is it better to create 8 separate instrument tracks, each with an instance of Omnisphere, and have just a single sound in each one.

I ask because a friend said if they're all stacked in a single instance, they can only use one CPU thread.
__________________
Pearlman Church Microphone > Great River MP-2NV > Warm Audio WA-76 > Apogee Symphony MK II 8x8+8MP > PT2018 on 2018 Mac Mini with 32GB of RAM running Mojave.
Reply With Quote
  #2  
Old 10-16-2018, 03:12 PM
BScout BScout is offline
Member
 
Join Date: Mar 2007
Location: Los Angeles, CA
Posts: 4,141
Default Re: Multiple Instnaces of VIs vs. multiple MIDI tracks targeting a single instance?

The DAW manages multcore processing for plugins.

Omnisphere (as a multitimbral instrument) will run in more limited threads than if you had more than one instance of Omnisphere. 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. So they can't be processed completely independently.

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. However, Omnisphere is not that intensive.
__________________
Pro Tools Ult 2024.3, HDX 2, MTRX/SPQ, RME BBF Pro + MADIface ProS1 x 2, Fire HD10 + Max11, Dock, iPad Air5 Mac Mini 14,12, 12 core, macOS 13.6.5RAM 32GB, SSD 4TB, GPU 19 coreQNAP TVS-872XT 148TB TB3

Last edited by BScout; 10-17-2018 at 12:31 PM. Reason: typo
Reply With Quote
  #3  
Old 10-16-2018, 03:42 PM
kirkbross's Avatar
kirkbross kirkbross is offline
Member
 
Join Date: Jul 2004
Location: Los Angeles
Posts: 372
Default Re: Multiple Instnaces of VIs vs. multiple MIDI tracks targeting a single instance?

Quote:
Originally Posted by BScout View Post
The DAW manages multcore processing for plugins.

Omnisphere (as a multitambral instrument) will run in more limited threads than if you had more than one instance of Omnisphere. 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. So they can't be processed completely independently.

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. However, Omnisphere is not that intensive.
Thanks for the response. I'm still unclear on the bottom line. 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?

I do appreciate the (in my view) better organization of having 8 instrument tracks... 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.
__________________
Pearlman Church Microphone > Great River MP-2NV > Warm Audio WA-76 > Apogee Symphony MK II 8x8+8MP > PT2018 on 2018 Mac Mini with 32GB of RAM running Mojave.
Reply With Quote
  #4  
Old 10-16-2018, 06:20 PM
BScout BScout is offline
Member
 
Join Date: Mar 2007
Location: Los Angeles, CA
Posts: 4,141
Default Re: Multiple Instnaces of VIs vs. multiple MIDI tracks targeting a single instance?

Unless you are having problems running 1 omnisphere with 8 MIDI, I would leave it that way. Omnisphere doesn't really tax a computer's resources in the first place. Spreading to multiple omnisphere instances is only beneficial if only one core is spiking and the rest are not. Then making multiple instances allows that load to be shared across more cores.
__________________
Pro Tools Ult 2024.3, HDX 2, MTRX/SPQ, RME BBF Pro + MADIface ProS1 x 2, Fire HD10 + Max11, Dock, iPad Air5 Mac Mini 14,12, 12 core, macOS 13.6.5RAM 32GB, SSD 4TB, GPU 19 coreQNAP TVS-872XT 148TB TB3
Reply With Quote
  #5  
Old 10-17-2018, 05:30 AM
musicman691 musicman691 is offline
Member
 
Join Date: Dec 2009
Location: The Sopranos State (NJ)
Posts: 19,136
Default Re: Multiple Instnaces of VIs vs. multiple MIDI tracks targeting a single instance?

Quote:
Originally Posted by kirkbross View Post
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. i.e. 8 different sounds playing 8 different parts from a single instance of Omnisphere.

Is this the best practice in terms of computer resources or is it better to create 8 separate instrument tracks, each with an instance of Omnisphere, and have just a single sound in each one.

I ask because a friend said if they're all stacked in a single instance, they can only use one CPU thread.
In general and not just for Omnisphere but any multi-timbral vi it would spread the load better amongst cpu cores to have multiple instances of a vi rather than stacking all eight or whatever number of instruments into one vi. There are exceptions though.

Say I'm doing something orchestral where I have several instruments each sometimes playing both staccato and long notes. A trumpet line playing both staccato & longer notes would have one instance of a vi (Kontakt or EW Play in my case) with two trumpet instances with one MIDI line that play staccato notes going to the trumpet instance that has staccato samples. The other MIDI line that plays longer notes would go to that same instance of Kontakt or EW Play to the instrument that has longer samples. Now include a tuba with staccato and longer notes - that would go to another separate instance of Kontakt or EW Play. I would not stack every brass instrument in one instance of Kontakt or Play.
__________________
Jack
See profile for system details
iMac dead & retired as of 11/4/17

QAPLA!
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Using One Instance of VI Instrument for Multiple MIDI Tracks adam79 Virtual Instruments 9 12-23-2017 07:11 AM
Import single midi file of a keys track from logic opens multiple tracks in PT alfalaschi Pro Tools 12 2 04-10-2017 07:15 PM
Single track to multiple tracks or aux realizment Pro Tools 10 2 11-16-2012 11:28 PM
Recording multiple midi drum channels to multiple audio tracks? ewan.mcghee MIDI 7 07-18-2011 01:46 PM
Multiple CD tracks from single file ThB Music Digidesign Hardware & Software 0 09-15-1999 10:54 PM


All times are GMT -7. The time now is 12:44 PM.


Powered by: vBulletin, Copyright ©2000 - 2008, Jelsoft Enterprises Limited. Forum Hosted By: URLJet.com