6 Mar
2009
6 Mar
'09
11:08 a.m.
Le 6 mars 09 à 15:56, Hans Fugal a écrit :
MarcO'Chapeau wrote:
There is *nothing* specific done on OSX. I guess the CoreAudio
interrupt just stops and restart when system resume.
Stephane
On Thu, 5 Mar 2009 09:07:10 -0500, Paul Davis
<paul(a)linuxaudiosystems.com
wrote:
It's interesting that I haven't had major issues with sleep on my
laptop
(running OSX). I didn't expect JACK to survive the first time and was
surprised to see it come back to life with just an xrun or two. More
often than not that's what happens, though it has crashed a few
times on
resume. (disclaimer: I don't have JACK going all the time, so the
sample
size isn't great. Also, I might have had it in soft mode.)
On Thu, Mar 5, 2009 at 9:02 AM, nescivi
<nescivi(a)gmail.com> wrote:
do
Hiho,
It seems that JACK (just tested with v0.116) does not survive
when the
computer is put to sleep, and woken up again.
Is there any reason why this is so?
JACK will see this as a major system malfunction. If you are using
JACK, not let your computer sleep, or suspend, or
engage in CPU frequency
scaling.
These all appear to JACK as indistinguishable from your audio
interface
ceasing to function in a way that leads it to quit or die.
Remember that
JACK is watching the passing of absolute time.
While cpu freq scaling *might* confuse JACK, it seems is not the
case here.
Sleep is a whole different story...