Don't know if anyone noticed... VST3

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

Post

Mark Vera wrote:
VitaminD wrote: in other news.. I *was* compiling and getting the plugin, the problem was its labeled as a *.vst3 so I didn't realize what it was :o It was also on an entirely different drive than the one with my SDK on it.. :nutter:

in other other news.... I just realized that my host of choice (orion) doesn't recognize vst3 plugins nor when they're relabeled as DLLs... so all of this was pointless to me :hihi:
The path is set in the project to the global VST3 path the SDK mentions. Silly place, and puzzles me why user path is omitted officially under Windows when it's "supported" in Mac. Especially now that Vista may have limitations on installings stuff to global paths.

But you're right no VST3 under Orion, quite obvious that the SDK was released just hours ago.
yeah it seems the sdk was refined more for mac use in my experiences.. :shrug:

oh and well I was hoping that (somehow I knew it was highly unlikely) the vst3 plugins would be backwards compatible to vst2.4 but obviously this isn't the case :hihi:

Post

VitaminD wrote:oh and well I was hoping that (somehow I knew it was highly unlikely) the vst3 plugins would be backwards compatible to vst2.4 but obviously this isn't the case :hihi:
vst2.4 isn't fully backwards compatible with vst2.3, so what did you expect...
"Until you spread your wings, you'll have no idea how far you can walk." Image

Post

[DELETED]

Post

[DELETED]
Last edited by ObsoleteAcc99 on Sat Jan 19, 2008 6:50 am, edited 1 time in total.

Post

[DELETED]

Post

[DELETED]

Post

[DELETED]

Post

[DELETED]

Post

wallander:-
Is there a technical reason why they don't run the GUI on the slave as well and just export the window graphics and mouse/key events? Feels like this would be the reasonable way to do multi-computer processing, and any host should be able to do this today for all its plugins, regardless of plugin standard.
Agreed 110%. Steinberg (and Apple) don't like that approach (generally termed RFB - remote frame buffering) because it's likely to be marginally less efficient than MVC (at least for network bandwidth), and a bit more complicated for the host developer.. I don't think they appreciate how bad an idea it is to push the extra complexity on to the thousands of plug-ins out there.

ttoz:-
this is the last topic., there were two more before that but i think this covers everything best. Yes, THIS i am pissed about. but again, vst3 solves it. Mind you automation was not sample accurate in cubase 3 either, just easier to edit.
Thanks for the link - but wouldn't, um, "fixing the damn bug" solve it too? Looks pretty obvious to me, and even ought to be easy, given that other VST2 hosts don't suffer from this. There is nothing in VST3 which would require a host to break VST2 support. BTW it is imho pretty appalling how you're getting treated in that thread. Do you really trust those people with the future of audio plug-ins?

BTW:- a rewrite like VST3 to address a couple of small, easy automation issues, sidechaining, and silence detection, is very much a case of, as they say in Germany, using cannons to kill sparrows.

Cheers,
Angus.
This account is dormant, I am no longer employed by FXpansion / ROLI.

Find me on LinkedIn or elsewhere if you need to get in touch.

Post

----
Last edited by Rangtangtang on Tue Jan 29, 2008 2:57 pm, edited 1 time in total.

Post

Just to let you know, we (together with Synapse Audio's developer) have already implemented 'sample accurate' automation in VST2, by introducing 'kVstAutomationType' event type (and the according "canDo"). It carries structure with three values: automation param id, new value and sample offset.

It's really very easy to do, especially if plug-in already supported MIDI CC events.
Image

Post

Rangtangtang wrote:Would VST3 mean better sampler?
Better in what aspect?
Image

Post

After giving VST3 a look over, I just hope that steinberg and the other major host developers continue full support for 2.4 for another couple of years.
The level of complexity of the new SDK coupled with the usual very thin
documentation means ill need that long to get up to speed with it.
They really need to have at least a similar level of info as Apple has for
AU. I develop for OSX only at the moment so it odd that the supplied PluginTestHost app doesnt even run properly - the .srf is missing i think, and
after compiling and loading again.vst3 it crashes Cubase 4...

Post

FYI, any developers:- Ben has kindly set us up an announce-list for organising efforts to develop an open plug-in API. Mail me (angus _at_ fxpansion _dot_ com) if you would like to be involved.
This account is dormant, I am no longer employed by FXpansion / ROLI.

Find me on LinkedIn or elsewhere if you need to get in touch.

Post

---
Last edited by Rangtangtang on Tue Jan 29, 2008 2:55 pm, edited 1 time in total.

Post Reply

Return to “DSP and Plugin Development”