Don't know if anyone noticed... VST3

DSP, Plugin and Host development discussion.
Post Reply New Topic
RELATED
PRODUCTS

Post

Ben [Camel Audio] wrote:the main problem would seem to be supporting VST3 due to the model-view-controller approach that Angus mentioned.
It's not a problem as long as you can implement AudioUnits. AudioUnits basically use the same approach, they even call it similarly (wikipedia describes this academic approach which appeared together with SmallTalk). It boils down to writing an event bridge that can transfer events (and data) from DSP to UI and back.
Image

Post

Interesting. I was just taking a look at the SDK. "processReplacing" has been replaced by a "process" method that takes a ProcessData object. This object appears to bundle up information about timestamped events, such as parameter changes and MIDI events, as well as holding the input and output buffers.

Post

Fred e wrote: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.
Remember the VST Module Architecture SDK? 8-)
"Until you spread your wings, you'll have no idea how far you can walk." Image

Post

First impression: Wow, someone has been busy :clap:
Second Impression: The first hurdle to adapt to this system is huge and I'm still sceptical about the whole COM-like design. TBH, from a more aesthetical position I always found COM just enormously ugly :lol: but we'll see, although I doubt anyone is in a hurry to move onto it yet ...

Post

bummer, on paper this looked great form the user-end...

Post

from what steinberg have said a number of host developers have been included in the making of this (although they have never stated who). So I suspect the likes of virsyn and other friends of steinbug may have vst 3 plugs out pretty soon

and i expect every plug-in developer will have people moaning at them to go vst 3 in the same way they had people moaning at them to go AU or UB or whatever

who would be a plug-in developer ?
I believe every thread should devolve into character attacks and witch-burning. It really helps the discussion.

Post

ericj23 wrote:and i expect every plug-in developer will have people moaning at them to go vst 3 in the same way they had people moaning at them to go AU or UB or whatever
AU and UB are different story: you can't live without them on Mac considering Apple software does not support VST.

With VST3 we have standard that does not make anyone's life easier, or changes it in any way at all. VST3 is what probably makes Steinberg developer's life easier - not others. It's Apple's habits and Microsoft's programming approaches mix. :)
Image

Post

ericj23 wrote: and i expect every plug-in developer will have people moaning at them to go vst 3 in the same way they had people moaning at them to go AU or UB or whatever
I'd rather see the independent developers thrash out an independent standard, TBH.
An idiot on Set Theory:
"In some cases there is an object called red that contains everything that is red. In much the same way a pot is a plate."

Post

ericj23 wrote:from what steinberg have said a number of host developers have been included in the making of this (although they have never stated who). So I suspect the likes of virsyn and other friends of steinbug may have vst 3 plugs out pretty soon
Well, even the ones they had in the showcase yesterday havn't finished the transition - spoke to one of them and what we saw wasn't a VST3 (EDIT: that's how I understood "nah, we havn't finished any yet").

I think I'm not so much annoyed about the amount of work involved and the design of the SDK. I'm mostly annoyed about how they market it. Hardly anything is new, hardly anything can't be done with what we have. As always with marketing, most of it is just made up. I hate that crap.

And the result is just that: Users will be bugging us because they are made to believe the utter crap.
Last edited by Urs on Fri Jan 18, 2008 8:24 pm, edited 1 time in total.

Post

[DELETED]

Post

They appear to have a few updated on their Cubase Essential 4, like HALion.
--==> http://www.steinberg.net/1592+M52087573ab0.html

Post

ttoz wrote:well the sample accurate automation and cpu saving features are what is of interest to me as an end user. what crap am i believing?

it works.. you can see with the included vst3 plugs in C4.
Its already been said in this thread out that these could be implemented with minimal extension to the existing VST2.4 standard.
An idiot on Set Theory:
"In some cases there is an object called red that contains everything that is red. In much the same way a pot is a plate."

Post

ttoz wrote:well the sample accurate automation and cpu saving features are what is of interest to me as an end user. what crap am i believing?

it works.. you can see with the included vst3 plugs in C4.
All this stuff still has to be coded into the VSTs. Only because the parameter automation comes with time stamps doesn't mean they're magically interpolated.

I'm pretty full of doubts regarding the mystical algorithm that detects silence. I'm using lots of different ones for delay, chorus, reverb, filters and I had a hard time debugging them. I suppose that this is put on our shoulders as well.

Just like the "advanced preset browsing" is a host thing. Poor host developers. If they got something better (NI Kore anyone?) they still have to copy Cubase or what?!?

Post

first off im defintely not saying I particularly like this - it seems like steinberg putting the programming load onto plug-in developers for no huge gains to anyone (other than maybe steinberg's host writers - and for the amount the host costs they shouldn't need this "help")

but i find this wierd
Aleksey Vaneev wrote:
ericj23 wrote:and i expect every plug-in developer will have people moaning at them to go vst 3 in the same way they had people moaning at them to go AU or UB or whatever
AU and UB are different story: you can't live without them on Mac considering Apple software does not support VST.

With VST3 we have standard that does not make anyone's life easier, or changes it in any way at all. VST3 is what probably makes Steinberg developer's life easier - not others. It's Apple's habits and Microsoft's programming approaches mix. :)
why does one software producer forcing their customers plug-in developers to take on a new standard for no gain in function differ because they happen to be the OS developer ?

The independant developers standard thing sounds interesting - but surely you need some of the host developers on board - developing plug-ins just to run in reaper, xt etc is all well and good but a significant amount of the money is with people who's preferred host is logic/cubase/pro tools, none of which will support this standard anytime soon

so if your running a business doesn't your open standard just make even more work maintaining an even bigger codebase or alienate you froma significant number of your customers ?

cool if you can have the standard so open that you can produce the plug without any huge increase in work - which i'm guessing is the aim
Last edited by ericj23 on Fri Jan 18, 2008 8:31 pm, edited 1 time in total.
I believe every thread should devolve into character attacks and witch-burning. It really helps the discussion.

Post

[DELETED]

Post Reply

Return to “DSP and Plugin Development”