Nedko Arnaudov | 24 Oct 13:54 2012
Face

jack2 jackdbus needs testing

Stephane plans to release jack-1.9.9 soon. He fixed the freeze and
crash on jack server stop bugs that I was able to reproduce on my
machine. I know other jackdbus users are affected by these bugs as
well. So please check if the latest jack2 git fixes the issues for you.

The fixes are commited into the master branch and are merged to the
ladi-experimental branch.

Feel free to report other jackdbus bugs that affect your ladish
workflow.

If no problems are found by the end of the week (Oct 28th), jack-1.9.9
will be released.

--

-- 
Nedko Arnaudov <GnuPG KeyID: 5D1B58ED>
Stephane plans to release jack-1.9.9 soon. He fixed the freeze and
crash on jack server stop bugs that I was able to reproduce on my
machine. I know other jackdbus users are affected by these bugs as
well. So please check if the latest jack2 git fixes the issues for you.

The fixes are commited into the master branch and are merged to the
ladi-experimental branch.

Feel free to report other jackdbus bugs that affect your ladish
workflow.

If no problems are found by the end of the week (Oct 28th), jack-1.9.9
(Continue reading)

Nedko Arnaudov | 27 Oct 13:40 2012
Face

test, please ignore

please ignore this mail
-- 
Nedko Arnaudov <GnuPG KeyID: 5D1B58ED>
please ignore this mail
--

-- 
Nedko Arnaudov <GnuPG KeyID: 5D1B58ED>
Dan Muresan | 31 Aug 08:09 2012
Picon

dbus-related start-up failures

Hi,

I get this kind of failure once in a while. I don't know how to fix
it, except for restarting X, which (according to Murphy's laws) is
usually a no-no at the time (e.g. I'm running some long backup
procedure):

$ laditray

Traceback (most recent call last):
  File "/usr/bin/laditray", line 120, in <module>
    laditray().run()
  File "/usr/bin/laditray", line 43, in __init__
    laditools.manager.__init__(self,
self.global_config.get_config_section ('ladimenu'), autostart)
  File "/usr/lib/laditools/laditools/ladimenu.py", line 54, in __init__
    self.jack_start ()
  File "/usr/lib/laditools/laditools/ladimenu.py", line 89, in jack_start
    self.get_jack_controller().start()
  File "/usr/lib/laditools/laditools/jack_controller.py", line 64, in start
    self.iface.StartServer ()
  File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 70, in __call__
    return self._proxy_method(*args, **keywords)
  File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 145, in __call__
    **keywords)
  File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line
651, in call_blocking
    message, timeout)
dbus.exceptions.DBusException: org.jackaudio.Error.Generic: Failed to
open server
(Continue reading)

Dan Muresan | 27 Aug 08:34 2012
Picon

Multi-client processes reusing port names

Hi,

it seems that, when a single process starts multiple jack clients (say
C1 and C2), but those clients reuse port names (say C1:in, C2:in,
C1:out, C2:out), ladish only sees one instance for each port.

Non-mixer tends to do this when using multiple strips. In any case...
it was frustrating to be unable to connect a port because of naming
assumptions.

--

-- 
Dan Muresan
http://alumnus.caltech.edu/~muresan/
Marc-Olivier Barre | 9 May 17:29 2012

TEST - please ignore

Thank you :)

--
Marc-Olivier Barre
XMPP ID : marco@...
www.MarcOChapeau.org

Wayne | 24 Apr 01:22 2012

Re: updated ebuild

Il giorno mar, 17/04/2012 alle 00.58 +0200, Alessio Treglia ha scritto:
Hi,

ahoy Alessio,

    thanks for the reply and sorry for me delayed response.  the requested info is below:

On Mon, Apr 16, 2012 at 1:25 PM, Nedko Arnaudov <nedko-pIwpoS7APZaLwutG50LtGA@public.gmane.org> wrote: >> $ ladi-system-tray >> Gtk-Message: Failed to load module "gnomesegvhandler" Dunno, never seen before. >> ERROR:root:Could not find any typelib for AppIndicator3 When ladi-system-tray starts, it tries to load itself as an AppIndicator object rather than a system tray icon. If the library is not available (it's a common scenario on non-Ubuntu systems) it fallbacks on the old Gtk's StatusIcon [1]. So please ignore that message, it doesn't hurt at all. >> the menu still appears in the system tray area, but the >> theme/decorations are all different that the other icons, and the actual >> laditray icon is missing. Could you show me a screenshot?

    attached.

Which desktop environment/window manager do you use? If you use GNOME, could you give me more information about the GTK+ theme you use?

    i am using GNOME 2.32.1 on Gentoo, Metacity window manager. with the Clearlooks theme.

>> i am currently trying to install dev-libs/libappindicator to remove the >> ERROR, but so far that is not installing either. > > libappindicator seems to be Unity/Ubuntu specific component. Maybe its > not strictly required. Alessio, please confirm. As per what I said above, yes I confirm. Cheers. [1] You can force ladi-system-tray to load into the system-tray by running it with --no-appindicator

<div>
Il giorno mar, 17/04/2012 alle 00.58 +0200, Alessio Treglia ha scritto: 
<blockquote type="CITE">

Hi,

</blockquote>
<br>
ahoy Alessio,<br><br>
&nbsp;&nbsp;&nbsp; thanks for the reply and sorry for me delayed response.&nbsp; the requested info is below:<br><br><blockquote type="CITE">

On Mon, Apr 16, 2012 at 1:25 PM, Nedko Arnaudov &lt;<a href="mailto:nedko@...">nedko@...</a>&gt; wrote:
&gt;&gt; $ ladi-system-tray
&gt;&gt; Gtk-Message: Failed to load module "gnomesegvhandler"

Dunno, never seen before.

&gt;&gt; ERROR:root:Could not find any typelib for AppIndicator3

When ladi-system-tray starts, it tries to load itself as an AppIndicator object
rather than a system tray icon. If the library is not available (it's a common
scenario on non-Ubuntu systems) it fallbacks on the old Gtk's StatusIcon [1].
So please ignore that message, it doesn't hurt at all.

&gt;&gt; the menu still appears in the system tray area, but the
&gt;&gt; theme/decorations are all different that the other icons, and the actual
&gt;&gt; laditray icon is missing.

Could you show me a screenshot? 

</blockquote>
<br>
&nbsp;&nbsp;&nbsp; attached.<br><br><blockquote type="CITE">

Which desktop environment/window manager
do you use? If you use GNOME, could you give me more information about
the GTK+ theme you use?

</blockquote>
<br>
&nbsp;&nbsp;&nbsp; i am using GNOME 2.32.1 on Gentoo, Metacity window manager. with the Clearlooks theme.<br><br><blockquote type="CITE">

&gt;&gt; i am currently trying to install dev-libs/libappindicator to remove the
&gt;&gt; ERROR, but so far that is not installing either.
&gt;
&gt; libappindicator seems to be Unity/Ubuntu specific component. Maybe its
&gt; not strictly required. Alessio, please confirm.

As per what I said above, yes I confirm.

Cheers.

[1] You can force ladi-system-tray to load into the system-tray by
running it with --no-appindicator

</blockquote>
<br>
</div>
Wayne | 29 Mar 17:27 2012

updated ebuild

ahoy Nedko & co.

    after an update, i noticed that laditray had stopped running.  from the error, it looked like it needed dev-python/pyyaml.  i added it to the laditools-9999.ebuild (attached) and it seems to be working now.  if this is indeed a dependency, perhaps you can update the master ebuilds in the ladi overlay?

    thanks as always for the great software.

peace, w

PS.  maybe the non-live ebuilds will need the same dependency info?
# Copyright 1999-2010 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: $

EAPI="3"

inherit distutils git-2

DESCRIPTION="LADITools is a set of tools to improve desktop integration and user workflow of Linux audio systems"
HOMEPAGE="http://www.marcochapeau.org/software/laditools"

EGIT_REPO_URI="git://git.marcochapeau.org/laditools.git"

LICENSE="GPL-3"
SLOT="0"
KEYWORDS=""
IUSE=""

PYTHON_DEPEND="2:2.6"

RDEPEND="dev-lang/python
	dev-python/pyyaml
	>=dev-python/enum-0.4.4
	>=media-sound/jack-audio-connection-kit-0.109.2-r2[dbus]
	>=x11-libs/vte-0.30.1[introspection]"

DOCS="README"
# Copyright 1999-2010 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: $

EAPI="3"

inherit distutils git-2

DESCRIPTION="LADITools is a set of tools to improve desktop integration and user workflow of Linux audio systems"
HOMEPAGE="http://www.marcochapeau.org/software/laditools"

EGIT_REPO_URI="git://git.marcochapeau.org/laditools.git"

LICENSE="GPL-3"
SLOT="0"
KEYWORDS=""
IUSE=""

PYTHON_DEPEND="2:2.6"

RDEPEND="dev-lang/python
	dev-python/pyyaml
	>=dev-python/enum-0.4.4
	>=media-sound/jack-audio-connection-kit-0.109.2-r2[dbus]
	>=x11-libs/vte-0.30.1[introspection]"

DOCS="README"
Nedko Arnaudov | 14 Jan 18:42 2012
Face

github

github provides useful features for colaboration so I created set of
LADI related repos there:

https://github.com/LADI

repo.or.cz is not deprecated, and stays as alternative to github.

-- 
Nedko Arnaudov <GnuPG KeyID: 5D1B58ED>
github provides useful features for colaboration so I created set of
LADI related repos there:

https://github.com/LADI

repo.or.cz is not deprecated, and stays as alternative to github.

--

-- 
Nedko Arnaudov <GnuPG KeyID: 5D1B58ED>
Dan Muresan | 3 Jan 10:33 2012
Picon

lash-compat

Hi, a question about lash-compat.

My understanding is that it enables old programs that need
/usr/include/lash to compile, and perhaps even work better (L2 instead
of L1/0) under ladish.

It now seems that Debian is dropping lash-compat from their packaging
of ladish [1], because it is "not needed any more". True, many old
LASH programs have compile-time flags to disable LASH.

Is this a good thing? Are old LASH programs better of as L0 (by
compiling them with --disable-lash or whatever) or as L2 (using
lash-compat)?

[1] http://anonscm.debian.org/gitweb/?p=pkg-multimedia/ladish.git;a=summary

-- Dan
Dan Muresan | 2 Jan 07:27 2012
Picon

Adding Jack transport support?

Hi,

I was thinking about adding in Gladish a simple "Tools/Transport"
sub-menu (Start, Stop, Rewind). It's annoying to start a separate
qjackctl or gjacktransport client just for these simple tasks.

However, looking at the jack2 source, I see that
dbus/controller_iface_transport.c seems to be an empty stub. Nedko, am
I misreading that? Can jackdbus affect the transport?

-- Dan
Nedko Arnaudov | 19 Dec 18:56 2011
Face

[ANN] LADI Session Handler - Version 1

This release marks end of the preview series. It brings three new user
visible features - virtual graph manipulation, LASH support and
jack-session support.

Virtual graph manipulation allows to perform these operations:
 * Split (create new client and move capture ports to the the new
   client)
 * Join (move ports of one clients to another client and remove the
   first client)
 * New client
 * Move port
 * Rename client
 * Rename port
 * Remove (empty) client

The added LASH and jack-session support allows apps to be run in rooms
at LASH or jack-session level. jack-session support requires
jack-1.9.8.

= Download =
The tarballs are available at the usual location:

 * http://ladish.org/download/
 * http://ladish.org/download/ladish-1-with-deps.tar.bz2
 * http://ladish.org/download/ladish-1-with-deps.tar.bz2.sig
 * http://ladish.org/download/ladish-1.tar.bz2
 * http://ladish.org/download/ladish-1.tar.bz2.sig

There are two tarballs. ladish-1-with-deps.tar.bz2 is 5.3 MiB and
bundles the major dependencies that are usually needed for running
ladish:
 * flowcanvas
 * LADI Tools
 * a2jmidid
 * jack2

All of these are either development (git/svn) versions or release
versions that are patched to work better with ladish. The last released
versions of these dependencies are expected work with ladish. The most
serious "incompatibility" is that the jack2 mainline is missing the
no-self-connect changeset. This changeset adds option to jack that
allows prevention of jack apps self connection to "hardware" ports
(usually system:playback_N). As such self-connecting apps are not rare
at all, without it, the studio/room separation is not-effective and
the workflow can get very confusing.

If you are compiling the software by yourself, then you should
probably use this "fat" tarball.

The ladish-1.tar.bz2 tarball is 586 KiB and contains only ladish
itself. It is expected to be used mainly by packagers.

= Known issues =
If you want to use yoshimi-0.060.10, beware that its jack-session
implementation is broken. As a workaround, in gladish settings dialog,
"JS delay" can be set to few seconds instead of the default 0. Two
seconds should work in most cases. For more info, check
http://ladish.org/ticket/187

= More info on the ladish project =

Homepage: http://ladish.org/

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. Check the project goals for more info. 

Project goals:
 * Save and restore sets of JACK (audio and MIDI) enabled
   applications.
 * Provide JACK clients with virtual hardware ports, so projects can
   be transferred (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: 5D1B58ED>
_______________________________________________
Jack-Devel mailing list
Jack-Devel <at> lists.jackaudio.org
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

Gmane