Hi, I just sent you the VEP. Yes, every channel is affected: all plugins, buses, etc.

Here are the links just in case. One is the VEP6 that was already imported from VEP5 and shows all the channels ‘on' even though some are disabled (e.g all the channels in the Drums & Percussion instance). And then there’s the VEP5 file before importing so you can open it in both VEP6 and VEP5 and see the difference. Please let me know if you need anything else.

 
VEP6:  https://www.dropbox.com/s/dcxwaz31chvqh1a/VEP%20Master%20Template%20%20v12.1%20%28VEP6%29.vesp64?dl=0
 
VEP5:
https://www.dropbox.com/...%28VEP5%29.mframe64?dl=0
 
Thanks!

After upgrading to VEP6 from VEP5 I can't enable channels that were disabled on my template (to save resources). Also, VEP6 doesn't remember the estate they were and show that all are enabled. But those that were previously disabled won't play or receive MIDI (even after turning on/off again, reloading them, etc).

Help?

Loading normally refers to loading instruments inside VEP. What you describe is connection times (e.g how long the DAW takes to connect to VEP), that's why there some confusion. 

FWIS I noticed this thread becuase *I am* having slower loading times when VEP loads my Kontak instruments. I also know some people used to have connection issues, but I think this has been resolved.  

Anybody?

Hey guys,

Having a weird problem here with Zebras + VEP. If I host it on VEP (PC) Zebra output volume won't go down all the way to zero when sending MIDI controllers. Zebra works fine when I host it directly on my DAW. 

I already psoted on the Zebra forum, but haven't heard anything yet.

 

Any ideas? 
Thanks!

I just sent it, thanks.

Hi everybody,

I'm having a bizarre issue that won't let me work at all. Whenever I try to record in a MIDI track pointing to a VEP instrument Cubase will eventually crash. It will playback fine -it only happens when I record enable the track. In fact, sometimes I get the crash just by recording enabling the MIDI track.

Originally I thought it was a Cubase issue and I posted in their forum plus I contacted support. But after a long thread and lots of trial and error, they support person concluded that the problem is VEP related. So here I am...

My system:

Mac Pro 2008 2.8 GHz Quad 26 GB
NVIDIA GeFOrce GTX 2048 MB
OS X 10.8.5
MOTU 2408mk3
VEP with 2 PC Slaves
Cubase 7.5.2 (running in 64b)

I have a crash report that I would love to upload, but don't know how?

Thanks a lot of the help!

Thanks for the info Paul.

Hey guys,

I'm trying to open a vframe that was created on MAC and even though I own all the same synths on my PC (OMNISPHERE, ZEBRA, KONTAKT, etc) the vframe won't open correctly since those were AU instruments. Is there any way to tell VEP that those are actually the same instruments? or a way to convert them before hand?

Thanks so much!

I think the reason we are concluding that is DP specific is because DP needs to use the Event input instances which in turn seem to be buggy. Why are you using them in Cubase (I assume you know you don't need them)? Or are you just testing them to see if they give the same error?

It really doesn't really have anything to do with whether you mix in Cubase or in VEP. You can always send the stems to a VEP bus and mix in VEP if you wish.

Most patches don't really share the same MIDI part, so most of the time you are stuck with 16 and every time you ran out of a port you need to create a Kontakt instance and possibly a new audio bus. With a big orchestral palette it adds up to way too many of them...
Even if you have a fast CPU and the difference is not too much, it's a pain in the ass when you want to add or remove libraries. You have to add Kontakt Instances (or VEP channels) and set the channels for each one. With only one instance or 2 the whole thing would be so much faster.

It's also very useful for moving thing around different vFrames and creating new pallets. And the horizontal scrolling IS a pain :(


In any case, it's not the end of the world, but kind of weird it doesn't work

Not being able to receive more than 1 port in Kontakt is actually less efficient and pretty messy when working with a big pallet.



The main problem is that if you are working with a big library (lets say a brass collection) and want to setup the Kontakt mixer with more than one output (high brass, low brass, brass fxs, etc) you are gonna have to be splitting it several instances and when you add your other libraries you end up with a very large horizontal pallet. Also, since you are limited to 16 channels for instance you will have to create multiple outputs of the same kind of stem (e.g long brass) and then grouping them together in one VEP bus instead of sending them directly to your DAW, so you are actually using more resources too.


When you add other libraries to the same vframe you end up with a big mess, especially if you are using a multiport DAW like Cubase...


Having each library in one Kontakt instance would be much more modular too. You can just load it when you need it, or if you want to move it to another it vframe is super easy since you just load one Kontakt instance.

Hey guys,

I'm trying to setup Kontak to receive more than 1 port in VEP, but the ports 2,3 & 4 are disabled, even when I set the MIDI ins as OMNI. Anyway to setup this or do I have to create a Kontakt instance for each 16 MIDI tracks I use?

Thanks!

Hey guys,


Any progress on this? I'm also having this issue. I can also confirm that it doesn't happens with DP or Logic. It does look like something Cubase needs to resolve with Kontakt in collaboration (instead of throwing the ball to the other side).


This is a pretty big issue, hopefully it gets resolved soon...


Thanks!

I tried this, but it happens with too many different libraries...


BTW This thread shouldn't be marked as "solved" The solution was a work around that doesn't really work for other people and the basic problem is still there.

Yes, it's a bit of a nightmare here...



I'm slowly moving to Cubase for this reason (although Cubase is having some other big issues as well)

There was a survey on the VI-Control forum and Cubase was the most popular DAW by a large margin. Second Logic and third DP.




Many of the composers on the VI forum tend to be younger, so that might be why DP didn't get more votes, which is still very popular among more veteran composers, but in general Cubase tend to be more common, especially with European composers. DP has lost a lot of ground and Cubase seems to work better with VEP, so I think this tendency will continue.




For recording PT is the undisputed champion, of course.




I think DP is still the best software for film scoring as far as features and workflow goes, but the lack of support for VEP is becoming a deal breaker for me, so I might switch to Cubase.

So, no hope for DP users then? It's been way to long….

It's not clear who can (and should) fix this issue, so I'm posting in both forums. I know Vienna is aware of this problem, so I'd like to hear if there's any progress with this issue.

So I just did some testing and the issue is still there. Any updates regarding this fix?

So this issue hasn't been fixed yet?

I just updated to the DP 8.05 hoping this last updates fixed the stuck notes, but haven't really tested it yet.

BTW This issue was also on DP 7.24 and the workaround was also to turn the delay compensation off.

I'm having this same problem and found this thread from long time ago. This hasn't been fixed yet? Any workarounds?

Same problem here. I've posted it a while and Vienna is aware of it. Not sure where they are with it. I was just refreshing my post and found this thread.

Hey guys,

Any progress on this?

Thanks

I'm on Mac and have the same problem. I'm only using AU instruments (no VST). Actually, this problem has been on DP since ver 7 when it couldn't run VST.