LADI Session Handler https://ladish.org/
Go to file
Nedko Arnaudov 04086f1fef doxygenize app_supervisor.h 2010-05-08 17:54:24 +03:00
a2jmidid@cfe15af111 a2jmidid and jack2 submodules 2009-12-29 07:02:55 +02:00
art art: web logo 2010-04-27 10:52:12 +03:00
common remove the obsolete "safety" memory functions 2010-04-04 21:45:53 +03:00
daemon doxygenize app_supervisor.h 2010-05-08 17:54:24 +03:00
dbus remove the obsolete "safety" memory functions 2010-04-04 21:45:53 +03: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@d4e5ba7a5c Update flowcanvas submodule to latest svn version 2010-02-26 07:39:46 +02:00
gui gui: remove room views when ladishd crash is detected. Fix for #84 2010-04-25 01:50:32 +03:00
jack2@4c48a9e116 update the jack2 submodule to include the no-self-connect fix 2010-04-24 16:10:52 +03:00
laditools@d70fc9fa25 update the laditools submodule 2010-04-17 15:35:49 +03:00
lash_compat Eradicate the compat liblash implementation 2009-09-04 02:21:48 +03:00
lib daemon: fill the Basic room template with ports and copy them when creating studio rooms 2010-03-24 01:11:53 +02:00
proxies daemon: initial implementation of user notification 2010-04-18 01:49:36 +03:00
.gitignore Basic wscript 2009-07-12 15:11:14 +03:00
.gitmodules a2jmidid and jack2 submodules 2009-12-29 07:02:55 +02:00
AUTHORS New logo and icons by Lapo Calamandrei 2009-09-05 15:53:28 +03: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 fix ASSERT to evaluate the expression only once 2010-05-04 23:20:31 +03:00
catdup.c implement catdup4() 2009-12-12 15:10:06 +02:00
catdup.h implement catdup4() 2009-12-12 15:10:06 +02:00
common.h min and max macros 2009-12-12 17:10:38 +02:00
dbus_constants.h jmcore - JACK multicore (snake) 2010-04-11 12:25:30 +03:00
jmcore.c jmcore: one JACK client per pair 2010-04-11 13:36:26 +03:00
ladish_control fix names of some studio room and room template methods 2010-03-21 23:18:04 +02:00
log.h rename log macros 2009-09-20 18:23:42 +03:00
waf Basic wscript 2009-07-12 15:11:14 +03:00
wscript configure option to enable doxygen docs generation 2010-05-08 16:09:40 +03:00

README

========================
  LADI Session Handler 
========================

http://ladish.org/

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.

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
a2jmidid

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
   applications.
 * 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
   saved/restored.
 * 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
   saved/restored.