LADI Session Handler
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Go to file
Max Audron 1e69f48936 add meson build files
build common, cdbus, alsapid, and proxies as static libraries.
daemon aka ladishd links to them at build time.
3 years ago
a2jmidid@60f75d97e8 Update a2jmidid submodule 13 years ago
alsapid add meson build files 3 years ago
art Move the desktop file to the gui folder 13 years ago
cdbus add meson build files 3 years ago
common add meson build files 3 years ago
daemon add meson build files 3 years ago
doc Minor formatting fix in coding_style.txt 11 years ago
example-apps Basic code to enable LADISH level 1 support to an event driven Qt (3/4) application. 14 years ago
flowcanvas@05fa427cee Update flowcanvas submodule 13 years ago
gui gladish: Fix load project dialog 3 years ago
jack2@a4eac4f832 update jack2 submodule to 1.9.8 ladi branch 12 years ago
laditools@f4d4a23d60 Update jack2 and laditools submodules 14 years ago
lash_compat Fix unused-parameter warnings in plain C code 11 years ago
lib daemon: Router templates 13 years ago
po update translations, new string 12 years ago
proxies add meson build files 3 years ago
.gitignore Update gitignore (sometimes compiled *.po files may appear not in build dir) 13 years ago
.gitmodules a2jmidid and jack2 submodules 14 years ago
AUTHORS Update Nikita Zlobin e-mail 13 years ago
COPYING clarify the dual-licensing in the dbus/ tree 13 years ago
Doxyfile doxygenize app_supervisor.h 14 years ago
INSTALL Update INSTALL 11 years ago
NEWS Update NEWS for version 1 12 years ago
README Fix some typos in README 14 years ago
afl21.txt clarify the dual-licensing in the dbus/ tree 13 years ago
assert.h waf: fix the include path workaround 13 years ago
common.h Fix unused-parameter warnings in plain C code 11 years ago
conf.c Fix unused-parameter warnings in plain C code 11 years ago
dbus_constants.h setting for jack conf tool 12 years ago
gpl2.txt clarify the dual-licensing in the dbus/ tree 13 years ago
jmcore.c Fix unused-parameter warnings in plain C code 11 years ago
ladish_control ladish_control: py3 compatibility 4 years ago
log.h Improve logging 11 years ago add meson build files 3 years ago
string_constants.c use strings for app levels 13 years ago
syncpo Fix syncpo 13 years ago Add a script to generate an unpacked instance of the waf all-in-one blob. 12 years ago
waf waf: switch to 1.6.1 13 years ago
wscript Fix implicit fallthrough warning with gcc 9.3.0 4 years ago


  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