ladish news
(Nedko Arnaudov`s blog)

Last night I fixed some ladish-0.3 issues. You can now safely start L1 aware apps in terminal or through shell scripts that create intermediate processes between ladish and the real jack app. This fix also renders the Debian/Ubuntu default shell (dash) usable for L1 apps (launched without terminal). The other two issues that I fixed are related to the liblash emulation library and its python bindings (ladish can be built to provide them both). The one should make jack-rack buildable against ladish liblash. The other one is actually the addition of the python bindings, it is not good idea to use pylash from lash-0.6.x with liblash from ladish, because liblash supports only the 0.5.x LASH API and this results in nasty messaged in jack_rack and zynjacku/lv2rack.

Now on the top of my TODO list is to teach ladish to recognize what process creates what alsa client. The ALSA library does not provide such feature so I plan to use some LD_PRELOAD magic. I’m yet to decide how the child process will announce the process <-> ALSA client association (D-Bus or unix pipes) and whether a2jmidid should maintain this information or only ladishd will care about this.

Lately Nikita Zlobin is working quite actively on the ladish codebase and hopefully I’ll be soon able to review the bunch of changes that he made as part of his “process adoption” work and decide whether they will get into 0.3 or process adoption functionality will be merged after the 0.3 release. He made some generally useful fixes that are already merged and I hope there will be more of them in the future :)

Filipe (KXStudio) has pointed me to a nice KXStudio 10.04.2 Review that features ladish. It is really inspiring to see people using your software :)

As last note, I’d like to share a nice ladish trick that I found today. If one starts bash (in terminal) as an app in ladish and starts a command-line tool like jack-smf-player, after the first start & manual connect, ladish will restore the connection(s) for the following invocations. So what I did is that I created a project in my basic room and stated bash in it. Then I started download of random .mid files from Internet through wget. The jack-smf-player midi output is connected to the playback midi port of the room and it in turn is connected to a sf2 player in the studio itself. The nice part is that the box that appears on canvas is always named like the bash app (custom name).

Created: Mon Oct 25 00:34:32 +0300 2010

Valid XHTML 1.0 Strict Valid CSS!