AES Amsterdam.JonHodgson wrote:I'll still insist you buy the first beer if Dave gets any of those emails I described though!
In addition to that, I will see to it that it's Belgian beer.
Fredo
AES Amsterdam.JonHodgson wrote:I'll still insist you buy the first beer if Dave gets any of those emails I described though!
If the invitation was on VST mailing list then I do not care. I dislike discussion mailing lists. Somebody from Steinberg could arrive on THIS public forum, or on another public forum. Such things should not be done in a local fashion.Fredo Gevaert wrote:Yvan told me that the number of reactions was dissapointing, probably due to the overload of work they were facing with MacIntel & Vista.
... With VST2.4 you can ... if a host e.g. Logic decides not to support VST2.4 is another matter of course ...daverich wrote:another vote here for either LV2, or something similar.
We really do need an open standard.
It's always suprised me why with the plugin architecture you can't just write one plugin, and then every host on every platform be able to use it...
+1daverich wrote: We really do need an open standard.
if a large number of devs decide to just release plugins in this new format, I'd be very intrigued to see how long any daw would go without supporting it.asseca wrote:... With VST2.4 you can ... if a host e.g. Logic decides not to support VST2.4 is another matter of course ...daverich wrote:another vote here for either LV2, or something similar.
We really do need an open standard.
It's always suprised me why with the plugin architecture you can't just write one plugin, and then every host on every platform be able to use it...
... for a number of reasons already mentioned earlier in this thread I think that some VST developers would like an open standard which is similar to VST2.4 ... LV2 looks like a deviation from that idea ...daverich wrote:if a large number of devs decide to just release plugins in this new format, I'd be very intrigued to see how long any daw would go without supporting it.
for Logic it'd be a case of - "well at least it's not VST", and for cubase "at least it's not AU" etc etc...
I'm still in shock about your saying here!Urs wrote:Also, once I doubleclicked the numerical gain value to manually edit it, it wouldn't respond to changes of the slider anymore. Hmmm.Urs wrote:Btw. I just built again.vst3, but I can't resize the editor window...?
I don't know...quikquak wrote:What in the world is that all about.
I get the feeling that the original VST3 was a continuation based on VST2.4, and then somebody decided VST3 needed a complete new specification ...ttoz wrote:and the were going to release it one full year ago, so it makes you wonder, what the hell have steiny been doing?
I would disagree, in that the process is going to make all the difference in the results. When the setting and modifying of standards is controlled by a small number (sometimes just one) of companies that have their own agenda, bad things are more likely to happen for those who are not participating in the process. In the end, those who try to control the process may find themselves faced with competition from an open standard developed by everyone else. It's certainly possible in this case.Crandall1 wrote:*sigh*
I'm not sure how one determines whether a VST developer is "major" or "minor," but we weren't invited, and I think it's safe to say that we sell far more VST plugins than AudioEase does. No other developers I know were invited. I'm not sure what this invitation consisted of, but as far as I can ascertain, it wasn't on the VST dev list.
That isn't really important, though...
LADSPA ?We really do need an open standard.
Submit: News, Plugins, Hosts & Apps | Advertise @ KVR | Developer Account | About KVR / Contact Us | Privacy Statement
© KVR Audio, Inc. 2000-2026