In the future I will test ladish. While I don't like jack_snapshot and lash very much, I do like qtractor a lot.
I guess a good idea would be not to use a mess of Linux audio apps, but one application that stores audio and MIDI connections and is able to include virtual synth and fx and is a sequencer and hd recorder, qtractor does, qtractor is. Anyway, if I e.g. like to use Rosegarden because of some features and QSampler because I need a GIG, something better than jack_snapshot and lash is welcome :). I'm interested in ladish and glad that somebody did think about the features ladish will cover. Hopefully I'll be able to use it, while jack_snapshot is easy to use, lash is a PITA. I'll be very impressed if this should be fine: "* Collaborate with the X11 window manager so window properties like window position, virtual desktop and screen (multimonitor) are saved/restored." Thank you, a good idea to save this too. I'll give ladish a chance. Cheers, Ralf Nedko Arnaudov wrote: > The first milestone is reached and result is a tarball that brave souls > may want to download and try. It contains implementation of JACK > multiconfig functionality. JACK server settings can be saved as part of a > studio. Then, loading studio will cause JACK settings stored as part of > the studio to be restored. > > Build will produce three operational components: > * ladishd - The daemon, a D-Bus service > * gladish - GTK GUI interface > * ladish_control - Command-line interface > > In the tarball you will also find bundled suitable (latest and gratest) > flowcanvas and LADI Tools. > > Download: > http://ladish.org/download/ladish-0.1.tar.bz2 > http://ladish.org/download/ladish-0.1.tar.bz2.sig > > Homepage: http://ladish.org/ > Roadmap: http://ladish.org/roadmap > > --------------------------------------------------------------------- > 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 its 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 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. _______________________________________________ Linux-audio-dev mailing list [email protected] http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev
