23 Nov
2004
23 Nov
'04
9:52 p.m.
On Wednesday 24 November 2004 02:27, Jack O'Quin wrote:
Yes, exactly what
Wolfgang wont :) (to restore manualy the connection)
Gilles Degottex <gilles.degottex(a)net2000.ch>
writes:
bit
> 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
> CPU usage, just enough to raise the jack process
function and throw away
the
data.
You could use jack_deactivate(), but then you'd have to restore your
port connections when it's time to jack_activate() again.