From: FFADO <ffa...@ff...> - 2011-03-08 13:38:32
|
#325: Problems with ffado-mixer routing tab and Saffire PRO40 -------------------------+-------------------------------------------------- Reporter: darkbasic | Owner: arnonym Type: bug | Status: new Priority: major | Milestone: Component: ffado-mixer | Version: FFADO SVN (trunk) Keywords: | Device_name: Focusrite Saffire PRO 40 -------------------------+-------------------------------------------------- I can't map inputs and outputs to the mixer using the routing tab. In Windows I mapped analog input 1 to mixer input 1, analog input 2 to mixer input 2, [...], DAW 1 to mixer input 17 and DAW2 to mixer input 18. In the routing tab I expected to see 1394:0 and 1394:1 in mixer:16 and mixer:17 and that's what I found, but if set them to "disconnected" they remain still mapped! I also expected to find "analog input 1" in mixer:0 [etc.] but instead I found "disconnected"! Why? How does ffado mixer maps analog inputs to mixer inputs? In Windows I also mapped mixer output 1 to analog output 1, mixer output 2 to analog output 2, etc... Where are these mappings in the ffado-mixer routing tab? Also, as soon as I touch something in the ffado-mixer routing tab peak meters stop working, even if I revert the modifications I made :/ I use latest ffado and lib1394 snapshots with the new firewire stack and kernel 2.6.38. OS is gentoo amd64 with pro-audio overlay. -- Ticket URL: <http://subversion.ffado.org/ticket/325> FFADO <http://subversion.ffado.org/index.fcgi> Free Firewire Audio Drivers |
From: Ilya Z. <zim...@gm...> - 2011-03-09 19:56:13
|
Hi there. I am still agonizing on the utility for Tascam FW-1804. Can someone please explain me how to use raw1394_arm_register function to say 0xffff00000404 register? I tried the code below, but this doesn't seem to work: static int arm_handler(raw1394handle_t handle, unsigned long arm_tag, byte_t request_type, unsigned int requested_length, void *data) { printf("ARM Handler: %x, %x\n", request_type, requested_length ); return 0; } ... int res = raw1394_arm_register(rh, TASCAM_ADDR + 0x0404, 0x01, NULL, (octlet_t)&arm_handler, RAW1394_ARM_READ | RAW1394_ARM_WRITE, RAW1394_ARM_WRITE, 0); ... Thanks, Ilya |
From: Stefan R. <st...@s5...> - 2011-03-09 21:24:36
|
On Mar 09 Ilya Zimnovich wrote: > int res = raw1394_arm_register(rh, TASCAM_ADDR + 0x0404, 0x01, NULL, > (octlet_t)&arm_handler, RAW1394_ARM_READ | RAW1394_ARM_WRITE, > RAW1394_ARM_WRITE, 0); The length argument (the third one) needs to be a multiple of four. -- Stefan Richter -=====-==-== --== -=--= http://arcgraph.de/sr/ |
From: Ilya Z. <zim...@gm...> - 2011-03-10 17:08:22
|
Hi there. On 03/10/2011 12:24 AM, Stefan Richter wrote: > On Mar 09 Ilya Zimnovich wrote: >> int res = raw1394_arm_register(rh, TASCAM_ADDR + 0x0404, 0x01, NULL, >> (octlet_t)&arm_handler, RAW1394_ARM_READ | RAW1394_ARM_WRITE, >> RAW1394_ARM_WRITE, 0); > The length argument (the third one) needs to be a multiple of four. How can I trace the whole range of registers, say from 0x0200 to 0x0400? Should the 5th argument be a pointer to a register handling function? Best regards, Ilya |
From: Ilya Z. <zim...@gm...> - 2011-03-09 21:45:20
|
Thanks for your answer! How can I trace the whole range of registers, say from 0x0200 to 0x0400? Should the 5th argument be a pointer to a register handling function? On 03/10/2011 12:24 AM, Stefan Richter wrote: > On Mar 09 Ilya Zimnovich wrote: >> int res = raw1394_arm_register(rh, TASCAM_ADDR + 0x0404, 0x01, NULL, >> (octlet_t)&arm_handler, RAW1394_ARM_READ | RAW1394_ARM_WRITE, >> RAW1394_ARM_WRITE, 0); > The length argument (the third one) needs to be a multiple of four. |
From: Stefan R. <st...@s5...> - 2011-03-11 20:27:00
|
On Mar 10 Ilya Zimnovich wrote: > Thanks for your answer! How can I trace the whole range of registers, > say from 0x0200 to 0x0400? Should the 5th argument be a pointer to a > register handling function? Simply specify 0xffff00000200ull as the start and e.g. 0x1000 as length. The rest, i.e. how to specify and implement the ARM handler, you need to figure out by yourself. I never programmed on top of libraw1394 myself, and the good folks who added its address range mapping API forgot to document half of it (and to add a test of it to testlibraw). -- Stefan Richter -=====-==-== --== -=-== http://arcgraph.de/sr/ |
From: Damien Z. <dam...@gm...> - 2011-03-12 08:52:27
|
There is an example in the ffado source somewhere because I was able to use it for the 003 and made it talk to an arm handler. |
From: FFADO <ffa...@ff...> - 2011-04-09 11:44:11
|
#325: Problems with ffado-mixer routing tab and Saffire PRO40 ----------------------------------------+----------------------------------- Reporter: darkbasic | Owner: arnonym Type: bug | Status: new Priority: major | Milestone: Component: ffado-mixer | Version: FFADO SVN (trunk) Resolution: | Keywords: Device_name: Focusrite Saffire PRO 40 | ----------------------------------------+----------------------------------- Changes (by nils): * cc: nils (added) -- Ticket URL: <http://subversion.ffado.org/ticket/325#comment:1> FFADO <http://subversion.ffado.org/index.fcgi> Free Firewire Audio Drivers |
From: FFADO <ffa...@ff...> - 2012-04-10 13:28:18
|
#325: Problems with ffado-mixer routing tab and Saffire PRO40 ----------------------------------------+----------------------------------- Reporter: darkbasic | Owner: arnonym Type: bug | Status: new Priority: major | Milestone: Component: ffado-mixer | Version: FFADO SVN (trunk) Resolution: | Keywords: Device_name: Focusrite Saffire PRO 40 | ----------------------------------------+----------------------------------- Comment (by jwoithe): I suspect that at least some of these difficulties are worked around by r2109 and r2110. If possible could you please re-test with a recent SVN snapshot and report your observations? It may be that those changes are sufficient to close this ticket, but if not it would be good to know what exactly still needs to be done. -- Ticket URL: <http://subversion.ffado.org/ticket/325#comment:2> FFADO <http://subversion.ffado.org/index.fcgi> Free Firewire Audio Drivers |
From: Philippe C. <la-...@or...> - 2012-04-10 17:13:58
|
Le mardi 10 avril 2012 à 13:28 +0000, FFADO a écrit : > #325: Problems with ffado-mixer routing tab and Saffire PRO40 > ----------------------------------------+----------------------------------- > Reporter: darkbasic | Owner: arnonym > Type: bug | Status: new > Priority: major | Milestone: > Component: ffado-mixer | Version: FFADO SVN (trunk) > Resolution: | Keywords: > Device_name: Focusrite Saffire PRO 40 | > ----------------------------------------+----------------------------------- > Comment (by jwoithe): > > I suspect that at least some of these difficulties are worked around by > r2109 and r2110. If possible could you please re-test with a recent SVN > snapshot and report your observations? It may be that those changes are > sufficient to close this ticket, but if not it would be good to know what > exactly still needs to be done. I think this bug was prior to r2060 for which router becames available for PRO 40 and 24. Philippe -- Philippe Carriere <la-...@or...> |
From: FFADO <ffa...@ff...> - 2012-04-10 23:41:40
|
#325: Problems with ffado-mixer routing tab and Saffire PRO40 ----------------------------------------+----------------------------------- Reporter: darkbasic | Owner: arnonym Type: bug | Status: new Priority: major | Milestone: Component: ffado-mixer | Version: FFADO SVN (trunk) Resolution: | Keywords: Device_name: Focusrite Saffire PRO 40 | ----------------------------------------+----------------------------------- Comment (by jwoithe): From Philippe Carriere via the ffado-devel mailing list: > I think this bug was prior to r2060 for which router becames available for PRO 40 and 24. The initial report certainly predates r2060 (and the commits immediately before it, in which the actual router work was done), which would suggest that the issue is most likely resolved. It would be good if the original reporter ("darkbasic") could re-test with the latest SVN trunk and report back so we know that their particular issues have all been fixed. In the absence of information information to the contrary after 1-2 weeks this bug can probably be closed on the assumption that all is well. -- Ticket URL: <http://subversion.ffado.org/ticket/325#comment:3> FFADO <http://subversion.ffado.org/index.fcgi> Free Firewire Audio Drivers |
From: FFADO <ffa...@ff...> - 2012-04-11 12:25:19
|
#325: Problems with ffado-mixer routing tab and Saffire PRO40 ----------------------------------------+----------------------------------- Reporter: darkbasic | Owner: arnonym Type: bug | Status: new Priority: major | Milestone: Component: ffado-mixer | Version: FFADO SVN (trunk) Resolution: | Keywords: Device_name: Focusrite Saffire PRO 40 | ----------------------------------------+----------------------------------- Comment (by nils): Here are my observations with ffado-mixer from SVN r2117: The router seems to work in general for me now, but it seems inputs and outputs have been swapped without swapping the mixer table rows and columns, i.e. formerly there were 18 inputs as columns and 16 outputs as rows on the mixer, now the inputs are rows and the outputs are columns, but they are still 16 and 18 respectively. After using the new ffado- mixer, the 2 right-most columns contain garbage values and channel 17 is mapped to an "invalid" output (which is obviously missing from the router). See these screenshots: Trunk/r2117: http://i.imgur.com/1UoJx.png ffado-2.1.0-0.7.20111030.svn2000.fc16.x86_64, apparently from r2000 (started after the above with a bit of leftover garbage?): http://i.imgur.com/zQpc3.png When I change routing, the labels in the mixer tab don't change, I have to restart the GUI to get correctly labeled inputs and outputs. Also, as in the original report, on 48kHz the LED VU meters don't work for me, but when I switch to 96kHz they do. I haven't changed anything on the router there yet... a) I don't dare breaking it there as well and b) output to the interface only works intermittently for me on 96kHz. Is there anything else I should check? -- Ticket URL: <http://subversion.ffado.org/ticket/325#comment:4> FFADO <http://subversion.ffado.org/index.fcgi> Free Firewire Audio Drivers |
From: Philippe C. <la-...@or...> - 2012-04-11 19:13:40
|
Le mercredi 11 avril 2012 à 12:25 +0000, FFADO a écrit : > #325: Problems with ffado-mixer routing tab and Saffire PRO40 > ----------------------------------------+----------------------------------- > Reporter: darkbasic | Owner: arnonym > Type: bug | Status: new > Priority: major | Milestone: > Component: ffado-mixer | Version: FFADO SVN (trunk) > Resolution: | Keywords: > Device_name: Focusrite Saffire PRO 40 | > ----------------------------------------+----------------------------------- > Comment (by nils): > > Here are my observations with ffado-mixer from SVN r2117: > > The router seems to work in general for me now, but it seems inputs and > outputs have been swapped without swapping the mixer table rows and > columns, i.e. formerly there were 18 inputs as columns and 16 outputs as > rows on the mixer, now the inputs are rows and the outputs are columns, > but they are still 16 and 18 respectively. After using the new ffado- > mixer, the 2 right-most columns contain garbage values and channel 17 is > mapped to an "invalid" output (which is obviously missing from the > router). > > See these screenshots: > > Trunk/r2117: http://i.imgur.com/1UoJx.png > Apparently, you have got involved with mismatching versions of ffado-mixer, ffado-dbus-server and libffado. I (very) rapidly wrote a page at: http://www.premiumorange.com/la-page-web-of-phil/index.php?page=P030601 including screenshots of what must appear by now. Note that matrix-mixer channels numbering, for instance, starts now at 1, not at 0. Since you have two co-existing ffado versions, you must take particular care for setting the right environment variables; uninstall properly (including manual erasing of some remaining ffado python scripts in the corresponding lib directory) the possible older svn revision and install the r2117 one; and manually kill the ffado-dbus-server if you test the different versions (neither ffado-mixer nor jackd stop the ffado-dbus-server). > ffado-2.1.0-0.7.20111030.svn2000.fc16.x86_64, apparently from r2000 > (started after the above with a bit of leftover garbage?): > http://i.imgur.com/zQpc3.png > > When I change routing, the labels in the mixer tab don't change, I have to > restart the GUI to get correctly labeled inputs and outputs. > This is the purpose of the new "refresh" button in the Edit menu (a rough way for this, I admit). > Also, as in the original report, on 48kHz the LED VU meters don't work for > me, but when I switch to 96kHz they do. I haven't changed anything on the > router there yet... a) I don't dare breaking it there as well and b) > output to the interface only works intermittently for me on 96kHz. > You will have to reset your configuration for this, by using, one first time the Focusrite firmware under Windows of Mac OS. I did not yet write such a reset function. Note it must be reset only one time, provided you will use revision >= 2110 further. 96kHz does not work correctly, 88.2kHz does. > Is there anything else I should check? > Regards, Phil -- Philippe Carriere <la-...@or...> |
From: FFADO <ffa...@ff...> - 2012-04-12 00:29:38
|
#325: Problems with ffado-mixer routing tab and Saffire PRO40 ----------------------------------------+----------------------------------- Reporter: darkbasic | Owner: arnonym Type: bug | Status: new Priority: major | Milestone: Component: ffado-mixer | Version: FFADO SVN (trunk) Resolution: | Keywords: Device_name: Focusrite Saffire PRO 40 | ----------------------------------------+----------------------------------- Comment (by jwoithe): Thanks for testing this Nils. In response, Philippe Carriere wrote via the ffado-devel mailing list: > Apparently, you have got involved with mismatching versions of ffado- mixer, ffado-dbus-server and libffado. I (very) rapidly wrote a page at:[[BR]] > [[BR]] > http://www.premiumorange.com/la-page-web-of-phil/index.php?page=P030601 [[BR]] > [[BR]] > including screenshots of what must appear by now.[[BR]] > [[BR]] > Note that matrix-mixer channels numbering, for instance, starts now at 1, not at 0.[[BR]] >[[BR]] > Since you have two co-existing ffado versions, you must take particular care for setting the right environment variables; uninstall properly (including manual erasing of some remaining ffado python scripts in the corresponding lib directory) the possible older svn revision and install the r2117 one; and manually kill the ffado-dbus-server if you test the different versions (neither ffado-mixer nor jackd stop the ffado-dbus- server).[[BR]] It seems that Philippe is concerned that some of these issues are caused by running a ffado-dbus-server from one ffado revision and ffado-mixer from another. Is this possible, or is it simple misunderstanding of your latest post? Continuing with Philippe's response: > > When I change routing, the labels in the mixer tab don't change, I have to restart the GUI to get correctly labeled inputs and outputs. > This is the purpose of the new "refresh" button in the Edit menu (a rough way for this, I admit). Could you try this new "refresh" button and let us know if it works as described by Philippe? A final note from Philippe: > > Also, as in the original report, on 48kHz the LED VU meters don't work for me ... > You will have to reset your configuration for this, by using, one first time the Focusrite firmware under Windows of Mac OS.[[BR]] > [[BR]] > I did not yet write such a reset function. Note it must be reset only one time, provided you will use revision >= 2110 further. 96kHz does not work correctly, 88.2kHz does. -- Ticket URL: <http://subversion.ffado.org/ticket/325#comment:5> FFADO <http://subversion.ffado.org/index.fcgi> Free Firewire Audio Drivers |
From: FFADO <ffa...@ff...> - 2012-04-17 16:05:56
|
#325: Problems with ffado-mixer routing tab and Saffire PRO40 ----------------------------------------+----------------------------------- Reporter: darkbasic | Owner: arnonym Type: bug | Status: new Priority: major | Milestone: Component: ffado-mixer | Version: FFADO SVN (trunk) Resolution: | Keywords: Device_name: Focusrite Saffire PRO 40 | ----------------------------------------+----------------------------------- Comment (by nils): My ffado-mixer troubles indeed stemmed from mixing new libffado, new ffado-mixer but old (packaged) ffado python modules. Let's continue discussion of this on the mailing list. -- Ticket URL: <http://subversion.ffado.org/ticket/325#comment:6> FFADO <http://subversion.ffado.org/index.fcgi> Free Firewire Audio Drivers |
From: FFADO <ffa...@ff...> - 2012-04-18 00:40:25
|
#325: Problems with ffado-mixer routing tab and Saffire PRO40 ----------------------------------------+----------------------------------- Reporter: darkbasic | Owner: arnonym Type: bug | Status: new Priority: major | Milestone: Component: ffado-mixer | Version: FFADO SVN (trunk) Resolution: | Keywords: Device_name: Focusrite Saffire PRO 40 | ----------------------------------------+----------------------------------- Comment (by jwoithe): Since the history of this issue is currently contained entirely in this ticket, it's probably best that discussion continues in the ticket. Otherwise it will be harder to follow in future, especially if some key information is posted in ffado-devel and never makes it back to the ticket. In general I have suggested (on ffado-devel) that ticket discussions are conducted from the ticket. The reason for ffado-devel being CCed from the ticket is that it alerts others to developments within the ticketing system, making it easier for them to determine whether a response from them is warranted. It essentially means that people don't have to monitor each and every ticket. -- Ticket URL: <http://subversion.ffado.org/ticket/325#comment:7> FFADO <http://subversion.ffado.org/index.fcgi> Free Firewire Audio Drivers |
From: FFADO <ffa...@ff...> - 2012-04-18 07:34:54
|
#325: Problems with ffado-mixer routing tab and Saffire PRO40 ----------------------------------------+----------------------------------- Reporter: darkbasic | Owner: arnonym Type: bug | Status: new Priority: major | Milestone: Component: ffado-mixer | Version: FFADO SVN (trunk) Resolution: | Keywords: Device_name: Focusrite Saffire PRO 40 | ----------------------------------------+----------------------------------- Comment (by nils): > Since the history of this issue is currently contained entirely in this ticket, it's probably best that discussion continues in the ticket. Oh, I was just referring to the side issue of me mixing up stuff old and new. A far a I'm concerned, the only remaining issue is that of the broken LED meters, but that may be just another side issue as well. -- Ticket URL: <http://subversion.ffado.org/ticket/325#comment:8> FFADO <http://subversion.ffado.org/index.fcgi> Free Firewire Audio Drivers |
From: FFADO <ffa...@ff...> - 2012-05-01 12:11:29
|
#325: Problems with ffado-mixer routing tab and Saffire PRO40 ----------------------------------------+----------------------------------- Reporter: darkbasic | Owner: arnonym Type: bug | Status: new Priority: major | Milestone: Component: ffado-mixer | Version: FFADO SVN (trunk) Resolution: | Keywords: Device_name: Focusrite Saffire PRO 40 | ----------------------------------------+----------------------------------- Comment (by jwoithe): With the recent round of changes, has the subject of this ticket been resolved? Are there still issues with the LED meters which we know how to resolve and just need the time to do so? Philippe? -- Ticket URL: <http://subversion.ffado.org/ticket/325#comment:9> FFADO <http://subversion.ffado.org/index.fcgi> Free Firewire Audio Drivers |
From: Philippe C. <la-...@or...> - 2012-05-01 12:45:19
|
Le mardi 01 mai 2012 à 12:11 +0000, FFADO a écrit : > #325: Problems with ffado-mixer routing tab and Saffire PRO40 > ----------------------------------------+----------------------------------- > Reporter: darkbasic | Owner: arnonym > Type: bug | Status: new > Priority: major | Milestone: > Component: ffado-mixer | Version: FFADO SVN (trunk) > Resolution: | Keywords: > Device_name: Focusrite Saffire PRO 40 | > ----------------------------------------+----------------------------------- > Comment (by jwoithe): > > With the recent round of changes, has the subject of this ticket been > resolved? Are there still issues with the LED meters which we know how to > resolve and just need the time to do so? Philippe? > Hi Jonhatan, routing tab issue was solved by the first changes I submitted. LED meters issue has been solved by the last changes I committed 2 or 3 weeks ago (I don't remember exactly), for both Pro 40 and 24. So the ticket can be considered as solved, from my viewpoint. Regards, Phil -- Philippe Carriere <la-...@or...> |
From: FFADO <ffa...@ff...> - 2012-05-02 00:10:58
|
#325: Problems with ffado-mixer routing tab and Saffire PRO40 ----------------------------------------+----------------------------------- Reporter: darkbasic | Owner: arnonym Type: bug | Status: closed Priority: major | Milestone: Component: ffado-mixer | Version: FFADO SVN (trunk) Resolution: fixed | Keywords: Device_name: Focusrite Saffire PRO 40 | ----------------------------------------+----------------------------------- Changes (by jwoithe): * status: new => closed * resolution: => fixed Comment: From Philippe on ffado-devel: > routing tab issue was solved by the first changes I submitted. LED meters issue has been solved by the last changes I committed 2 or 3 weeks ago (I don't remember exactly), for both Pro 40 and 24. So the ticket can be considered as solved, from my viewpoint. Thanks for your work on this Philippe. -- Ticket URL: <http://subversion.ffado.org/ticket/325#comment:10> FFADO <http://subversion.ffado.org/index.fcgi> Free Firewire Audio Drivers |
From: Yves G. <yve...@nu...> - 2012-05-12 17:51:52
|
Le 12/05/2012 17:10, Adrian Knoth a écrit : > On Sat, May 12, 2012 at 04:55:06PM +0200, Yves Grenier wrote: > >> Now comes the problem (if I understand it correctly). When I install the >> following packages with: >> sudo aptitude install jackd jackd2 jackd2-firewire libffado2 >> pulseaudio-module-jack qjackctl vlc-plugin-jack >> >> ubuntu 12.04 installs two versions of libffado: >> >> -rw-r--r-- 1 root root 1837496 févr. 17 16:55 /usr/lib/libffado.so.2.999.0 >> /usr/lib/libffado2: >> total 2008 >> lrwxrwxrwx 1 root root 19 févr. 17 16:55 libffado.so.2 -> >> libffado.so.2.999.0 >> -rw-r--r-- 1 root root 2050584 févr. 17 16:55 libffado.so.2.999.0 >> >> There are two files called libffado.so.2, one in /usr/lib and on in >> /usr/lib/libffado2. When I compile libffado, It will only overwrite the >> one in /usr/lib, not the one in /usr/lib/libffado2. Am I correct, or did >> I miss something? > > Your observation is correct, there are two libraries, but the one in > /usr/lib/libffado2 won't get loaded when you start jackd: > > adi@foh:~$ /sbin/ldconfig -p | grep ffado > libffado.so.2 (libc6,x86-64) => /usr/lib/libffado.so.2 > libffado.so (libc6,x86-64) => /usr/lib/libffado.so > > > The version in /usr/lib/libffado2/ is for ffado-debug, because in > contrast to the one in /usr/lib/, it was compiled with DEBUG=True. > > adi@foh:~$ cat /usr/bin/ffado-debug > #!/bin/sh > > export > LD_LIBRARY_PATH=/usr/lib/libffado2${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH} > > exec "$@" > > > So you can say > > $ jackd -d firewire > > to start your ordinary, slightly optimized libffado or > > $ ffado-debug jackd -d firewire > > if you want to load the one with more verbose output, assertions and the > lot. Add -v5 to the command line to notice the difference. > > > > HTH > Thanks for the information. Starting from that, I compile ffado (rev 2149) and I effectively observe that the library libffado in /usr/lib is overwritten: $ ls -l $(find /usr/lib -name "libffado*") | grep "mai 12" lrwxrwxrwx 1 root root 13 mai 12 18:48 /usr/lib/libffado.so -> libffado.so.2 lrwxrwxrwx 1 root root 19 mai 12 18:48 /usr/lib/libffado.so.2 -> libffado.so.2.999.0 -rwxrwxr-x 1 root root 9685074 mai 12 18:47 /usr/lib/libffado.so.2.999.0 Unfortunately, jackd won't start: $ jackd -d firewire -r 48000 -v6 jackdmp 1.9.8 Copyright 2001-2005 Paul Davis and others. Copyright 2004-2011 Grame. jackdmp 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 no message buffer overruns no message buffer overruns no message buffer overruns JACK server starting in realtime mode with priority 10 firewire ERR: Incompatible libffado version! (libffado 2.999.0-2149) Cannot initialize driver JackServer::Open() failed with -1 no message buffer overruns Failed to open server So at this point, I am blocked. How can I make jack work with the svn version of ffado? Regards Yves |
From: Jonathan W. <jw...@ju...> - 2012-05-13 10:27:16
|
Hi Yves On Sat, May 12, 2012 at 07:51:44PM +0200, Yves Grenier wrote: > Thanks for the information. Starting from that, I compile ffado (rev > 2149) and I effectively observe that the library libffado in /usr/lib is > overwritten: Yes, that is what I would expect. > Unfortunately, jackd won't start: > > $ jackd -d firewire -r 48000 -v6 > jackdmp 1.9.8 > Copyright 2001-2005 Paul Davis and others. > Copyright 2004-2011 Grame. > : > firewire ERR: Incompatible libffado version! (libffado 2.999.0-2149) Oh bother. I *really* thought we'd resolved this. > So at this point, I am blocked. How can I make jack work with the svn > version of ffado? What happened here should not have happened. The history of this can be found in the ffado-devel archives. However, let's just see if we can work out why things fell over in your case and get you up and running again. I am assuming that you haven't compiled jackmp yourself and that it was installed at the time you compiled libffado. The fact that a version of libffado resulted that was not compatible with the jackd you had on your system means that ffado's detection of jackd must have failed somehow. Could you please re-run "scons" in the ffado source tree and post the 4 lines which report checks on the jack version, plus the line which follows these (it should mention setbuffersize)? It's possible to force libffado to be compatible with your jackd by including ENABLE_SETBUFFERSIZE_API_VER=false as an option to scons. However, this *really* should have been correctly detected and I would very much like to work out why it wasn't. Regards jonathan |
From: Adrian K. <ad...@dr...> - 2012-05-13 12:05:32
|
On 05/13/2012 01:50 PM, Yves Grenier wrote: > Checking for jack>= 0.122.0... (cached) yes > Checking for jack>= 1.9.9... (cached) no > Installed jack supports FFADO setbuffersize API > > The second check seems wrong; if I check jack version, I get: > $ jackd --version > jackdmp 1.9.8 Where does you jackd come from? Self-compiled? Please post the output of $ dpkg -l libjack-jackd2-dev libjack-dev Cheers |
From: Yves G. <yve...@nu...> - 2012-05-13 12:19:41
|
Le 13/05/2012 14:05, Adrian Knoth a écrit : > On 05/13/2012 01:50 PM, Yves Grenier wrote: > >> Checking for jack>= 0.122.0... (cached) yes >> Checking for jack>= 1.9.9... (cached) no >> Installed jack supports FFADO setbuffersize API >> >> The second check seems wrong; if I check jack version, I get: >> $ jackd --version >> jackdmp 1.9.8 > Where does you jackd come from? Self-compiled? > > Please post the output of > > $ dpkg -l libjack-jackd2-dev libjack-dev > > Hi Adrian I did not compile jack. I use the packages provided with ubuntu 12.04 $ dpkg -l libjack-jackd2-dev libjack-dev Souhait=inconnU/Installé/suppRimé/Purgé/H=à garder | État=Non/Installé/fichier-Config/dépaqUeté/échec-conFig/H=semi-installé/W=attend-traitement-déclenchements |/ Err?=(aucune)/besoin Réinstallation (État,Err: majuscule=mauvais) ||/ Nom Version Description +++-=============================================-=============================================-========================================================================================================== un libjack-dev <aucun> (aucune description n'est disponible) Aucun paquet ne correspond à libjack-jackd2-dev. Here are the installed jack packages: $ dpkg -l '*jack*' | grep ii ii jackd 5 JACK Audio Connection Kit (default server package) ii jackd2 1.9.8~dfsg.1-1ubuntu1 JACK Audio Connection Kit (server and example clients) ii jackd2-firewire 1.9.8~dfsg.1-1ubuntu1 JACK Audio Connection Kit (FFADO and FreeBoB backends) ii libjack-jackd2-0 1.9.8~dfsg.1-1ubuntu1 JACK Audio Connection Kit (libraries) ii pulseaudio-module-jack 1:1.1-0ubuntu15 jackd modules for PulseAudio sound server ii qjackctl 0.3.8-1 User interface for controlling the JACK sound server ii vlc-plugin-jack 2.0.1-4 Jack audio plugins for VLC Regards Yves |
From: Yves G. <yve...@nu...> - 2012-05-08 12:02:13
|
Hello I upgraded from ubuntu lucid lynx 10.04 to ubuntu precise pangolin 12.04 LTS. In order to benefit from the recent improvements in ffado-mixer for Saffire Pro 24, I decide to continue to use the svn version and compile ffado (as well as jack and qjackctl). Ubuntu precise is using revision 2019 of ffado. When I launch ffado-mixer, the terminal shows many repetitions of the same error: <begin> KeyError: dbus.String(u'') Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/ffado/widgets/crossbarrouter.py", line 176, in updateLevels self.switchers[peak[0]].peakValue(peak[1]) <end> and ubuntu opens a popup saying that it has encountered an internal error, and the execution path show /usr/bin/ffado-mixer. At that moment, ffado-mixer is still active and can still work correctly. I cannot really confirm it because ubuntu keep opening so many new popups that it prevents me from continuing the tests. But I can switch from mixer to crossbar panel, make changes in both, update the current panel and see changes appear.... Regards Yves |