I have just installed VEP in a Mac-master/PC-slave setup running Logic Pro X on the master and VEP on the slave. I am doing orchestral work using mostly Play. It seems to be working fine for the most part but I do have a couple of questions.
I am using the one instance per instrument approach I've come across others using for Logic/AU with each instrument's articulations taking up many of the 16 channels. That amounts to a lot of instances for a full orchestral project.
The first question is about Multithreading: With this setup what setting should I use? I'm thinking either 2 or 8 but what would others advise? My slave's CPU is a quad-core i7 with hyperthreading so it has 8 virtual cores. I'll be using around 40 instances or more.
The second question is concerning the fact that most of the time when I re-start both computers and I load up a previously saved project in Logic, I have to manually re-connect all the VEP plugins to their respective instances in VEP. This happens even though I am saving the VEP project as well as the Logic one and whether or not I load that project before loading the Logic one. I believe what should happen is that I'd start the VEP Server on the PC (without loading any project there), then start Logic and as soon as I load the project/song there, the VEP server side should automatically populate and everything should re-connect as it was. This does happen some of the time but more times than not I have to re-connect everything manually, which is obviously un-workable in the long run.
I wonder if this could be happening because I do not have a static IP address on either computer? The reason for this is my provider charges extra for that service(!) So before I pay for having a static IP I want to make sure that that is what's causing the lack of re-connection upon loading. I think that might be the case because it seems that sometimes the address(es) change and sometimes they seem to stay the same. Could that possibly result in everything connecting sometimes but not others?
So can anyone confirm that this is the likely culprit?
Thanks, Mark