<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;">--- On <b>Thu, 12/9/10, Donald Steven <i><t6sn7gt@aim.com></i></b> wrote:<br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"><br>From: Donald Steven <t6sn7gt@aim.com><br>Subject: [PlanetCCRMA] Major problem / confusion<br>To: PlanetCCRMA@ccrma.Stanford.EDU<br>Date: Thursday, December 9, 2010, 6:21 AM<br><br><div class="plainMail">I recently rebuilt my computer, moving to 64-bits from 32. I've <br>installed F13, the CCRMA core and my favorite apps. I now can't get <br>jack to work, and of course no apps that need it. In fact, with pd <br>installed, I now have two jacks (one 686 and one 64-bit) and one <br>qjackctl. Nothing works. Do I just again from scratch? Any idea what <br>I did wrong? Thanks for any guidance anyone can
offer.<br><br>Don<br></div></blockquote>Don -<br><br>Any chance you are using audio that is integrated into the motherboard of this new computer? My new motherboard/audio interface requires that something be plugged into whatever jack you want to use before that part of the (analog) audio interface is activated. For example, I only had a cable hooked up to the output and so could only start Jack in 'Output-only' mode, since nothing was plugged in to the Input - Jack would throw lots of error messages and finally fail to connect if I tried to start it in 'Duplex' mode. The digital (S/PDIF) interface doesn't seem to behave that way, however. Still need to do more testing here...<br><br>Len<br><div class="plainMail"><br></div><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"><div class="plainMail"></div></blockquote><div class="plainMail"><br></div></td></tr></table><br>