Hello everybody,

I had no time to write on this before: NASPRO is officially and definitely partecipating at GSoC 2008.

We had one slot assigned to us for a student to develop a data based file format to store parametrized FIR and/or IIR filters and make them work in NASPRO, which means a good opportunity to start showing the potential of the framework with supporting exotic ways of representing effects (non-algorithmic in this case) as well as test it and make it easier than ever to develop effects (non-algorithmic == you don't have to write code).

Hello,

We had a "little" problem with the database on our server: it was accidentally deleted and the latest backup was from late January.

So, since then, almost all content added (not a big amount luckily) has been lost forever.

I "took the chance" to tune a couple of things in the website, so it should be healtier than ever (for example you can add pictures to your profile).

Have fun!

P.S.: NASPRO will probably have 1 slot for GSoC, more on this after April, 21st. ;-)

Great great news!

Yesterday night I introduced NASPRO to the Audacious guys on their IRC channel and talked about the opportunity of supporting their effects plugin API and writing a bridging plugin (NASPRO-to-Audacious) to open up their media player to the world of sound processing objects beyond LADSPA...

I decided to move the NASPRO-devel mailing list from Sourceforge.net to Freelists.org and to create a new mailing list (which I just set up): the NASPRO-news mailing list, a low traffic newsletter for those who want to stay informed about the progress of NASPRO.

Interested people: please, subscribe!

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

Well... even this last part has proven to be a lot harder than expected, but finally the code is almost completed. There are two little things missing: a bit of documentation on the latest part of the API and messages all around the code.

In the next days (hopefully tomor... ehm.. today ;-) I will update the code wrote in these holidays within all the missing stuff.

Tomorrow I will leave for my hometown and, as you know, there I have connection problems, so I don't know if I'll be capable of uploading code and be present in general.

I don't even know how much time I'll have to develop NASPRO, since I have university exams in January, and this time can be very precious to me to study.

Finally!

It took longer than expected but everything is there, tested, working and freezed for the first development release. The code might look a bit unpolished and messy in several points, but hey, this is the first release! The important thing for now is the overall structure and the fact that it works - all refinings, even structural, will come later.

Now the library misses only the module loading and filesystem interaction parts, which should be quite easy to do, compared to the huge amount of work (for one person working in spare time and such complex matters) already done.

Hi folks,

these days I'm concentrating on the organization and structure of the project to encourage possible contributors and interested people to get involved easily.

Currently I'm revamping the docs, explaining in detail (much more then before) the motivations behind every little decision taken till now; I also made some adjustments to the website and am trying to open the discussion around the project in general.