http://jamoma.org/ got a facelift this week, thanks to Julien Rabin. Details are @ http://groupware.bek.no/groups/jamoma/weblog/5dce3/New_Jamoma_web_site_on_rails.html . Nice work, Julien!

This past week saw the introduction of multichannel signal connections in PureData.

This is thanks to a new implementation of Jamoma Multicore for Pd. Special thanks go to IOHannes Zmoelnig for help with figuring out some of the Pd inner-workings to do this!

Traditionally, January seems to be one of the most active months for Jamoma development. This year was no exception. Here are some highlights:

• Jamoma Foundation project extended to allow compiling for the iPhone/iPod/iPad.
• Jamoma DSP expanded through the addition of a new FFT Lib extension for spectral processing, based on the Ooura library
• Jamoma DSP’s Filter Lib optimization and clean-up work
• Jamoma Multicore was largely re-written to address limitations of the internal architecture as it had previously existed.
• Ruby language binding fleshed out and made to work doing live-coding DSP with Jamoma Multicore.
• Jamoma Modular saw a continuation of work on the NodeLib (for managing tree structures of modules, parameters, etc.). The Virage DeviceManager (a daemon that loads plug-ins) has now been integrated through a new Max external called jcom.deviceManager. This allows communication with Minuit, OSC, CopperLan and potentially more protocols by building dedicated plugins.
• Many other things have also been going. Not all of them can be listed, but some include: A UserLib module wrapping ol.autotalent~ (autotune for MSP); jmod.cueManager/jcom.cuemanager improvements (cue moving, autofollow and comments features); website improvement; and new modules for motion capture retrieval and processing, including selecting models for marker placement and biomechanics, and GDIF implementation.

There are always lots of things going on with Jamoma development, thanks to the growing community of people contributing. These developments are available through the source code repository – these should also make it into future installers and releases. Here are a few highlights from the last month:

• A New Window-Function Library has been introduced as a DSP extension
• Expansion of the Ruby language bindings, including a Ruby on Rails example app using the Window Function Lib
• A lot of contributors spent the last month working on some Jamoma-related publications for upcoming conferences and journals
• The jcom.vimic~ external was made public in the DSP project
• Bug fixes and improvements for the upcoming Jamoma 0.5.1 release
• Continued work on the Jamoma NodeLib, which provides an OSC addressing system for objects in the Jamoma Platform.

As noted by Trond Lossius , papers from past Sound and Music Computing Conferences are now available online. A paper on which I was a co-author (from this year’s conference in Porto) can be found @ http://smcnetwork.org/node/1233 .

Enjoy!

I started working on Jamoma 0.5 more than 2 years ago. Most of the Jamoma developers began working on Jamoma 0.5 over 18 months ago as Max 5 was released.

Jamoma 0.5 was a major effort. Originally it was envisioned as a port from Max 4 to Max 5. However, we did a lot more than that, and significantly overhauled major portions of Jamoma to dramatically improve performance, stability (particularly on Windows), and ease of use. We’ve also improved the documentation, distribution, and organization of Jamoma.

Here are some resources to get started with Jamoma 0.5 (codename: Château de Salette):

• A good place to start is the download page
• Jamoma 0.5 Tutorials
• Guide to porting modules from Jamoma version 0.4
• The Change Log lists major changes since version 0.4.
• You can http://redmine.jamoma.org/account/register on the Jamoma Development page to submit feature requests and bug reports.
• If you are a Tap.Tools user, you may want to download a version of Tap.Tools compatible with Jamoma 0.5
• The main site has all other things Jamoma, including publications and a list of supporters.
• And of course, don’t forget:
  

A lot of people and organizations have put a lot of time, energy, and financial resources into Jamoma 0.5. For full details, check the acknowledgments page at jamoma.org. I’m very very grateful for the incredible team of people contributing to this project! It’s not a closed group either, so if you have something to contribute (especially with Windows programming experience ;-) please feel free to participate!