Skip to content
LADI Session Handler
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
a2jmidid @ 60f75d9 Update a2jmidid submodule Aug 28, 2010
alsapid fix alsapid build on non-linux systems. #181 Oct 10, 2011
art Move the desktop file to the gui folder Aug 20, 2010
cdbus Fix unused-parameter warnings in plain C code Dec 2, 2012
common
daemon minor coding style fix Feb 10, 2013
doc
example-apps Basic code to enable LADISH level 1 support to an event driven Qt (3/… Jan 8, 2010
flowcanvas @ 05fa427 Update flowcanvas submodule Sep 2, 2010
gui
jack2 @ a4eac4f update jack2 submodule to 1.9.8 ladi branch Dec 19, 2011
laditools @ f4d4a23 Update jack2 and laditools submodules Jul 25, 2010
lash_compat Fix unused-parameter warnings in plain C code Dec 2, 2012
lib
po
proxies
.gitignore
.gitmodules a2jmidid and jack2 submodules Dec 29, 2009
AUTHORS
COPYING clarify the dual-licensing in the dbus/ tree Jan 29, 2011
Doxyfile doxygenize app_supervisor.h May 8, 2010
INSTALL
NEWS
README Fix some typos in README Sep 3, 2009
afl21.txt clarify the dual-licensing in the dbus/ tree Jan 29, 2011
assert.h
common.h
conf.c
dbus_constants.h setting for jack conf tool Dec 18, 2011
gpl2.txt clarify the dual-licensing in the dbus/ tree Jan 29, 2011
jmcore.c Fix unused-parameter warnings in plain C code Dec 2, 2012
ladish_control fix ladish_control new app commands. #183 Oct 2, 2011
log.h Improve logging Dec 2, 2012
string_constants.c use strings for app levels Jul 28, 2011
syncpo Fix syncpo Dec 28, 2010
unpack_waf.sh
waf waf: switch to 1.6.1 Nov 14, 2010
wscript

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.
You can’t perform that action at this time.