Saffire PRO 24
Submitted by arnonym on Mon, 10/12/2009 - 21:07.
Manufacturer:
Focusrite
Device Info on Vendor Site:
Support Status:
ExperimentalSupport Contact(s):
arnonymSmaller brother of the PRO 40, this device has the same state of support and works with trunk...
ffado update
Hello,
I'm relatively new in Ubuntu. I'm running UbStudio 12.04LTS with ffado Version: 2.1.9999. Now I'd like to update to the new ffado version 2.1.0 but I have no idea how to do this. I searched for hours but only found how tos for much older versions and other distros. Can someone please help me with that.
I hope to get an updated ffado Mixer because the one I'm running right now is not easy to handle because there are nearly no descriptions of the in and outputs and the other functions.
Thank you very much indeed.
Johannes
SAFFIRE PRO 24 DSP SOFTWARE DONT WORK
IMAC 27
saffire pro 24 dsp
the unit is not recognized by the logic pro
it is recognized by the imac
and it is recognized by reaper 64
software "MIX CONTROL" CRASH ERROR
GREAT IM REALLY HAPPY WITH SAFIRE SO FAR!!!! (SARCASTIC)
ANY HELP APPRECIATTED
SAFFIRE SUPPORT CENTER UNABLE TO SOLVE MY PROBLEM
Process: Saffire MixControl [730]
Path: /Applications/Saffire MixControl.app/Contents/MacOS/Saffire MixControl
Identifier: com.focusrite.SaffireMixControl2
Version: ??? (2.1)
Code Type: X86 (Native)
Parent Process: launchd [181]
Date/Time: 2012-11-28 19:18:09.081 +0900
OS Version: Mac OS X 10.7.5 (11G63)
Report Version: 9
:
=====
This post has been editted by the site admin. It seems to be a report of a bug encountered using Focusrite-supplied drivers under MacOSX. This has nothing to do with FFADO and the FFADO team are unable to assist.
Re: SAFFIRE PRO 24 DSP SOFTWARE DONT WORK
As per the note in the main post, the problem being reported appears to relate to the use of Focusrite drivers under MacOSX. The FFADO project is a volunteer effort which allows selected Firewire-based audio interfaces to run under the Linux operating system. We are therefore unfortunately not in a position to assist.
JACK server not started
Here is log:
bloodyfoxy@bloodyfoxy:~$ sudo jackd -d firewire -n 3 -p 2048
[sudo] password for bloodyfoxy:
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
00131131177: (ffado.cpp)[ 92] ffado_streaming_init: libffado 2.999.0- built Jun 27 2012 22:38:12
00131439524: Warning (dice_eap.cpp)[1398] read: No routes found. Base 0x7, offset 0x4000
00131465506: Warning (dice_eap.cpp)[ 881] updateNameCache: What is this function about?
00131567666: (dice_avdevice.cpp)[ 626] showDevice: DICE Parameter Space info:
00131567674: (dice_avdevice.cpp)[ 627] showDevice: Global : offset=0x0028 size=0360
00131567682: (dice_avdevice.cpp)[ 628] showDevice: TX : offset=0x0190 size=0568
00131567684: (dice_avdevice.cpp)[ 629] showDevice: nb= 1 size=0280
00131567688: (dice_avdevice.cpp)[ 630] showDevice: RX : offset=0x03C8 size=1128
00131567689: (dice_avdevice.cpp)[ 631] showDevice: nb= 1 size=0280
00131567693: (dice_avdevice.cpp)[ 632] showDevice: UNUSED1 : offset=0x0830 size=0016
00131567694: (dice_avdevice.cpp)[ 633] showDevice: UNUSED2 : offset=0x0000 size=0000
00131567698: (dice_avdevice.cpp)[ 635] showDevice: Global param space:
00131569195: (dice_avdevice.cpp)[ 638] showDevice: Owner : 0x00000000FFFF0000
00131570786: (dice_avdevice.cpp)[ 641] showDevice: Notification : 0x00000000
00131573753: (dice_avdevice.cpp)[ 644] showDevice: Nick name : Pro24-001fb9
00131575134: (dice_avdevice.cpp)[ 648] showDevice: Clock Select : 0x02 0x0C
00131576723: (dice_avdevice.cpp)[ 652] showDevice: Enable : false
00131579013: (dice_avdevice.cpp)[ 656] showDevice: Clock Status : locked 0x02
00131580618: (dice_avdevice.cpp)[ 659] showDevice: Extended Status : 0x00000000
00131581984: (dice_avdevice.cpp)[ 662] showDevice: Samplerate : 0x0000BB80 (48000)
00131583589: (dice_avdevice.cpp)[ 665] showDevice: Version : 0x01000400
00131584977: (dice_avdevice.cpp)[ 674] showDevice: Version : 0x01000400 (1.0.4.0)
00131586613: (dice_avdevice.cpp)[ 677] showDevice: Clock caps : 0x112C001E
00131588643: (dice_avdevice.cpp)[ 680] showDevice: Clock sources :
00131588651: (dice_avdevice.cpp)[ 686] showDevice: AES1
00131588656: (dice_avdevice.cpp)[ 686] showDevice: AES2
00131588681: (dice_avdevice.cpp)[ 686] showDevice: SPDIF-OPT
00131588685: (dice_avdevice.cpp)[ 686] showDevice: SPDIF
00131588687: (dice_avdevice.cpp)[ 686] showDevice: AES_ANY
00131588690: (dice_avdevice.cpp)[ 686] showDevice: ADAT
00131588692: (dice_avdevice.cpp)[ 686] showDevice: ADAT_AUX
00131588696: (dice_avdevice.cpp)[ 686] showDevice: Word Clock
00131588697: (dice_avdevice.cpp)[ 686] showDevice: Unused
00131588702: (dice_avdevice.cpp)[ 686] showDevice: Unused
00131588704: (dice_avdevice.cpp)[ 686] showDevice: Unused
00131588707: (dice_avdevice.cpp)[ 686] showDevice: Unused
00131588708: (dice_avdevice.cpp)[ 686] showDevice: Internal
00131588711: (dice_avdevice.cpp)[ 689] showDevice: TX param space:
00131588713: (dice_avdevice.cpp)[ 690] showDevice: Nb of xmit : 1
00131588716: (dice_avdevice.cpp)[ 692] showDevice: Transmitter 0:
00131590014: (dice_avdevice.cpp)[ 695] showDevice: ISO channel : -1
00131591636: (dice_avdevice.cpp)[ 697] showDevice: ISO speed : 2
00131592989: (dice_avdevice.cpp)[ 700] showDevice: Nb audio channels : 16
00131594592: (dice_avdevice.cpp)[ 702] showDevice: Nb midi channels : 1
00131595954: (dice_avdevice.cpp)[ 705] showDevice: AC3 caps : 0x00000000
00131597612: (dice_avdevice.cpp)[ 707] showDevice: AC3 enable : 0x00000000
00131599918: (dice_avdevice.cpp)[ 710] showDevice: Channel names :
00131599932: (dice_avdevice.cpp)[ 715] showDevice: IP 1
00131599936: (dice_avdevice.cpp)[ 715] showDevice: IP 2
00131599942: (dice_avdevice.cpp)[ 715] showDevice: IP 3
00131599945: (dice_avdevice.cpp)[ 715] showDevice: IP 4
00131599950: (dice_avdevice.cpp)[ 715] showDevice: SPDIF L
00131599953: (dice_avdevice.cpp)[ 715] showDevice: SPDIF R
00131599958: (dice_avdevice.cpp)[ 715] showDevice: ADAT 1
00131599960: (dice_avdevice.cpp)[ 715] showDevice: ADAT 2
00131599967: (dice_avdevice.cpp)[ 715] showDevice: ADAT 3
00131599970: (dice_avdevice.cpp)[ 715] showDevice: ADAT 4
00131599975: (dice_avdevice.cpp)[ 715] showDevice: ADAT 5
00131599978: (dice_avdevice.cpp)[ 715] showDevice: ADAT 6
00131599983: (dice_avdevice.cpp)[ 715] showDevice: ADAT 7
00131599986: (dice_avdevice.cpp)[ 715] showDevice: ADAT 8
00131599993: (dice_avdevice.cpp)[ 715] showDevice: Loop 1
00131599996: (dice_avdevice.cpp)[ 715] showDevice: Loop 2
00131600011: (dice_avdevice.cpp)[ 719] showDevice: RX param space:
00131600014: (dice_avdevice.cpp)[ 720] showDevice: Nb of recv : 1
00131600020: (dice_avdevice.cpp)[ 722] showDevice: Receiver 0:
00131601513: (dice_avdevice.cpp)[ 725] showDevice: ISO channel : -1
00131602892: (dice_avdevice.cpp)[ 727] showDevice: Sequence start : 0
00131604524: (dice_avdevice.cpp)[ 730] showDevice: Nb audio channels : 8
00131605896: (dice_avdevice.cpp)[ 732] showDevice: Nb midi channels : 1
00131607506: (dice_avdevice.cpp)[ 735] showDevice: AC3 caps : 0x00000000
00131609102: (dice_avdevice.cpp)[ 737] showDevice: AC3 enable : 0x00000000
00131610877: (dice_avdevice.cpp)[ 740] showDevice: Channel names :
00131610887: (dice_avdevice.cpp)[ 745] showDevice: Mon 1
00131610889: (dice_avdevice.cpp)[ 745] showDevice: Mon 2
00131610893: (dice_avdevice.cpp)[ 745] showDevice: Line 3
00131610895: (dice_avdevice.cpp)[ 745] showDevice: Line 4
00131610898: (dice_avdevice.cpp)[ 745] showDevice: Line 5
00131610900: (dice_avdevice.cpp)[ 745] showDevice: Line 6
00131610903: (dice_avdevice.cpp)[ 745] showDevice: SPDIF L
00131610905: (dice_avdevice.cpp)[ 745] showDevice: SPDIF R
firewire ERR: Could not start streaming threads
Cannot start driver
JackServer::Start() failed with -1
Failed to start server
FW LED is glowing until JACK cannot start server. That is strange.
Re: JACK server not started
bloodyfoxy@bloodyfoxy:~$ sudo jackd -d firewire -n 3 -p 2048
You shouldn't be trying to run jackd using sudo. While this may not be the root cause of your problem, you will want to read up about how to run jackd on your distribution as an ordinary user. My recollection is that there's something about jackd which causes it to misbehave when run as root.
If you could tell us which distribution and version you're using there may be people who can point you to specific instructions which apply to your particular setup.
In the meantime, you might like to add "-v 6" to the end of your jackd command line. This will produce a lot more debugging information, but there might be something in there which points to the cause of your trouble.
Not recognized on Ubuntu Studio 11.04
Hello, I just purchased a Saffire Pro 24 DSP and I can't get it to work on Ubuntu Studio 11.04. It's just not being recognized. Can anyone help?
P.S: I'm a newbie in Ubuntu so humour me :P
Valiant Sheep
I am also trying to put
I am also trying to put Saffire Pro 24 DSP to work on Ubuntu, version 11.10. I get ffado to recognize the device but then error with firmware version. The cpp file is nowhere on the computer though.... help?
Thanks!
Works with Ubuntu Studio 12.10 after updating libffado
Hello,
After many tries and reading many confusing posts, I found a simple way to get Saffire Pro 24 DSP to work in Ubuntu Studio 12.10.
- I did a fresh install of Ubuntu Studio 12.10.
- It comes with Jackd2-firewire (jackdmp 1.9.9) and libffado 2.999.0
- I didn't un-install anything, but manually compiled and installed libffado 2.1.9999-2255 on top of the previous version, using these step-by-step instructions: http://subversion.ffado.org/wiki/Dependencies/Ubuntu
- I only re-installed libffado, not jackd:
$ sudo apt-get build-dep libffado
$ sudo apt-get install build-essential libavc1394-dev python-qt4-dev subversion libtool
$ svn checkout http://subversion.ffado.org/ffado/trunk/libffado ffado-svn
$ cd ffado-svn
$ scons PREFIX=/usr
$ sudo scons install
...and we're done. Start the applications:
$ ffado-dbus-server &
$ jackd -R -d firewire -n 3 -p 64 &
$ ardour2
...and start making some sweet music! :) I hope this helps.
What is the error with
What is the error with firmware?
The .cpp file is an C++ soure code file from ffado SVN repository. I must compile ffado from source after any changes in source codes.
read this documentation http://subversion.ffado.org/wiki/InstallingFfadoFromSource
This stack is not supported by FFADO
I get the following messages from ffado-diag on fedora 14.
The new FireWire kernel stack is loaded.
This stack is not supported by FFADO. Please use the old stack.
Does this mean that I need to downgrade to the 1eee1394 modules?
Can someone tell me what needs to be done to resolve this?
Here are the package version currently installed.
rpm -qa | grep ffado
ffado-2.1.0-0.1.20101015.svn1913.fc14.x86_64
libffado-2.1.0-0.1.20101015.svn1913.fc14.i686
ibffado-2.1.0-0.1.20101015.svn1913.fc14.x86_64
rpm -qa | grep 1394
libraw1394-2.0.5-2.fc14.x86_64
libavc1394-0.5.3-9.fc12.x86_64
libavc1394-0.5.3-9.fc12.i686
libraw1394-2.0.5-2.fc14.i686
libdc1394-2.1.2-3.fc12.x86_64
rpm -q kernel
kernel-2.6.35.13-92.fc14.x86_64
lsmod | grep firewire
firewire_ohci 21314 0
firewire_core 45817 11 firewire_ohci
crc_itu_t 1563 1 firewire_core
Re: This stack is not supported by FFADO
The message from ffado-diag that you reference is IMHO old and out of date. It was added during the early days of the "new" kernel firewire stack because back then there were real problems using the "new" stack with ffado. However, since around kernel 2.6.34 or there abouts my understanding is that the "new" stack generally works with ffado - although we do still get reports of issues with certain hardware combinations.
To avoid confusion the ffado-diag message clearly needs to be reworked. These days we should probably only display it if "known bad" kernel/libraw1394 combinations are detected.
In the case of your system, I would be tempted to just try ffado with your device (assuming it's one we support) and see what happens. Notwithstanding hardware issues, I think your existing kernel and libraw1394 are sufficiently recent to give you a good chance of things working.
It works
Hi guys,
Just a brief message to thank you for your nice job. I got my Pro24 work quite well under my Dell laptop E6500, for both playback and recording.
I first got a lot of xruns with the default lowlatency kernel used by default under Tango Studio. I have now replaced it by the new (Jan 29th, 2011) realtime kernel in Tango Studio and... no more xruns! (sample/period 256, 48000 Hz, 3 period/buffer, jackd priority 68). The latency is still a little bit high (16ms) but it is the best I ever had, so... (trying to decrease samples, or increase freq result in a few xruns anew).
Thanks again,
G.
Problems in AVLinux
Hi, I'm using the latest AVLinux version (I downloaded it yesterday from the official page) after having many struggles with other distributions to set up my Saffire Pro 24, but I still can't get FFADO to work. I've gone through all the steps, and I think I have the latest firmware version (I upgraded it a few months ago, but my Windows partition is messed up currently so I can't check if it is the latest). It seems that the FFADO D-Bus service doesn't detect my firewire adapter, or something like that... I'm quite a noob in music production with Linux (and in Linux in general), so I'm not sure what is the problem. Here is the information I thought would be useful:
chema@chema-pc:~$ groups
chema dialout cdrom floppy audio video plugdev netdev powerdev
#My user belongs to groups 'audio' and 'video'.
chema@chema-pc:~$ lsmod|grep 1394
raw1394 20472 0
ohci1394 25948 0
ieee1394 75188 2 raw1394,ohci1394
#Module raw1394 loads correctly at startup, or so I think. I tried 'modprobe raw1394', nothing changed.
chema@chema-pc:~$ lspci|grep 1394
04:07.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A IEEE-1394a-2000 Controller (PHY/Link)
#My Firewire adapter is recognised by the operating system (isn't it?).
chema@chema-pc:~$ cat /etc/udev/rules.d/60-raw1394.rules
KERNEL=="raw1394", GROUP="audio"
#I added that rule to udev after looking it up on some forum. No luck.
chema@chema-pc:~$ ffado-test ListDevices
-----------------------------------------------
FFADO test and diagnostic utility
Part of the FFADO project -- www.ffado.org
Version: 2.999.0-
(C) 2008, Daniel Wagner, Pieter Palmers
This program comes with ABSOLUTELY NO WARRANTY.
-----------------------------------------------
no message buffer overruns
#FFADO does not recognise my Saffire.
chema@chema-pc:~$ ffado-dbus-server
-----------------------------------------------
FFADO Control DBUS service
Part of the FFADO project -- www.ffado.org
Version: 2.999.0-
(C) 2008, Pieter Palmers
This program comes with ABSOLUTELY NO WARRANTY.
-----------------------------------------------
00689665173: (ffado-dbus-server.cpp)[ 270] main: Discovering devices...
00689787030: Fatal (devicemanager.cpp)[ 191] initialize: No firewire adapters (ports) found.
00689787079: Error (ffado-dbus-server.cpp)[ 277] main: Could not initialize device manager
00689787151: Debug (ffado-dbus-server.cpp)[ 202] exitfunction: Debug output flushed...
no message buffer overruns
#The D-Bus service cannot find my Firewire adapter.
chema@chema-pc:~$ ffado-mixer
-----------------------------------------------
FFADO Control DBUS service
Part of the FFADO project -- www.ffado.org
Version: 2.999.0-
(C) 2008, Pieter Palmers
This program comes with ABSOLUTELY NO WARRANTY.
-----------------------------------------------
00694601893: (ffado-dbus-server.cpp)[ 270] main: Discovering devices...
00694730036: Fatal (devicemanager.cpp)[ 191] initialize: No firewire adapters (ports) found.
00694730294: Error (ffado-dbus-server.cpp)[ 277] main: Could not initialize device manager
00694730346: Debug (ffado-dbus-server.cpp)[ 202] exitfunction: Debug output flushed...
no message buffer overruns
00:08:30 logginghandler ERROR Could not communicate with the FFADO DBus service...
PanelManager.__del__()
Exception AttributeError: "'PanelManager' object has no attribute 'polltimer'" in ignored
#ffado-mixer does not work because of the D-Bus service.
Thank you very much to those who take the time to read this. Any help is appreciated.
AVLinux version?
What version of AVLinux are you using? I have used the Pro24 with AVLinux 4.1 and 4.2, but with 4.2 you must revert to the 4.1 kernel (2.6.31.12-rt21-avlinux-realtime-pae-rev3) because the Pro24 does not work (completely) with the new firewire stack in the Liquoix kernel used by AVLinux 4.2. At least, I think that the Pro24 has the same problem with as the Pro40 (see the FFADO page), in that playback does not work, but recording does.
You can start the d-bus service by hand with this command: ffado-dbus-server. See if that improve things (though normally you should not have to start it by hand, so there must be another problem).
Finally fully working
After some troubles I finally have my system using fully my Saffire pro 24.
First I struggled with the firewire controller. Here are the results:
VIA Technologies Inc. IEEE 1394 Host Controller (rev 46) => NOT working
Agere L-FW323-06 => Working
VIA Technologies, Inc. Device 3403 (on my new MOBO) => Working
My next problem was using the alsa softwares. The simple alsa to jack plugin (using asoundrc) was ok but my favourite music player cmus was kinda crashing. But overall it's satisfying.
http://alsa.opensrc.org/index.php/Jack_%28plugin%29
I tried also the solution of the alsa-jack bridge but it is fairly complicated and wasn't stable on my system.
http://alsa.opensrc.org/index.php/Jack_and_Loopback_device_as_Alsa-to-Ja...
Luckily the sound card on my new MOBO has an SPDIF output. I plugged it into the SPDIF input of the Saffire and now my alsa applications use alsa, the sound is redirected to the Saffire hardware style and everything works smoothly. :-)
Thanks for developing FFADO !
New firmware
It does not work with the new firmware :
01694722311: Warning (dice_eap.cpp)[1398] read: No routes found. Base 0x7, offset 0x4000
01694750311: Warning (dice_eap.cpp)[ 881] updateNameCache: What is this function about?
01694752366: Error (saffire_pro24.cpp)[ 114] discover: This is a Focusrite Saffire Pro24 but not the right firmware. Better stop here before something goes wrong.
01694752385: Error (saffire_pro24.cpp)[ 115] discover: This device has firmware 0x10008 while we only know about version 0x10004.
01694752402: Error (devicemanager.cpp)[ 632] discover: could not discover device
I don't know what I have to do... Downgrade the firmware? :(
I edited the
I edited the saffire_pro24.cpp to modify the condition so it accepts the 0x10008 firmware, and it seems to work!
I changed « if (tmp[0] != 0x00010004 ) » to « if (tmp[0] != 0x00010008 ) ».
Happy go lucky :)
Hey, thanks for that clue. That did the trick for me.
I have the dsp version, so in order to get the ffado-mixer working I edited the saffire_dice.py and changed line:
if self.configrom.getModelName() == "SAFFIRE_PRO_24"
to
if self.configrom.getModelName() == "SAFFIRE_PRO_24DSP"
I can't really tell if the mixer works as expected on the DSP cause I've just started playing with it.
Cheers for the effort on getting the DICE chip support in FFADO. Awesome.
Great!
Hey...!
I just wanted to say thanks to everyone working on ffado. I just got my saffire pro 24 to work on ubuntu 10.04.
So.... great work, guys! Thanks for that!
Works on AVLinux!
I just got a Focusrite Saffire PRO 24 and it works more or less out-of-the-box on AVLinux 4.0 (http://www.bandshed.net/AVLinux.html) by virtue of the fact that AVLinux contains a recent SVN version of ffado. I did have to update the firmware (on other OS) and add raw1394 to /etc/modules (to automatically load raw1394 at boot). After that it worked(!). Now I have to figure out how to use ffado-mixer. What is the information on "Matrix" page?
Which application should I use to record?
Thanks to you and Google, I finally managed to install ffado and jackd and make my saffire pro 40 work ( I still can believe) !!
Now the last step is to capture the 8 microphone signals and write each of them in a different audio file. I mean since I have 8 microphone here, I need to assign an audio file to each microphone stream and write its audio stream in it.(For further processing one should have access to each microphone stream instead of their combination so it is not allowed to mix all 8 signals together and write them in one file).
Now The question is, which application can I use to record these audio signals from jack except ardour which it seems can´t be controlled from command line and konsole??
Cheers
recording apps
You can use any jack-aware recording app you like. Please forgive us for not extensively helping on that (very wide!) subject. A better place to ask is the linux-audio-users list at http://lists.linuxaudio.org/listinfo/linux-audio-user
Can´t hear anything
Hi
Thanks. I found some useful app for recording. But a problem has still remained. It seems my routing in ffado-mixer is wrong and there is no signal coming in Ardour or any other recording app.
So would you please specifically let me know what routing configuration should be set in ffado-mixer? Since it says you can just assign one source to each destination, how can i send 8 microphone signals (that I guess they are analog:00-07)to 1394:00 port?
BTW, what is this matrixmixer? should I change its values?
I have no idea about this routing. Thanks in advance for helping me.
Cheers
Routing
In the router you select a source for each destination. The current interface isn't optimal, a better one is in the pipeline... So for recording the first 8 analogue inputs you would choose them as sources for the '1394' destination. To the best of my knowledge this is also the default after you connected the device in windows.
So it should basically just work. Just to be sure: You do see a huge list of system:capture_* and system:playback_* when you run "jack_lsp" while jackd is running?
The matrix-mixer is really just needed when you also want to listen to the signals without feeding them through your computer.
Thanks
Finally I succeeded to install ffado and record from 8 channels. Thanks for your wonderful support
Compilation issue (Ubuntu 10.04 64Bit, gcc 4.4.3)
I am trying to compile ffado lib for my updated Linux box (distro Ubuntu 10.04 64bit), It is complaining about c++ compiler. I think I have got all needed dependencies I didn't have this problem on 9.04). Output:
abc@abc:~/Documents/source/ffado-svn/libffado$ scons
scons: Reading SConscript files ...
scons: warning: The Options class is deprecated; use the Variables class instead.
File "/home/daniel/Documents/source/ffado-svn/libffado/SConstruct", line 38, in
scons: warning: The BoolOption() function is deprecated; use the BoolVariable() function instead.
File "/home/daniel/Documents/source/ffado-svn/libffado/SConstruct", line 43, in
scons: warning: The PathOption() function is deprecated; use the PathVariable() function instead.
File "/home/daniel/Documents/source/ffado-svn/libffado/SConstruct", line 45, in
scons: warning: The EnumOption() function is deprecated; use the EnumVariable() function instead.
File "/home/daniel/Documents/source/ffado-svn/libffado/SConstruct", line 73, in
Checking for a working C-compiler (cached) yes
Checking for a working C++-compiler no
It seems as if your system isn't even able to compile any C-/C++-programs. Probably you don't have gcc and g++ installed. Compiling a package from source without a working compiler is very hard to do, please install the needed packages.
Hint: on *ubuntu you need both gcc- and g++-packages installed, easiest solution is to install build-essential which depends on gcc and g++.
gcc/g++ confitmation
abc@abc:~/Documents/source/ffado-svn/libffado$ g++ -v
Using built-in specs.
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 4.4.3-4ubuntu5' --with-bugurl=file:///usr/share/doc/gcc-4.4/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --enable-shared --enable-multiarch --enable-linker-build-id --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.4 --program-suffix=-4.4 --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug --enable-plugin --enable-objc-gc --disable-werror --with-arch-32=i486 --with-tune=generic --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5)
Any reason why does it not work?
You probably installed g++
You probably installed g++ after your first compilation attempt.
Please wipe scons' cache by doing "rm -Rf .scon* cache/conf* cache/objects" and then try again. If that still fails, please take a look at cache/config.log and if that doesn't give you a clue, let us take a look at it.
ffado-mixer won't display
Greetings! When I launch ffado-mixer (with or without JACK running) I get the following. Any ideas on what/how to fix? Otherwise, my Focusrite Saffire Pro 24 seems to be working with Ardour! Thanks :)
22:35:12 dbus DEBUG connecting to: Updated on /org/ffado/Control/DeviceManager (server: org.ffado.Control)
22:35:12 panelmanager DEBUG PanelManager::updatePanels()
22:35:12 panelmanager DEBUG going to add 00130e0401c00c02
22:35:12 panelmanager DEBUG Adding device 0: 00130e0401c00c02
22:35:12 panelmanager DEBUG Found (00130e0401c00c02, 130E, 7) Focusrite SAFFIRE_PRO_24
22:35:12 registration DEBUG version/GUID combo already registered
Traceback (most recent call last):
File "/usr/local/lib/python2.5/site-packages/ffado/panelmanager.py", line 333, in updatePanels
""" % (mixerapp.lower(), mixerapp.lower(), mixerapp) )
File "", line 2, in
File "/usr/local/lib/python2.5/site-packages/ffado/mixer/saffire_dice.py", line 168, in
class MonitoringDelegate(QtGui.QStyledItemDelegate):
AttributeError: 'module' object has no attribute 'QStyledItemDelegate'
Looks as if your version of
Looks as if your version of Qt is to old. The QStyledItemDelegate was introduced in Qt4.4, which version do you have installed? And what distribution?
Thanks for the help; I
Thanks for the help; I believe I have version 4.3.4 installed through repositories.
I'm running Ubuntu 8.04 with kernel 2.6.24-27. I have the following packages related to "qt":
dpkg -l | grep qt
ii avidemux-qt 1:2.4.1-0.0ubuntu1
ii libavahi-qt3-1 0.6.22-2ubuntu4.1
ii libdbus-qt-1-1c2 0.62.git.20060814-2build1
ii libdbus-qt-1-dev 0.62.git.20060814-2build1
ii libqt3-headers 3:3.3.8-b-0ubuntu3
ii libqt3-mt 3:3.3.8-b-0ubuntu3
ii libqt3-mt-dev 3:3.3.8-b-0ubuntu3
ii libqt4-core 4.3.4-0ubuntu3.1
ii libqt4-dev 4.3.4-0ubuntu3.1
ii libqt4-gui 4.3.4-0ubuntu3.1
ii libqt4-qt3support 4.3.4-0ubuntu3.1
ii libqt4-sql 4.3.4-0ubuntu3.1
ii libqthreads-12 1.6.8-6ubuntu1
ii pyqt-tools 3.17.4-1ubuntu4
ii pyqt4-dev-tools 4.3.3-2ubuntu4.1
ii python-qt4 4.3.3-2ubuntu4.1
ii python-qt4-common 4.3.3-2ubuntu4.1
ii python-qt4-dbus 4.3.3-2ubuntu4.1
ii python-qt4-dev 4.3.3-2ubuntu4.1
ii qt3-dev-tools 3:3.3.8-b-0ubuntu3
ii qt4-designer 4.3.4-0ubuntu3.1
ii qt4-dev-tools 4.3.4-0ubuntu3.1
ii qt4-qtconfig 4.3.4-0ubuntu3.1
Is this possibly due to having QT3 and QT4 installed simultaneously? I need QT3 for a lot of apps, I think (e.g. Hydrogen).
When I run ffado-diag I see prerequisite determined disappointingly (for both run-time and static):
PyQt............... Python User Interface Compiler 3.17.4 for Qt version 3.3.8b
No, the problem is solely
No, the problem is solely that the StyledItemDelegate is only present in Qt4.4 or higher, not in the 4.3 you have installed. Can you create a ticket for this so I won't forget it?
And on a side-note, can you also create a ticket for the ffado-diag tool to check for the correct version of PyQt?
Thanks.
Ok, two tickets created and
Ok, two tickets created and assigned to you.
Thanks for the help, in the meantime I've downloaded the latest Qt source tarball and if time allows, I may freeze/lock my repository version and replace/update some files from the tarball.
I built and installed the
I built and installed the latest QT (not sure if it really overwrote my existing files from repository packages) and tried rebuilding trunk revision 1817... still didn't work. Then I copied all the includes from the latest QT into /usr/include/qt4 and overwrote the old ones, then rebuilt ffado... still the same problem.
When launching ffado-mixer, there are also the following errors, they come before the panelmanager updates:
(:20126): GLib-GObject-WARNING **: IA__g_object_set_valist: object class `GtkMenuItem' has no property named `label'
(:20126): GLib-GObject-WARNING **: IA__g_object_set_valist: object class `GtkCheckMenuItem' has no property named `label'
I've done a complete cleanup
I've done a complete cleanup of all my QT files and re-installed the repository packages (versions as above), and I've done a fresh build of rev 1827. Here's the results of my attempt at ffado-mixer:
18:44:25 dbus DEBUG connecting to: Updated on /org/ffado/Control/DeviceManager (server: org.ffado.Control)
18:44:25 panelmanager DEBUG PanelManager::updatePanels()
18:44:25 panelmanager DEBUG going to add 00130e0401c00c02
18:44:25 panelmanager DEBUG Adding device 0: 00130e0401c00c02
18:44:25 panelmanager DEBUG Found (00130e0401c00c02, 130E, 7) Focusrite SAFFIRE_PRO_24
18:44:25 registration DEBUG version/GUID combo already registered
18:44:25 matrixmixer DEBUG Mixer has 16 rows and 18 columns
Traceback (most recent call last):
File "/usr/local/lib/python2.5/site-packages/ffado/panelmanager.py", line 349, in updatePanels
mixerwidget.buildMixer()
File "/usr/local/lib/python2.5/site-packages/ffado/mixer/saffire_dice.py", line 207, in buildMixer
Generic_Dice_EAP.buildMixer(self)
File "/usr/local/lib/python2.5/site-packages/ffado/mixer/generic_dice_eap.py", line 46, in buildMixer
self.router = CrossbarRouter(self.hw.servername, self.hw.basepath+"/EAP/Router", self)
File "/usr/local/lib/python2.5/site-packages/ffado/widgets/crossbarrouter.py", line 154, in __init__
self.vubtn.setChecked(self.settings.value("crossbarrouter/runvu", False).toBool())
TypeError: argument 2 of QSettings.value() has an invalid type
Will I be successful at running ffado-mixer if I am successful at installing the latest version of QT? It's a massive build/install... Thanks :)
Hmph, more functions that
Hmph, more functions that where added in newer versions of Qt.
Can you please try to compile the current versions on your own? Or maybe look for ppa- or overlay-repositories shipping the newer versions.
Ok, thanks, I'll come back
Ok, thanks, I'll come back to this in a week or two, currently doing a recording project (with FFADO svn/trunk as it is, without mixer, working stable and good, thanks).
How could you record without mixer
Hi
I'm not a musician and actually not knowing too much about audio interfaces. However, during one academic project, I found it is very useful to use these interfaces to simultanously connect 8 microphones to computer instead of building microphone arryas from the scratch. Now PROBLEM is, I couldn't install ffado-mixer. So it was very interesting for me that how could you start recording without using ffado-mixer? Is there any way to initialize the device parameters such as sampling rate by some commands and then start to read from firewire by a matlab or java program?
Cheers
recording without mixer
The standard setup will probably already do what you want as the analog (and spdif and adat) inputs are routed both to the mixer and to the firewire.
But you can only use ffado with jack for recording. And plain reading from firewire is not as easy as reading from serial console...
Quick question, is there any
Quick question, is there any way I can do the following without ffado-mixer?
a) get the driver to sync clocksource to external (spdif through optical), and
b) get the driver to accept spdif instead of ADAT over the optical?
Many thanks!
No, this things are really
No, this things are really only configurable via the mixer. But if you want that as the static "always on" configuration, you can do that in the official software on the other OS and save it as default to the device.
I wish I would have known
I wish I would have known this during my last recording project (when I asked the question on optical spdif)...
ffado-test Discover (to show the node and active clock source, among other things)
ffado-test -n 0 SetClockSource 2 (to set active clock source to SPDIF OPT)
ffado-test -n 0 SetClockSource 12 (to set to focusrite internal clock source)
It's imperative to have the clock source set to the external converter when recording spdif from said external converter, else you'll get popping.
I found I can change the clock source to SPDIF OPT this way before running JACK, and then JACK messages confirmed that I was using 0x2 (ID 2) instead of OxC (ID 12).
How embarrassing, I've just
How embarrassing, I've just realized that my previous post has exact same error as a few posts back... sorry! Even though I did upgrade to QT4.4.x in between. As you suggested on May 12, I'll search for later versions through other repositories, else I'll have to do the *big build* of the 4.6.2 libs from Nokia, and possibly build my own Skype (and whatever else that breaks).
Thanks again! That sorta
Thanks again! That sorta worked (optical spdif yes, external sync no) but it's off-topic.
I found QT4.4 in Hardy Backports repositories; I tried this instead of building the latest source again. Last time I built the latest source it took overnight and it broke my Skype, so I'm keen to try ready-built. So, after installing all the QT4.4 packages, I rebuilt revision 1827 and tried ffado-mixer; here's what I got:
20:01:28 panelmanager DEBUG Found (00130e0401c00c02, 130E, 7) Focusrite SAFFIRE_PRO_24
20:01:28 registration DEBUG version/GUID combo already registered
20:01:28 matrixmixer DEBUG Mixer has 16 rows and 18 columns
CrossbarRouter.__del__()
Exception exceptions.TypeError: 'argument 2 of QSettings.setValue() has an invalid type' in ignored
20:01:31 panelmanager DEBUG devlistPostUpdate failed (9)
20:01:33 panelmanager DEBUG PanelManager::updatePanels()
20:01:33 panelmanager DEBUG going to add 00130e0401c00c02
20:01:33 panelmanager DEBUG Adding device 0: 00130e0401c00c02
20:01:33 panelmanager DEBUG Found (00130e0401c00c02, 130E, 7) Focusrite SAFFIRE_PRO_24
20:01:33 registration DEBUG version/GUID combo already registered
20:01:34 matrixmixer DEBUG Mixer has 16 rows and 18 columns
CrossbarRouter.__del__()
Exception exceptions.TypeError: 'argument 2 of QSettings.setValue() has an invalid type' in ignored
.... (many repeats of above before final output below) ....
SAFFIRE_PRO_24
20:02:40 registration DEBUG version/GUID combo already registered
20:02:40 matrixmixer DEBUG Mixer has 16 rows and 18 columns
Traceback (most recent call last):
File "/usr/local/lib/python2.5/site-packages/ffado/panelmanager.py", line 349, in updatePanels
mixerwidget.buildMixer()
File "/usr/local/lib/python2.5/site-packages/ffado/mixer/saffire_dice.py", line 207, in buildMixer
Generic_Dice_EAP.buildMixer(self)
File "/usr/local/lib/python2.5/site-packages/ffado/mixer/generic_dice_eap.py", line 46, in buildMixer
self.router = CrossbarRouter(self.hw.servername, self.hw.basepath+"/EAP/Router", self)
File "/usr/local/lib/python2.5/site-packages/ffado/widgets/crossbarrouter.py", line 154, in __init__
self.vubtn.setChecked(self.settings.value("crossbarrouter/runvu", False).toBool())
TypeError: argument 2 of QSettings.value() has an invalid type
Just did a complete QT4.4
Just did a complete QT4.4 cleanup and compiled/built (overnight) QT4.6.2.
I tried rebuilding ffado-svn revisions 1827 and 1839.
I am compiling with: scons DEBUG=True ENABLE_DICE=True ENABLE_OPTIMIZATIONS=True.
In either case, I get what appears to be the same error when I try to launch the mixer:
$ ffado-mixer
(:9609): GLib-GObject-WARNING **: IA__g_object_set_valist: object class `GtkMenuItem' has no property named `label'
(:9609): GLib-GObject-WARNING **: IA__g_object_set_valist: object class `GtkCheckMenuItem' has no property named `label'
13:16:58 dbus DEBUG connecting to: Updated on /org/ffado/Control/DeviceManager (server: org.ffado.Control)
13:16:58 panelmanager DEBUG PanelManager::updatePanels()
13:16:58 panelmanager DEBUG going to add 00130e0401c00c02
13:16:58 panelmanager DEBUG Adding device 0: 00130e0401c00c02
13:16:58 panelmanager DEBUG Found (00130e0401c00c02, 130E, 7) Focusrite SAFFIRE_PRO_24
13:16:58 registration DEBUG version/GUID combo already registered
13:16:59 matrixmixer DEBUG Mixer has 16 rows and 18 columns
Traceback (most recent call last):
File "/usr/local/lib/python2.5/site-packages/ffado/panelmanager.py", line 349, in updatePanels
mixerwidget.buildMixer()
File "/usr/local/lib/python2.5/site-packages/ffado/mixer/saffire_dice.py", line 207, in buildMixer
Generic_Dice_EAP.buildMixer(self)
File "/usr/local/lib/python2.5/site-packages/ffado/mixer/generic_dice_eap.py", line 46, in buildMixer
self.router = CrossbarRouter(self.hw.servername, self.hw.basepath+"/EAP/Router", self)
File "/usr/local/lib/python2.5/site-packages/ffado/widgets/crossbarrouter.py", line 154, in __init__
self.vubtn.setChecked(self.settings.value("crossbarrouter/runvu", False).toBool())
TypeError: argument 2 of QSettings.value() has an invalid type
On the side, I'd be happy to skip the mixer for now if I could just set the clock source to SPDIF Optical.
It's clear from dice_defines.h, and from the output of Dice ShowDevice(), that the clock source I want
is 0x02 (integer 2).
I tried forcing it with "idx = 2;" after the declaration ClockSelect::select(int idx) in ClockSelect.cpp
but that didn't work; still defaults to internal clock source 0x0C.
I also thought to try forcing it in Dice setActiveClockSource(clocksource s) but it's gonna take
me a while to understand these datatypes (clocksource, fb_quadlet_t).
How do I change firmware?
Just got my Focusrite Sapphire Pro 24 today, and just finished building FFADO from SVN trunk, doing permissions, rebuilding JACK, etc. ffado-mixer works without errors, but interface is not found, so I did a
./ffado-test Discover
and found the following in the mix:
00773592349: Debug (Configuration.cpp)[ 163] showSetting: Group: (null)
00773592395: Debug (Configuration.cpp)[ 185] showSetting: vendorid = 4878 (0x0000130E)
00773592431: Debug (Configuration.cpp)[ 185] showSetting: modelid = 7 (0x00000007)
00773592472: Debug (Configuration.cpp)[ 209] showSetting: vendorname = Focusrite
00773592508: Debug (Configuration.cpp)[ 209] showSetting: modelname = Saffire PRO 24
00773592547: Debug (Configuration.cpp)[ 185] showSetting: driver = 20 (0x00000014)
00773592582: Debug (Configuration.cpp)[ 209] showSetting: mixer = Saffire_Dice
00773704546: Warning (dice_eap.cpp)[ 881] updateNameCache: What is this function about?
00773706207: Error (saffire_pro24.cpp)[ 114] discover: This is a Focusrite Saffire Pro24 but not the right firmware. Better stop here before something goes wrong.
00773706282: Error (saffire_pro24.cpp)[ 115] discover: This device has firmware 0x10002 while we only know about version 0x10004.
00773706318: Error (devicemanager.cpp)[ 632] discover: could not discover device
00773719771: Debug (devicemanager.cpp)[ 665] discover: Discovery finished...
How do I change my firmware? Do I need to find a Windows or Mac machine, install the software, and I will see a firmware-writing option/util? Hoping a neighbor will let me install this stuff on their machine, as I have no Mac or Windows at this time.
Thanks!
Sorry for the late
Sorry for the late reply...
Yes, you need a windows or mac machine to update the firmware trough the official driver. The only alternative would be the development tools from tc itself, but I am told these run on windows only too.
Could not start streaming threads
I compiled ffado from svn/trunk, and also compiled jackd. My Saffire PRO 24 seems recognized with "ffado-test Discover" of "ffado-test ListDevices":
ffado-test ListDevices
-----------------------------------------------
FFADO test and diagnostic utility
Part of the FFADO project -- www.ffado.org
Version: 2.999.0-1807M
(C) 2008, Daniel Wagner, Pieter Palmers
This program comes with ABSOLUTELY NO WARRANTY.
-----------------------------------------------
=== 1394 PORT 0 ===
Node id GUID VendorId ModelId Vendor - Model
0 0x00130e0401c00f89 0x0000130E 0x00000007 Focusrite - SAFFIRE_PRO_24
1 0x0017fb340000e0f4 0x000017FB 0x00000000 Linux - ohci1394 -
no message buffer overruns
But using qjackctl gives me errors:
JACK compiled with System V SHM support.
loading driver ..
00770280213: (ffado.cpp)[ 92] ffado_streaming_init: libffado 2.999.0-1807M built Apr 3 2010 23:32:45
00770674067: [Warning (dice_eap.cpp)[1398] read: No routes found. Base 0x7, offset 0x4000
00770706026: [Warning (dice_eap.cpp)[ 881] updateNameCache: What is this function about?
00770829523: (dice_avdevice.cpp)[ 625] showDevice: DICE Parameter Space info:
00770829537: (dice_avdevice.cpp)[ 626] showDevice: Global : offset=0x0028 size=0360
00770829543: (dice_avdevice.cpp)[ 627] showDevice: TX : offset=0x0190 size=0568
00770829547: (dice_avdevice.cpp)[ 628] showDevice: nb= 1 size=0280
00770829552: (dice_avdevice.cpp)[ 629] showDevice: RX : offset=0x03C8 size=1128
00770829556: (dice_avdevice.cpp)[ 630] showDevice: nb= 1 size=0280
.../...
00770874829: (dice_avdevice.cpp)[ 739] showDevice: Channel names :
00770874845: (dice_avdevice.cpp)[ 744] showDevice: Mon 1
00770874853: (dice_avdevice.cpp)[ 744] showDevice: Mon 2
00770874861: (dice_avdevice.cpp)[ 744] showDevice: Line 3
00770874874: (dice_avdevice.cpp)[ 744] showDevice: Line 4
00770874881: (dice_avdevice.cpp)[ 744] showDevice: Line 5
00770874894: (dice_avdevice.cpp)[ 744] showDevice: Line 6
00770874901: (dice_avdevice.cpp)[ 744] showDevice: SPDIF L
00770874914: (dice_avdevice.cpp)[ 744] showDevice: SPDIF R
firewire ERR: Could not start streaming threads: -1
DRIVER NT: could not start driver
cannot start driver
no message buffer overruns
I would appreciate any help
Please provide logs as
Please provide logs as indicated in the README files. You can then create a bug-report or contact us on the mailinglists. These comments here are probably not good to post big files...
From the output I can't even guess what is wrong. But something is working as it detects the device...
Saffire Pro Adat
It would great to get some confirmation whether the adat part of this device is working. 16 inputs is just what I'm looking for. I had my eye on the "pro 26", but I don't need that many channels.
Thanks, Ailo.
adat
I don't have an actual adat device to connect. But from the drivers side all is working. You can route the adat inputs whereever you want in ffadomixer, directly the outputs (rendering the device into a plain adat-analog-converter, into the mixer or into the firewire-stream...
If you really find that its not working, we can try to fix it. But I am pretty sure that adat will be working as fine as spdif input (which is working fine here).