Title sums it up. I open my template in VEPro 4, fire up DP...and what *should* happen is that DP connects to all my instances that are loaded. Instead, it keep creating all new ones, ignoring the ones that already exist. I've tried preserving the new ones, deleting the old ones, etc...but every time I load the project in DP, it just keep creating new instances. This only started happening with Mountain Lion, and yes, my software is up to date. Anyone?
-
DP Opening New Instances Instead of Connecting to Existing
-
Ok...so why would it suddenly start behaving differently when I didn't change anything? Also, IP address? I'm on one machine. I see on the "server interface" there's a thing that says "Slave: 127.0.0.1" but I have no idea what that's referring to since I have no idea what that IP is or where it came from. What am I missing with that? Also, "instance name" is defined in VEPRo itself. I don't understand how the plug-in has any kind of access to the instance name. If it does, where can I edit it? For example, in my metaframe, I have an instance called "VE-WW." In DP, I have a VI with a VEPro plug-in. Forever and always, it has automagically connected my "VE Woodwinds" Aux track to the "VE-WW" instance in VEPro because that's what I connected it to when I first started the project. But now, it just creates a new (unnamed) instance out of nowhere.
-
Hello AaronG,
Please note, that the VE PRO Server Preference "Open instances minimized on load" only applies when loading a Metaframe, but not when you open a project through your DAW.
Would you mind sending us your Metaframe and a zipped copy of your DP project to so we can better look into your other issue?
Best, Marnix