hello,
to clarify the current format capabilities of the library:
the library for now can be used to create:
- vst plugins for linux and windows (so / dll)
- standalone executables for linux and windows ('elf' exe/ 'pe' exe).
the standalone executables are not plugin host containers, but they can use
most of the library features such as gui widgets, drawing capabilities,
image decoding, file i/o etc. such executables can be useful for debugging a
plugin gui for example so that no host is needed to load into.
also the standalone executable can be created with no plugin ideas in mind
at all. an example for that would be a gui plotting program that can write
the resulted data from a buffer to the hard-drive.
standalone exacutables may eventually have some sound processing
cababilities, for example: reading a wavetable from disk and sending the
signal to the sound interface. also some primitive host capabilities for
plugins (i personally do not see much use for that).
on the plugin side there are a lot of possibilities and we are eventually
going to expand to more plugin formats like ladspa, other linux formats and
possibly au (while adding some osx platform code).
the general idea for the plugin formats is to have *unified plugin syntax
that can be compiled easily for different formats by simply switching a
compiler flag e.g. -DAX_FORMAT_VST / -DAX_FORMAT_LADSPA.
*or a least unified as much as possible ;)
of course any suggestions and comments are welcome and appreciated in the
same notion.
lubomir
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev@email-addr-hidden
http://lists.linuxaudio.org/listinfo/linux-audio-dev
Received on Wed Jun 9 00:15:02 2010
This archive was generated by hypermail 2.1.8 : Wed Jun 09 2010 - 00:15:02 EEST