DP9.01 and optimization

[Don T]

Please expatiate... those facts you know would be most appreciated.

I didn't want to start that same this vs that daw convo BUT...
Installed DP and everything is fine. DP using 4 core MIDI threads in the activity monitor.
Installed PT which is running fine but now DP has CPU spikes and runs slow.

Looking at the activity monitor DP is now using 28 threads for MIDI with a huge CPU hit.

Went in and put the PT MIDI driver in a "disabled plug-in" folder and restart System. DP returns to 4 core MIDI threads and runs normal. PT still has MIDI function using the core MIDI driver.

Try running Adobe CC and PT on the same system, which ever was installed last runs OK the one installed first is buggy.

Your experience will vary depending on components and hardware installed.

Don

[MIDI Life Crisis]

Still waiting on the "know for a fact" part to be validated.

[Don T]

Still waiting on the "know for a fact" part to be validated.

Well, since I was not there to witness their intent I can only ass/u/me that since the driver caused both DP & Logic to malfunction in the same way and PT's MIDI functions were unaffected by the driver removal that it gives way to their intent. When corporations battle for dominance, users loose functionality, that you cannot deny and it applies to more that just DAW software.

[mikehalloran]

Actually, it's not unusual for another install to corrupt DP. This can be an OS upgrade or a new plugin. I have had it happen a few times.

I would reinstall DP, repair permissions and reboot. See if you still have a problem. Often this fixes things.

If not, turn the background processing monitor on. You will find it in DP Preferences. Sometimes you will see something fail that should be loading or some other weirdness.

[MIDI Life Crisis]

So it's not a fact. Ok.

[mikehalloran]

So it's not a fact. Ok.

Agreed.