Originally Posted by: thenightwatch 
In other words, everything just worked without me having to select the MAS version of the VEPro Ensemble Pro, or de-select the AU version in DP. All I had to do was re-connect the instances.
Are these MAS instances, or do I need to merge projects from an AU instance to a MAS instance and then aim my midi tracks to the new instance? Or has this already been taken care of by VEPro?
Thanks!
Brian posted in motunation a couple of advices about VEpro MAS migration proceeding:
*deselect in preferences>plug-in tab all VE pro AU versions and select just MAS versions (I also reverted to Pre Gen mode).
*use remap midi devices function and change old event input midi output to new MAS multiport VE pro instances
That's all.