Ubuntu packages of ladish, laditools and jack2 (with jackd classic and jackdbus) can be found here.<br><br>Debian, Mandriva, ..., on their way... (!?)<br><br><a href="http://ladish.org/wiki/installing">http://ladish.org/wiki/installing</a><br>
<a href="http://ladish.org/wiki/installing_on_ubuntu">http://ladish.org/wiki/installing_on_ubuntu</a><br><br>\r<br><br><div class="gmail_quote">On Tue, Dec 29, 2009 at 9:22 AM, Nedko Arnaudov <span dir="ltr"><<a href="mailto:nedko@arnaudov.name">nedko@arnaudov.name</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">The second milestone is reached and result is a tarball that brave souls<br>
may want to download and try. It can start apps and restore their<br>
connections. Level 1 apps are supported.<br>
<br>
Beware that no apps have implemented level 1 yet. If non-level-1 app is<br>
started at level 1, it will probably quit on save, because the default<br>
signal handler for SIGUSR1 terminates the process.<br>
<br>
This preview also features a2jmidid support. Run the a2j script as an<br>
app in the studio.<br>
<br>
This is a beta quality software, use it with double caution.<br>
<br>
I would like to thank the early adopters and especially Frank Kober for<br>
their help with testing the git ladish code and for the valuable<br>
suggestions they gave.<br>
<br>
Build will produce three operational components:<br>
* ladishd - The daemon, a D-Bus service<br>
* gladish - GTK GUI interface<br>
* ladish_control - Command-line interface<br>
<br>
In the tarball you will also find bundled:<br>
* flowcanvas-0.6.0<br>
* LADI Tools (svn version)<br>
* a2jmidid-6 (contains the a2j script for use in ladish)<br>
* jack2 from the ladi branch<br>
<br>
The jack2 ladi branch contains fixes for two important issues:<br>
* Race that causes connection restore to fail sometimes during studio<br>
startup (<a href="http://ladish.org/ticket/28" target="_blank">http://ladish.org/ticket/28</a>)<br>
* A deadlock on studio start (<a href="http://ladish.org/ticket/35" target="_blank">http://ladish.org/ticket/35</a>)<br>
<br>
Hopefully, these fixes with be in the next jack2 release (1.9.5).<br>
<br>
The jack2 ladi branch also contains the no-self-connect changeset that<br>
adds new engine option, for disabling self connect of apps. Default<br>
value for this option is to allow self connections.<br>
<br>
Make sure to configure jack2 with --dbus (and maybe with --classic too).<br>
<br>
Download:<br>
<a href="http://ladish.org/download/ladish-0.2.tar.bz2" target="_blank">http://ladish.org/download/ladish-0.2.tar.bz2</a><br>
<a href="http://ladish.org/download/ladish-0.2.tar.bz2.sig" target="_blank">http://ladish.org/download/ladish-0.2.tar.bz2.sig</a><br>
<br>
Homepage: <a href="http://ladish.org/" target="_blank">http://ladish.org/</a><br>
Roadmap: <a href="http://ladish.org/roadmap" target="_blank">http://ladish.org/roadmap</a><br>
<br>
---------------------------------------------------------------------<br>
LADI Session Handler or simply ladish is a session management system<br>
for JACK applications on GNU/Linux. Its aim is to allow you to have<br>
many different audio programs running at once, to save their setup,<br>
close them down and then easily reload the setup at some other<br>
time. ladish doesn't deal with any kind of audio or MIDI data itself;<br>
it just runs programs, deals with saving/loading (arbitrary) data and<br>
connects JACK ports together. It can also be used to move entire<br>
sessions between computers, or post sessions on the Internet for<br>
download.<br>
<br>
Project goals:<br>
* Save and restore sets of JACK (audio and MIDI) enabled<br>
applications.<br>
* Provide JACK clients with virtual hardware ports, so projects can<br>
be transfered (or backups restored) between computers running<br>
different hardware and backups.<br>
* Don't require session handling library to be used. There is no need<br>
of such library for restoring connections between JACK clients.<br>
* Flow canvas based GUI. Positions of elements on the canvas are<br>
saved/restored.<br>
* Allow clients to use external storage to save its state. This<br>
includes storing internal state to non-filesystem place like memory<br>
of a hardware synth. This also includes storing client internal<br>
state (client project data) in a way that is not directly bound to<br>
ladish project.<br>
* Import/export operations, as opposed to save/load. Save/load<br>
operate in current system and may cause saving data outside of<br>
project itself (external storage). Import/export uses/produces<br>
"tarball" suitable for transferring session data over network to<br>
other computer or storing it in a backup archive.<br>
* Hierarchical or tag-based organization of projects.<br>
* List of JACK applications. Applications are always started through<br>
ladish to have restored runtime environment closer to one existed<br>
before project save.<br>
* Distributed studio - network connected computers. Netjack<br>
configuration is part of the studio and thus is saved/restored.<br>
* Collaborate with the X11 window manager so window properties like<br>
window position, virtual desktop and screen (multimonitor) are<br>
saved/restored.<br>
<font color="#888888"><br>
--<br>
Nedko Arnaudov <GnuPG KeyID: DE1716B0><br>
</font><br>_______________________________________________<br>
Jack-Devel mailing list<br>
<a href="mailto:Jack-Devel@lists.jackaudio.org">Jack-Devel@lists.jackaudio.org</a><br>
<a href="http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org" target="_blank">http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org</a><br>
<br></blockquote></div><br>