What's new

VEPro 7 now available!

Anyone else having VE Pro 7 crash when they mute and unmute channels within VE Pro? Doesn't matter if it's VI Pro instances or Kontakt. If I click faster than say 1 per every 4-5 seconds, it will crash the entire program. Sent a support ticket already about it earlier in the week.

Thanks
 
Anyone else having VE Pro 7 crash when they mute and unmute channels within VE Pro? Doesn't matter if it's VI Pro instances or Kontakt. If I click faster than say 1 per every 4-5 seconds, it will crash the entire program. Sent a support ticket already about it earlier in the week.

Thanks
By "mute and unmute" do you mean disable and enable? If so, I have been having the same problem in VE Pro 6. On my system, it seems to be limited to VI Pro and the free Vienna Instruments. I haven't seen it with Kontakt yet. Like @maestro2be, I've tentatively decided that it is related to disabling and enabling in rapid succession -- something I would normally do to replace one instrument with another in an arrangement. But I haven't been able to prove that this is the source of the problem. Tech support has been unable to identify a cause from the crash report I sent them.

I haven't installed VE Pro 7 yet because I hope to have some time to investigate further in version 6.
 
By "mute and unmute" do you mean disable and enable? If so, I have been having the same problem in VE Pro 6. On my system, it seems to be limited to VI Pro and the free Vienna Instruments. I haven't seen it with Kontakt yet. Like @maestro2be, I've tentatively decided that it is related to disabling and enabling in rapid succession -- something I would normally do to replace one instrument with another in an arrangement. But I haven't been able to prove that this is the source of the problem. Tech support has been unable to identify a cause from the crash report I sent them.

I haven't installed VE Pro 7 yet because I hope to have some time to investigate further in version 6.

I actually just meant inside of VE Pro, hitting the "M" to mute that channel. If I do that in any sort of rapid succession it would crash every time. It got so bad I decided to uninstall VE Pro 7 and go back to VE Pro 6. So far all good with no crashes. I will just stay here for a while.
 
Finally had a chance to install and begin to work with VEP 7; seems to be functioning well though I've hardly put it through it's paces.

I really like the vertical alignment option for instances.
 
Ok the problem with VST3 plugin and Reaper seems solved in the last beta release of Reaper.
I have to publicly thank VSL devs who kept me updated and solved this issues together with Reaper devs.

I reserve myself to test it deeply once it cames out in a final release.
 
Ok the problem with VST3 plugin and Reaper seems solved in the last beta release of Reaper.
I have to publicly thank VSL devs who kept me updated and solved this issues together with Reaper devs.

I reserve myself to test it deeply once it cames out in a final release.

Indeed it should be fixed now. Glad that we could help :)
 
Finally got around to installing VEP 7. I was hesitant because I'm wrapping up a big project and I didn't want to risk it. Similar deal with Nuendo 10. But I figured what the heck, worst thing I'll need to do is reinstall v6... I can report that VEP 7 and Nuendo 10 are working very nicely together with my set up. I've found that saves in N10 are just a bit more snappy, though who knows it could be my imagination.
 
  • Like
Reactions: EgM
Finally got around to installing VEP 7. I was hesitant because I'm wrapping up a big project and I didn't want to risk it. Similar deal with Nuendo 10. But I figured what the heck, worst thing I'll need to do is reinstall v6... I can report that VEP 7 and Nuendo 10 are working very nicely together with my set up. I've found that saves in N10 are just a bit more snappy, though who knows it could be my imagination.

I believe faster saves were part of this update.
 
Sounds like good news, glad there's light at the end of your tunnel Daniele.

Yeah finally, now I have to try it on my main installation, I'm waiting for Reaper devs to put it in a final release to fully test it but from the portable installation I tried now it works great. I have only to test what workflow works best in my template.

Indeed it should be fixed now. Glad that we could help :)

Thank you for helping me and for sorting this out, and thank you for keeping me updated on your progress.
This has been a good point for Reaper too because they should have solved some lacking VST3 implementations.
 
Sharing my experience: Moved to VEpro7 right after it came out. Vertical instance list is nice and the GUI looks sharper, however loading projects takes about 50% longer as well as saving. It’s worth mentioning that I have about 100 instances, so maybe that’s why my experience is different from the majority.
Actual performance with Logic Pro is the same as with VEPro6
 
Sharing my experience: Moved to VEpro7 right after it came out. Vertical instance list is nice and the GUI looks sharper, however loading projects takes about 50% longer as well as saving. It’s worth mentioning that I have about 100 instances, so maybe that’s why my experience is different from the majority.
Actual performance with Logic Pro is the same as with VEPro6

Similar Experience with Cubase 10. Slow load and extremely slow closing a sequence compared to VE PRO 6. It is discussed on the Vienna forum with no one from Vienna participating in the discussion....very disappointing that they are not engaged in the conversation.
 
Sharing my experience: Moved to VEpro7 right after it came out. Vertical instance list is nice and the GUI looks sharper, however loading projects takes about 50% longer as well as saving. It’s worth mentioning that I have about 100 instances, so maybe that’s why my experience is different from the majority.
Actual performance with Logic Pro is the same as with VEPro6

I actually measured it. VEPpro7 takes exactly the same amount of time to load the projects I tried compared to VEPro6. Exactly the same. test projects were around 100 tracks of VSL instruments. Its always possible other plugins have issues, but measure it before saying it takes 50% longer, I doubt it.

Now that being said, could be because of 100 instances too, I don't use that setup, Measure it exactly and report it to VSL if so. I have found them to be pretty responsive when real bugs are actually found. way more responsive then a lot of other software companies. I give them that..

I can also tell you with measured certainty also that VEPro7 is significantly better CPU performance then VEPro6, but only if you're on Mojave. If you're on an older version of OSX, then VePro6 is in fact a little more performant then VePro7. VePro7 is making use of newer GUI related libraries that are apparently making better use of Mojave, Metal and all that... its definitely better performance, particularly with regards to when the GUI is open, and when using HiDPI, etc. I did measured and methodical performance tests and also had some communication with VSL engineers who also saw much superior performance on their Mojave based system as well.
 
I actually measured it. VEPpro7 takes exactly the same amount of time to load the projects I tried compared to VEPro6. Exactly the same. test projects were around 100 tracks of VSL instruments. Its always possible other plugins have issues, but measure it before saying it takes 50% longer, I doubt it.

Now that being said, could be because of 100 instances too, I don't use that setup, Measure it exactly and report it to VSL if so. I have found them to be pretty responsive when real bugs are actually found. way more responsive then a lot of other software companies. I give them that..

I can also tell you with measured certainty also that VEPro7 is significantly better CPU performance then VEPro6, but only if you're on Mojave. If you're on an older version of OSX, then VePro6 is in fact a little more performant then VePro7. VePro7 is making use of newer GUI related libraries that are apparently making better use of Mojave, Metal and all that... its definitely better performance, particularly with regards to when the GUI is open, and when using HiDPI, etc. I did measured and methodical performance tests and also had some communication with VSL engineers who also saw much superior performance on their Mojave based system as well.
Actually, I run VEPro only on my Windows 10 slave, so I have no idea how it would run in Mac, but in my setup (using many instances) it does take way longer to load.
 
I actually measured it. VEPpro7 takes exactly the same amount of time to load the projects I tried compared to VEPro6. Exactly the same. test projects were around 100 tracks of VSL instruments. Its always possible other plugins have issues, but measure it before saying it takes 50% longer, I doubt it.

Now that being said, could be because of 100 instances too, I don't use that setup, Measure it exactly and report it to VSL if so. I have found them to be pretty responsive when real bugs are actually found. way more responsive then a lot of other software companies. I give them that..

I can also tell you with measured certainty also that VEPro7 is significantly better CPU performance then VEPro6, but only if you're on Mojave. If you're on an older version of OSX, then VePro6 is in fact a little more performant then VePro7. VePro7 is making use of newer GUI related libraries that are apparently making better use of Mojave, Metal and all that... its definitely better performance, particularly with regards to when the GUI is open, and when using HiDPI, etc. I did measured and methodical performance tests and also had some communication with VSL engineers who also saw much superior performance on their Mojave based system as well.


+1, but I too am on Mojave.
 
Actually, I run VEPro only on my Windows 10 slave, so I have no idea how it would run in Mac, but in my setup (using many instances) it does take way longer to load.

On windows 10 as well....and I can confirm in my case it loads probably 75% slower and close times can take over 10 minutes when it usually is less than a minute on VE PRO 6. This has been reported in detail to them with very little response. Judging from another users post on Vienna's site I do think it has to do with certain instruments and even more specifically maybe certain kinds of patches in instruments.

In my case I identified that I use a tremendous amount of HALion 6 and HALion Sonic SE instances, and when the patches utilize a convolution effect (either the convolution reverb or the amp vst which is convolution based) the initial connect time is very long only the first time then it behaves as normal. I thought this might be a Steinberg specific issue but last week this behaviour was reported by someone who does not use any HALion instruments. So it is possible that this is all related to the issues I am seeing in VE PRO 7.
 
Last edited:
Had purchased when it was announced some months ago. Installed yesterday over existing version 6. Everything fine on Win7 with Nuendo on main machine and Win8 slave. Projects load correctly. Feels snappier. Filesizes of saved projects are definitely smaller.
 
I have Kontakt 5 hanging with "Converting..."-something dialogue about every 3 times I load a project in VEP7. It seems to happen to the first instance using Kontakt. Obviously this is probably project-specific and if I rebuilt my VEP project with Kontakt 6 instead it would most likely not hang. Haven't gotten around to doing that though. Apart from that it seems loading speed is about the same as VEP6 here (Mac Pro, Mojave). Connecting/disconnecting seems faster though.
 
On windows 10 as well....and I can confirm in my case it loads probably 75% slower and close times can take over 10 minutes when it usually is less than a minute on VE PRO 6. This has been reported in detail to them with very little response. Judging from another users post on Vienna's site I do think it has to do with certain instruments and even more specifically maybe certain kinds of patches in instruments.

In my case I identified that I use a tremendous amount of HALion 6 and HALion Sonic SE instances, and when the patches utilize a convolution effect (either the convolution reverb or the amp vst which is convolution based) the initial connect time is very long only the first time then it behaves as normal. I thought this might be a Steinberg specific issue but last week this behaviour was reported by someone who does not use any HALion instruments. So it is possible that this is all related to the issues I am seeing in VE PRO 7.

My template opens up with everything disabled, so in my case I don’t think it has anything to do with a specific plugin. They are mostly Kontakt anyway....
 
Top Bottom