Don't know if anyone noticed... VST3

[Chris Walton]

I'd be happy for KVR to get behind something like this with any resources we could provide (domain, hosting, forums, storage, wiki, cvs/svn, etc.).

Let me know if there is anything I can do to help.

many thanks!

I'm definetely interested

[ObsoleteAcc99]

[DELETED]

[ObsoleteAcc99]

[DELETED]

[ObsoleteAcc99]

[DELETED]

[Fred e]

Is there any need to actually convert existing plugins to VST3 unless there is a need or costomer demand for the new possibilities? I mean, won't VST2.4 be host-supported like forever, at least I am not very likely to buy a host app that don't support 2.4. And the silence detection/switch off, can't you do that with 2.4 as well?

The most exciting new feature to me is the SKI, I can see a future of new "workflow plugins", that can well be the future of DAWs, provided this feature is going to be supported by others than steinberg.

[ObsoleteAcc99]

[DELETED]

[Urs]

It will be interesting to see how quickly and widely adopted the VST3 standard is - I wonder if/when Steinberg will drop VST 2.4 compatibility.

Here's my guess:

Steinberg drop VST2 within 3 years -> Cubase is dead, VST3 shortly thereafter
Steinberg don't drop VST2 within 3 years -> VST3 is born slightly dead

So, what's really new and exciting?

Unicode support -> good for emerging markets such as China. Investment in the future, say, 2023, unless Unicode is phased out by then.

ChannelLayouts -> might help Nuendo quite a bit. Some plugs specialized in surround may be cool and make life easier for film composers. Sounds like a niche for a standard next to a standard.

#---

Regarding the wrapper... it can be fully shared with source code (incl. VST/RTAS) among all developers who signed agreements with Digi and Steinberg. Why open source to the world for something that only 100 people are interested in. Wouldn't it be cool enough to just open source among an interest group?

Urs

[quikquak]

And the silence detection/switch off, can't you do that with 2.4 as well?

yes, everyone keeps saying that, but no one implements it in their plugins

If this new silence detection 'listens' to a tap delay, how will it know that another tap isn't arriving after a long blank pause....? I guess the dev has a choice to switch it on, and how many will do that?

[Urs]

soooooo.... u r saying developers ARE "obviously" going to adopt to vst3? That's what your post implies.

I don't know what the others will do. How would I?

I only know that all devs I talked to were not amused.

Wait. Some were pretty amused actually.

#---

Another thought: Devs who support multiple formats do usually keep stuff within the boundaries of the smallest common denominator of the formats. That's why hardly anyone uses ChannelLayouts in AU when they also support VST. So. I guess that the new flexibility won't be adopted widely as long as VST2 still has to be supported?

[nollock]

If there's so much plugin and host devoloper unrest about VST3 why not organize a boycott?

"so much"? so far i have seen 4 developers complain here on kvr (out of hundreds)

Maybe I overstated it because it will cause a huge amount of extra work for me. Possibly a rewrite of over 40,000 lines of code, if it realy is tied to C++.

[otristan]

Hey guys,


I was wondering who is at NAMM this year ?
In order to see in person, guys you see on ML daily.

For example Angus I owe you a beer for an old tips(2 year ago)

Either today or tomorrow. (I have an appointment with RedMatica guys at 2PM today but available the rest of the day)

Could be nice to talk and share some beers

Let me know what do you think.

[Urs]

In order to see in person, guys you see on ML daily.

I was there yesterday only. I've seen you standing behind Dave and Jim from UA during the VST3 event, but I couldn't just jump to say hello, and then you were gone

[Aleksey Vaneev]

so you are saying they ARE compatible?

Nope. I want to say that Steinberg can sell any kind of bulltalk. It's possible to support VST3 if you implement its support from the scratch. You do not have to drop existing VST2.4 - this is what Steinberg meant I think. But you still have to implement it from the scratch.

[Aleksey Vaneev]

Another thought: Devs who support multiple formats do usually keep stuff within the boundaries of the smallest common denominator of the formats. That's why hardly anyone uses ChannelLayouts in AU when they also support VST. So. I guess that the new flexibility won't be adopted widely as long as VST2 still has to be supported?

I try to support all useful features. But AudioUnits do not have means to report 'bouncing' state - so 'Auto' quality is disabled in AudioUnits. Seems like in AudioUnits a user can't give names to channels, so this feature is also left behind while it's supported in VST. VST had speaker arrangements from v2.1 I think - it allows dynamic IO (number of channels changes) and provides speaker setup (same as channel layout in AU I presume).

[VitaminD]

I just downloaded the SDK.. talk about redtape to get to it.. in the past I've seen the licensing agreement and the "I agree" button was essentially the link to the download..

not anymore.. oh no you need to register a username password.. which means they want name, address, phone number, birthdate, what type of products you're making (commercial, shareware, freeware), what previous products you've created, what products you're working on.. etc etc ETC.


then after going through 2 (or 3?) agreements, one gets the download link, great I click it.. a few moments later its downloaded. Extract and and peek into the docs folder, I noticed literally half the files in that folder are about licensing!!!