I'm a DP 7,24/VEP4 seasoned user. Since I inserted VEP and a Slave PC in my rig my workflow toke a leap forward and let me achieve results that with DP alone in a single machine I couldn't get.
In time I learned too deal with the little quirks that DP/VEP relationship revealed, the most annoying of them being that VEP tracks are not "Delay Compensated" (so I must always find the right amount of time to shift midi tracks by hear and, if I'm forced to change buffer size to lessen the burden on the CPU, I have to start over the process).
Another thing I leaned - from the precious contribution of VEP engineers in this forum - is that the more VEP plugin instances are opened, the more power is demanded on the CPU. So theoretically it would be better having just one plugin opened with 6 full Kontakt plugs (64 midi x 6) than multiple VEP instances with different Kontakt plugins.
And to achieve this goal VSL came up with VEP5 and Event Plugin, which let us AU users to override the 16 midi channels AU spec.
Than I understood that DP8 finally fixed the Auto Delay Compensation issue, fixing the way DP reports numbers to VEP plug In.
I have a very large template with 12 VEP full Kontakt instances and I could make use of the resources that narrowing the number of instances (with the Event Plugin) could be freed.
Now, I read here and there that things are not completely ironed out between DP8 and VEP5 and I would really appreciate if DP(7.24 or 8.01)/VEP5 users could chime in to state their current situation. What works best for you and what not (and your personal workarounds for what doesn't work).
Thanks in advance.