Hi, 

I am unsing VEP on Win 10 and wonder if I install it on mac, can I load all instances that had VST Samplers and Plugins  wihtout problems ? I 

I remember some thread talking about not suppor VST 3 or no VST support on mac at all ? Could somebody clarify please ?

 

THanks, lokotus

Yes, Latest Software: 

I think I fixed the problem. My Horror Settings were: ASio Guard Enabled in "High" Setting was causing this killing nosie blast / burst effect in Cub 10 Win 10 64bit. TUrning Asio Gard off for VEP semes to have solved it. Also one could try out Asio guard Medium setting but still, be carefull. (I also used maximum buffer setting 4, but I think that doesn´t have anything to do with it)

This has to be marked RED AND BOLD on the Purchase Page and in the VEP manual so you can find it google search. Never ever you ASIO GUARD ENABLEND IN CUBASE WITH VEP ON HIGH SETTINGS. BE CAREFULL WHEN IN "MEDIUM" SETTING. TURN IT OFF FOR VEP TO BE REAL SAVE. 

It could damage yours ears, monitors etc. The Noise can get about over 50db above 0dbfs , which is insane. I have never seen work fabfilter limiter on the masterbus so hard (MAXIMUM INSANE REDUCTION) 

I highly recommand the free plugin Ice9 on the master bus when working with VEP or noise blast, burst from other plugin, which sometimes happens. https://www.pluginboutiq...ols/72-Utility/2759-Ice9

It will mute the signal over a given threshold, which is much better than using a limiter. 

If you want to test this bug on your system, replicate my horror settings on a big cpu taxing project, turn the monitors levels way down and don´t use any headphones + use Ice9 on the master bus. When you toggle between any cubase internal VI instrument or channels and VEP Channels you might be able to reproduce this. ( I am using VEP as a local software on the same Computer)

@VSL: If you can reproduce this: Please sit together with Steinberg for the new VEP release. You just can not release a software with certain settings that could potentiall kill your career. And if you can not solve this problem but reporduce it reliably, please make this BOLD AND RED everywhere and also when the information box for installing VEP appears. 

I can´t image a worse bug in my entire live. The next step is a bug that burns your motherboard, - but even with that, your ears could survive it :)

Thanks, Cheers, lokotus

I think I fixed the problem. My Horror Settings were: ASio Guard Enabled in "High" Setting was causing this killing nosie blast / burst effect in Cub 10 Win 10 64bit. TUrning Asio Gard off for VEP semes to have solved it. Also one could try out Asio guard Medium setting but still, be carefull. (I also used maximum buffer setting 4, but I think that doesn´t have anything to do with it)

This has to be marked RED AND BOLD on the Purchase Page and in the VEP manual so you can find it google search. Never ever you ASIO GUARD ENABLEND IN CUBASE WITH VEP ON HIGH SETTINGS. BE CAREFULL WHEN IN "MEDIUM" SETTING. TURN IT OFF FOR VEP TO BE REAL SAVE. 

It could damage yours ears, monitors etc. The Noise can get about over 50db above 0dbfs , which is insane. I have never seen work fabfilter limiter on the masterbus so hard (MAXIMUM INSANE REDUCTION) 

I highly recommand the free plugin Ice9 on the master bus when working with VEP or noise blast, burst from other plugin, which sometimes happens. https://www.pluginboutiq...ols/72-Utility/2759-Ice9

It will mute the signal over a given threshold, which is much better than using a limiter. 

If you want to test this bug on your system, replicate my horror settings on a big cpu taxing project, turn the monitors levels way down and don´t use any headphones + use Ice9 on the master bus. When you toggle between any cubase internal VI instrument or channels and VEP Channels you might be able to reproduce this.

@VSL: If you can reproduce this: Please sit together with Steinberg for the new VEP release. You just can not release a software with certain settings that could potentiall kill your career. And if you can not solve this problem but reporduce it reliably, please make this BOLD AND RED everywhere and also when the information box for installing VEP appears. 

I can´t image a worse bug in my entire live. The next step is a bug that burns your motherboard, - but even with that, your ears could survive it :)

Thanks, Cheers, lokotus

HI thanks for getting back. 

 

thanks you could also try this I found for protecting ears as it mutes loud signals completely: https://www.pluginboutique.com/products/2759-Ice9?guide#instructions

Has anyone eperienced this issue outside VEP ? I can´t remember using onyl vst and plugins inside Cubase iwhtout VEP and hear this noise blast problem occur. If VEP is the problem, athen I at least have less variables to play with for troubleshooting...

 

Thanks, lokotus

Hi, 

yes (is vep 7 out yet ? ) - I am using latest versions. No I haven´t disabled asio guard yet since it is helping me loading and playing the huge amount of samples without clicks and pops. but maybe i should try to disable it and increase the audio soundcard buffer instead. 

Cheers, lokotus

PS : have you tried any hardware limiter solutions ? this is seriously dangerous. 

Hi, 

yes (is vep 7 out yet ? ) - I am using latest versions. No I haven´t disabled asio guard yet since it is helping me loading and playing the huge amount of samples without clicks and pops. but maybe i should try to disable it and increase the audio soundcard buffer instead. 

 

Cheers, lokotus

Hi community, 

 

this is really back since I have a current project going on and can’t find a solution yet. There are too many variables - but I was reading a lot about this topic. I am using Cub 10, win 10, with East West Play, Spaces II, Illusion, Komplete Kontrol, Kontakt, SWAM. 

It does not seem Reproducible, but more often than not, I get an almost reproducible noise blast / burst out of the VEP channels when switching with the mouse from internal Cubase Channels to VEP Channels. 

 

 

Whats I did: I tried avoiding Plugin Alliance plugins, but this has not improved anything. I did open up older VEP templates that worked fine before I update to Cubase 10 (from 9.5) and Updated East West Play Engine 6 & VEP 6 to the currently newest version . The problem occurred also in the older VEP templates that worked on the same Computer & Win 10 System. 

- Closing, Opening Cubase Project and reconnecting to VEP did not solve the problem. 

 

So has any one tried to experiment with these things and improved this situation ? 

- East West & VEP problem ? - Avoiding East West newest update to Play Engine

- Avoiding Cubase 10

- May High VEP buffer Settings (maximum4) cause this problem ?

- Asio Guard Settings in combination VEP

- Firewall Settings 

 

There are so many variables… Maybe somebody has found a solution for his system in the past ? Everything is legit, ilok, eliecnser etc…

 

 

Thanks, lokotus

Hi,

Did anyone use Cubase 9 with deactivating / re-activating VEPS without problems ? 

Cubase 9 seems to get extremely confused with VEP Outs routing - Here is my problem: Everything is inside one Cubase project file. I have composed about 20 Music Cues (Each Music Cue is a separate VEP Instance (as Cubase Instrument Track) with 128 Channels and 24 Midi ports). 

Every time I composed a new music cue, I deactivated the former VEP (Music cue). I have also added some permanently activated VEP Templates for Strings, Wood, etc. that remain active all the time.

Here is the problem or bug I am experiencing: I have all 20 Music Cues deactivated and wanted to return to my first Music Cue. After re-activating the first VEP, Cubase does very weird things with its VEP Outs Routing: 

a) Some VEP outputs are duplicated, which should not happen :( seems extremely weird: 

(I had one Bass Sound for example with Out 3/4. And now Cubase shows me 3 (VEP Outs) with the same Bass Sound Name that all receive audio from the Sound but belong to the same VEP Out 3/4 inside the Cubase mixer. 

The Sound is therefore also louder than in my original mix . 

b) The activated VEP suddenly has received more (VEP Outs) from other VEPS that were not in the original Music Cue: Cubase mixed in some (VEP Outs) with some names from my permanently activated VEP Templates inside the re-activated Music Cue. 

c) It should not matter, but could this be a problem or bug with using the „newer“ (Cubase Instrument Track) instead of the old (Cubase Instrument Racks) ?

This buggy routing behaviour with re-activated VEPs got me so confused, I can´t really trust this feature in Cubase nor can I understand why this conflict is happening. Maybe Cubase just doesn´t know yet how to correctly re-activate VEP when working with several Veps?? 

Does somebody have a similar experience or is VSL in contact with Cubase to solve this perhaps already known problem ? 

Thanks a lot, nostaller

Dear Support,

a separate window for making Notes inside an Instance would be great. It would help remembering routing and automation specific things much more easily...

Thanks, lokotus

can´t check the horns thing, don´t have it - its best to write a separate thread about it. @ VSL Support, Please check this CPU behaviour and fix it... Thanks 

Hi,

Its on WIn 10 64bit: In the lower righr corner CPU Usage Always Shows 0,0% with this newest update. Anyone else having this behaviour ? 

 

THanks, lokotus

HI folks, 

I have been reading at the steinberg website about a few tweaks for improving performance. Basically turning off

Intel Turbo Boost, Enhanced Intel SpeedStep (EIST), C-States in bios & disabling CPU Parking via a "registry hack" while having full perofrmance (power settings) turned on should lead to a better perfomance. 

Now, while VEP does not need an audio driver, it still should deliver very good realtime performance, so I was wondering if it would be a good Idea to have the same settings on a VEP Slave PC ? 

Cheers, nostaller

Hi,

VEP5 woks beautifully here -> my setup: MBP Cubase Host connected over Lan to VEP 5 PC Win7 Slave (Streaming all Samples)

From my understanding, VEP is already somehow synced to the host computer -> I was wondering because I think that a lot of guys have "weaker" host systems (Laptops) connected to more powerful slave (Desktop like Pcs, a lot of ram, more powerful graphic cards and Monitor options) systems for streaming samples: Would it be possible to include an interface in the VEP Slaves Software that would allow loading a movie ?

I imagine some kind of SMPTE Timecode running from the host over ethernet to the Slave VEP Software, allowing perfect frame sync . That way one could reduce the stress on the macbook Pros (or any other Laptops) Graphic Card and could also easily have an exclusive Monitor option for video playback only - Does this sound like a useful idea to anyone and would it be theoretically practical/possible to include such an option ??

Cheers, nostaller

same problem here, not a good thing ....

Hi,

Every DAW user knows the audio performance is "supposed" to be better when set to "Background services", at least if we believe the very broad consensus about it... But what about in in Win7 64bit?

Is ASIO still a background service ?? And does this setting really matter if I only use the PC as a slave with VEP server instances? - Since I even don't have any soundcard installed - is "backround service" the right choice for my Slave PC or should I justz leave it to "Programs" ?

Thanks, lokotus

Hi folks,


Au is currently at the limit of 1 Midi Port and 16 Outputs. VST 3 has 128 Audio Audio Ports and much more than only 1 Midi Ports. How does this situation look like with RTAS ?
Furthermore - did somebody change from Cubase 5 to Pro Tools 9. Pro Tools looks interesting with the integrated Sib Score Editor ... Any user exprience with Pro Tools & VEP for scoring to picture ? (any similar Keysiwtch features ala Expression Maps or Time Warp features for aligning tempo and bars to cues ? )

Thanks, cheers lokotus

Hi guys,

My Main Mac Cubase 5.5 is connected over ethernet with VEP on Win7 64bit. As I load EW Play Engine on VEP, it does not really sync up to the exact Tempo of my Main Mac. I can change Tempo on my Main Mac and it does somehow follow those changes, but nevertheless its not exactly in sync with my metronome. I noticed it when playing around with some HS measured tremolo patches. Omnisphere is wokring fine by the way. Any other users experiencing such a behaviour or any suggestions? Thanks, lokotus

convenient solution. thanks ... cheers, nostaller

OK, I know of the limitation that Logic and AU can not handle multiple Midi ports. Therefore I need to reopen serveral VEP istances each with 16 Midi channels.

Now I realize, that Cubase and VST 3 support multiple MIDI Ports per Instance, put i can only route 16 Stereo outputs from one instance back into Cubase 5.5...

Is that TRUE?? It seems like I have to open the same number of instances in Logic and Cubase, since I usually wanna route each instrument back via an separate audio track over ethernet ...

cheers, nostaller

1) Was my post of any use to detect a problem with the Au Version in Logic9? 2)Can this one be reproduced on other systems? 3) Should I be worried about my system not working properly? I like the plugIns, but I could not really use them because of the circumstances mentioned... Thanks for the help, nostaller

Ok, so is there anything one can do about it or is it "normal" behaviour on all Macs with Logic 9? ... I just came across this whole problem because of my crazy spinning fans... The weird thing is of course: a totally different behaviour with the vst 3 version in cubase 5.1.1 on my mac... Everything seems to be there in "normal" CPU numbers (without crazy fans) after closing the GUI of the plugIns. So there is certainly "something", more I can not really say since I don't know anything about programming and so on. If its not the GUI, whats the problem then? Unfortunately, if this situation remains like this, I am not really able to use those plugIns with my beloved Logic ... Cheers, nostaller

Ok,
I realize there are problems with closing Logic projects...

But I was really only referring to the closing of the User Interface (not the deleting of the entire Plugin from the insert slot) of a Vienna Suite plugIn. Closing the PlugIns UI will still have a remaining high demand on CPU. Just look at the uploaded video. I would appreciate any help ...... Cheers, nostaller

thanks for the extended Demo opportunity ...