Diva 1.4.8 poor performance using VST2 in DP11

[mesayre]

The recent update seems to have affected DIVA's performance when using VST2 in Digital Performer 11.32 on Windows 10.

Anyone else able to confirm?

I'm getting a significant CPU load increase above what I used to see when using VST2, and changing DIVA's "quality" setting has no effect. Switching to VST3 seems to solve the problem. I can do that going forward but it's a pain for existing projects.

[tasmaniandevil]

The VST2 and VST3 have a pretty identical performance in DP 11, on Mac and on Windows.
Maybe it was a temporary glitch. Try rebooting your computer to see if that helps.

If you want to continue using the VST2, please note that version 1.4.8 is the last version that comes with VST2 support. Any further updates will be VST3, AU, AAX and CLAP only.

[mesayre]

Thanks for the reply. After rebooting I'm still seeing a pretty big difference in performance.But, I guess knowing that VST2 is EOL, probably not worth it to troubleshoot too much. I'll just switch.

This, however, surfaces another problem: automation does not read correctly in DP11 on Windows using VST3. VST2 works, but VST3 doesn't.

I'm reporting this to MOTU as well.

[tasmaniandevil]

Can you elaborate on that? Which parameter isn't automated correctly when using VST3, and in which way?

[tasmaniandevil]

I now see what you mean.
VST3 parameter automation simply does nothing at all most of the time. Only on playback start it sets the parameter to the first value of the automation curve.

I have tried it with SurgeXT, Fabfilter Twin3 and NI MassiveX. Same everywhere.

It seems as if automation is simply not implemented in Digital Performer for the VST3 format.
Please let MOTU know about this, as it's nothing we can fix on our side.

[mesayre]

Thanks for trying that out. I will 'bug' them about it.