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.I am writing and joining the ranks of the pro composers who are having big issues with VE Pro and Cubase 8. In short I must say I had the same problem wth AG2, which is also affecting the stability of smaller projects, even not involving VE Pro I must say. In any case, I don't understand where the fix must be done, if at VSL or Steinberg. I can only say that I had to switch back to Cubase 6, which was the version I was working on, to deliver what I have to do now. I am maybe sacrificing the possibility of a bigger template to the relative tranquillity of a reliable machine. Regarding AG2, by the way, I don't have the feeling of it being well developed, at least judging frm my personal experience. I will follow the developments here. Regards, Alessandro
-
-
This is taken more than seriously. But as Vienna is reluctant to 'to make the plugin operate completely asynchronously', reconfiguring the Cubase audio engine is no joke either.
The respective engineering departments are in touch to discuss what needs to be done on both sides.
As per the specific BON-7519 entry, this was related to updating the VST SDK3 to support prefetch information, which has been accomplished. Be sure there are other entries open.
(I can't find any other open issues on their forum on this issue, incidentally)
I have a couple of questions, Martin - could you explain a little more fully what is meant by "Meanwhile, we are reverting the prefetch disabling for the upcoming VEP release"? Is this behaviour the same as with version 5.4.13741 where I'm able to run VE Pro with asioguard 2 set to low, but no higher?
Secondly, seeing how discussions are progressing. I understand that both sides are in difficult positions, but given that it's been nearly a year now that pro composers have been fighting with workarounds, it would be good to hear some positive news.
-
I'll add my voice. I really had hoped it would work but C8 hangs even one small projects when changing tracks. I've never had that issue with LP and Martin's message earlier explains why. I was really hoping to make a go of it and am still trying.
-
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
-
Is it better to use the VST2 plug-ins instead of the VST3 versions in Cubase 8?
Steinberg has already said that you must use the VST3 version with ASIO GUARD 2. I can tell you from experience when I had a bunch of VST2 versions in my template before I knew this I was getting all kinds of CPU spiking issues.
-
Unfortunately no change in Cubase 8.5. The known issues document from Steinberg simply states:
7519: Switching between tracks using instruments from Vienna mutes the audio playback for a short moment
Please deactivate ASIO-Guard for these plug-ins using the Plug-in Manager.
-
Maybe I don't understand the issue completely, but as far as I can tell this problem appears to be fixed in the latest update (5.4.14074) of VEP. The changelog of the update includes this statement: "Improved. Mixdown performance with Cubase Asio Guard 2".
I activated Asio-Guard on Cubase at the Normal level, then switched the Asio-Guard switch on for the VEP plug-in (VST3 version). I I was able to switch between tracks with no muting delay. Experienced no audio dropouts or other artifacts. Not quite sure how to best measure CPU load, so I can't report on that. At least it does seem that the VEP plug-in works now with Asio-guard 2.
Evocatus
Cubase 8.5.0 Pro 64, Tascam FW-1884, i7, 24Gb.
-
No change here at all. Still have the 4 second muting when changing tracks.
Maybe I don't understand the issue completely, but as far as I can tell this problem appears to be fixed in the latest update (5.4.14074) of VEP. The changelog of the update includes this statement: "Improved. Mixdown performance with Cubase Asio Guard 2".
I activated Asio-Guard on Cubase at the Normal level, then switched the Asio-Guard switch on for the VEP plug-in (VST3 version). I I was able to switch between tracks with no muting delay. Experienced no audio dropouts or other artifacts. Not quite sure how to best measure CPU load, so I can't report on that. At least it does seem that the VEP plug-in works now with Asio-guard 2.
Evocatus
Cubase 8.5.0 Pro 64, Tascam FW-1884, i7, 24Gb.
-
Are you sure you are switching to "different" intances of viframes or VE PRO instances. Choosing different tracks within the same VE PRO instance does not cause the issue.
What is your soundcard buffer? I assume it is below 1024 because you said you are running ASIO GUARD 2 at Normal setting. That is 1024 buffer so if you are at 1024 buffer it would not cause the issue or give you ant benefit.
I wonder why it's happening to you and not to me?
-
-
Hey everyone,
Just did the upgrade to my studio, one machine wasn't enough anymore...Bought a new master, old one is slave now...got the vep5, made the template, got the issues... And now stumbled on these threads and got very disapointed.
For years I am hearing about wonderfull world of vep and cubase, and now when I finally got into it only to find this...
I am thinking of returning vep5, still got 10 days left for that.
What would you guys do in my place? To install C7.5 and use it with vep5? Or return it and maybe connect two PCs via audio interfaces? Via Adat/spdif/light-pipe...don't know much about those things...but I have rme hdspe aio on master rig and hdsp 9632 on the slave.
Hope this vep5/asioguard2 issue will be resolved soon, as I really like vep5 and whole idea.
-
Hi shomynik, I have had this question at the back of my mind, since my purchase, but the integrated MIR and the fact that VEP uses less CPU within C8, with same plugins setup, still sells it to me. Yes I wish the .vst3 problem will be sorted soon and I could do with two MIR licenses (to have slave and/or same PC use), like I have three for VEP. There is the lack of project carry over eg: if I save a *.frame on my PC, then try to open it on my slave, the same project does not appear. There are a few other implementations, which may be solved, that are worth considering and waiting for.