On Fri, 15 Aug 2008, Peder Hedlund wrote:
Quoting "Kjetil S. Matheussen"
<k.s.matheussen(a)notam02.no>no>:
Peder Hedlund:
There's something fishy going on in .18 and
onwards.
Thanks for the report. 0.9.28 is just put out.
Please cc me next time. :-)
Since I'm reading the list in digest mode it takes some
time before reading the messages.
No problem (for me anyway). For my modest use .17 was just fine.
The bug is present in .17 as well, it's just a
coincidence that .18 works for you while .17 does
not.
As far as my tests go, no version of jack_capture
works on fecora core 6 using those options.
However, I would guess that .17 and earlier
work in redhat 8, the distribution I used
when writing that specific (and horrible buggy
(what was I thinking!)) code.
And a
trivial note: once you've started the GUI there seems to be no
way of ending it apart from Ctrl-C or killing the process.
You mean jack_capture_gui?
Well, it should stop if you press Ctrl-C.
Assuming you start it from a terminal window and Ctrl-C in that.
But what if someone runs it from a shortcut?
May I propose this patch (here's to hoping the email will preserve
whitespace):
--- jack_capture-0.9.28/jack_capture_gui 2008-08-15 19:23:05.307743667
+0200
+++ jack_capture-0.9.28/jack_capture_gui_new 2008-08-15 21:59:53.837317418
+0200
@@ -15,7 +15,13 @@
0) jack_capture $OPTIONS | Xdialog --stdout --msgbox " RECORDING IN
PROGRESS\n PRESS OK TO STOP REC " 10 40
echo "Recording stopped"
;;
- 1) Xdialog --msgbox "Ok no recording started" 10 40
+ 1) Xdialog --stdout --yesno "Ok. No recording started\n Press No to
exit" 10 40
+ case "$?" in
+ 0)
+ ;;
+ 1) exit 0
+ ;;
+ esac
Thanks, I'll add that patch.