23 Nov
2004
23 Nov
'04
8:42 p.m.
On Wednesday 24 November 2004 00:55, Wolfgang Woehl wrote:
Gilles Degottex <gilles.degottex(a)net2000.ch>ch>:
The whole point is: In a recording session you set up a certain
connection jack <-> fmit. You use fmit -- which has an appetite for cpu
cycles -- and then you want to release the cpu from fmit. So you want
to halt it's operation.
But you don't want to manually setup the connection again. You want to
hit a button and have fmit back connected to where you left it.
"Preferred jack source" is not always applicable, it's session
specific. fmit could remember it's connections and restore them
whatever they were, right?
In a fast research, JACK does not seems to support a
"suspend" state or
something like this, but I'll simulate one. There will be always a little bit
CPU usage, just enough to raise the jack process function and throw away the
data.
Gilles
On Tuesday 23 November 2004 11:43, Wolfgang Woehl
wrote:
-- fmit
being ready with one mouse-click. Instead it
disconnects any jack-connections and unregisters from jack.
Unexpected behaviour I think.
I currently stop then restart the sound capture to simulate a pause
state. It's usefull when you have to reset the capture system, just
hit twice the pause button.
to avoid register at each unpause, you can add your prefered jack
source in the settings dialog.
Should I concider add a real reset button and do a real pause button
?