Wowzer.. So, quite the output from that command you gave me - Very.. err.. verbose :)
You can find it here: http://pastebin.com/m345b2ad3 And here's the output qjackctl's Messages gives me when I try to run as realtime: http://pastebin.com/m62e0c812 Thanks a ton, Chris! On a related topic, can anyone point me toward a good guide to understanding and configuring qjackctl? I'd like to know what sort of latency is realistic, and how to achieve it. Thanks! ~holotone On 11/12/07, Chris Dawson <[EMAIL PROTECTED]> wrote: > > strace is "system call trace." It simply runs a program within a > harness that outputs all the system calls made. In this case, it will > output and tell you where the jackd program is dying. In my case I > saw that it was dying when it tried to open and write to the > directory. > > It is absolutely harmless to run strace, it just outputs a lot of > extra information you probably won't understand, but would be useful. > If you'd like run it and send me the output. You can do this: > > strace -ooutput.txt /usr/bin/jackd -R -u -dalsa -dhw:0 -r44100 -p1024 -n2 > & > > Then, it'll either die on its own, or you'll need to run: > > killall -9 strace jackd > > ...to kill it. Then, send me the output.txt file and I can look for > something suspicious. Or, you can check it out youself and perhaps > you can figure it out. > > Chris >
-- Ubuntu-Studio-users mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
