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

test, please ignore

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

please ignore this mail
--

-- 
Nedko Arnaudov <GnuPG KeyID: 5D1B58ED>

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

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/

TEST - please ignore

Thank you :)

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

Re: updated ebuild

<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>

updated ebuild

# 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"

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>

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

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

ladish_control documentation?

<div>
    Greetings.&nbsp; Where can I find documentation for ladish_control ?<br><br><div class="moz-signature">-- <br><div>
        Jonathan E. Brickman<br><a href="http://ponderworthy.com">Ponderworthy Music</a><br>
        805 SW Jewell Ave<br>
        Topeka KS 66606-1610<br><a href="mailto:jeb@...">jeb@...</a>
      </div>
    </div>
  </div>