[LAU] Fedora 12 & CCRMA

[Fernando Lopez-Lezcano]

On Sun, 2010-05-16 at 22:49 -0700, Fernando Lopez-Lezcano wrote:
> Looks like a different issue. The computer is not locked AFAICT. It was
> only rebooted because jackd is unkillable (maybe it could have beeen
> killed by kill -9 but that was not tried

Sorry, "-9" was tried and jack was still unkillable. At that point I bet
the kernel had oopsed or something like that. That would make the whole
audio subsystem unavailable until the machine is rebooted, which matches
the symptoms. 

-- Fernando


>  - even then the
> hardware/software might be left in a bad state needing a reboot). 
> 
> Only Ardour is hung, most probably because jack itself is hung, most
> probably due to a driver vs. hardware problem. 
> 
> > HOWEVER -- in testing out a new $5.00 soundcard, I also experienced
> > transient lock-ups again with jackd/qjackctl. The one thing that I
> > could point to consistently as causing problems: having the wrong
> > settings in 'alsamixer', i.e. when one of these is set to "on" you can
> > neither play directly through ALSA, and jackd will hang:
> >  ( http://old.nabble.com/Re:-QXGEdit-(was-Re:-Suzuki-QC1-Qchord-Digital-Songcard-Guitar-)-p28541528.html )
> >         ** in alsamixer (F3-playback):
> >         Item: "Multi Track Rate Locking" set to  [Off]
> >         Item: "Multi Track Rate Reset" set to [Off]
> > 
> > 
> > Likewise, if the card is locked to the wrong sampling rate , jack may
> > not be able to reset it if the above settings are wrong.... To make
> > things worse, it seems like some of these settings are "sticky" and
> > may require loading/unloading the driver module or rebooting for the
> > change to take effect. 
> > 
> > 
> > Similar badness may be going on w/ your soundcard, which has been a
> > source of longstanding problems in jack and alsa ... problems that
> > often can be remedied via alsamixer
> > magic: http://www.google.com/search?hl=en&q=SiS+SI7012
> > +jackd&aq=f&aqi=&aql=&oq=&gs_rfai=  
> 
> Those reasons seem more likely. 
> 
> We should wait till we hear what comes out of basic tests of command
> line invocations of jackd. So far the only test is running ardour which
> does not give any feedback on what might be happening.