LADI Session Handler
Go to file
graciasfidel c787d3e78f Update translations menu entries to "New Application..." 2010-12-26 20:29:24 +02:00
a2jmidid@60f75d97e8 Update a2jmidid submodule 2010-08-28 04:39:11 +03:00
alsapid alsapid: hide the init function. Fixes #122 2010-12-01 02:56:00 +02:00
art Move the desktop file to the gui folder 2010-08-20 14:43:09 +01:00
common gladish: credit translators in the about dialog 2010-12-22 17:00:01 +02:00
daemon ladishd: make vgraph filtering in interlink_client() actually work 2010-12-25 18:17:19 +02:00
dbus gladish: Don't log dbus error when studio is not loaded on gladish start 2010-12-23 02:36:58 +02:00
doc doc: improve virtualizer diagram 2010-04-07 18:10:06 +03:00
example-apps Basic code to enable LADISH level 1 support to an event driven Qt (3/4) application. 2010-01-09 00:59:08 +02:00
flowcanvas@05fa427cee Update flowcanvas submodule 2010-09-03 01:11:27 +03:00
gui gladish: rename "Run..." menu entries to "New Application..." 2010-12-25 05:25:48 +02:00
jack2@8bf2cd1413 update the jack2 submodule 2010-09-24 00:55:40 +03:00
laditools@f4d4a23d60 Update jack2 and laditools submodules 2010-07-25 03:24:36 +03:00
lash_compat pylash. Fixes #112 2010-10-24 06:01:13 +03:00
lib daemon: Router templates 2010-09-05 03:06:15 +03:00
po Update translations menu entries to "New Application..." 2010-12-26 20:29:24 +02:00
proxies gladish: add menu items for reactivating jackdbus and a2jmidid. Fixes #132 2010-12-25 05:12:19 +02:00
.gitignore Update gitignore (sometimes compiled *.po files may appear not in build dir) 2010-12-22 19:18:39 +05:00
.gitmodules a2jmidid and jack2 submodules 2009-12-29 07:02:55 +02:00
AUTHORS Add falktx to authors 2010-12-18 20:51:55 +02:00
COPYING Initial checkin 2005-09-13 05:22:59 +00:00
Doxyfile doxygenize app_supervisor.h 2010-05-08 17:54:24 +03:00
INSTALL jmcore - JACK multicore (snake) 2010-04-11 12:25:30 +03:00
NEWS Update NEWS 2009-12-29 09:01:46 +02:00
README Fix some typos in README 2009-09-03 20:05:25 +03:00
assert.h waf: fix the include path workaround 2010-11-14 19:27:56 +02:00
common.h min and max macros 2009-12-12 17:10:38 +02:00
conf.c confd: emit "changed" signal when value is initially set 2010-09-23 01:57:35 +03:00
dbus_constants.h ladishd: Basic recent projects functionality 2010-10-09 16:53:03 +03:00
jmcore.c jmcore: Don't rely on jack unique name generation 2010-09-05 14:26:11 +03:00
ladish_control ladish_control: Add project load/unload/save commands 2010-09-05 22:25:59 +03:00
log.h rename log macros 2009-09-20 18:23:42 +03:00
updatepot Fix updatepot script 2010-12-21 04:38:29 +05:00
waf waf: switch to 1.6.1 2010-11-14 19:20:29 +02:00
wscript gladish: add menu items for reactivating jackdbus and a2jmidid. Fixes #132 2010-12-25 05:12:19 +02:00


  LADI Session Handler 

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

ladish has GUI frontend, gladish, based on lpatchage (LADI Patchage)
and the ladish_control command line app for headless operation. LADI
Tools is set of apps that interface with ladish, JACK server and

ladish requires D-Bus and JACK compiled with D-Bus support.

LADI Session Handler is rewrite of LASH.

Project goals:
 * Save and restore sets of JACK (audio and MIDI) enabled
 * Provide JACK clients with virtual hardware ports, so projects can
   be transfered (or backups restored) between computers running
   different hardware and backups. 
 * Don't require session handling library to be used. There is no need
   of such library for restoring connections between JACK clients.
 * Flow canvas based GUI. Positions of elements on the canvas are
 * Allow clients to use external storage to save their state. This
   includes storing internal state to non-filesystem place like memory
   of a hardware synth. This also includes storing client internal
   state (client project data) in a way that is not directly bound to
   ladish project. 
 * Import/export operations, as opposed to save/load. Save/load
   operate in current system and may cause saving data outside of
   project itself (external storage). Import/export uses/produces
   "tarball" suitable for transferring session data over network to
   other computer or storing it in a backup archive.
 * Hierarchical or tag-based organization of projects.
 * List of JACK applications. Applications are always started through
   ladish to have the restored runtime environment closer to one existed
   before project save.
 * Distributed studio - network connected computers. Netjack
   configuration is part of the studio and thus is saved/restored.
 * Collaborate with the X11 window manager so window properties like
   window position, virtual desktop and screen (multimonitor) are