Digital Performer 11.32 loading times under Ventura 13.6.7

[James Steele]

Well in the "annoying YMMV department" I just checked and I have 864 items in my VST3 plugins folder and now slow load times. Weird.

[pencilina]

Curious: does disabling VSTs in DP accomplish the same thing?

No, it does not. They have to be absent from the VST folders to speed up launches

What happens if these VSTs are temporarily moved to an external folder? Will they work again when put again in their relevant place?

Yes

[dwilliams]

I never understand all these replies about fast application and project loading times. It always takes forever for me. I launch DP, then go do something else, then later go back and open the project and go do something else.

[James Steele]

I never understand all these replies about fast application and project loading times. It always takes forever for me. I launch DP, then go do something else, then later go back and open the project and go do something else.

I wish I had an answer. I have never really had an issue with DP launching slowly. As far as project load times, my projects aren't really that large... just typical rock/pop type song with 2 or 3 VIs including a drum VI and several plugins. I've loaded projects with lots and lots of audio tracks and was surprised how quickly those load. It seems to me what slows the load process a lot are the presence of many internally loaded VIs. But it's never been really bad.

Then again, my projects are on my internal drive on the Mac Studio which has stupidly fast read times.

DiskSpeedTest.png (232.94 KiB) Viewed 1742 times

[pencilina]

I never understand all these replies about fast application and project loading times. It always takes forever for me. I launch DP, then go do something else, then later go back and open the project and go do something else.

I often spend more time on crash, recovery, and troubleshooting than I do on work. Digital performer’s plug-in handling is a joke.

[dix]

Curious: does disabling VSTs in DP accomplish the same thing?

No, it does not. They have to be absent from the VST folders to speed up launches

What happens if these VSTs are temporarily moved to an external folder? Will they work again when put again in their relevant place?

Yes, they do. All my VSTs had passed validation before I moved them to an "unused VSTs" folder. If I need to access one, because the AU version is wonky or whatever, I just move that one plug-in into DP's (used) VST folder, relaunch DP and enable that VST in prefs.

[dix]

I never understand all these replies about fast application and project loading times. It always takes forever for me. I launch DP, then go do something else, then later go back and open the project and go do something else.

Well, that method works too. But if you're not using VST's and would like to speed up DP's launch time you could try what I'm suggesting - a bare minimum VST folder. FYI the glacial DP launch times, when there's a full VST folder, only occur once per computer startup. After the long start, (bc of VSTs), subsequent DP launch times are normal until you restart the computer.

Project launch times are a different subject. Those depend on a different set of factors. Project size, plug-ins used etc.

[HCMarkus]

Reducing sample buffer ( pre-load) size in Kontakt and other VIs to minimum will shorten project load times and reduce RAM hit. Just don’t try this if you house your samples on spinning rust.

[James Steele]

Reducing sample buffer ( pre-load) size in Kontakt and other VIs to minimum will shorten project load times and reduce RAM hit. Just don’t try this if you house your samples on spinning rust.

Been meaning to ask you... what settings are you using on Kontakt?

[HCMarkus]

Reducing sample buffer ( pre-load) size in Kontakt and other VIs to minimum will shorten project load times and reduce RAM hit. Just don’t try this if you house your samples on spinning rust.

Been meaning to ask you... what settings are you using on Kontakt?

Minimum. All the way down. No issues with samples on NVMe SSD. NI says it is fine with even SATA SSDs.

[James Steele]

Reducing sample buffer ( pre-load) size in Kontakt and other VIs to minimum will shorten project load times and reduce RAM hit. Just don’t try this if you house your samples on spinning rust.

Been meaning to ask you... what settings are you using on Kontakt?

Minimum. All the way down. No issues with samples on NVMe SSD. NI says it is fine with even SATA SSDs.

Thanks... I'll check my settings. Do you know if setting this in the standalone then applies it to when you launch as a plugin? I'll guess I'll just give it a shot right now and see where I have it set!

It was set to 60K which is the default:

60k.jpg (44.5 KiB) Viewed 1591 times

I went ahead and dropped it to 6k. Be interesting to see if DP projects containing Kontakt load any faster. I needed to do this for a while I guess.

6k.jpg (48.73 KiB) Viewed 1591 times

[hama]

Since I use every day before turning off the Mac the „Clean Cache“ function from the app „CleanMyMac“ from macpaw.com. I had never again that problem of long loading times from DP.