[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
On Monday 04 May 2009 16:07, Simon Williams wrote: > Tom Potts wrote: > > On Tuesday 28 April 2009 02:41, Simon Williams wrote: > >> The jack server itself is usually where you get problems. > > > > Could be it - I get 'silence' followed by burst of clicks on the speakers > > matching a whole bunch of stuff in the log files but none of the > > connections from it seem to work. > > I'll just have to risk arrest and deportation to Cuba and use the command > > line. > > I highly doubt that will make any difference. Qjackctl is literally just > a controller for the command line jack and alsaconnect. Thats what I thought - however connections made with Jack don't work and those with aconnect do > > xruns are the main problem. Usually you need to adjust options to jack, > though I can't remember what. I think it's a case of balancing settings > to match your machine/sound card. I get a lot of xruns in jackctl message box when nothing is happening but nothing associated with anything I'm doing. Tom te tom te tom -- The Mailing List for the Devon & Cornwall LUG http://mailman.dclug.org.uk/listinfo/list FAQ: http://www.dcglug.org.uk/linux_adm/list-faq.html