15 Jun
2015
15 Jun
'15
4:39 p.m.
* Kjetil Matheussen <k.s.matheussen(a)gmail.com> [2015-06-14 14:31]:
Yes,
when I run from a terminal it reconnects every time indeed.
Thank you so much!
P
On Sun, Jun 14, 2015 at 7:49 PM, Peter P.
<peterparker(a)fastmail.com> wrote:
I
managed to do something like this with GNU screen:
screen -dm jack_capture -dc --meterbridge --timemachine --port system:playback_1
/dev/null
which fires up the meters, and auto-(re)connects nicely. Now the problem
remains, once I close the meters by closing their window (clicking the X
in my windown manager's window decoration) jack_capture itself will
continue to run, as it is waiting for user input.
* Peter P. <peterparker(a)fastmail.com>
[2015-06-14 13:22]:
[...]
But I am afraid the the meters still don't come up every time.
The --no-stdin does not help as well, but has other unpleasant results.
It seems that jack_capture needs to have a console it can output things
to.
Maybe it's possible to start an invisible terminal thats jack_capture.
I don't know how to do that though. Maybe there's a general X option
for starting a program minimized? (I tried googling it, but didn't find any) Strangely
this does not work when I start it from fluxbox' menu, ie.
without a visible (x)terminal. The application (and hence the
meterbridge) close immediately. Do you have an idea why this could
happen?
Sorry, I posted before doing my homework
The --disable-console option helped here. Furthermore,
automatically reconnecting to jack applications which play
back audio, does only happen if jack_capture/meterbridge have been
started when that application (mplayer in my case) was already playing
back.
But this is only a problem if you don't run it from a terminal?