Hi.

A fellow composer has just told me about this. I installed the faulty update last week.

A Mac repair man earlier today spent two hours at my studio trying to mend my computer. He had never come across a problem like it. The only way the internet could be accessed was through Chrome - Mail, Safari, iTunes, App Store, etc. wouldn't connect - and my main Mac Pro wasn't being seen as a shared computer by the other Macs on my network.

£210 his time cost me. He left without having fixed it and, on his advice, I am now in the process of a clean install.

I have to admit that I really am not very happy at all.

VSL, can I please ask: why didn't you email everyone to inform them that this update was buggy? If you had have done, I would have been aware that the fault lay with your update and I wouldn't have needed to get anyone out to try to fix my computer. If you'd like to reimburse me the £210, I'll happily forward you macman.co.uk's invoice.

Nick

Hi all.

Any news on a fix for this yet?

Best.

Nick

Hi Will.

The latency problems occur with me irrespective of whether I'm using tempo synced patches or not. The Logic example I sent to VSL last year featured only an individual snare hit.

It happens no matter what plug-in or patch I use, from cellos to synths, arpeggiated sounds to pianos...

Hope you're well.

Nick

You should have all of my emails from last year still on your system with the screengrabs and audio files I attached as examples of the the latency problem. If you haven't let me know and I'l resend.

FYI I doubt whether it's a Logic problem as I experimented with using one of my slave MacBook Pros as the Master and the problems didn't occur - no latency at all. They only seem to happen when using the MacPro as the Master with the servers either on the slaves or solely on the MacPro. Weird!

So unfortunately unless I have the buffer of all my instances set to 0 on my MacPro I'm still having to bounce in real-time.

Cheers.

Nick

Jim.

I've been having the same problem as you since I first starting using VE-Pro last year. 

I brought it to VSL's attention and Maya from VSL tried to replicate the problem back in November, but although a few emails bounced back and forth nothing was resolved unfortunately.

I'm using the latest VE-Pro update with Logic 9.1.1, OS 10.6.4, a Master MacPro and two slave MacBook Pros. The latency issue occurs both when using the servers on the slaves as well as solely on the MacPro.

Nick

Problems here too. Started when updating to Kontakt 4.1, and only affects the last channel. Happens with both versions 5436 and 5814 with a 32 bit server, Snow Leopard and Logic 9.1.1.

Most annoying.

Christian, any news on upgrade paths for specific First Edition instruments?

Unzipping the exe files with UnRarX works a treat. Thanks so much for that.

I'm going to miss a lot of the First Edition legato instruments. Are there upgrade paths available for the flute, clarinet and bassoon in particular?

I agree it's incredibly generous of you. Thankyou.

I'm Mac too by the way. Can't do much with an exe file unfortunately.

Yes. I just registered it. Realising that you 'may' very kindly be offering Kontakt programs to EXS users I went to my registration page and noticed I hadn't yet registered Epic Horns that I bought years ago.

The EXS libraries that I own (and should have registered) are Epic Horns, Concert Guitar, Glass and Stones, Mallets, Solo Strings, and First Edition.

Thanks so much.

Nick

Hi Christian.

The link took me to a Kontakt 2 page, but there's nothing in there.

You've got me excited now though. :)

I certainly hope VSL will make it compatible.

Sorted. Thanks Maya for the great email support. :)

Thanks for that Martin.

Unfortunately, after following your advice I wasn't able to get internet access (either airport or ethernet - my ADSL router is attached to the network switch which must have something to do with it). Obviously I've had to revert back to the original settings - life without internet? Has there ever been such a thing? - but before I did so, all computers were showing up on the network and there was indeed a connection on first launch of the project. :)

It's a shame that my ADSL router doesn't seem to like the manual settings. Any other ideas?

Hope you're well.

Nick

I emailed VSL about this problem last week and got this fantastically prompt response (the VSL support really is top notch by the way):

-----

Do you use DHCP for your slave computers? When the DHCP lease times  
out, and you turn on your slaves the next day - they get their IP  
addresses changed and VE Pro cannot recognize them anymore.

-----

As I'm not much of an expert on networks I don't know how to change this. There are a variety of other configuring options available - Using DHCP with manual response, Using BootP, Manually, Off, Create PPPoe service - but I'm afraid that being the ignoramus I am, I'll completely screw up my system if I start fiddling!

That's fixed it!

Thanks Maya for your prompt reply. Very much appreciated.

Hi.

This is a problem I've had with all versions of VE-Pro. I'm currently using the latest BETA.

When turning on the computers at the beginning of a working day and first loading up a project featuring VE-Pro on two slaves (all Snow Leopard Macs including the Master computer) I get incredibly long load times when it comes to the moment where the Vienna Ensemble Pro plug-in in Logic 9.02 is attempted to be loaded. I launched the current project 15 minutes ago and it's still stuck on the little VE-Pro loading window with the progress bar about a third of the way across.

From experience I know that in about 10 minutes the project will eventually load up, but without the VE-Pro plug-ins being connected to the slaves. I have to click on the VE-Pro plug-ins and connect them manually. Only then will they kick start the slaves to load up their respective plug-ins.

After having saved the project and relaunching, the problem goes away. Until I turn the computers off and start again...

Is this a known bug?

Nick

PS. Any news on the still unfixed 'midi tracks not playing' bug? To use multipe tracks, I'm having to launch multiple VE-Pros at the moment.

Thanks Jay. I tried your suggestion but unfortunately the problem still occurs.

Nick

Sorry. I was a tad too hasty there. Just tried it with a bigger template and the problem persists.

Thanks a lot VSL. Version 4604 seems to have fixed this problem.

Nick

Look forward to a fix Karel.

Cheers.

Nick

Thanks for the link to the other thread. Yep, that's what's happening my end too.

Sorry to hear you're having problems, but glad that Wolfsterik and I aren't the only ones encountering these issues.

Nick

OK. Getting somewhere now.

I took my main MacPro out of the equation and used one of my MacBook Pro slaves as the DAW and the other as its slave. I then loaded up numerous Kontakt midi tracks and they all worked fine.

I guess that this means that the problem is probably at the MacPro end of the chain. Obviously this still needs to be my main DAW, so until a fix can be found (wherever the fault lies) VE-Pro is sadly unusable for me.

Incidentally I've just tried to create a new template omitting Kontakt altogether. Only using Omnisphere, when I reached the fourth midi track the 'no sound but obvious triggering' problem occured.

This obviously indicates that the problem doesn't actually lie with Kontakt at all.

Nick

Hi Maya.

I'm using the latest version of VE-Pro (4536) on all computers. My two slaves are OS10.6.1, my main DAW is OS10.5.8 and the Kontakt version is 3.5.0.025.

The small template (5 Kontakt tracks and 3 Omnisphere) that I emailed you as an example of the midi tracks not working is still problematic. Even when setting it up I wasn't able to trigger the last two Omnisphere tracks 7 & 8 and have reloaded it numerous times to no avail. I've tried taking the second slave (unused in this example) out of the network but it doesn't make any difference unfortunately.

My ethernet hub is a 5 port 10/100 mbps switch. Not sure if this is relevant...

Thanks.

Nick

Edit: Just bypassed the hub altogether and plugged the MacPro directly into the MacBook Pro. Still the same problem, so I guess the 5 port switch isn't at fault.