Don't know if anyone noticed... VST3

[asseca]

Everyone is surrounding the dance floor but no one wants to go on first. Gotta love humans

We are waiting for Ben[KvR] and Angus to open a dedicated developer's forum for the open plugin standard initiative ...

In the meantime we are just keeping the camp fire burning ...

[stefancrs]

I kinda like the ring of FST.

Free Studio Technology?

If so, I like the abbreviation but not the full name. Other FxT's (FPT, FTT, FNT, FCT etc! Works a treat!) roll nicely off the tongue too.

Someone hurry! Cite Shakespeare!

edit: But we can deal with all this later, like Aleksey says

[mystran]

I kinda like the ring of FST.

Free Studio Technology?

..or F**k S****b**g Technology?

Sorry.. just couldn't resist it.

[Angus_FX]

We are waiting for Ben[KvR] and Angus to open a dedicated developer's forum for the open plugin standard initiative ...

Just to clarify on this -- there will be a dedicated forum, on an invite basis initially, and there's a long list of people who want to be involved. The reason we haven't opened it yet is that I want to give others in the industry a chance to get back from NAMM etc. and be invited on the 'ground floor' -- there are some devs who should be involved that I've not had a chance to contact yet, and I don't want them to have to start from a forum that already has 1,500 posts.

We have also set up an announce mailing list, seperate from the forum, that *anybody* who wants to create an open plugin standard can use as a directory of interested parties.

[lowkey]

GO DEVS!!!

Seriously, we user's are behind ya so show them how it should be done!

[Gavin@FAW]

JUCE has pretty much solved the problem of having to cope with multiple SDK's. Used by Arturia, Korg, Cycling 74, TC Electronics and lots more.
Also maybe better letting the dust settle on VST 3.0 before rushing head long into it.

[lowkey]

This might be worth looking into...

http://www.grame.fr/~letz/jackdmp.html

It covers Windows, OSX and Linux. Heres how its implemented in Linux...

http://jackit.sourceforge.net/docs/design/

It could side step having DAWS support it a new plugin format because its between the audio application and the soundcard driver.

[stefancrs]

This might be worth looking into...

http://www.grame.fr/~letz/jackdmp.html

It covers Windows, OSX and Linux. Heres how its implemented in Linux...

http://jackit.sourceforge.net/docs/design/

It could side step having DAWS support it a new plugin format because its between the audio application and the soundcard driver.

I hope I'm not completely off here, but since jack isn't really a plugin standard, but more of a protocol one (at least afaik?), the main drawback, imo, is that your project won't be self-contained, so to speak.

Sorry if I'm wrong about this.

[Tallisman]

For what it's worth... I am dying to see an OPiS

Open Plug-in Standard !

or perhaps an OPuS

Open Plug-in Standard.

Not to be confused with opensource plugins

.t

how about Open Studio eXtensions

DSP

I am not crazy about Open Studio eXtensions, as we already have one major OSX to deal with.

Being that Opus is a Musical Composition, I think there is a nifty little link there.

FST imho is so close to VST I'd feel like I was still swingin' on Steiny's loins and nether regions, Plus acronyms lack personality.

OPiS rolls nicely off the tongue.

.t

[liqih]

one thing that worries me is that I see many devs (who even support the open standard planned here) may run to be among the first to release VST3 updates, just maybe for they are "afraid" of loosing market positions.
IMHO a presequisite for the success of the open standard is a little delay on the VST3 update. Who agree?

[edited for clarity]

[WilliamK]

one thing that worries me is that I see many devs (who even support the open standard planned here) may run to be among the first to release VST3 updates, just maybe for they are "afraid" of loosing market positions.
IMHO a presequisite for the success of the open standard is a little boycottage of the VST3 update. Who agree?

Not sure if I got what you mean, but I'm one that don't really care at all for VST3. If hosts won't support VST 2.4 anymore, its THEIR lost, not our problem I think. Right? I'm still thinking over this, but I'm not that worried about this yet. Took me over a year to really care about porting our code to the VST SDK 2.4 and we didn't had many complaints about that.

Wk

[Angus_FX]

Hi Liqih,

Speaking only for myself.. right now I see no compelling commercial reason to support VST3, no real user benefit, and a lot of work. So I don't have any plans to work on it right now, and I don't see many that do.

On the flip side.. I think it's counter productive to promote any open API as an anti-VST specifically, it should be pitched as an anti(any less-open, less well designed standard). After all, Steinberg is hardly the only big-dog developer who's caused unnecessary work and pain to developers around here. Apple is if anything more guilty, and while my experiences with Digidesign have only really been positive, others here will tell a different story I'm sure.

So, until we have an independent API that can be promoted on its own merits, I don't see any point in doing anything specifically anti-VST3.

Regards,
Angus.

[liqih]

ok William, I see you are not one of those who will run to be among the first with VST3 supported, <grin> good to me, thanks

[WilliamK]

So, until we have an independent API that can be promoted on its own merits, I don't see any point in doing anything specifically anti-VST3.
Regards, Angus.

+1

Wk

[wikter]

IMHO, VST 2.4 is enough powerful to keep programming using it.
The optimizations to switch off plugins (Jeskola Buzz switches off any silenced generator and "noinput" effects since... 1997), route channels and process only one channel on mono signals don't need a version switch. Isn't it?

Note: I hate Stereo>Stereo plugins.
Logic PC user (Only VST 2.3).