u-he

aaron aardvark · Post by **aaron aardvark** » Sat Jul 26, 2014 4:36 pm

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.

SJ_Digriz · Post by **SJ_Digriz** » Sat Jul 26, 2014 4:49 pm

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.

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 · Post by **aaron aardvark** » Wed Jul 30, 2014 3:37 am

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.

Compyfox · Post by **Compyfox** » Wed Jul 30, 2014 9:50 am

He indeed means the ///

aaron aardvark · Post by **aaron aardvark** » Thu Jul 31, 2014 4:13 am

Thank you Compyfox.

mkdr · Post by **mkdr** » Sat Aug 23, 2014 12:54 pm

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.

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.

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 · Post by **AdmiralQuality** » Sat Aug 23, 2014 1:06 pm

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.

ALL plug-ins are by third parties! That's why they're called plug-ins and not HOST FEATURES!

Rommelaar · Post by **Rommelaar** » Wed Aug 27, 2014 10:57 am

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.

Urs · Post by **Urs** » Wed Aug 27, 2014 11:02 am

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.

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.

mkdr · Post by **mkdr** » Sun Aug 31, 2014 7:55 pm

AdmiralQuality wrote:
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.
ALL plug-ins are by third parties! That's why they're called plug-ins and not HOST FEATURES!

You are referring to the economical view. I mean the technical implementation.
Retrologue and Padshop are VST3 plugins for example. The fact that they come with Cubase has nothing to do with this.

antithesist · Post by **antithesist** » Thu Oct 23, 2014 2:50 pm

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!

zvenx · Post by **zvenx** » Thu Oct 23, 2014 2:56 pm

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

Guillermo Navarrete · Post by **Guillermo Navarrete** » Thu Oct 23, 2014 3:00 pm

Hello,

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!

I will gladly answer some of your questions:

What's the current official policy as of today?

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.

Is it gone for good?

No, not at all. I have no idea where this information comes from but it is not correct.

Best regards,
GN

zvenx · Post by **zvenx** » Thu Oct 23, 2014 3:09 pm

lol.....Guillermo he meant vst3 as per u-he stuff not vst3 in general

.

But would be nice to have you guys help u-he to sort it out.
rsp

#rob · Post by **#rob** » Thu Oct 23, 2014 3:11 pm

Guillermo Navarrete wrote:I have no idea where this information comes from but it is not correct.

I think the phrase "VST3" in this case only refers to our VST3 ports, not the entire format.

antithesist wrote:What's the current official policy as of today?

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:I'd think discontinuing VST3 should be a "known issue."

There's a ReadMe file about this matter in all installer .ZIPs

antithesist wrote:Is it gone for good?

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.

u-he

KVR Audio

VST3 - known issues (Updated Jan 2019)