Hi Phillipe

Well, I have that exception in place, and even if I only enable Bitdefender on the Slave (I haven't even tried on the host system yet - there I still have Bitdefender disabled), my host fails to see my slave completely.

For now I have Bitdefender disable don both systems - it's the only way I can work.  I'm using Bitdefender Total Security 2016.

Jules

Originally Posted by: Philippe BAYLAC

Hi Trailerman,

try to create these exception rules in your Bitdefender firewall(s) :

vienna ensemble pro.exe (Authorize)

vienna ensemble X64 (Authorize)

Best.

Philippe

Hi Phillipe

I'm not seeing the X64 app at all.  Are you sure that still exists in VE Pro 6?

Jules

Originally Posted by: Paul

HI Jules, 

Did you open the network ports as described in the VE PRO 6 manual on pages 3/4/5?

Best, 
Paul

Hi Paul

Unfortunately Bitdefender's Firewall is application rather than Port based.  I have created an exception for the VE Pro app, but it's still blocking all VE Pro traffic, such that the host does not see the slave at all if the firewall is enabled.  As soon as I disable it, my slave pops up in the host plugin GUI.

For now I've disabled the Bitdefender Firewall completely, but am still seeing intermittent issues with the slave not being seen.   I'll perservere, but am not quite sure what else to try.  Bitdefender didn't cause problems previously so I guess an update has messed things up, or changes in the VEP networking protocol with v6 are perhaps working differently to V5.

Thanks as ever.

Jules

Mmmmmm ... having been sure it was a Bitdefender issue.  My slave has yet again completely disappeared from my VE Pro host, even with Bitdefender disabled.

Bitdefender is definitely involved - I could see the slave disappear/reappear as I turned it on/off - but it looks like there are still other issues with VE Pro networking.

It's getting very frustrating.  I'm using fixed IP addresses, both systems see each other 100% reliably via all other network connections, but in VE Pro it's toitally flaky and now seemingly random whether it will or won't work.

Jules

Hi

I've been having nightmares with network connectivity in VE Pro for the last few days.

I finally worked out today, that Bitdefender's Firewall now seems to be blocking all VE Pro connections via the network.   If you have it active on the Slave system, the host cannot see it at all.  I can literally watch in the plugin connection GUI - as soon as I turn off Bitdefender Firewall on the slave system, it suddenly appears in the interface.  Turn it on, and the slave disappears again.

Does anyone have any idea how I could add VE Pro to my Bitdefender Firewall rules, so that it is no longer blocked?

No idea why this has changed, but it's potentially going to cause problems for anyone connecting over the network.

Jules

Originally Posted by: MS

Could you please send the crash reports?

Mine was more of a hang than a crash (ie. VEP becomes unresponsive, white screen, have to manually force quit the process) - I just checked the crashdump folder and no dump was created.  Next time it happens I'll run a manual process dump when it hangs.

I'm afraid I'm seeing similar issues.   With Play 5, my template often doesn't complete loading, and the Play load progress bar remains on screen.  If I try and do anything to my Play instance within VE Pro, VEP6 crashes.

I was really hoping Play 5 would finally solve the ongoing unhappiness between Play and VEP but I'm afraid it's no better here and possibly worse.

Jules

Thanks Simon - I'm glad I'm not the only one.

Thing is, it's not at all subtle, the difference is really obvious.  Although EQ'ing can help, it causes it's own problems, because one then has awful sounding, over-EQ'ed dynamic and staccato samples, merged with ok sounding longs.

It would be really good to hear something from VSL, because I'm pretty sure either a) the dynamics they sampled for the longs were not as loud as for the shorts and dynamic samples or b) some kind of filtering/EQ'ing has for some reason been applied to certain articulations (more likely from what I'm hearing).

Jules

Hi

I've owned Vienna Choirs for a few years now, and keep trying to use them in mixes, but always struggle with the tone.  To my ear, the sustained articulations (even at the highest velocity/vel-X level) sound like they have a low-pass filter across them, so that all the fizz and breath is removed from the samples.  

The issue is exacerbated by the fact that the staccato articulations, and the dynamic swells don't suffer from this - the breath and sizzle is very present, whcih makes it even more glaring when switching between articulations that something is not right with the sustains.

The issue is particularly noticable with the Sopranos.

Ami I missing something?  Is there some hidden setting which is causing an LP filter to sit across some articulations and not others?   I've checked everything obvious iin VI Pro and cannot see anything unusual.

Thanks for any suggestions or feedback.

Jules

Sorry - hadn't realised this thread was being updated.

I'm running Mir as a plugin in ProTools (NOT within VE Pro) and seeing the issues described every time I load my ProTools session.  I have now discovered that I can get Mir working by shutting it down (whilst leaving ProTools open) and then restarting Mir standalone.  When I do this, ProTools seems to connect to Mir and Mir loads the correct venue and Instrument settings.

Jules

What are people now doing in order to avoid glitches with Cubase/Nuendo tempo changes?

I have an orchestral track which needs lots of tempo changes and every time Cubase/Nuendo hits a tempo change node, I get CPU overs and glitches.  I've even had the odd crash.

I'm using VE Pro servers on 3 different systems, albeit with Kontakt instances only running on 2 systems (probably about 70 Kontakt instances total).  Do I need to go through every Kontakt instance and disable ext tempo sync for each one, and will that do the trick?

Many thanks for any help.

Jules

It's definitely Mir related.  Nothing else has changed on my system.

Seeing the exact same issue today: first load of ProTools session, Mir loads but does not load a venue or any instruments.  Shut down ProTools, Force Quit Mir, reload ProTools and load session, and second time everything loads correctly.

I am seeing the exact same issue with ProTools HD 12.4 on Mac (OS 10.9.5).

Yesterday after installing the Mir update, my first session load in ProTools loaded Mir, but with an empty venue and no instruments loaded.   I had to restart ProTools and forceibly shutdown Mir and second time it loaded correctly.

This morning I'm seeing the exact same problem - first load of my template in ProTools and Mir appears but the venue is empty and no instruments are showing.  I'm currently trying again to see if it loads second time.  This will become an issue if it happens all the time.

Let me know what information I can provide to help resolve.

Jules

EDIT: Again, it loaded correctly on the second attempt.

PS. This has only started happening since I updated Mir and VE Pro to latest builds yesterday.

For a moment I was excited.

Great shame that this remains unresolved.

Hi Paul

I just managed to resolve it!  I'm 99% sure that some parental control software which was installed on this machine (which is now my son's) was interfering with VE Pro.

The software is called Qustodio and uses VPN technology to limit network/internet interractions.  I uninstalled it, and VE Pro server is now running fine.

Kind of a weird one, and unlikely to crop up again, but worth knowing I guess.

Many thanks for your help.

Jules

Thanks Paul - tried and failed I'm afraid.

I've moved all my VST and Component plugins into hidden folders so VE Pro doesn't scan them on startup.

Still getting the Server Object error every time I try and launch, even after a fresh reboot.   Happens with 32bit and 64bit versions.

Anything else I can try?  What else might cause this error?

Thanks again.

Jules

PS. Is there any way to bypass the plugin scan process as VE Pro starts?   I trashed all prefs reinstalled and rebooted and first start VE Pro seemed to be loading and started scanning plugins, but it subsequently crashed and now gives me the same error again.

If I could bypass plugin scanning (or change the directory it's looking in) I might be able to get it to load up at least.   I can't remove/hide all my plugins because I need them for Logic, but I could move just the ones I need in VE Pro and perhaps get things working that way

Thanks

Jules

Hi

Just installed VE Pro latest on an old Mac Pro in order to revisit a track for a client.

For some reason, VE Pro standalone launches fine, but VE Pro Server (64bit or 32bit) always fails to launch with the "Unable to create server object" error message.

I realize this is normally due to VE Pro or one of its background processes running already, but in this case there are no VE or other VSL processes running at all.  I have checked repeatedly in activity monitor.

Please, what else might be causing these errors?  I've uninstalled, reinstalled and done everything I can think of, but failed to find a solution.   I somehow have to get this up and running so I can deliver stems today, hence the slight tone of desperation.

Many thanks for any help.

Jules

+1

I'm having to rebuild my main metaframe at the moment because VE Pro has started crashing, and being able to shift vframes around within the metaframe would save hours of time.

It would be good to get an uypdate on this situation.  If memory serves, it's been almost a year since this issue was identified and I'm unclear on where things stand with regard to a resolution.

I can live with older versions of Nuendo and Cubase for now, but I have Cubase 8 and Nuendo 7 licenses which are currently redundant, and at some stage I can't help feeling that something is going to need to done.

Has any progress been made?  Are discussions still taking place?  Any news gratefully received.

Jules

This is a little worrying.

Clearly those kind of latency figures are not going to be workable, which leaves us back with the audio dropout issue, which for me personally is also unworkable.    Turning off AG2  for VE Pro is not really a fix - for bigger sessions I saw CPU overloads which I did not have with Cubase 7.x / Nuendo 6.x.

For now staying with older versions of Cubase and Nuendo is fine (this is where I've ended up), but can only really be an interim solution.   Unless VSL are now drawing a line and saying that VE Pro is no longer fully supported in current iterations of Cubendo, I can't help feeling that the onous to find a way forward lies on this side of the fence.  Certainly there's no public sign of Steinberg being willing to update it's PDC implementation for the sake of 1 plugin, much as we might wish they would.

It would be extremely sad if Steinberg DAW users no longer enjoyed full compatibility with VE Pro, because the combination is exceptionally powerful.   Reading between the lines though, it seems the issue is not going to be resolved any time soon, and judging by the fairly low numbers of contributors to this thread, I can only assume there are relatively few users affected.  That being the case, I don't see it getting a lot of attention in the near future.

It looks like Nuendo 6.5 isn't going to be uninstalled any time soon, but here's hoping.

Hi Martijn

What version of Cubase 8 (there's an update just out or due out soon I think)?  It's possible there's been a fix on Steinberg's side, as I know they've fixed some MIDI issues.

Have you got Asio Guard manually disabled for the VE Pro plugin individually perhaps (Devices->Plugin Manager->VST Instruments->Vienna Ensemble Pro->show info and check if ASIO GUARD button shows active or not)?

Can you perhaps test with a buffer size of 512 samples and see if you still get no audio dropouts?

Fingers crossed there's been an unreported fix somewhere down the line, but I suspect it's something else.

Thanks for your help.

Jules

Originally Posted by: paaltio

Yes this performance regression has been a constant in my tests, and a similar difference was already present in C6 -> C7.

Would it be possible to have a "set the number of buffers for all VE Pro plugins" button like we have for decouple all? Would make it a little easier to at least manage our own extra buffers in large sessions if we can't use AG.

Thanks,
Panu Aaltio

Hi Martin

I would also be interested to know what the latency implications are for having the VE Pro plugin run asynchronously.  As things stand it seems that the new VST SDK and proposed VE Pro implimentation does not resolve the situation in any way - we are still left with either audio dropouts (if AG2 is enabled) or increased CPU load (if it's not). 

I would really like to kow how bad the additional latency would need to be, in order to run VE Pro with AG2 enabled but also accomodating Cubendo's need to rebuffer.  One way or another we're going to need to find a workaround, if not a solution, because remaining on legacy versions of Steinberg software is only going to be possible for so long.

Would some kind of external MIDI workaround resolve the situation, such that instead of selecting the VE Pro plugin when you select a track in Cubendo, you're actually selecting a virtual MIDI port, which is then in turn routed to a VE Pro server instance?  Would this mean that Cubendo does not need to reset it's audio engine every time a track is selected?   Just trying to come up with ideas ...

Thanks for any more info.

Jules