LADI Session Handler
Go to file
Alessio Treglia 466d958b82 Refresh against the laditools' first stable release.
ladiconf -> ladi-control-center
2012-03-23 19:19:55 +01:00
a2jmidid@60f75d97e8 Update a2jmidid submodule 2010-08-28 04:39:11 +03:00
alsapid fix alsapid build on non-linux systems. #181 2011-10-10 04:41:16 +03:00
art Move the desktop file to the gui folder 2010-08-20 14:43:09 +01:00
cdbus cdbus: macros for defining interfaces with default handler 2011-11-09 02:59:26 +02:00
common fix compiler warning 2011-10-11 01:24:53 +03:00
daemon cdbus: macros for defining interfaces with default handler 2011-11-09 02:59:26 +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 disable lash apps in studios 2011-12-19 01:33:53 +02:00
jack2@a4eac4f832 update jack2 submodule to 1.9.8 ladi branch 2011-12-19 18:05:10 +02:00
laditools@f4d4a23d60 Update jack2 and laditools submodules 2010-07-25 03:24:36 +03:00
lash_compat Fix small misspellings. 2012-01-13 21:04:36 +01:00
lib daemon: Router templates 2010-09-05 03:06:15 +03:00
po update translations, new string 2011-10-13 01:13:21 +04:00
proxies dbus/ -> cdbus/ 2011-11-09 02:45:13 +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 Update Nikita Zlobin e-mail 2011-05-02 18:36:42 +06:00
COPYING clarify the dual-licensing in the dbus/ tree 2011-01-29 14:24:07 +02: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 for version 1 2011-12-19 00:54:16 +02:00
README Fix some typos in README 2009-09-03 20:05:25 +03:00
afl21.txt clarify the dual-licensing in the dbus/ tree 2011-01-29 14:24:07 +02:00
assert.h waf: fix the include path workaround 2010-11-14 19:27:56 +02:00
common.h liblash: export as public only LASH API symbols 2011-09-10 04:11:50 +03:00
conf.c cdbus: macros for defining interfaces with default handler 2011-11-09 02:59:26 +02:00
dbus_constants.h Refresh against the laditools' first stable release. 2012-03-23 19:19:55 +01:00
gpl2.txt clarify the dual-licensing in the dbus/ tree 2011-01-29 14:24:07 +02:00
jmcore.c cdbus: macros for defining interfaces with default handler 2011-11-09 02:59:26 +02:00
ladish_control fix ladish_control new app commands. #183 2011-10-02 03:37:47 +03:00
log.h rename log macros 2009-09-20 18:23:42 +03:00
string_constants.c use strings for app levels 2011-07-28 15:15:47 +03:00
syncpo Fix syncpo 2010-12-28 11:43:39 +05:00 Add a script to generate an unpacked instance of the waf all-in-one blob. 2012-01-09 18:50:33 +01:00
waf waf: switch to 1.6.1 2010-11-14 19:20:29 +02:00
wscript version 1 2011-12-19 00:36:27 +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