yep, and many more

 

Does that VST technology is protected by a copyright the same way as a song or is it the same way as a technologie ?

Because for the technology, it's protected with a patent and usually it can be for 20 years and after it become public (at least in Europe it's like that, or maybe it's 25/30 year, I'm not sure, also maybe different in USA/rest of the world). So maybe that's why they do this, if the VST 2 patent is from 1999, it will become public next year, so basically every developper could use it, so making the VST3 standard now would give Steinberg 10 more year (as it's from 2008 this I think) to exploit a VST patent.

I'm not really sure how it work on software/programming patent/copyright, but it work like that with physical technologie. Like the Technics turntable patent for its platter that became public in the early 00s and allow lot of brand using the same technologie (with their own improvment) to release their turntable

 

well to be fair, they did give a five-year warning in 2013. in computer terms, five years is a lifetime.

 

For those who don't know hope this helps

New VST3 features

Improved performance
Managing large plug-in sets and multiple virtual instruments on typical studio computer systems can often be difficult because of CPU performance limits. VST3 helps to improve overall performance by applying processing to plug-ins only when audio signals are present on their respective inputs. Instead of always processing input signals, VST3 plug-ins can apply their processing economically and only when it is needed.

Multiple dynamic I/Os
VST3 plug-ins are no longer limited to a fixed number of inputs and outputs. Their I/O configuration can dynamically adapt to the channel configuration they’re inserted in, meaning that any VST3 plug-in can be surround-capable with true multi-channel processing. For example, all the new VST3 plug-ins in Nuendo 4 can work in stereo-mode when inserted into a stereo channel, but switch to 6 channels when inserted into a 5.1 channel. Each audio channel is processed independently. Interaction between channels depends on the type and design of the plug-in. In addition to their flexible audio bussing capabilities, VST3 plug-ins may also offer a dedicated event bus. Typically, this is a MIDI input for control/modulation but these busses are no longer restricted to MIDI standard only. Future plug-ins may replace the common MIDI interface with alternative methods of control.


Activating/deactivating busses
A typical issue with current virtual instruments is their audio output bussing system and how they’re connected to the mixer after loading. Especially virtual samplers with multiple outputs often occupy more mixer channels than need. The VST3 interface offers the possibility to deactivate unused busses after loading and even reactivate those when needed. This cleans up the mixer and further helps to reduce CPU load.

Resizable edit windows
VST3 introduces a new approach to plug-in GUIs though window resizing, allowing for extremely flexible use of valuable screen space.


Sample-accurate automation
VST3 also features vastly improved parameter automation with sample accuracy and support for ‘ramped’ automation data, allowing completely accurate and rapid parameter automation changes.

Logical parameter organization
The plug-in parameters are displayed in a tree structure. Parameters are grouped into sections which represent the structure of the plug-in. Parameters like “Cutoff” and “Resonance” could be grouped into a section called “Filter”. This makes searching for a certain parameters easier, such as on an automation track. This also allows assigning a group of parameters to a specific MIDI Channel input and audio output bus.


Optional VST3/SKI combination
As a direct result of the modular interface design of VST3, the Steinberg Kernel Interface (SKI) can be combined with VST3 plug-ins. SKI is an additional SDK that allows extremely close integration of a plug-in with a Steinberg host application, and allows functions to be carried out almost from within the application. This extends to the ability to create tracks, copy, cut, paste or process events in the Steinberg host application. SKI is provided to selected industry partners upon request.

VSTXML for remote controllers
Remote controllers for audio and MIDI software applications have become increasingly popular. With VSTXML, VST3 offers far more flexible control of VST plug-ins by remote controllers. Using the knobs and faders on the control surface, parameters can be recorded, renamed and edited in many ways. Parameters that cannot be edited can be routed for display purposes to the control surface, for example to show Gain Reduction on compressor.


UTF16 for localized parameter naming
In VST3, all strings that can be displayed to the user are in Unicode (UTF16) format. Usage of this universal character base allows the host application to display characters in localized languages.

No MIDI restriction for parameter value transfers
VST3 has a dedicated interface for event handling that carries a much wider range of functionality than standard MIDI events would be able to provide. This opens up a big range of opportunities for musical use cases with very high potential for innovative product design. For example with VST3 some controller events (for example, pitch) can be referred to a note event (using a note unique ID). This offers the possibility to e.g. modulate only a single note which itself is part of a chord.


Audio inputs for VST instruments
The VST3 interface expands VST instruments by adding the ability to create audio input busses. As a result, audio data can be routed to an VST3 instrument. A synthesizer which has a built-in e.g. vocoder effect is able to process audio data coming in from other sources as well.

Multiple MIDI inputs/outputs
Unlike with VST 2.x,, a VST3 plug-in can have more than only one MIDI input or one MIDI output at the same time.


64-bit processing
VST3 plug-ins are generally able to process audio data in 64-bit.

-------------------------------------------------------------------------------

I have added this information as well, again i hope it's useful for somebody.

VST Expression
VST Expression is a groundbreaking technology introduced by Steinberg in Cubase 5 and significantly extended in Cubase 6. The latest version, VST Expression 2, is based on three core technologies: Note Expression, Expression Maps and VST Dynamics.

Note Expression
Note Expression is a revolutionary new way of controller editing, introduced in Cubase 6. As an alternative to viewing/editing controller data in the Controller Lane in the Key Editor, controller data can now be viewed/edited directly on the associated MIDI note events. Controllers now have a much more logical and musical character. A note event and its associated controller data are treated as a unit. A single note or multiple selected notes can be moved, copied, duplicated or deleted, and all their associated controller information will follow. Controllers can be conveniently edited using intuitive tools in the new Note Expression editor. This allows for more intuitive and more accurate editing of controller data.

A major limitation of MIDI is the nature of controller information. With the exception of poly pressure (polyphonic aftertouch), controller messages such as modulation or pitch bend are channel messages. It is important to understand that articulation data on one note usually also affect any other note playing on the same track/channel at the same time.

With VST 3, Cubase is able to break free from the limitations of MIDI controller events by providing access to new VST 3 controller events that circumvent the laws of MIDI and provide articulation information for each individual note — even in a polyphonic arrangement. Articulating each note in a chord individually creates a much more natural feel, just like multiple players playing the same instrument at the same time but each one adding his own personality to the notes played. Of course, this not only requires a new set of controller parameters, the socalled VST 3 Controllers, but it also requires an instrument capable of playing back these new controller messages. HALion Sonic SE and HALion Sonic 1.5 are the first Note Expression compatible VST 3.5 instruments available on the market that support this revolutionary new technology.


Expression Maps help you work with musical articulations. Articulations define how certain notes “sound”, i.e. how they should be performed on a given instrument. They allow you to specify that a string instrument is bowed (not plucked), a trumpet muted (not played open), and so on.

In Cubase, when you select an Expression Map for a MIDI or instrument track, the articulations (sounds) defined in the map are automatically applied during playback. Cubase recognizes the expressions scored for the MIDI part, searches for a matching articulation, and then the current note is either modified (e.g. played louder), or the MIDI channel, program change or key switch information is sent to the connected instrument, so that a different sound is played.




Go to top

 

Last edited: May 18, 2018

.....i'm scared!!!

 

Now is the best time to switch to a new, open-source, license-free standard that is independent from Steinberg and any other company!
If enough developers refuse to write VST3 plugins and discuss and steer towards new alternatives, Steinberg can do nothing.
Today we have enough developers who really know about coding and how a good plugin SDK should look like. They can communicate easily with the help of the magnificent internet too.

Otherwise, the most popular underground file share will be the Steinberg VST2 SDK

 

Too late!
Many companies already fully rely on VST3 and are considering to cease VST2. Many others are about to release VST3 versions of their plugins shortly. In the long run no manufacturer will be able to get around the VST3 standard - not even NI!
A good chance for a "revolution" would have been 5 years ago, when the cancellation from Steinberg came.

If today a "Linus Torvalds of the plugins" would get up, how far would he get? Linux distributions started in 1992 and where are they today? Ridiculous ~2% of installations on desktops (http://gs.statcounter.com/os-market-share/desktop/worldwide)! Not even the Windows 8 disaster changed that. Nothing against free standards, but it takes half an eternity for them to prevail, if they do at all.
But that's another story...

 

Last edited: May 18, 2018

Might be a good thing to drive evolution forward If developers stop creating VST2 Plugins, NI might finally add the VST3 support.

 

I was the manager of Men's Underwear and Accessories at a large department store in NYC when I was 20, so when I tell you that Pagurida speaks the truth, you can believe him. I am a consumate professional and I sanction the veracity of his message.

 

Thank you, Sir, immense honor!

I appreciate the independent, honest, impartial recognition of a great expert!

(PS. I'll put the dough in the usual place...)

 

Last edited: May 18, 2018

In the end, we can see this as something very similar to DirectX versions. Well, and Windows versions. Not that they don't improve, but obviously is mainly about the money. And they got us by the balls, because there isn't an alternative for the 90% of us.

For example take VST3 Polyphonic per-note expression. Steinberg's Sampler (I don't even remember its name lol) it's the first to support it.

But we also must remember that developing and maintaining a complex technology like VST is not an easy task.

Probably some of this applies but I don't know much about patents.
What I know is that in the software world nowadays you can use most of the more powerful tools (Visual Studio with DirectX tools, the famous JUCE framework, VST3 SDK) for free as long you don't make money. You want to make money, you pay.

That would be perfect, but just for being free almost all commercial plugin developers wouldn't support it. Because plugin developers also have to eat.

 

Last edited: May 18, 2018

There is nothing to maintain when those files haven't changed for over a decade. But I get it, it's way too costly to supply a bunch of kilobyte-sized files, which also end up compressed when downloaded, even as the VST3 SDK is orders of magnitude larger than that.

I'm literally sick of excuses from clown developers when their bullshit is obvious. This company deserves to be bankrupt, both morally and economically.

Just think about. It costs nothing to supply a few kilobytes of headers. So if VST3 really was "adopted" by many devs "gravitating" towards it as their PR bullshit claims, then why force it? They seem afraid it would never catch on. I hope this move kills them off for good and devs switch to something like LV2 instead.

 

The fact that you can't pick where to install vst3 plugins is one of the dumbest design decisions ever. What's the point of doing that? Go to hell, Steinberg.

 

unfortunately it looks like big players in the industry are moving more and more towards proprietary solutions...
more money, less problems.....for them...

 

"proprietary" is a word meaning they own you.

 

how is it spelled correctly ? or did i misunderstand your post :D

 

And any plugs made using it must be free and underground too. It's licensed technology.

Time for an open standard.

All things must pass.

 

Well, more than moving it's kind of they always were there.

 

If there's any company that's not going to go the way of gibson, it's Yamaha.

 

we should start coding our plugins here at AS and show middle finger to all :D ...i would love to see AudioSEX CompreXor, Eq-eXor, etc :D