LADI Session Handler - Preview 3
(Nedko Arnaudov`s blog)

After a year of development ladish-0.3 is out! The main feature that
this release implements is the hardware port virtualization. Studios
that manage JACK and the overall infrastructure of the setup now can
contain the so called rooms. The rooms provide a predefined set of
ports that are linked to the studio through a virtual JACK multicore
(aka snake). The “contents” of the rooms are the projects. As with
studios, projects manage apps and connections between them. However
projects are not bound to particular audio/midi hardware and JACK
setup because project apps are connected to the room-studio link ports
that are fixed. On the studio side, these room-studio link ports can
be connected to the actual hardware ports, to ports of apps that are
part of the studio or even to room-studio link ports of different
rooms. Yes, you can have more than one room in the studio! It is quite
possible that room usage will fall into one of these two categories:

Central and side rooms are interconnected in the studio. The studio
setup (JACK settings, connections between hardware and rooms) is
supposed to be almost static.

The new user visible features include:

ladish now can install the python bindings for liblash that are used
by some apps (jack_mixer, zynjacku). The ladish implementation of
liblash is still not functional, lashified apps will be told that lash
server is not available. The jack-session support is also not
implemented yet.

In the past year lot of people helped the project, but some of them
played a major role:

The tarballs are available at the usual location:

There are two tarballs. ladish-0.3-with-deps.tar.bz2 is 3.6 MiB and
bundles the major dependencies that are usually needed for running

All of these are either development (git/svn) versions or release
versions that are patched to work better with ladish. The last released
versions of these dependencies are expected work with ladish. The most
serious “incompatibility” is that the jack2 mainline is missing the
no-self-connect changeset. This changeset adds option to jack that
allows prevention of jack apps self connection to “hardware” ports
(usually system:playback_N). As such self-connecting apps are not rare
at all, without it, the studio/room separation is not-effective and
the workflow can get very confusing.

If you are compiling the software by yourself, then you should
probably use this “fat” tarball.

The ladish-0.3.tar.bz2 tarball is 569 KiB and contains only ladish
itself. It is expected to be used mainly by packagers.

Known issues
There is one known jack2 bug that sometimes hits the ladish
workflows. If two instances of same app are started in parallel and
these apps don’t request unique jack client name but instead rely on
jack feature that autorenames clients, apps usually fail to start. The
bug has a ticket recorded in the jack bugtracker:

More info on the ladish project

LADI Session Handler or simply ladish is a session management system
for JACK applications on GNU/Linux. Its aim is to allow you to have
many different audio programs running at once, to save their setup,
close them down and then easily reload the setup at some other
time. ladish doesn’t deal with any kind of audio or MIDI data itself;
it just runs programs, deals with saving/loading (arbitrary) data and
connects JACK ports together. It can also be used to move entire
sessions between computers, or post sessions on the Internet for
download. Check the project goals for more info.

Project goals:

Created: Sun Jan 09 21:46:48 +0200 2011

Valid XHTML 1.0 Strict Valid CSS!