Mission #1 accomplished. NASPRO core 0.1.0 is finally completed.

Good things:

• it works well enough for a development release
• it has enourmous potential and shows some good ideas
• it is very small
• porting to POSIX conformant OSes other than Linux should require minimal effort
• it shouldn't contain too many bugs (I hope :-)
• good level of documentation for this stage of development

Bad things:

• the API is immature, unstable and not perfectly clean
• the code is messy in many points and its behaviour is not always perfect
• not every operation is totally thread-safe
• many messages missing (going to be fixed before NASPRO 0.1.0 release)

All these problems are to be solved during the first development cycle (before NASPRO 0.2.0, which will be the first stable release), so I can't suggest its use for any program which is going to be publicly distributed.

The official release will come together with the other components of NASPRO 0.1.0 (NASPRO objects, NASPRO objects modules and probably a demo app).

About NASPRO
NASPRO, recursive acronym for "NASPRO Architecture for Sound PROcessing", will be a free, powerful, reusable, modular, real-time capable, thread-safe, scalable, standard-agnostic, cross-platform framework for digital signal processing, especially focused on sound processing.

Its main aim is to give audio application developers a full-featured, yet scalable, high-performance and integrated tool to make use of virtually any external sound processing component (including, but not limited to, LADSPA/DSSI, LV2, VST, AudioUnits and DirectX plugins) via a single, fully transparent and platform-independent API.

So, an application using NASPRO will be capable of running simultaneously and exchange data among sound processing components which would be normally incompatible, without even having knowledge of what kind they actually are.

And this is just the tip of the iceberg!