Its a big template and takes about 3 to 4 minutes to load. But takes over 7-8 minutes to quit VEP!

That's longer than the already too long save time of 4-5min.

At the end of the day/night waiting 6 to 10 minutes before I can turn off my PC is very annoying and I've taken to force quit by shutting down (after saving of course).I have 3 dedicated farms and they all take nearly double the time just to unload/quit the app than they do to load or save. The more samples loaded the longer.

Will force quitting do any harm to my projects or the app databases etc?

Why cant VEP just bail quickly? Once Ive saved why does it have to spend all this time unloading samples? Just dump them already.

Windows 11, 12900k/128gb, nvme, VEPro7.1.1384 (happened since v6), Nuendo (already quit N12 before though)

Is anyone here composing with MIR Pro 3d loaded and running on their VSTi?

If so what is your buffer setting. I saw somewhere MIR prefers 512/1024

Im finding the latency a bit too high. I normally can run at 128 but Nuendo cpu gets really jumpy and occasionally clicks, even on my 12900k/32 GB ddr5 machine.

Playback with no midi track monitored live is ok but I'd like to be playing and instrument whilst hearing it.

Thanks for the quick reply Dietz. I just edited above to say

"to homogenise those beds with an "overall space" and spot 3 or 4 instruments as ambisonics/atmos objects and send from those to MIR. Is this approach possible or flawed?"

Yes I see what you are saying. More object orientated. 

edit: what if my groups are 7.1.4, or anything greater than mono or stereo?

Hi thanks for the great news!

I am installing the demo now and considering signal flow, bus setup and room library.

I really like the 7.1.4 space I can create with vsti multi mics, when they are available, so I dont want to loose that. I'd rather use MIR Pro3d to homogenise those beds with an "overall space" and spot 3 or 4 instruments as ambisonics/atmos objects and send from those to MIR. Is this approach possible or flawed?

Should I replace my VSTi out channel sends to 7.1.4 alg reverb with MIR or is it better to add one on the instrument buss? 

More background info:

• My monitoring is 7.1.4 speakers in Nuendo 12, windows 11, 12900k/32GB/NVME/HHD. All of my VSTi and final busses are 7.1.4.
• Currently I "construct" a 7.1.4 bed to taste from the vsti using multi mics and a 7.1.4 alg EA reverb send. From instrument bus to master my path is always 7.1.4, so mono or stereo sound sources are using steinbergs multipanner to the bus.
• It's a big template, 200+ instrument busses. The main DAW is bringing in all 500 or so VEP7 inputs from servers. It just runs FX, small amount of audio, all reverbs and no VSTi at all.
• To maximise instrument count on my slaves I have disabled all their reverbs where possible. I am not looking to install MIR Pro3d on the slaves and I'm happy with the multi mics in pairs to the DAW.

I have chosen Synchron Stage, Room 6 to demo as well.

I used to run MOLCP3 then moved over to Copperlan over 7yrs ago. Been happy ever since.

http://copperlan.org/index.php/download

I too am very annoyed with the license downgrade or double the price. And wont upgrade until I see their cards on the table. It better be good!, VST3 and AU3 - hello! Better audio FX insert workflow, network, cpu efficiency.

Describing it as if "you lose nothing just keep using v6 in addition" is just dressing it up BS and insulting our intelligence. Yes I could still use win98se with the software from back then but I actually dont have a choice in terms of running a business.

We know for SURE you cant connect v6 slave to a v7 host or vice versa. It is confirmed! Period!

They are stopping development of 6 - that will eventually become bugy and left in the dirt as OSs and plugins move on, needing the latest.

This is a server/farm based product! I will eat my hat if there are more users who use just one pc or even 2 and will NEVER need that extra license. The 3 licence core product of previous is a good and natural feature for such a product.

Mediocre FX (that wont work on anything but inside VSL products) and a generic sample library are a bit of an insult really.

Actually there IS a competing product. Reaper with Reamote or Reastream. This upgrade and the way they are trying to BS us and avoid the real truth in the marketing along with a big step up in expense and future new high level of pricing that will continue to hike is making me look closer at Reamote. VSL now remind me of AVID! Trying hard to hold on to their overly expanded infrastructure by scewing their users! I left AVID for Reaper.

I vote for granfathering the 3 licenses accross and wont upgrade until THEY treat us with respect.

+1

+1

I'm posed with the same sort of dilema going from v6 to v7.

Do I have to upgrade my 3 licenses? I thought last time I upgraded from 5 to 6 I only needed to upgrade one main lcense and the others followed.

To upgrade my main license plus 2 additional ones from v6 to 7, do I really have to pay:

EU 75 + 45 + 45 = 165?

if so, firstly I think thats too expensive given that there's not much in the upgrade except a promise of "more to come". Secondly is it arbitrary what license I choose to assign the main EU75 main upgrade?

What If I only upgraded my main DAW license and not the other 2, will it run, will I get the benefit of the upgrade on the farm PCs?

Thanks Paul

Note that the only way I could stop it crashing was to let it download again and install over.

There must be something in the automatic install process or the automatically downloaded version that is different form the MyVSL version.

UPDATE: I completely re-installed after searching thru all system folders for VSL and deleting, Again came up with quest on both PCs to update to 6.0.15401 even though that is what I just installed.

**So this time: I let it download and install again the same version. (refer to ** in previous post)

Note: This time on remote server, a firewall rule request came up on 1st load which I allowed. This was probably because I used CCleaner the clean registry after de-install. There were firewall rules that were removed here.

Once the RE-install was done on each computer and I loaded up and connected, no problem. Problem solved.

Is there a difference in the install file downloadeed from MyVSL compared to the one that VEPro downloads vias automatic update? Or is there a file not installed properly by the stand alone installer?

What is the MSVCR120.dll error from?

I am getting and instant crash when connecting to remote empty instance from any daw software. Plugin/client will see the remote server no probs but once I press the connect button, bang crash.

• Have tried creating an instance first, able to load plugins etc
• have tried vst2 and 3
• have tried different buffers
• have updated windows 10pro 64bit to latest anninversay edition on remote since issue started (to re-test) but no difference. My main workstation is on deferred updates hence on win 1511
• VEPro 6.0.15401 on both systems
• have deleted vst cache and rescanned
• happens with no plugins loaded ie new empty instance or plugins populated - doesnt matter.
• once finished VEP update and opening for 1st time VEP asked for update to 6.0.15401 even though I just did that.. Happened on all pcs. **EDIT: This first time when asked to install 15401 I cancelled the download/re-install because I had just updated to 15401

crashes with this windows log report:

Faulting application name: Vienna Ensemble Pro.exe, version: 6.0.0.15401, time stamp: 0x5809ef17

Faulting module name: MSVCR120.dll, version: 12.0.21005.1, time stamp: 0x524f83ff

Exception code: 0xc0000005

Fault offset: 0x000000000003c963

Faulting process ID: 0x198

Faulting application start time: 0x01d22f3bda4b6801

Faulting application path: C:\Program Files\Vienna Ensemble Pro\Vienna Ensemble Pro.exe

Faulting module path: C:\WINDOWS\SYSTEM32\MSVCR120.dll

Please add the ability to use VST3 plugins inside VEPro. Including the audio input version.

It seems odd that VEPro has a VST3 version of itself yet it doesnt support vst3 plugins inside it!

And please make sure that we can load the vst3 plugins within a vst2.4 instance of VEPro because then it will solve the issue of the host not being vst3 compatible. ie VEPro becomes a vst3 to vst2 wrapper.

PT11 doesnt have these settings is there an alternative way to ensure this in windows 8 pro 64bit, vepro latest, pt11.1.2hd?

I would get this occasionally with windows 8 but recently after updating to 8.1 many of my programs are loading on the wrong monitor which makes it extremely hard to grab if that monitor is off and in another room like mine. Dam inconvienient I say - probably a microsoft issue though. It would be nice if VEPpro had a key command for switching monitors on an extended desktop.

Thanks for replys. Well today it didnt happen. Loaded fine. Weird. Maybe it is a win8/pt thing. Hope it's not one of those things that happens intermittantly just when you dont want it.

Out of interest was there VEP update that improved it earlier in this thread? Something to watch out for?

BTW Decouple mode was off. Will update to 12508 and report if required

Cheers

Im having the same problem. With Win8pro 64bit updated and VEPro 5.2.12800 on all machines. In PTHD11.02 I save the project come back next day to load and all the work done in Omnisphere is lost, the multi is empty. Wishing I had saved from the remote VEPro machine to a unique name but I shouldnt have to. Any solution yet?

I sent it in couple of hours ago. Did you receive?

Its actually comforting to know that you have same problems because I've been through everything and no one was listening. Now there's 2 of us.

Anyone? Please give me a clue.

Is anyone running VEP with 11.01HD without crashes on exit?

1) If so are they both latest versions?
2) Is your network set to a static ip?

3) Have you tried low buffer settings like 64 or 128 samples?

I'm now running RME digiface instead of Scope, VEP v5.1.12377 on main DAW and on 2 remote servers

Further testing shows that when I use a Scope card and change from a song with VEP and a song without VEP it crashes (I think due to flakey ASIO drivers of Scope) but when doing the same thing using the RME there is no crash at that point. But when I finally exit PT it crashes.

If in any one session with PT I dont load a VEP instance there are no crashes.

anyone else getting this with pt11HD.01 or is anyone running VEP with protools 11.01HD and not getting any problems?

I'm consistently getting a bex64 crash on exit anytime a VEP is loaded. No bex64 crashes when there's no VEP. I think it is also corrupting the protools driver or something because now after second re-install it keeps crashing with runtime 6025 errors with not muchloadedat all.

I'm able to change from one song with VEP to the another without VEP with no bex64 crashes but now that protools is corrupted somehow i get crashes all over the place.

Thanks. I updated win 8 earlier today. PT was like this before though. To track it down I updated bios (tested before and after), redid all settings for cards, windows optimizations, switching between sound cards. I will try changing songs instead of quitting.

Mine is bex64 event as well.

hi

v11.01 downloaded 2 days ago

Just tried a different soundcard/driver (FF800) and closing PT11 with VEP loaded still produces a crash. Anyone else?

Hi

When ever I load a VEP aax64bit in PT11 it will crash on exit. Some projects that contain VEP will crash upon loading. I have tried using diiferent asio drivers/sound cards. Has anyone else had this issue?

Setup:

VEP 5 aax 64bit latest version

i7 3930k/32GB GSkill/2011 chipset
Asrock x79 extreme6 (not OC'd, all C states off, no HT, no turbo or speedstep or VT)
VirtuVia PCIe to PCIx4 external expansion with 550w ATX PSU
Windows 8 pro 64bit, Scope 5.1 64bit
Scope Pro 14dsp NFR(2002) w/24 ADAT, Scope Project 6DSP (2003) w/24 ADAT, Sync plate) in VV
Currently HPET is on w/dynamic tick disabled, previously had dynamic tick unchanged (enabled)
Dedicated word clock distributor with all ADAT i/o utilized. All sound cards run from WC from the master clock.

Ben