Can I set DP11 to use all the cores in my Mac Studio?

[wilkinsi]

I am using an M2 Max Mac Studio with 12 core CPU, 512GB storage and 32GB RAM. My projects are all 24 bit, 44.1k. When arming a track with my synth plugin as an insert to an instrument track, the DSP% hits overload. This is with a latency of 64ms or 128ms setting. I found an article on Google that says DP will only see the first 4 cores on the CPU, and that only a small number of DAW's like Reaper can use all the cores on the processor. Is this true? Is there a setting in either my mac or DP that allows me to force DP11 into using all or as many cores needed to drastically reduce the DSP%? I don't want to start using another DAW, which is what Apple are suggesting I do. Not when I paid for that DP licence (including multiple upgrades) and want to keep it's workflow.

[Michael Canavan]

I am using an M2 Max Mac Studio with 12 core CPU, 512GB storage and 32GB RAM. My projects are all 24 bit, 44.1k. When arming a track with my synth plugin as an insert to an instrument track, the DSP% hits overload. This is with a latency of 64ms or 128ms setting. I found an article on Google that says DP will only see the first 4 cores on the CPU, and that only a small number of DAW's like Reaper can use all the cores on the processor. Is this true? Is there a setting in either my mac or DP that allows me to force DP11 into using all or as many cores needed to drastically reduce the DSP%? I don't want to start using another DAW, which is what Apple are suggesting I do. Not when I paid for that DP licence (including multiple upgrades) and want to keep it's workflow.

DP11 uses all your cores, it's Logic, Live and Bitwig that do not. I get similar results from stress tests with Reaper, I don't own Cubase.


Something else is going on. One thing to do right away is open the Effect Performance window and see which plugins are running in Real Time (RT) and which are PreGen (PG), if you have multiple aux tracks with heavy plugins they run in real time and suck up CPU, every record armed track runs in real time, and you can set plug ins to run in real time when the GUI is open.


The second thing is the fun time possibility that the plugin you're using is spiking DP, I've had this happen with plugins over the years, check for an update etc. Also try using a different plugin format, it can help.

[HCMarkus]

Looks like a single-core overload situation. It is my understanding that single synth plugin on a track cannot use more than one core simultaneously, regardless of the DAW. You can look at Activity Monitor (Applications> Utilities) to gain a little more understanding.

Are you running any other plugins on the synth track? Turn them off while recording.

Are you running Master Bus FX? Turn them off while recording.

If all else fails, just increase DP's buffer while recording with the problem synth, or record with something easier on the CPU and replace after your MIDI track is recorded and record has been disabled on that track.

[mikehalloran]

I found an article on Google that says DP will only see the first 4 cores on the CPU, and that only a small number of DAW's like Reaper can use all the cores on the processor. Is this true?

There’s lots of nonsense on the internet.

Normally, a single instance of a VI in a Player uses a single core. Multiple instances of the Player, not the VI, are balanced among the cores by the OS, true for both Mac and Windows. There are now a number of Players that support multi core so this is no longer true for everything. Kontakt, for example, can make use of multiple CPUs or multi-core processors. To switch multi-processor support on and off and to set the number of processors / cores you want to use for Kontakt, select the corresponding entry from the Multiprocessor support menu.
https://www.native-instruments.com/ni- ... rt%20menu.

The Activity Monitor often reads well over 100%.. This is because a Mac with multiple cores (all recent Macs) count each core as 100%. So, an eight-core iMac has a total of 800% of CPU time available. This tab lets you know which apps are working the hardest.

This does not change with Apple Silicon. My M2 Ultra studio has a 24-core CPU with 16 performance cores and 8 efficiency cores. It’s theoretically possible for the Activity Monitor to show up to 2400% without there being a problem — I imagine that the fans would get quite loud were that to ever happen.

[cuttime]

Another point: Is the plugin operating under Rosetta? Perhaps an update is called for? What is the plugin?

[wilkinsi]

The plugin is UVI Falcon, and it is not in Rosetta. I never open any app or plugin in Rosetta.

[mikehalloran]

The plugin is UVI Falcon, and it is not in Rosetta. I never open any app or plugin in Rosetta.

If an app requires Rosetta 2, it will just open over it and you won't know.

Falcon is AS Native as of 2022. If you haven't done so lately, run the UVI Portal and get your free update to Falcon 3.current. The same goes for any UVI Libraries you own.

Neither UVI Workstation nor Falcon support multi-threading, this means that each plug-in (Player) instance will work on a single processor core only. For every VI you load in Falcon, generate a new Instance. Here are more tips from UVI Support.
https://support.uvi.net/hc/en-us/articl ... re%20only.

If you are opening old MOTU libraries downloaded prior to December 2022, log into your MOTU account and download the latest AS compatible versions of those, too. These are not available on the UVI site although many of them are found in newer versions sold by UVI.

[HCMarkus]

Another option: Disable some of a VI's oscillators while recording, then re-enable once you are playback-only.

[wilkinsi]

The plugin is UVI Falcon, and it is not in Rosetta. I never open any app or plugin in Rosetta.

If an app requires Rosetta 2, it will just open over it and you won't know.

Falcon is AS Native as of 2022. If you haven't done so lately, run the UVI Portal and get your free update to Falcon 3.current. The same goes for any UVI Libraries you own.

Neither UVI Workstation nor Falcon support multi-threading, this means that each plug-in (Player) instance will work on a single processor core only. For every VI you load in Falcon, generate a new Instance. Here are more tips from UVI Support.
https://support.uvi.net/hc/en-us/articl ... re%20only.

If you are opening old MOTU libraries downloaded prior to December 2022, log into your MOTU account and download the latest AS compatible versions of those, too. These are not available on the UVI site although many of them are found in newer versions sold by UVI.

I am already using the latest version of Falcon 3. I keep all my plugins up to date.

[Killahurts]

I am using an M2 Max Mac Studio with 12 core CPU, 512GB storage and 32GB RAM. My projects are all 24 bit, 44.1k. When arming a track with my synth plugin as an insert to an instrument track, the DSP% hits overload.

But does it affect your sound? Are you getting pops, dropouts, etc?

If not, and if you're referring to the audio performance meter in the control panel, you could try what I did many years ago, which is to turn that stupid thing right off, and never look at it again.. out of sight, out of mind.

[HCMarkus]

But does it affect your sound? Are you getting pops, dropouts, etc?

Good point! Even if you get some weirdness while recording, playback should be fine.

Back in the Cheesegrater days, I turned that meter off, too. Nowadays, I leave it on... nice to have the easy visual reference that lets you know nothing went bad during a mix down.

[mikehalloran]

…
I am already using the latest version of Falcon 3. I keep all my plugins up to date.

Good.

To recap, the answer to your original question is No, that’s not how things work, Mac or Windows.

As to the meters, it’s not an issue if there are no ill effects. If overloading is occurring, UVI’s Support page that I linked and other suggestions made here should help.

[wilkinsi]

I am using an M2 Max Mac Studio with 12 core CPU, 512GB storage and 32GB RAM. My projects are all 24 bit, 44.1k. When arming a track with my synth plugin as an insert to an instrument track, the DSP% hits overload.

But does it affect your sound? Are you getting pops, dropouts, etc?

If not, and if you're referring to the audio performance meter in the control panel, you could try what I did many years ago, which is to turn that stupid thing right off, and never look at it again.. out of sight, out of mind.

Unfortunately, I am getting distorted pops and clicks.