From: allcoms <al...@gm...> - 2010-08-30 18:01:29
|
Hi List! Thanks to Arnold and Rocco for help and esp. Stefan for his very comprehensive and thorough responses I have now got my pro 26 working at both 48 and 96Khz under buntu lucid. The manual seems to indicate it can also handle 192Khz under Mac/Win although I've not tried that under either of those OSs I can't get jack to start at 192Khz under buntu but to be honest I don't think I'll really be using 192Khz anyway. On Sun, Aug 29, 2010 at 4:54 PM, Stefan Richter <st...@s5...> wrote: > For the old stack, you have to add an udev rule like this if your distribution > defaults to /dev/raw1394 access denied: > KERNEL=="raw1394", GROUP="audio" > > (These rules can be put into a new file in /etc/udev/rules.d/ with a name of > your choise. New udev rules become effective whenever a device file is > created; i.e. when a device is discovered by firewire-core or when raw1394 is > loaded into the kernel.) This turned out to be the fix I required but I didn't do this until after I had installed ffado trunk and jack svn so I'm not sure if just doing this (as well as adding your user to the audio group etc.) would be enough to get the standard FFADO in the lucid repos to work? I did try re-installing the lucid ffado and jack but I was unable to fully revert to the old versions for some reason - does ffado scons have an uninstall script? I didn't find this out was the problem until I ran the ffado-diag script which alerted me to the fact my user couldn't access /dev/raw1394. Hence, the real problem here was really jack's indescript, vague and not very helpful error messages. I've already complained about a similar problem to Paul (when trying to start jack on a device already being used by another sound system/app) so I'll do my best to convince him we need more descriptive and helpful error messages when trying to start JACK w/ ffado too. It would save him as well as all linux audio devs and users a lot of time and headaches if he did! I still have a prob with trunk in that jack often doesn't start the first (couple of) time(s) I try as I get an error like this: 18:05:42.988 JACK is starting... 18:05:42.989 /usr/bin/jackd -dfirewire -r48000 -p1024 -n3 jackd 0.119.0 Copyright 2001-2009 Paul Davis, Stephane Letz, Jack O'Quinn, Torben Hohn and others. jackd comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details 18:05:42.999 JACK was started with PID=1584. no message buffer overruns JACK compiled with System V SHM support. loading driver .. 00065894659: (ffado.cpp)[ 92] ffado_streaming_init: libffado 2.999.0-1882 built Aug 30 2010 12:29:27 18:05:45.027 Statistics reset. 18:05:45.545 Client activated. 18:05:54.449 JACK connection graph change. 18:05:54.553 JACK connection change. firewire ERR: Could not start streaming threads: -1 DRIVER NT: could not start driver cannot start driver 18:06:02.810 JACK connection graph change. no message buffer overruns 18:06:02.976 JACK connection change. cannot read server event (Success) cannot continue execution of the processing graph (Bad file descriptor) cannot continue execution of the processing graph (Bad file descriptor)18:05:42.988 JACK is starting... 18:05:42.989 /usr/bin/jackd -dfirewire -r48000 -p1024 -n3 jackd 0.119.0 Copyright 2001-2009 Paul Davis, Stephane Letz, Jack O'Quinn, Torben Hohn and others. jackd comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details 18:05:42.999 JACK was started with PID=1584. no message buffer overruns JACK compiled with System V SHM support. loading driver .. 00065894659: (ffado.cpp)[ 92] ffado_streaming_init: libffado 2.999.0-1882 built Aug 30 2010 12:29:27 18:05:45.027 Statistics reset. 18:05:45.545 Client activated. 18:05:54.449 JACK connection graph change. 18:05:54.553 JACK connection change. firewire ERR: Could not start streaming threads: -1 DRIVER NT: could not start driver cannot start driver 18:06:02.810 JACK connection graph change. no message buffer overruns 18:06:02.976 JACK connection change. cannot read server event (Success) cannot continue execution of the processing graph (Bad file descriptor) cannot continue execution of the processing graph (Bad file descriptor) That last line being printed numerous times until jack gives up. Any idea what causes that? Rocco - Yes, CCRMA was the final audio distro I was going to try. I've heard very good things about it and I know Paul respects it very much as its what he runs and develops Ardour/JACK under. The problem for me is that it seems F12 is the latest release to be supported by CCRMA and its (non-audio) packages are getting on a bit now. I've been the primary tester of Ardour 3's MIDI functionality so I need to know I can build A3 without much fuss and I don't fancy replacing/ updating lots of old libs etc. Thanks again to everyone for their help and support- much appreciated! Dan |