[openbeosmediakit] Common Plugin API for BeOS Audio

  • From: "Frans van Nispen" <xlr8@xxxxxxx>
  • To: "Marcus" <dos4gw@xxxxxx>, "Jimmy Packes" <Axxepackes@xxxxxxx>,"Bruno G. Albuquerque" <bga@xxxxxxxxxxxxx>,"Dane Scott" <cte06376@xxxxxxxxxxxxxxxxxxxxxx>,<stippi@xxxxxxxxxxxxxxx>, <emilseg@xxxxxxxxxx>,<oxygenum@xxxxxxxxxx>, <openbeosmediakit@xxxxxxxxxxxxx>,<marcone@xxxxxxxxx>, <Buba@xxxxxxxxxxxx>
  • Date: Thu, 29 Aug 2002 21:16:03 +0200

This mail is important !

As you all know, support is very important for BeOS/OBOS. It is the most
powerfull platform for audio.

I have been working to get as much support from 3th parties as possible to
make OpenBeOS an accepted media choice and with some success.

We have found two companies that allowed me to port their VST plugins to
BeOS, I got someone to hand me a VSTGUI library that supports VSTGUI up to
version 2.0,
one company is now discussing details with us about porting their VSTi
instrument to BeOS and Ohm Force started to support BeOS again.

With all these efforts, it still does not look like Steinberg will concider
BeOS an option to support VST3.0. I have made serveral attempts to contact
them, but no coöperation or what so ever.

Besides this, VST does not meet all the conditions to make it 'the'
professional audio format and there are even companies that will not support
VST because of this.

OpenBeOS has so much potential, and as we are developing plug-in API's for
our SampleStudio and upcoming MultiStudio, we would like to take this
opportunity to let you all in on this.

This means, we want a plugin API that can be used by any BeOS/OBOS developer
to add plugin support to their audio application. We want this to be a
standard for BeOS.

To even make this more exciting, Sonic Timeworks is concidering to port
their plugins to BeOS if we can meet these goals and add their 2$ to the

We still will support VST for our products, but as we need a descent native
plugin API anyway, we could as well create a global usable one. After all,
the BeOS mediakit already was capable to host instruments, and doesn't need
VSTi for this.

Of course, this API will be a realtime one, as is the power of BeOS. We will
call these API's: 'RealtimeFX' - plugins. This standard will do realtime
effects, audio generation controlled by MIDI or other apps (Instruments) and
offline processing as needed in SampleStudio and ColdCut.

If we all can come to a common format for SampleStudio, XRS, ColdCut,
Sounplay, ... I will put in a bonus and make the first set of plugins for
BeOS, available for free.

I will proceed to create the RealtimeFX plugin library and API's anyway, but
hope we all can make it a BeOS standard.

Please react to this at frans@xxxxxxxxxxxxxx If you are with me on this, I
will setup a maillist to discus futher details.

Frans van Nispen,

Other related posts: