VST3 - known issues (Updated Jan 2019)
-
aaron aardvark aaron aardvark https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=248508
- KVRAF
- 2667 posts since 22 Jan, 2011 from near Los Angeles
Does anyone know if the default setting on the trial version of Cubase Elements 7 is VST3 or VST2? I tried out Mac OSX 10.9.3 and trial version of Cubase Elements 7, and it did not work well with my Zebra, Diva, and some of my "French" synth plug-ins. I reverted back to my "ancient" Mac OSX 10.6.8 and Cubase LE4 and things are working much better again. Not sure if this is related to this thread or not.
You can hear my original music at this link: https://www.soundclick.com/artist/defau ... dID=224436
- KVRAF
- 6095 posts since 5 Jul, 2001 from Just about .... there
there is not default, you either load a VST2 or VST3 instrument. You'll know the difference based on the 3 hash marks (or not) next to the plugin name.aaron aardvark wrote:Does anyone know if the default setting on the trial version of Cubase Elements 7 is VST3 or VST2? I tried out Mac OSX 10.9.3 and trial version of Cubase Elements 7, and it did not work well with my Zebra, Diva, and some of my "French" synth plug-ins. I reverted back to my "ancient" Mac OSX 10.6.8 and Cubase LE4 and things are working much better again. Not sure if this is related to this thread or not.
If you have to ask, you can't afford the answer
-
aaron aardvark aaron aardvark https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=248508
- KVRAF
- 2667 posts since 22 Jan, 2011 from near Los Angeles
SJ_Digriz,
Thank you for replying! I always wondered what the /// meant........that is what you mean? Or are you saying it is ###? I call those pound signs, but with the kids and their hash-tags, I'm not sure.
Thank you for replying! I always wondered what the /// meant........that is what you mean? Or are you saying it is ###? I call those pound signs, but with the kids and their hash-tags, I'm not sure.
You can hear my original music at this link: https://www.soundclick.com/artist/defau ... dID=224436
-
- KVRAF
- 14658 posts since 19 Oct, 2003 from Berlin, Germany
He indeed means the ///
-
aaron aardvark aaron aardvark https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=248508
- KVRAF
- 2667 posts since 22 Jan, 2011 from near Los Angeles
Thank you Compyfox.
You can hear my original music at this link: https://www.soundclick.com/artist/defau ... dID=224436
-
- Banned
- 1374 posts since 5 May, 2007 from Finland
I've not had any issues with Steinbergs VST3 plugins or Cubase 7 or Asio Guard. So clearly you are talking baloney here. I'm pretty sure your "ASIO engine nuking" is just another issue of "poorly built Mobo" / "Intels crappy power saving" and nothing to do with Steinberg or ASIO or more to the point VST3.Compyfox wrote: Most recent VST3 creations however, and especially Cubase 7, reveal that this resuts in sometimes drastic spikes - nuking the ASIO engine. I can't be sure, but I think this was also somewhat the reason why they created the ASIO guard system.
VST3 plugins from 3rd parties do seem to be broken however. Everyone would love to see a solution to that. So stay on topic.
Another thing: why i'd love to see VST3 versions of U-HE plugins is the Cubase's new tuning system. I've had similar features on my HW synths and would love to get them on software too. Hopefully someday
-
AdmiralQuality AdmiralQuality https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=83902
- Banned
- 6657 posts since 10 Oct, 2005 from Toronto, Canada
ALL plug-ins are by third parties! That's why they're called plug-ins and not HOST FEATURES!mkdr wrote:VST3 plugins from 3rd parties do seem to be broken however. Everyone would love to see a solution to that. So stay on topic.
- KVRist
- 244 posts since 12 Sep, 2013
I know the comments made about the VST3 plugins, but until know I have not experienced any troubles with the VST3 versions of various U-he plugins. That is until the August 2014 built, the Diva 64-bit VST3 plugins cause my Cubase to hang and crash. I have resorted to using the VST2 64-bit plugin, but it might help to know the changes made since the last build the Jan. 2014 hotfix, worsened the stablility of the Diva VST3 64-bit plugin in Cubase at least.
AMD Ryzen 3900X & RX 5700XT, 128GB RAM, Windows 11 Pro 64-bit
Waldorf Blofeld & Pulse 2, Akai MAX49 & MPD226, Steinberg UR44 & CMC controllers
Cubase Pro 13, Nuendo 13, Wavelab Pro 12, Dorico Pro 5, Rapid Composer v5, FL Studio 21
Waldorf Blofeld & Pulse 2, Akai MAX49 & MPD226, Steinberg UR44 & CMC controllers
Cubase Pro 13, Nuendo 13, Wavelab Pro 12, Dorico Pro 5, Rapid Composer v5, FL Studio 21
- u-he
- Topic Starter
- 28064 posts since 8 Aug, 2002 from Berlin
Yeah, we'll look into that and try to fix it, if a quick fix is available. There's also another Diva crash that we hadn't caught yet, maybe it's related.Rommelaar wrote:I know the comments made about the VST3 plugins, but until know I have not experienced any troubles with the VST3 versions of various U-he plugins. That is until the August 2014 built, the Diva 64-bit VST3 plugins cause my Cubase to hang and crash. I have resorted to using the VST2 64-bit plugin, but it might help to know the changes made since the last build the Jan. 2014 hotfix, worsened the stablility of the Diva VST3 64-bit plugin in Cubase at least.
-
- Banned
- 1374 posts since 5 May, 2007 from Finland
You are referring to the economical view. I mean the technical implementation.AdmiralQuality wrote:ALL plug-ins are by third parties! That's why they're called plug-ins and not HOST FEATURES!mkdr wrote:VST3 plugins from 3rd parties do seem to be broken however. Everyone would love to see a solution to that. So stay on topic.
Retrologue and Padshop are VST3 plugins for example. The fact that they come with Cubase has nothing to do with this.
-
- KVRian
- 1400 posts since 9 Feb, 2012
Another thread mentioned VST3 being dropped altogether.
I haven't read this thread, but I'd think discontinuing VST3 should be a "known issue."
What's the current official policy as of today?
Is it gone for good?
Might we lose other formats if problems with them can't be solved?
Thanks!
I haven't read this thread, but I'd think discontinuing VST3 should be a "known issue."
What's the current official policy as of today?
Is it gone for good?
Might we lose other formats if problems with them can't be solved?
Thanks!
WEASEL: World Electro-Acoustic Sound Excitation Laboratories
- KVRAF
- 13223 posts since 16 Feb, 2005 from Kingston, Jamaica
I could be wrong, but if we are talking about the same other thread, I think that was a forum member talking out of the 'wrong' hole..
Last I read, it was on the to be revisited category.
rsp
Last I read, it was on the to be revisited category.
rsp
sound sculptist
-
Guillermo Navarrete Guillermo Navarrete https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=306387
- KVRist
- 478 posts since 4 Jun, 2013 from Hamburg, Germany
Hello,
Best regards,
GN
I will gladly answer some of your questions:antithesist wrote:Another thread mentioned VST3 being dropped altogether.
I haven't read this thread, but I'd think discontinuing VST3 should be a "known issue."
What's the current official policy as of today?
Is it gone for good?
Might we lose other formats if problems with them can't be solved?
Thanks!
VST3 is not being dropped it is the latest technology and it is still going to be developed at least for a while. We have just released a new SDK not so long ago.What's the current official policy as of today?
No, not at all. I have no idea where this information comes from but it is not correct.Is it gone for good?
Best regards,
GN
- KVRian
- 573 posts since 20 Aug, 2013
I think the phrase "VST3" in this case only refers to our VST3 ports, not the entire format.Guillermo Navarrete wrote:I have no idea where this information comes from but it is not correct.
Products that already had VST3 versions will continue to be provided with VST3 versions, although the VST3 plugins will not be installed by default (user-selectable option) and are considered "experimental". New products (Bazille, Presswerk, Hive) will not have VST3 versions for the time being, that's why VST3 is not (or will not be) listed in the spec box on their respective product pages.antithesist wrote:What's the current official policy as of today?
There's a ReadMe file about this matter in all installer .ZIPsantithesist wrote:I'd think discontinuing VST3 should be a "known issue."
Gone for the time being. All major hosts still support VST2 and will (likely) continue to do so, which makes providing VST3 plugins desirable regarding flexibility and future compatibility, but not an inevitable necessity as of yet. As soon as we can afford to invest the time to re-port our VST2 plugins to VST3, we will consider it.antithesist wrote:Is it gone for good?