<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'>
<div><br></div>Hello everyone. I have been having some great fun with the low latencies using qjackctl, sooperlooper, audacity, a dunlop crybaby wah-wah pedal, and a seymour duncan tweakfuzz pedal. Anyways, my question is about jack and more specifically, jackdmp. I recently compiled and installed jackdmp from a subversion link provided on the official jack page. I read that the jackdmp installation 'replaces' files in the existing qjackctl and is made to operate better with multi-core CPUs. I use an Intel Quad Core @ 2.4GHz x 4 so this would be good for me. Is there a way I can make sure that I have installed this properly? <div><br></div><div>Fernando. I think saw that you were on the contributors list as making jackdmp compatible with fedora 13. That's what I put your name in the subject. :) Also, I was wondering if there was a site where people post the latencies they are able to achieve using jack. I think it would be interesting to see how people achieve very low-latencies and what those latencies are. <br><br>> From: planetccrma-request@ccrma.Stanford.EDU<br>> Subject: PlanetCCRMA Digest, Vol 30, Issue 13<br>> To: planetccrma@ccrma.Stanford.EDU<br>> Date: Sat, 14 Aug 2010 12:00:01 -0700<br>> <br>> Send PlanetCCRMA mailing list submissions to<br>>         planetccrma@ccrma.stanford.edu<br>> <br>> To subscribe or unsubscribe via the World Wide Web, visit<br>>         http://ccrma-mail.stanford.edu/mailman/listinfo/planetccrma<br>> or, via email, send a message with subject or body 'help' to<br>>         planetccrma-request@ccrma.stanford.edu<br>> <br>> You can reach the person managing the list at<br>>         planetccrma-owner@ccrma.stanford.edu<br>> <br>> When replying, please edit your Subject line so it is more specific<br>> than "Re: Contents of PlanetCCRMA digest..."<br>> <br>> <br>> Today's Topics:<br>> <br>> 1. Re: jack+firewire (Oded Ben-Tal)<br>> 2. Re: jack+firewire (Orcan Ogetbil)<br>> <br>> <br>> ----------------------------------------------------------------------<br>> <br>> Message: 1<br>> Date: Sat, 14 Aug 2010 09:38:19 -0700 (PDT)<br>> From: Oded Ben-Tal <oded@ccrma.Stanford.EDU><br>> Subject: Re: [PlanetCCRMA] jack+firewire<br>> To: Orcan Ogetbil <oget.fedora@gmail.com><br>> Cc: planetccrma@ccrma.Stanford.EDU<br>> Message-ID:<br>>         <alpine.LFD.2.00.1008140931500.31344@ccrma-gate.stanford.edu><br>> Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed<br>> <br>> thanks.<br>> <br>> Yes, the permission change solved the problem.<br>> <br>> I did notice odd behaviour with the firewire connection. Since the builtin <br>> firewire chip is Ricoh, when I need to connect the saffire card (which <br>> isn't every day) I use an expresscard (with TI chipset). Interestingly I <br>> need to shutdown and start again to get the system to recognise the extra <br>> card, just rebooting doesn't work (cold boot works hot boot doesn't). this <br>> isn't new, BTW, it's been the case for a while.<br>> <br>> and ffado-test seems to have disappeared. I added ffado-devel just in <br>> case but I don't seem to have it.<br>> <br>> Oded<br>> <br>> <br>> <br>> <br>> On Sat, 14 Aug 2010, Orcan Ogetbil wrote:<br>> <br>> > On Sat, Aug 14, 2010 at 6:29 AM, Oded Ben-Tal wrote:<br>> >> here we go again,<br>> >><br>> >> After I (foolishly) updated libffado last week I can't get jack to start.<br>> >> The error I get is:<br>> >> could not open driver .so '/usr/lib/jack/jack_firewire.so': libffado.so:<br>> >> cannot open shared object file: No such file or directory<br>> >> could not open component .so '/usr/lib/jack/jack_firewire.so':<br>> >> libffado.so: cannot open shared object file: No such file or directory<br>> >> Unkown driver "firewire"<br>> >><br>> >> The file of course exists:<br>> >> ls -al /usr/lib*/jack/jack_firewire.so<br>> >> -rw-r--r--. 1 root root 35873 2009-11-21 19:22<br>> >> /usr/lib/jack/jack_firewire.so<br>> >><br>> ><br>> > Looks like bad permissions. Just do<br>> > # chmod +x /usr/lib/jack/jack_firewire.so<br>> > This needs to have executable permissions.<br>> ><br>> ><br>> >> This is on Fedora12 2.6.31.12-1.rt20.1.fc12.ccrma.i686.rtPAE<br>> >> jack-audio-connection-kit-1.9.4-1.fc12.ccrma.i686<br>> >> ibffado-2.0.1-3.20100706.svn1864.fc12.i686<br>> >><br>> >> running the fwdiag script I noticed<br>> >> ./fwdiag: line 85: ffado-test: command not found<br>> >> (I presume that means at some point ffado-test was removed from the<br>> >> library though I'm not sure it was in the last update).<br>> >><br>> ><br>> > I don't know about the fwdiag, but to get the ffado-test you need to<br>> > install the ffado package<br>> > # yum install ffado<br>> > The libffado package contains the library only. The applications stuff<br>> > are in the ffado package.<br>> ><br>> > Orcan<br>> ><br>> > _______________________________________________<br>> > PlanetCCRMA mailing list<br>> > PlanetCCRMA@ccrma.stanford.edu<br>> > http://ccrma-mail.stanford.edu/mailman/listinfo/planetccrma<br>> ><br>> <br>> <br>> <br>> ------------------------------<br>> <br>> Message: 2<br>> Date: Sat, 14 Aug 2010 12:53:14 -0400<br>> From: Orcan Ogetbil <oget.fedora@gmail.com><br>> Subject: Re: [PlanetCCRMA] jack+firewire<br>> To: S C Rigler <riglersc@gmail.com><br>> Cc: Oded Ben-Tal <oded@ccrma.Stanford.EDU>,<br>>         planetccrma@ccrma.Stanford.EDU<br>> Message-ID:<br>>         <AANLkTi=2Hr2woG4XQsVxYwdhX5YLbMMASreJSZvX0mLj@mail.gmail.com><br>> Content-Type: text/plain; charset=UTF-8<br>> <br>> On Sat, Aug 14, 2010 at 10:10 AM, S C Rigler wrote:<br>> > On Sat, 14 Aug 2010 08:13:53 -0500, Orcan Ogetbil<br>> > wrote:<br>> ><br>> >> I don't know about the fwdiag, but to get the ffado-test you need to<br>> >> install the ffado package<br>> >> # yum install ffado<br>> >> The libffado package contains the library only. The applications stuff<br>> >> are in the ffado package.<br>> >><br>> >> Orcan<br>> >><br>> ><br>> > It doesn't look like ffado-test made it into my install of ffado:<br>> ><br>> <br>> Sorry, I meant ffado-diag. Refreshing my memory, I realized that we<br>> left the test suite out during the package review since it seemed like<br>> the tests were for development purposes only. Of course this might be<br>> a wrong assumption. Currently, the test suite consists of:<br>> <br>> ./dbus_test.py<br>> ./test-avccmd<br>> ./scan-devreg<br>> ./systemtests/ffado-test-isorecv<br>> ./systemtests/ffado-test-isoxmit<br>> ./systemtests/test-clock_nanosleep<br>> ./systemtests/gen-loadpulses<br>> ./systemtests/test-sysload<br>> ./test-volume<br>> ./test-timestampedbuffer<br>> ./test-echomixer<br>> ./test-ieee1394service<br>> ./test-bufferops<br>> ./dumpiso_mod<br>> ./test-devicestringparser<br>> ./test-scs<br>> ./streaming/ffado-test-streaming-ipcclient<br>> ./streaming/ffado-test-streaming-ipc<br>> ./streaming/ffado-test-streaming<br>> ./test-messagequeue<br>> ./test-streamdump<br>> ./test-focusrite<br>> ./test-watchdog<br>> ./test-enhanced-mixer<br>> ./test-ipcringbuffer<br>> ./test-shm<br>> ./test-dice-eap<br>> ./test-fw410<br>> ./ffado-test<br>> <br>> Do you folks need any of these executables bundled in the ffado<br>> package? Or maybe, do you need all of them?<br>> <br>> If that's the case, please file a bug at https://bugzilla.redhat.com<br>> with the reasons so that I have a reference. When people ask me "Why<br>> did you re-include the tests?" I can say "Look at this bug, the users<br>> need these tests."<br>> <br>> Thanks,<br>> Orcan<br>> <br>> <br>> <br>> ------------------------------<br>> <br>> _______________________________________________<br>> PlanetCCRMA mailing list<br>> PlanetCCRMA@ccrma.stanford.edu<br>> http://ccrma-mail.stanford.edu/mailman/listinfo/planetccrma<br>> <br>> <br>> End of PlanetCCRMA Digest, Vol 30, Issue 13<br>> *******************************************<br></div>                                            </body>
</html>