VEPro MAS version is out

[labman]

Willie. In our experience, DP runs like greased lightening when offloading the VI's to VEP. It is shocking how efficient DP seems to become. I would suggest running the VEP instances decoupled, and just save any project specific metaframes inside the DP project folder. Or if you are always using the same basic orch template, just load it at the beginning of each day, launch DP, and you are off to the races. (Note: if doing that scenario, you can still load some K5 instances inside DP for mission specific insist without loading DP down much)

Hats off to Paul and the folks at Vienna for the MAS version of VEP which is truly a thing of beauty.

[dreamuse]

I have a rather naive question about MAS instances: As it's often better to have multiple VEP instances --too allow multiprocessing-- what is the advantage of creating one big instance with, say 48 tracks? Is the overhead of each VEP instance so great that it's good to reduce them via this method?

Much thanks,

Len