Re: [Jack-Devel] jackdus - was Re: Jack 1.9.7 on ARM crashes when killing a client

PrevNext  Index
DateMon, 21 Feb 2011 15:13:57 +0100
From torbenh <[hidden] at gmx dot de>
ToRobin Gareus <[hidden] at gareus dot org>
Cc"[hidden] at lists dot jackaudio dot org List" <[hidden] at lists dot jackaudio dot org>
In-Reply-ToRobin Gareus [Jack-Devel] jackdus - was Re: Jack 1.9.7 on ARM crashes when killing a client
On Mon, Feb 21, 2011 at 01:56:53PM +0100, Robin Gareus wrote:
> On 02/19/2011 07:13 PM, torbenh wrote:
> > On Sat, Feb 19, 2011 at 02:22:26PM +0100, Robin Gareus wrote:
> >> On 02/18/2011 12:23 PM, torbenh wrote:
> >>> On Thu, Feb 17, 2011 at 02:01:06PM +0100, Robin Gareus wrote:
> >> [..]
> >>>>
> >>>>
> >>>> while you're at it: Would it be unreasonable to ask looking into 
> >>>> ignoring device disconnect?  f.i. have jackd survive and not crash
> >>>> when an interface (eg ALSA-USB) goes away.
> >>>>
> >>>> No further action should be taken by JACK (well, maybe some
> >>>> hook-script could be invoked or a d-bus command send); some 3rd
> >>>> party software could issue d-bus commands to switch backends.
> >>>
> >>> i basically did this with tschack. using pyjackd this should be
> >>> working. not well tested, as i dont have an usb soundcard with me
> >>> very often.
> >>
> >> I've updated jackdmp and tschack to latest svn/git and check this with a
> >> USB UA-25. annotated logs attached.
> >>
> >>
> >> 	tschack (git 7b7a48d)
> >> terminates with exit 0 if the interface goes away.
> > 
> > you did not use pyjackd.
> > the jackd binary that comes with tschack is supposed to behave excactly
> > like a jackd binary should.
> > i didnt add a callback to the control api yet. but pyjackd should be
> > ignoring the SIGUSR2 thats sent to the process leader upon backend exit.
> > 
> > so it probably wont exit.
> > the behaviour of tschack while it doesnt have a backend, is probably not
> > really nice. (there are places where it waits for a graph switch) 
> > this is definitely fixable though.
> 
> Hi Torben,
> 
> mmh. python/jackd.py is not executable. I could neither find a dbus
> .service file nor a README and and
> http://hochstrom.endofinternet.org/trac/tschack does not tell much about
> it either.

its still in its infancy.
it accepts the same options as jackd.
(but options are obtained via controlapi)

the python directory in the tschack repo is going to go away at some
point, i already created a separate PyJackd package with a setup.py


it will enter a commandline prompt, where you can issue a switch
command:

jack> switch alsa -d hw:0

for example. 

> 
> How do I launch tschack's dbus control server? Can I do so in a sandbox
> or chroot (1)?

tschack doesnt have dbus yet.

> 
> with jack2, I can use a few symlinks with LD_LIBRARY_PATH and
> JACK_DRIVER_DIR to start 'jackdbus auto' and run the whole thing from
> the source-tree. This schema only works with tschack's jackd, but not
> with jackd.py.

hmm... maybe ctypes is not honouring LD_LIBRARY_PATH
you can probably use the full path to the libs in python/jackctl.py


-- 
torben Hohn
PrevNext  Index

1298297661.27553_0.ltw:2,a <20110221141357.GA10799 at siel dot b>