1 Sep
2009
1 Sep
'09
8:04 a.m.
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.
--
Nedko Arnaudov <GnuPG KeyID: DE1716B0>
1 Sep
1 Sep
9:37 a.m.
Hello Nedko!
I've just got ladish and I'm installing it. I've looked into the
requirements. I see there's a lot of GUI and GUI-related, which seems to be
required. My question: Could you consider making as much as possible of the
GUI-stuff optional. I don't have and I don't need any GUI, so I need to
install quite a bit. In any case, the daemon itself doesn't require it, so
does the minimum user tool (ladi_control).
Kindest regards
Julien
--------
Music was my first love and it will be my last (John Miles)
======== FIND MY WEB-PROJECT AT: ========
http://ltsb.sourceforge.net
the Linux TextBased Studio guide
======= AND MY PERSONAL PAGES AT: =======
http://www.juliencoder.de
9:48 a.m.
Julien Claassen <julien(a)c-lab.de> writes:
Hello Nedko!
I've just got ladish and I'm installing it. I've looked into the
requirements. I see there's a lot of GUI and GUI-related, which seems
to be required. My question: Could you consider making as much as
possible of the GUI-stuff optional. I don't have and I don't need any
GUI, so I need to install quite a bit. In any case, the daemon itself
doesn't require it, so does the minimum user tool (ladi_control).
Making GUI stuff optional is perfectly possible and I like the idea. Do
you want to make a patch (or git commit somewhere) for this?
the command-line tool is called ladish_control not ladi_control
--
Nedko Arnaudov <GnuPG KeyID: DE1716B0>
9:55 a.m.
Oops, sorry about the ladi_control.
Well I think I can't do the patch. I can have a look, but this will take
time and energy, I'm not much into configurations and I've never seen the waf
system. I gather it's python based.
Kindest regards
Julien
--------
Music was my first love and it will be my last (John Miles)
======== FIND MY WEB-PROJECT AT: ========
http://ltsb.sourceforge.net
the Linux TextBased Studio guide
======= AND MY PERSONAL PAGES AT: =======
http://www.juliencoder.de
9:53 a.m.
Hello Nedko!
Now I've come up against a wall, which I don't want to climb.
It's all to do with GUI-toolkits and their relatives. Especially flowcanvas.
I dearly hope and plea for the feature, to optionalise the GUI-parts.
Flowcanvas seems to require something ese, which is tedious. Because now I
could go on installing ad nauseam, without getting anywhere in a short while.
Well you might say, that I'm a special case, being blind, having no graphic.
But I think this might hit other people as well. People with other
main-GUI-toolkits or other commandline friends, and there are some.
I'd be glad to know, if you're so far along on your way, that you seperated
the GUI parts from the real thing.
Kindest regards
Julien
--------
Music was my first love and it will be my last (John Miles)
======== FIND MY WEB-PROJECT AT: ========
http://ltsb.sourceforge.net
the Linux TextBased Studio guide
======= AND MY PERSONAL PAGES AT: =======
http://www.juliencoder.de
10:06 a.m.
Julien Claassen <julien(a)c-lab.de> writes:
Hello Nedko!
Now I've come up against a wall, which I don't want to climb.
It's all to do with GUI-toolkits and their relatives. Especially
flowcanvas. I dearly hope and plea for the feature, to optionalise the
GUI-parts. Flowcanvas seems to require something ese, which is
tedious. Because now I could go on installing ad nauseam, without
getting anywhere in a short while.
Well you might say, that I'm a special case, being blind, having no
graphic. But I think this might hit other people as well. People with
other main-GUI-toolkits or other commandline friends, and there are
some.
I'd be glad to know, if you're so far along on your way, that you
seperated the GUI parts from the real thing.
Kindest regards
Julien
GUI (gladish) and the real thing (ladishd) are really separated. Later
today I'll try to modify the waf build script to support GUI-less
build. Here is a ticket for you: http://ladish.org/ticket/10
--
Nedko Arnaudov <GnuPG KeyID: DE1716B0>
10:08 a.m.
Thans Nedko! This is really kind of you! I appreciate it higly, be sure of it!
Friendly regards
Julien
--------
Music was my first love and it will be my last (John Miles)
======== FIND MY WEB-PROJECT AT: ========
http://ltsb.sourceforge.net
the Linux TextBased Studio guide
======= AND MY PERSONAL PAGES AT: =======
http://www.juliencoder.de
12:33 p.m.
New subject: [LAD] [ANN] LADI Session Handler - Preview 1
Nedko Arnaudov wrote:
Julien Claassen <julien(a)c-lab.de> writes:
cool. nedko, not intending to rehash the dbus carnage of yore, but:
for a headless system without a user logged in via some graphical
desktop, what is needed to be able to run LADI?
i for one would be interested in having a rudimentary start script that
gets all the $FOOkits and dbus-$GIZMOs in place so that LADIsh can work.
even if few people will use it on headless systems, it would be very
instructive and show how different system services work together.
best,
jörn
Hello Nedko!
Now I've come up against a wall, which I don't want to climb.
It's all to do with GUI-toolkits and their relatives. Especially
flowcanvas. I dearly hope and plea for the feature, to optionalise the
GUI-parts. Flowcanvas seems to require something ese, which is
tedious. Because now I could go on installing ad nauseam, without
getting anywhere in a short while.
Well you might say, that I'm a special case, being blind, having no
graphic. But I think this might hit other people as well. People with
other main-GUI-toolkits or other commandline friends, and there are
some.
I'd be glad to know, if you're so far along on your way, that you
seperated the GUI parts from the real thing.
Kindest regards
Julien
GUI (gladish) and the real thing (ladishd) are really separated. Later
today I'll try to modify the waf build script to support GUI-less
build. Here is a ticket for you: http://ladish.org/ticket/10
12:49 p.m.
New subject: [LAD] [ANN] LADI Session Handler - Preview 1
Jörn Nettingsmeier <nettings(a)folkwang-hochschule.de> writes:
cool. nedko, not intending to rehash the dbus carnage
of yore, but:
for a headless system without a user logged in via some graphical
desktop, what is needed to be able to run LADI?
The DBUS_SESSION_BUS_ADDRESS must contain the address of the session bus
daemon. Check the man page of "dbus-launch". I launch the session bus
daemon from by ~/.xinitrc script (I don't use xdm/kdm/gdm) like this:
eval `dbus-launch --sh-syntax --exit-with-session`
The man page has more documentation. Countrary to popular beleif, D-Bus
is not bound to desktop, in the GUI sense. It does not even make sense
for the system bus where HAL and other system stuff lurks.
i for one would be interested in having a rudimentary
start script that
gets all the $FOOkits and dbus-$GIZMOs in place so that LADIsh can work.
even if few people will use it on headless systems, it would be very
instructive and show how different system services work together.
You need to obtain the value for the session bus address on each tty
(local or ssh ones for headless operation). If you came with steps for
setting such envirnment, please share them - I want them on ladish.org
wiki.
--
Nedko Arnaudov <GnuPG KeyID: DE1716B0>
5:56 p.m.
New subject: [LAD] [ANN] LADI Session Handler - Preview 1
Nedko Arnaudov <nedko(a)arnaudov.name> writes:
Julien Claassen <julien(a)c-lab.de> writes:
The fix is in the git repository. To get the sources with git:
git clone -o nedko http://nedko.arnaudov.name/git/ladish.git
This will create ladish/ subdirectory where sources will be.
--
Nedko Arnaudov <GnuPG KeyID: DE1716B0>
Hello Nedko!
Now I've come up against a wall, which I don't want to climb.
It's all to do with GUI-toolkits and their relatives. Especially
flowcanvas. I dearly hope and plea for the feature, to optionalise the
GUI-parts. Flowcanvas seems to require something ese, which is
tedious. Because now I could go on installing ad nauseam, without
getting anywhere in a short while.
Well you might say, that I'm a special case, being blind, having no
graphic. But I think this might hit other people as well. People with
other main-GUI-toolkits or other commandline friends, and there are
some.
I'd be glad to know, if you're so far along on your way, that you
seperated the GUI parts from the real thing.
Kindest regards
Julien
GUI (gladish) and the real thing (ladishd) are really separated. Later
today I'll try to modify the waf build script to support GUI-less
build. Here is a ticket for you: http://ladish.org/ticket/10
7:58 p.m.
New subject: [LAD] [ANN] LADI Session Handler - Preview 1
Thanks Nedko. That's aweful. I'll get it and see, where I get.
Kindest regards
Julien
--------
Music was my first love and it will be my last (John Miles)
======== FIND MY WEB-PROJECT AT: ========
http://ltsb.sourceforge.net
the Linux TextBased Studio guide
======= AND MY PERSONAL PAGES AT: =======
http://www.juliencoder.de
5378
days inactive
5378
days old
linux-audio-user@lists.linuxaudio.org
10 comments
3 participants
participants (3)
-
Julien Claassen -
Jörn Nettingsmeier -
Nedko Arnaudov