Same here.  When the solution to the problem is "give us more money please" I feel scammed.

The templates are somewhat fixed so this is the closest solution so far, but this is still not the most efficient or elegant solution...

I'm shocked that this isn't something that comes up all the time!

Hmmm... 

Is there a way to do this so that A&B can still share files with each other and see our shared network drives?

Hi All!

I can't imagine this is a unique problem but I can't for the life of me figure out a solution to this.

We have two identical rigs in our writing studio.  Both are new Mac Pros (trashcan w/ Sierra and running Logic X 10.3) each with its own Mac Mini which is running VEP and Vienna Instruments.  

Everything is running like a dream except for when I open a project that was created on Rig A on Rig B.  On Rig A the project points to Mac Mini A's VEP and Vienna Instruments.  When I open it on Rig B I would like the project to load using the Mac Mini B's VEP and Vienna Instruments but instead it is connecting across the network to Mac Mini A! When this is the case Anyone working on Rig A can't connect to the Mac Mini A VEP Server.

Is there a way to force my rigs to ONLY point at their assigned Mac Mini and VEP Server? We work in a very fast environment and reconnecting each instance on load isn't an efficient solution.  

Does anyone have experience with this?

Thank you all so much!

Hi,

I have some old Vienna percussion giga samples and I'm wondering if there is a way to load them into VI (SE)

Any ideas?