<html><body>
<DIV>Let me say it this way - the setup for qjackctl either had options in it to use hw:0 hw:0,0 hw:1 etc but not multi_capture. So, because I could not get the setup to find the multi_capture device, I had to start from command line.</DIV>
<DIV> </DIV>
<DIV>If there's a way around that, again - this is more tuning and tweaking that I planned on finding in the future, but will gladly take advice from now.</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<BLOCKQUOTE style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">-------------- Original message -------------- <BR>From: "Rui Nuno Capela" <rncbc@rncbc.org> <BR><BR>> On Tue, July 11, 2006 02:53, Bob Wilkinson wrote: <BR>> > ... <BR>> > (8) Start the JACK daemon by command line "jackd -d ALSA -C <BR>> > *input_name_here* -P *playback_name_here* <BR>> > (9) Control of JACK can now be done using qjackctl (NOT start - it must <BR>> > be done by command line), and all other programs just work. <BR>> > <BR>> <BR>> Why you say qjackctl cannot start jackd as it should? Can you give us some <BR>> evidence? <BR>> <BR>> Bye now. <BR>> -- <BR>> rncbc aka Rui Nuno Capela <BR>> rncbc@rncbc.org <BR>> <BR>> _______________________________________________ <BR>> PlanetCCRMA mailing list <BR>> PlanetCCRMA@ccrma.stanford.edu <BR>> http://ccrma-mail.stanford.edu/mailman/listinfo/planetccrma </BL
OCKQUOTE></body></html>