Well that's depressing. I figured this would point to something obvious for someone. Rats.

 

The slave PC's 64 bit server isn't seen in on the Mac DAW in Logic Pro X, but the 32-bit is.  Thoughts?

And what do you have to put where to make that happen? My VEPro sees only the biggies that I assume installed themselves. What if I want to use some tiny synth nobody ever heard of in VEPro? How do I make VEPro see a synth?

Okay... a few hours later, it's fixed. And although I know what I changed, I don't know why it mattered. If somebody can fill in the reason, it would perhaps make this a searchable solution for others.

I looked at the slave pc's network and saw that it was "public." I chose "home." That's all.

I assume "home" is trusted and that security dropped. But I'd love a thoughtful explanation.

My old setup involved two machines getting internet and network from an older motorola wireless router.

New setup necessarily involves an airport extreme instead. I can't get out of this for now. I could add a switcher but can't remove the airport express. I don't want to run a cord between the machines directly, because then the PC won't see internet.

Synergy mouse and keyboard sharing work fine across the machines. But PC slave's VEPRO instances aren't showing up in the Mac DAW.

What to do? And if the answer involves setting up IP addresses as I expect it will, assume I don't know how to do that at all please.

thx!

Thank you both.

Did essentially what you advised.

I reinstalled Kontakt and directed the vsts into the common files folder and then pointed VE Pro at it by adding the folder to VE Pro ==> Prefs.

Everything good now.

probably an age old question.

"Add VSTi" menu doesn't show kontakt or any other NI ... only shows play_VST_x64.

How do you fix that?

I neglected to mention, I'm not especially good with network type stuff especially on a PC. But I'll try to figure out how to open ports. Thank you!

VEpro on the DAW is working locally, but the instances on the client are not shown anymore.

My DAW has been through two changes of late. The video card was replaced, and the router/gateway is a new one. I'll ilustrate because this is where I'm guessing the problem might be.

-- The previous router gateway was a wireless router. Internet was coming in and being served to wired and wireless clients in the studio.wall --> internet portDAW --> port 1slave --> port 2-- The new router is set up differently... it is a client... in other words, only the 1-4 ethernets are being used... wireless turned offwall ---> port 1DAW --> port 2Slave --> port 3printer --> port 4-- The builds on the DAW and slave do match. And they've been up and downgraded just as an experiment but neither of the two most recent builds solves my problem.thx!

And the answer is "yes."

Updating Kontakt Player to 4.1 from 4.0.5 fixed my problem in 5814 64-bit.

The only thing I can think of that has changed in my system is that I installed the K4 player and maybe added a couple of libraries to it. Is there some way that would corrupt the VEPRO relationship with K3.5?

Edit: A couple of restarts and a day later 5814 32-bit is loading k3.5 again, so maybe it was nothing. Getting a K4 Player upgrade now. Will see if it loads into 5814 64-bit shortly.

In my case, no.

I just updated to 5814 yesterday, (sorry I don't know what version I just replaced) in the hope that the problem would go away. It didn't.

The only AU's that are available are Apple DLS and Spectrasonics. There's nothing NI at all.

perhaps related, perhaps not, but...

today is the first time I've launched VEPro since installing k4 player. And not only do I not see k4 player as an AU, but mframes full of K3's won't load now either.

Will mess around and report back.

I'm doing something wrong.

I start VEPRO servers on a DAW and a Slave. Then I launch Logic and open my template. The VEPRO's on the DAW connect nicely.

But on the slave, duplicate vframes load into the slave's vepro server. So instead of 6 instances, I now have 12 and it's the latter 6 of them that say "connected."

What's desirable here is simply to load the VEPRO's and have the template not loading samples, right? So crashes or project changes don't necessitate sample loading times. Right?

Correct. Thank you both. Different beta versions was the problem.

anybody know why the master bus on my slave VEP instance would jump to zero as soon as I play a note?

slave is a pc.

master is a mac. 

latest beta's I believe.

And is there an instance limit? I'm finding that a sixth one causes things to hang, but it might be happenstance.

Will be a problem at some point, on my MacPro and on some PC's. And even if we're not pushing the limits, the question is still interesting.

PLAY for example is generally considered, on mac at least, more efficient at running many instances containing one patch each than one instance containing multiple patches.

I definitely want to know best practices here if anyone has the answer.