DP11 PERFORMANCE ISSUES

[akr]

I'm on mac os 10.13 running on a mac pro 5.1, the latest one with maximum upgrade 4x8core xeon 5690 and 128 Gb of RAM
I recently update from a mac pro 3.1 on dp 10 to have more cpu power..... but I'm afraid that problem is somewhere else in DP
LACK of power lack of CPU especially with dp11
RME fireface800

running a normal audio project the performance meters shift+Y peaks constantly to red and audio drop out and glitches.
buffer size 2048
work priority high
prime for millisecons up to 1000
stereo bus 32

my chunk was
18 audio tracks
14 internal bus

6 instances of Waves sslg channel
2 instances of Waves NLS
3 instances of Satin from uhe
12 instances of Front DAW
8 instances of hornet tape machine emulation
3 instances of psp emt454
1 instances of arturia space echo
2 instances of 1176 UAD with dsp card
2 instances of pultec uad with dsp card
4 instances of fabfilter proq 3
6 instances of melda mauto align
2 instances of inhase Waves
1 instance of TR 5 tape delay
1 wavefactory track spacer
1 Waves api 2500
1 instance of dseq3 tb pro audio
1 of bass lane
1 voxengo SPAN
1 youlean loudness meter

this project is not so heavy for my mac configuration.....

I cannot understand the monitor activty
DP11 is on 300%, but in the overall sistem performance the cpu is on 20% and audio continue dropping and glitching

whats wrong????

wich parameter in my configuration caoud I change?

I CAN RUN a similar project on logic 10.4 why????????????

thanx in advance for any advice

[Phil O]

My oldest mac is a 6.1 running OS 11.6.2 so I cant speak to a 5.1 and system 10. But, I can say that on that system the performance is quite good with the latest DP11. I've found that the highest buffer setting causes glitches and believe it or not a setting of 512 seems to be optimum for this system. Can't hurt. Try lower settings and pick the one that works best.

BTW, my Prime Milliseconds is 50.

Your friendly neighborhood Phil

[mikehalloran]

whats wrong????

A maxed out 12 system is still 12 years old. Some things cannot be upgraded.

[akr]

My oldest mac is a 6.1 running OS 11.6.2 so I cant speak to a 5.1 and system 10. But, I can say that on that system the performance is quite good with the latest DP11. I've found that the highest buffer setting causes glitches and believe it or not a setting of 512 seems to be optimum for this system. Can't hurt. Try lower settings and pick the one that works best.

BTW, my Prime Milliseconds is 50.

Your friendly neighborhood Phil

Thanks you I will try

[akr]

whats wrong????

A maxed out 12 system is still 12 years old. Some things cannot be upgraded.

What you mean exactly?
I have a poore english
You mean my plugins are too heavy for my system ?

Thise plugin are mostly from 2015 or 16
Juste One or two are from 2021

[EMRR]

Look at the plugin performance meter.

[cuttime]

Look at the plugin performance meter.

This. Also known as "Effect Performance". 300% means you are maxing out 3 cores.

[akr]

Tried out with 512 buffer size... Even sorta of possible. .

Looking. at effect performance, the guilty was front DAW.
I will contact the company because they sell this plugin as a CPU friendly plugin.
In my case is not.

I will switch back to NLS Channel

Thanx

[akr]

Tried out with 512 buffer size... Even sorta of possible. .

Looking. at effect performance, the guilty was front DAW.
I will contact the company because they sell this plugin as a CPU friendly plugin.
In my case is not.

I will switch back to NLS Channel

Thanx

[bayswater]

I've had glitches, and spiking meters a few times, and found that:

1) these two things do not always happen together. The meters, at least in earlier version of DP, if not current versions, were responsive to general resource usage other than CPU. In my case, a disk too slow or too full cause the meters to spike and the sound to be intermittent.

2) that some plugins that might be OK in other DAWs or in other formats, eat up a lot of CPU in DP for no apparent reason. This might be OS or DP version specific I stopped using bx-meter for that reason, although it seems very light in Mixbus, Logic and DSP-Q. Some Eventide plugins are very nice, but eat a lot of CPU in DP.

3) that on my old 2012 intel i7 machine, meter spiking happened a lot sooner than sound glitches, as long as other things were OK. (you can see what is and isn't OK in Activity Monitor. It often tells a different story than the one told by DP meters). In DP 9 and 10 I learned to ignore the DP meters and if there was a sound problem, look at Activity Monitor first. DP 11 seems more aligned with Activity Monitor, but I still don't know exactly what DP measures.

4) that the settings discussed in the Getting Started manual are worth looking at, and experimenting with. In my case, changing a value in what seems to be the wrong direction improved matters. I switched from a MOTU to a Focusrite interface and although they were quite similar in the number of channels, the best settings were entirely different. If you use two interfaces, all bets are off.

In the past I've posted the result of a test project on my current i7 2018 Mini with 32G Ram, probably not much more powerful than your Mac, if at all. I can run 500 tracks, 32 instances of Kontakt with 4 MIDI channels each, and 64 auxes, with EQ and compression on all channels, and all tracks playing either different MIDI or audio, The CPU gets close to the edge, but never peaks. The CPU meters run a little lower in Logic because I assume it runs fewer instances of a VI, even if you instantiate more instances. Even so, while there may be some items in a setup that cause CPU glitches, I don't think DP itself is one of the big factors. An exception might be busses (buses? let's have that debate again! ). I think a few people have suggested they seem to use more than their fair share of resources.

[HCMarkus]

An exception might be busses. I think a few people have suggested they seem to use more than their fair share of resources.

When I was using a 5,1 Mac Pro, adding busses (however spelled) definitely impacted performance.

[akr]

An exception might be busses. I think a few people have suggested they seem to use more than their fair share of resources.

When I was using a 5,1 Mac Pro, adding busses (however spelled) definitely impacted performance.

sorry what you mean with "spalled"?

[akr]

thak you for your replies

1 I have a NVME hard disk on pci bus so the speed of the disk is not a problem
I think the problem is front daw even if they sell it as cpu friendly plugin

however I cannot understand why my configuration seems to be greedy of CPU
I tested out 256 audio tracks with a NLS channel each and CPU runs 80%...
is normal?

[bayswater]

Spelled (not spalled) is a long term joke on this site, from an argument on how to spell buss or bus.

I'm don't know what you mean by "front daw". You mean host, or daw like DP or Logic?

I have no experience with NLS channel, so can comment, but you could look at the CPU usage for that plugin. Like I said, some plugins eat a lot of CPU, and 128 instance of it might be an issue.

On hard drive performance, I wasn't referring to speed, but capacity. Not having a lot of empty space can be an issue, maybe less so on an SSD. Although if you are recording 128 tracks I expect that might tax the hard drive, especially if it's a spinner.

How many busses do you have in this setup?

[labman]

I'm don't know what you mean by "front daw". You mean host, or daw like DP or Logic?

Front DAW is a front end simulator by United Plugins i believe. Got it when it first came out. Fairly decent for adding some hair from any of its emulations.