VEP 7.0.834

Mac OSX 10.14.4

Waves v.10

 

Just checked, nothing changes...

I tested a bit more, it happens with ALL Waves plugins, AU and VST, VIs and non VIs (INs and FX slots),

even if I detach the window. With Arturia it seems ok now.

Not for me, having the same problem on a Raven Mti 27" and a Philips 32", both 1920x1080, mirrored.

 

Unfortunately for me it happens since the first v.7 release...

It happens since v. 7 especially with Waves, sometimes with Arturia too (both VIs and FX), plugins open with a completely empty interface. No matter what I do, click, etc. Tried reinstalling, changing some preferences, nothing changes. It happens with both VST and AU. VEP 7.0.834 on Macpro running MacOS 10.14.4 (Mojave).

Anyone else has this problem ?

 

Yes, even though sometimes when I load the VEP it seems to scan some plugins anyways (even if I haven't changed anything).. also since version 7 when I instantiate some V.I.s their interface is completely dark... it happens with some Arturia and Waves, but it seems intermittent... but this is another subject...

So it seems by reinstalling all mcdsp and eventide stuff now passes validation...

Gonna try reinstalling Air and Flux

Still having big problems validating my plugins (yes, updated to the last VEP version)

I am on Mac / Mojave. Reset and rescan from VEP preferences.

Here's a list of plugins failing validation (all VST):

Native Instruments Absynth 5 FX
McDsp FilterBank Native v6
McDsp CompressorBank Native v6
McDsp EC-300 Native v6
McDsp FutzBox Native v6
AIR Hybrid
Flux EvoChannel
Eventide 2016 Stereo Room
Eventide 2016 Reverb
Eventide Ultrachannel Native
Eventide Ultrareverb Native
Eventide Ultratap
Eventide Blackhole
Eventide Newfangled Equivocate

Anyone else ?

Thanks

Since when I upgraded to VEP 7 sometimes when I work on kontakt and click on something the window becomes totally empty... I have to close it and reopen it. Sometimes it happens when I switch from ProTools to VEP, but haven't been able to connect precisely to a specific event or click... anyone has this problem ?

Edit : happens with all VIS (not only Kontakt). I've included a jpg

Also I'd really like that when you select an output on a channel (for example when assigning multiple kontakt audio outs) VEP could show the already used outputs with a different color...

Exactly, but you can find so many contradictory opinions out there...

anyways I will invesigate more to make sure this was the cause to what it looked more like a Midi problem to me...

Thank you for your help !

 

That's the problem Paul, it's very intermittent... For example yesterday searching through the internet I found a post by someone who apparently "solved" the problem by turning off the multiprocessor support in Kontakt... so today I tried it, and voilà, problem is gone ! BUT, turning it on again, the problem is not there anymore either... I can't figure out what else changed between yesterday and today.

Anyone else has this problem ?

Not easy to explain and not sure it's VEP related... anyways...:

Vep Pro 6.0.17226 (last version available) used on a MacPro 5,1 12core 3.33GHz, 64G RAM, with ProTools HD 12.5. Mostly use the VEP to load Kontakt instances while recording midi tracks in PT. 

Often, but not always, when I record a midi track in PT, notes already programmed on other midi tracks for other patches (IN THE SAME KONTAKT INSTANCE) get stuck, muted, or play indefinitely. Usually I have 4 midi ports enabled on each VEP instance, for each port I have one Kontakt instance with "All" midi channels enabled.

Might be some settings in the VEP or maybe Kontakt/PT related ?

Other settings I have : 

Multiprocessing : 12 threads, Audio outputs : 32 per instance, Audio inputs : 2 per instance, Buffers : 2

Thanks !

I can confirm this solution works well 

Doing it right now, thank you

Almost every time.

MacPro 5,1 2012 12 core 2x3.33GHz, 64G Ram, Mac Os 10.11.6, Pro Tools HD 12.5

Brian, what solved the problem for me was one particular setting in Kontakt.

Go to Options/Memory, turn OFF the "Use Memory Server" option under the "KMS - KONTAKT Memory Server" tab, then turn ON the "Override Instrument's Preload Size" under the "Instrument Preload buffer size" tab.

The inportant setting is how big you set this buffer size, for me setting it at 90.00 kB made everything completely load before playing, so no more chopped notes, you have probably to try different values until you find the smallest one that makes everything work on your system.

Hope this helps

 

Stv

Hello,
I'm successfully demoing the VEP Pro 5, but I have a couple problems, and just wanted to make sure it's not anything related to the VEP but to other plugins/applications.
I'm using typically 4-5 instances of Kontakt 5 (VST, last version, all updates done) with 64 audio outs into ProTools HD 11 (native) on MacPro 2010 Dual Quad Core 2,4 GHz, 32 GB RAM, running Yosemite.
I normally setup latency to 1 buffer on the VEP Server Interface.
 
When I load a session in PT, the VEP (quite slowly, but that's another story) loads all the Kontakts' patches.
When all seems loaded I play the session, but many notes are chopped or cut, as if Kontakt's still loading samples (I have the option "load samples in background" unchecked in Kontakt).
I have to play the whole session a couple times before having all my notes play. Is this normal ?


Another problem I have, sometimes when I select a stereo bus coming from the VEP as input in one aux/audio stereo track in ProTools I can't select the bus I want. For example I select bus 11-12 but it gives me 7-8.
It seems shifted by 4, some number cannot be selected at all.
I made a little video here :
https://www.youtube.com/watch?v=UIK3aiY2v3E Not sure it's strictly VEP-related, but who knows.

Thank you in advance

S.Galante