Roadmap Changes :-)

[NothanUmber]

If VST3 is off the map then presumably there won't be VST3.5 support either I guess?
In that case: Can you please reconsider adding voice-per-MIDI-channel support to your VST2 plugins the way you proposed a few years ago? That would be great and already cover the most desired VST3.5 feature from my perspective.
Pretty please!

[zvenx]

I am not sure how much VST3 specific stuff is already programmed in the U-he stuff. I imagine at the very least the function where the plugin doesn't really use cpu until it is processing audio. So I am not so concerned about lost of VST3 functionality for me.

However what I am concerned with, is what will happen when I open all my older projects that did in fact use vst3 versions of u-he plugins. I don't think Cubendo will look and notice the vst3 version is no longer installed(unless of course I freeze the version I use and never upgrade again) and automatically use the vst2 version with the correct parameter values.
That is my concern.
Anyway, here is hoping it doesn't come to that.
rsp

[Urs]

Sorry, I've been unspecific - mostly because I'm so frustrated that it's so difficult for us to make VST3 work.

With where VST3 is for us now, we can't ever make it work in Wavelab (probably other hosts as well), and we can't guarantee that we'll ever be able to display the name of the current preset when a song is reloaded. That's because in VST3 the GUI is split from the DSP part, and we have not found a way to determine in which order those two things come to life - if ever. There seems to be a random component, or maybe we're just too dumb to figure it out. We've implemented workaround after workaround, and all of those require more workarounds for whatever. It's an endless pit.

So what happens is, we'll continue with VST3 "as is", with no more workarounds or fixes. And once we have time, we will implement the easier version of VST3 which does not separate DSP and UI.

That also means, for the time being we will recommend to use VST2 because it does not have the problems we experience.

[zvenx]

ok, thanks for the update.. switching my defaults back to vst2 for now
rsp

[user5394]

Not yet. AAX, Diva, Satin, Zebra, that's still the major topics.

Does this including the RE version, is it still in progress or are there no capacities at the moment?

The RE version of Satin has to wait until the Satin "mute bug" is fixed. Before that we will not try to compile a RE.

Ah ok, thanks for the info.

[murnau]

I am willing to bet you don't use vst3.
Am I right?
rsp

nope..

..but i rather see one of my fav devs creating fascinating stuff in vst2 then struggle with vst3 all the time.

[knowix]

It's a shame that it would be extremely "non-trivial" for a group of developers to design their own independent plugin format. I'm sure everyone but Steinberg and Apple would be happy enough to integrate it into their DAWS.

[zvenx]

I am willing to bet you don't use vst3.
Am I right?
rsp

nope..

..but i rather see one of my fav devs creating fascinating stuff in vst2 then struggle with vst3 all the time.

But that is so exceedingly selfish.
I don't use ProTools or Reason.
How about if I say dropping RTAS/AAX64/RE wouldn't make a difference to my life.

"there will not be a shitstorm against u-he, maybe against avid (nothing new in the last time)..

..this will change n o t h i n g ! Very Happy"


rsp

[zvenx]

It's a shame that it would be extremely "non-trivial" for a group of developers to design their own independent plugin format. I'm sure everyone but Steinberg and Apple would be happy enough to integrate it into their DAWS.

Or Avid or Propellerheads who established their own despite other formats already available.
rsp

[zvenx]

........... and we can't guarantee that we'll ever be able to display the name of the current preset when a song is reloaded. .......

Btw, just created a Cubendo project using ACE, Zebra (not the one with the Distortion), Diva 2033 and Satin 2036...... using in one project Vst 3 versions and in another project vst 2, using presets.

in the VST3 project.... Ace and Zebra did not recall names, however both Diva and Satin did.

in the VST 2 version all patches were recalled in name, however the Satin bug reared its head and no audio......removed the plugin, re opened the project and project played, load VST3 version of Satin, and saved project.... reloaded projected and it still played fine.

rsp

[Urs]

both Diva and Satin did.

Until one day, they don't

[zvenx]

I see

rsp

[pdxindy]

I am willing to bet you don't use vst3.
Am I right?
rsp

nope..

..but i rather see one of my fav devs creating fascinating stuff in vst2 then struggle with vst3 all the time.

+1

[Bronto Scorpio]

Yeah, this whole AAX/OSX/VST3 thing has really slowed down a lot of developers this year.

Everyone would benefit from one single, well defined plugin standard. Plugin developers as well as the guys who provide the software that hosts the plugins.
Sadly that will never happen.

Just like MIDI will never die, even if it is the most horrible thing ever imo. Audio software would be much more advanced by now if we would have dropped MIDI 15 years ago.
Sadly we are still dealing with 7 bit messages and hex codes to get very basic stuff done..........in 2013.

Sorry for the OT!

Cheers
Dennis

[bighorse]

Everyone would benefit from one single, well defined plugin standard. Plugin developers as well as the guys who provide the software that hosts the plugins.
Sadly that will never happen.

Old engineer joke:
That's the wonderful thing about standards. There's so many to choose from!