This release include a large number of fixes to usability bugs and it introduce a first implementation of the pd externals source level compatibility kit.
The binary has been tested on Debian 5, Fedora, Ubuntu and Ubuntu Studio, Mandriva Spring 2010; check the installation instructions for specific caveats for some of the distributions<
With respect to the work presented to LAC 2009, the 0.6 beta include these major functionalities:
Note: since the alpha 0.5 snapshots never worked, i merge the announce of the 0.5 beta 1 with the previous text on the alpha. If you read already the announce on the alpha, read again for more details. 0.5 beta 1 solve the linking problem that prevented jMax to works on a file system location different from the build location.
I am pleased the announce the release of jMax Phoenix version 0.5 beta 1, that include a couple of nice step forward for the jMax Phoenix project.
First of all, to simplify versions and tracking on multiple platform, we added a release naming to the revision numbering we used up to now. A release will go thru multiple revision (build) number, and progress, like for other projects, thru a number of alpha, beta, rc, and GA versions.
The first jMax release is called 0.5, like in one half, to say it is still half baked :→. It is a beta now, because feature development is almost frozen (some plumbing work related to bug fixing is still going on). You'll find the download files in the usual sourceforge project site, under the 0.5 Beta 1 folder.
First step, support for LADSPA plugins: LADSPA plugins present on your platform are by default automatically loaded and transparently imported as jMax Phoenix objects. Check this sections for details on how LADSPA plugins are handled.
In order to work with the huge number of objects availables thanks to LADSPA integration (more than 600 with a vanilla Ubuntu Studio 9.04 installation), we added an object browser; the new user interface component is not yet documented, but is very intuitive to use: present the available objects in a list, where you drag a row to an open patch editor to instantiate the object. A search box allows to select objects by content, and a couple of popdown menus allows to select on the object category, package or author. By the way, the patch editor accept now also dragging of text from other application. Such a text will interpreted as a single object description, and the corresponding object will be created.
Please note that an other new functionality is becoming to surface: a
View menu that allows to select which part
of the user interface are shown. Unfortunately, you'll got the menu only before opening a patch editor, and than it will disappear; the problem need some changing in the way menus are handled, so it require a few days of work in order to be fixed.
Second step: platforms: the 0.5 beta 1 run on Mac OS X Leopard, Linux 32 and Linux 64 bit and Windows, based on the use of cygwin. Snapshots for Linux 64 bits and Mac OS X have been uploaded. The 32 bit Linux and the Windows snapshot will be upload next week. Please notes that snapshot for different platforms may have different revision number; that is normal.
The Mac OS X version is still kind of rough: it is lightely integrated with the Max OS X environment, and it have to be runned from the command line (follows the Linux instructions). More integration will slowly added in the next weeks. jMax should run on Leopard and Snow Leopard, and require Java 6 configured as default virtual machine. This also means that it will never run on Tiger, sorry about that, but no Java 6 is available for Tiger.
LADSPA plugins can be used also on Mac OS X.
Please note: this version is configured to use the default portaudio input output, that should be a reasonable default in each platform. This release use portmidi for midi, but the midi device is not yet configured in the configuration file. You can configure it following the documentation, or wait for the next snapshot.
A final warning: this is a very very first release of both LADSPA integration and Mac OS X porting: it is a snapshot, it is probably unstable, and probably have problems that we have not yet found. We are looking for testers !!!!! Please, contact us if you try to use jMax Phoenix and if does not works as expected, and also if it does works as expected.
This revision complete the migration from tcl to XML for configuration, including I/O configuration and user interfaces. The new I/O configuration simplify the configuration model, providing a simple space of named configuration to select from.
The wiki documentation migrated to the XML model and is being completed with complete documentation of the basic configuration (preferences and so on), i/o configuration, and later packages and user interfaces.
This snapshot is the baseline for the first planned public release of jMax Phoenix and for the Mac OS X (and hopefully Windows) port. No major functional evolution are planned before the Mac OS X port.
This snapshot is the first to be compiled with optimisations. The speed improvement should be around 6 times, from some benchmark i run.
This snapshot was possible thanks to a fix to a bug that happened only with optimisation.
This snapshot have the following important features:
1) Support portaudio. jMax support the default portaudio device at startup, but can be configured to use any audio device seen by portaudio.
2) Support portmidi. jMax can be configured to use all the MIDI connections seens by portmidi. THIS FEATURE IS UNTESTED. Beta tester are welcome, for the moment i do not have a MIDI setup that i can use.
3) Support different vector sizes (buffer size). jMax tradionally supported only 64 sample buffer size, now it can go up to 2048. See the file config/core.xml for how to configure this parameter. Vector size cannot be changed after startup.
I'll soon add some info on the wiki on how to configure the portaudio and portmidi device.
If you do not know, portaudio and portmidi are libraries that transparently access the underlying audio system, allowing to write portable code that run on ALSA, Jack, Core Audio on Mac OS X, various audio systems on Windows etc.
Adding portaudio was a cheap way to support ALSA (and jack if you have the right portaudio library version), and to prepare the porting of jMax to other platforms.
Fixed some user interface coherency issue. Added documentation (on the project wiki).
First public snapshot.
Printing do not yet works in jMax Phoenix.