ACE VST3 version crashes Cubase every time
-
- KVRer
- 17 posts since 25 Jan, 2014
Having just purchased ACE (which I love), I was disappointed to discover that the VST3 version crashes Cubase every time it is loaded on an instrument track and there are incoming MIDI Note-On messages. I'm running Cubase Pro 8.5 under Windows 10 Home 64-bit on an ASUS X750JA laptop with Intel Core i7 @ 2.40GHz and 6GB RAM. Is this a known issue? The file VST3_ReadMe.txt doesn't mention crashing Cubase. The VST3 version of ACE runs perfectly in Reaper and the VST2 version runs perfectly in Cubase
Last edited by robst247 on Sun Jul 24, 2016 9:43 pm, edited 1 time in total.
-
- KVRAF
- 2960 posts since 9 Dec, 2011 from falling
I believe u-he advises everyone not to use the VST3 version, and use the VST2 version instead.
Bitwig Certified Trainer
-
- KVRAF
- 4811 posts since 21 Jan, 2008 from oO
hey,
yea basically it's written in the vst3 readme file in your installer folder:
Once you saved the ACE.log file to your desktop, start up cubase and let it crash. After that it's best to provide the logfile via support(at)u-he.com with steps to reproduce.
cheers
yea basically it's written in the vst3 readme file in your installer folder:
Although a complete crash is new i think. You could help with following these steps: http://www.u-he.com/cms/faqs#how-do-i-c ... -debuggingImportant information about the VST3 version
--------------------------------------------
During installation, the VST3 version is not enabled by default, and we highly recommend using VST2 for the time being. If you need to install VST3, e.g. if you have existing projects that already include VST3 versions of our software, please use the customization option in the installer, and enable VST3.
After working on full VST3 versions for several months, we were still encountering random errors and glitches - we had simply underestimated the complexity. Steinberg's advice was to do a complete rewrite as "simplified" VST3 (also included in SDK). However, rewriting would have meant considerable work, so we finally decided to call our current VST3 implementation "experimental" until we can afford to take the necessary steps.
Known issues with the VST3 versions:
- they don't report parameters on preset changes
- in Wavelab, they show symbols instead of registration info
- they crash FL 11 beta
- they don't show the selected patch name when a project is reopened
Again: We recommend using the VST2 versions for now. They behave the same, they sound the same, they're tried and tested!
Once you saved the ACE.log file to your desktop, start up cubase and let it crash. After that it's best to provide the logfile via support(at)u-he.com with steps to reproduce.
cheers
JamWide - a cross-platform Ninjam client for DAWs
-
- u-he
- 30222 posts since 8 Aug, 2002 from Berlin
Yep, the old VST3 layer wasn't working well. We'd still recommend VST2, there is no disadvantage to using it with ACE.
We've worked with Steinberg to rewrite VST3 and it works well for effects so far (recently released Presswerk & Satin). We can however not yet provide for the same user experience in it as we do in VST2, AU and AAX, mostly due to the lack of MIDI Learn in VST3. This isn't possible yet without the workarounds that caused some of the trouble we had had in the first place. Things are moving slowly but we have provided a lot of stuff (e.g. reference host implementation) to Steinberg earlier this year. Hopes are high
We've worked with Steinberg to rewrite VST3 and it works well for effects so far (recently released Presswerk & Satin). We can however not yet provide for the same user experience in it as we do in VST2, AU and AAX, mostly due to the lack of MIDI Learn in VST3. This isn't possible yet without the workarounds that caused some of the trouble we had had in the first place. Things are moving slowly but we have provided a lot of stuff (e.g. reference host implementation) to Steinberg earlier this year. Hopes are high