VST Plugins Adapter's Notice
©2000, Georges-Edouard Berenger, berenger@francenet.fr
Hamburg, December 17th, 2000.
What is VST Plugins Adapter?
VST Plugins Adapter is a SoundPlay plugin that will bring VST Plugins support to that application.
In other words, it will allow SoundPlay to use the BeOS version of VST Plugins.[to continue...]
To know more about VST Plugins, please visit Steinberg's Web site.
Is the source code available?
Yes, here, at BeBits.
You are encourage to copy it to bring VST Plugins support to your own applications. I have started this project as the
last thing I have done while working for Steinberg for that purpose. Thanks to the Steinberg people for letting me do that.
Where can I find VST Plugins for BeOS?
For example, Here!
If you are interested in writing your own VST Plugins, you should start by downloading
the VST Plugins Developer Kit.
How does it work?
VST Plugins Adapter comes directly installed with SoundPlay. If you have installed SoundPlay properly, then you
only need to download VST plugins for BeOS and place them in some defined place(s). We recommend that you place them
in the /boot/home/config/add-ons/VST Plugins/ folder, but you can place them anywhere. You'll just have to tell
VST Plugins Adapter where to look for them though. To do that:
- Launch SoundPlay,
- select the Preferences panel,
- go to the Plugins/Filters section,
- double click on "VST Plugins Adapter", or select that item and press the "Configure" button.
- This has brought up the VST Plugins Adapter's configuration window. Use it to designate where your
VST Plugins are located.
Note: If you empty this list, VST Plugins Adapter will revert to the default setting.
Note 2: You can manually edit this list. It is a simple text file placed at this location:
/boot/home/config/settings/VST Plugins Folders List.
Troubleshooting
It happens that one suspects that some VST Plugin causes SoundPlay to crash, especially when SoundPlay starts (VST Plugins are
temporarily loaded then to build SoundPlay plugins list).
Here are a few tips to help.
- Deactivate VST Plugins Adapter completely. An easy way to do that is to move VST Plugins Adapter away from SoundPlay's plugins folder.
If the problem disappears, then you can suppose that a least one VST Plugin does something wrong. In which case, you will want
to try to indentify which plugin(s) is (are) culprit.
- Launch SoundPlay from a terminal. VST Plugins Adapter will print out what it is doing when it scans the VST plugins folder(s).
Since it is possible that a plugin corrupts memory which then causes some other plugin (or SoundPlay itself) to crash later,
a good idea is to type this in a terminal:
export MALLOC_DEBUG=10
Before you launch SoundPlay directly from that same terminal. If the plugin does something wrong in its memory management, then
you are very lickely to hear earlier about it... :)
Experience shows that it is not because a plugin works fine under Windows or MacOS that is doesn't contain any bug. Many bugs
remain long undiscovered because they don't produce visible enough side effects. The same bug might be invisible with some OS, but will
cause a direct crash with some other. Remember as well that BeOS is a more agressive OS regarding multithreading, which often does that
bugs are problematic only under BeOS.
Special Thanks!
A number of special thanks must be given:
- Le Buzz's editor Dane Scott for having the idea
in the first place and requesting it on his web site last summer!
- Steinberg Media AG for allowing me to start the project during my last days in the company.
- Steinberg's Yvan Grabit for his answers regarging VST Plugins & VST GUI.
- Marco Nelissen, SoundPlay's author, who made many improvements to SoundPlay's plugins architecture so that this plugin is now very
clean & simple. For instance, he added float buffers support as well as a new C++ interface for SoundPlay plugins. He also
contributed in code, testing & suggestions.
License
This software is a freeware.
This software is not endorsed by Steinberg Media AG, and therefore, questions, requests, bug reports should only be
sent to the author.
The author makes no warranties, express or implied, including
without limitation the implied warranties of merchandability and fitness for any particular
purpose, regarding this software. The author does not warrant, guarantee or make any
representations regarding the use or the results of the use of the software in terms of its
correctness, accuracy, reliability, currentness or otherwise. The entire risk as to the results
and performance of the software is assumed by you.
I'll be glad to hear about your bug reports, problems, comments, flames...
You can mail me directly : Georges-Edouard Berenger.
Before you get to me though, please be as sure as possible that the problem lies in VST Plugins Adapter itself, and
not in a specific VST Plugin or SoundPlay itself... In those later case, please get in touch with their respective authors.
Known bugs & problems
- At this time, VST Instruments are not supported, though there is a premiliminary support in the code.
Unfortunately, it requires an updated version of BeOS's Midi Server, and even, presents many issues.
- When for some reason, a VST Plugins crashes when trying to load it, then SoundPlay will go away as well.
Look at the troubleshooting section for more help.
History
v1.0 (December 17th, 2000)