Saffire PRO 40
Submitted by ppalmers on Sun, 12/21/2008 - 16:23.
Manufacturer:
Focusrite
Device Info on Vendor Site:
Support Status:
ExperimentalSupport Contact(s):
ppalmersThis device is NOT supported in 2.0. It was included in the 2.1 release that introduced DICE support.
A user (Jannis Pohlmann) has reported that a firewire host interface based on the VIA VT6315 chipset is not suitable for running this device at 88.2 kHz. The Pro40 worked fine with the same computer when a Texas Instruments XIO2213 based firewire card was used instead.
Damien has provided a tutorial which walks through his experiences with this device. It's currently available only in French: Audio details, Using ffado-mixer.
12.04 configuration problems
I had installed my saffire pro40 per the instructions on: http://www.audiorecording.me/focusrite-saffire-pro-40-in-ubuntu-11-10-in... and everything appeared to be working, however somehow I got confused in configuring the internal routing of the device and now get: a) no LED bars moving with mic inputs on the front of the unit b) no mic monitor output and c) a high-pitched noise on the output of the device.
I am under the saaumption that my problems are the result of an incorrect internal route configuration... Unfortunatley I don't have a windows install handy to restore the rout settings... (this would make for a swell feature in ffado-mixer)
I see that in the SVN of the ffado driver, we get the set-default... program, which I may interprate as a utility to restore the internal settings of the device, so I made a paralell install using scons (yuck) and ran the set-default utility. I get the following output:
set-default-router-config-dice-eap --samplerate=48000 --port=fw100
001496964251: Warning (ieee1394service.cpp)[ 375] initialize: Could not set SPLIT_TIMEOUT to min requested (1000000)
01496964277: Warning (ieee1394service.cpp)[ 379] initialize: Set SPLIT_TIMEOUT to min requested (1000000) did not succeed
01497234879: Warning (dice_eap.cpp)[1398] read: No routes found. Base 0x7, offset 0x4000
01497269889: Warning (dice_eap.cpp)[ 881] updateNameCache: What is this function about?
DICE Parameter Space info:
Global : offset=0x0028 size=0360
TX : offset=0x0190 size=0568
nb= 2 size=0280
RX : offset=0x03C8 size=1128
nb= 2 size=0280
UNUSED1 : offset=0x0830 size=0016
UNUSED2 : offset=0x0000 size=0000
Global param space:
Owner : 0x00000000FFFF0000
Notification : 0x00000040
Nick name : Pro40-0071ee
Clock Select : 0x02 0x0C
Enable : false
Clock Status : locked 0x02
Extended Status : 0x00000000
Samplerate : 0x0000BB80 (48000)
Version : 0x01000400
Version : 0x01000400 (1.0.4.0)
Clock caps : 0x1325001E
Clock sources :
SPDIF
AES34
SPDIF-OPT
AES78
AES-ANY
ADAT
ADAT_AUX
Word Clock
Unused
Unused
Unused
Unused
Internal
TX param space:
Nb of xmit : 2
Transmitter 0:
ISO channel : -1
ISO speed : 2
Nb audio channels : 10
Nb midi channels : 1
AC3 caps : 0x00000000
AC3 enable : 0x00000000
Channel names :
IP 1
IP 2
IP 3
IP 4
IP 5
IP 6
IP 7
IP 8
SPDIF L
SPDIF R
Transmitter 1:
ISO channel : -1
ISO speed : 2
Nb audio channels : 10
Nb midi channels : 0
AC3 caps : 0x00000000
AC3 enable : 0x00000000
Channel names :
ADAT 1
ADAT 2
ADAT 3
ADAT 4
ADAT 5
ADAT 6
ADAT 7
ADAT 8
Loop 1
Loop 2
RX param space:
Nb of recv : 2
Receiver 0:
ISO channel : -1
Sequence start : 0
Nb audio channels : 12
Nb midi channels : 1
AC3 caps : 0x00000000
AC3 enable : 0x00000000
Channel names :
Mon 1
Mon 2
Line 3
Line 4
Line 5
Line 6
Line 7
Line 8
Line 9
Line 10
SPDIF L
SPDIF R
Receiver 1:
ISO channel : -1
Sequence start : 0
Nb audio channels : 8
Nb midi channels : 0
AC3 caps : 0x00000000
AC3 enable : 0x00000000
Channel names :
ADAT 1
ADAT 2
ADAT 3
ADAT 4
ADAT 5
ADAT 6
ADAT 7
ADAT 8
01497443672: (set-default-router-config-dice-eap.cpp)[ 243] main: device supports EAP
set-default-router-config-dice-eap01497445283: (set-default-router-config-dice-eap.cpp)[ 260] main: Initial configuration
: symbol lookup error: set-default-router-config-dice-eap: undefined symbol: _ZN4Dice3EAP14showFullRouterEv
When re-opening the ffado-mixer, I see no changes in the router configuration.
p.s.
I am aware that it may not be a good idea to have paralell installations of the ffado drivers (from package manager, and installed from source) however, I could not get qjackctl to install without bringing along the ubuntu official versions of libffado, etc... (package manager ignored my custom install)
Is there a way to restore the device's internal settings? Is there a source where I can look them up and restore them by hand?
Also: these captchas are really hard!
Working Out of Box
FYI, today I installed my PCIe firewire card and the Saffire Pro 40 worked out of the box without any extra configuration. I also have a Lexicon Omega (years old) and was using that to record so of course had my studio setup to use that (software, jackd2, etc.) I looked at this http://www.audiorecording.me/focusrite-saffire-pro-40-in-ubuntu-11-10-in... and was about to try this, but then I decided to make sure that it didn't work before (lucky me) and found that it does work. I installed no other software other than the software that was installed previously for use with my Lexicon Omega.
I wish my Tascam US-2000 would work, but it never will.. screw TaSCAM never support them! I only purchased as I misread somewhere that is would work on Linux... I can say that preliminary tests (only started working with the Saffire Pro 40 today) place the Pro 40's sound WAAAAAY above the sound of the US-2000. Try a fresh install with default Ubuntu Studio packges, this may hold som benefit for you. I apologize if for some reason I am off topic or if this is useless...
THANKS FFADO! I will be supporting the devs!
Happily,
Stancliff of Buxley
Focusrite Saffire Pro 40
Ubuntu 12.04
Works out of box!
... Gonna try other versions now!
http://thebuxleys.com
Not so much
Focusrite Saffire Pro 40
Ubuntu 12.04
Works out of box!
... Gonna try other versions now!
http://thebuxleys.com
So after further investigation the meters don't seem to assign/route properly. Sorry for the premature post! Note that I am using the stock version of FFADO that comes with Ubuntu 12.04. I will test soon a compiled verson from this website as-well-as a "nightly" or SVN version. I will note this post after.
StanObuX
Please refer to what is
Please refer to what is indicated at the beginning of the page. Pro 40 is intended to be supported by release 2.1 of ffado. Using previous trunk versions (as is probably the case from your installed Ubuntu 12.04) will lead to unsupported behaviours, mainly corrected in the 2.1 release.
Now, if you would like additional features, refer to the latest trunk version (see Download section).
And suscribing to the users list would probably be a fruitful idea :-)
Phil
Re: 12.04 configuration problems (saffire pro40)
For the device-specific questions I'll have to defer to those who actually have a Saffire. I can provide some answers to your more general questions though.
Having a look through your report it seems that your parallel install of two FFADO versions is probably having a negative effect. In particular, the "undefined symbol" report suggests strongly that you're picking up the set-default utility from the new install but it's linking at runtime to the old libffado on your system (only newer libffado has the showFullRouterEv() method - and other related methods - used to configure the routing on this device).
The usual way to get around this problem in the past has been to get the compiled-from-source FFADO to install "over the top" of the files provided by the system package manager. The package manager is happy because it thinks it's still installed, and the system is happy because it doesn't have two versions of FFADO floating around. Like most software, the default install location for FFADO is /usr/local/, while distributions almost always put it in /usr/. To override the install destination, one simply adds "PREFIX=/usr" to the scons command when building FFADO ("scons install" doesn't require it since scons caches custom options supplied by the user).
In your case, I expect you have the old FFADO (as supplied by 12.04) in /usr and the new one in /usr/local/. The first thing you'll want to do is remove the "new" install. You should be able to do this using "scons -c install". Once this is done, run "scons PREFIX=/usr" to set things up for installation into /usr, followed by "scons install" to do the actual installation. This should result in only a single copy of FFADO on your system: the newest version as compiled by you.
Having the library issue sorted will probably be enough to get set-default utility working, and that may in turn solve the routing issues you're having. If not, feel free to post back here and hopefully someone with a similar device can provide some feedback. I've added the device to the subject to increase the chances that the right people will notice it. :-)
Regarding the captchas: yes, I know. However, it's sadly proven necessary due to the high level of spam directed at our site. Even with the captcha spam does get through from time to time.
Thanks
Thanks for getting back to me...
I did what you said and uninstalled FFADO using scons, and reinstalling it with PREFIX=/usr, but now I get the following when I try to run 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.
-----------------------------------------------
Library version mismatch. (required: libffado 2.999.0-, present: libffado 2.999.0-2192)
Please run this application against the exact corresponding library
it was compiled for. The most common cause for this is having more
than one version of libffado installed.
no message buffer overruns
****************************************************
It seems something is unhappy with the overlapping installs...
Re: Thanks
It appears that for some odd reason the original distribution-supplied ffado-dbus-server binary is still in place on your system. We can tell this by the library version that it's wanting: "2.999.0-" compared to "2.999.0-2192". The latter version number is consistent with a newly installed library, so at least part of the process is working. That is, while you seem to have a new libffado on your system, at least some of the support programs (such as ffado-dbus-server) do not appear to have been built and installed.
I suspect the problem may be related to the lack of certain "devel" packages on your system. Ubuntu splits most libraries into two parts. One supplies the files required to run programs which use the library, while the separate "-devel" package contains additional files required to compile applications which use the library.
Since libffado itself is evidently built OK we can conclude that libraw1394-devel is installed on your system. The lack of a new ffado-dbus-server may be due to missing dbus-related "-devel" packages at compile time. You might be able to get a clue as to what's missing from the messages reported at the start of the "scons" process. During startup scons checks for prerequisities and reports any which seem to be missing. If the source of trouble isn't immediately obvious, perhaps post the output from "scons" up to the "scons: Building targets ..." line and we'll see if we can determine what the problem might be.
Actually there is one other thing to check: do "which ffado-dbus-server". If it's /usr/bin/ffado-dbus-server then that's fine: that is the location that ffado will install this into if "PREFIX=/usr" has been specified. If for some reason the distribution's put it in another place then ffado's "scons install" won't overwrite it, and we'll have to make some manual adjustments. I expect that the existing distribution-supplied ffado-dbus-server is in /usr/bin/, but with these things it's best to be sure.
Intermittant output at 96kHz, okay at 88.2kHz
Using svn-2171 with Jackd2 1.9.9, routing and audio work fine at 48kHz and 88.2kHz, but at 96kHz output is intermittant on all channels - sound will cycle on for a couple of seconds then off for about 10 seconds. Inputs and routing appear to work fine. Using a Ubuntu 12.04 distribution, generic kernel on an i7 with TI PCIe firewire adapter.
Also the front panel metering is not operational at any sample rate - just occasional random flickering of the bottom leds. (I believe these were working okay with the distribution's ffado/jack2 packages (ffado svn-2019) at 48kHz at least, but routing was not)
Re: Intermittant output at 96kHz, okay at 88.2kHz
Problems with the Saffire interfaces at 96 kHz are known but the cause is not yet clear. Someone is looking into this when time allows; as such I don't have an ETA as to when any sort of fix might be available. It's interesting that you're getting some audio output; my understanding is that for most people things simply don't work at all at 96 kHz. See ticket 326 for more details on this.
In relation to the front panel metering, I was under the impression that issues regarding these meters had been resolved - see ticket 347. Philippe (who has done work on the Saffire support recently) may have something to add about this.
Unfortunately I'll have to defer to others to fill in more details here as I don't have a Saffire device myself and as a result I'm not familiar with the DICE driver which is used with them.
Re: Intermittant output at 96kHz, okay at 88.2kHz
Up to now, i have nothing to add to Jonathan comment regarding Pro 40 at 96kHz; it does not work properly and it is quite disappointing since Pro 24 does.
Problems concerning leds have been solved some times ago. Nevertheless, a correct initial configuration of the "router" is required. This can be obtained by running a small utility like
set-default-router-config-dice-eap --samplerate=48000 --port=fw1
at 48000 and 96000 Hz.
Or if you prefer, by returning to hardware default under an other OS.
Regards,
Phil
Re: Intermittant output at 96kHz, okay at 88.2kHz
Thank you both for your responses - much appreciated. As it happens, I tried firing it up on a Windows box last night and restored defaults; the meters are now working nicely on Linux, but thanks for the tip on how to do it under FFado as it won't be so easy once the interface is in-situ.
Regarding 96kHz - I'm content to run at 88.2k until you find the problem. Are there any logs I can capture that would help?
Cheers, and keep up the good work!
- Dan
Re: Intermittant output at 96kHz, okay at 88.2kHz
I'm glad that the meters are sorted.
In terms of logs I'll have to defer to Phil again. I can't think of anything that would add to what we already know, but he may have something in mind.
ffado mixer
Hi there... I would like some help! I finally fix my focusrite saffire (white model) firewire connection, works in linux mint 12. My last problem is that I can not start the ffado mixer!
I've tried all the things that I found on the web about it, but nothing!
Please give me some advice! Thanks in advance!
George
Re: ffado mixer
To help you we'll need a few more details about what you're doing and how it's failing. From what you've written I assume that audio is now working for you but you can't run ffado-mixer. Is this correct?
Assuming the above is accurate, we note that ffado-mixer should be started using the simple command "ffado-mixer". Is this what you've been trying?
The next thing we need to know is what happens when you try to run ffado-mixer in terms of messages displayed to the terminal. The best way to deal with this is to run ffado-mixer in a terminal and post the full output produced. Also describe the general appearance of any GUI windows if they appear.
Complete tutorial on Saffire Pro 40 on Ubuntu 11.10
Hi,
I have finally been able to record and play from my Saffire Pro 40 in Ubuntu 11.10 using new Firewire stack. I also do some test recordings in Ardour and JACK and it's quite impressive.
I documented all my installation steps in this tutorial here: http://www.audiorecording.me/focusrite-saffire-pro-40-in-ubuntu-11-10-in...
I also include my JACK settings, etc. for reference. I hope that tutorial would be useful to those Saffire Pro 40 users that have not been able to successfully run their audio interface using new stack in Ubuntu 11.10.
Many thanks to the developers for the FFADO project!
Cheers,
Emerson
Pro 40/Pro 24 routing and mixer issues corrections
My preceeding post last week never appeared (indeed, this "CAPTCHA is bewildering). So I attempt again.
Since version 2062 of the trunk, somes issues for Pro40 and Pro 24 are expected to be solved, but of course this requires addditional tests which will be welcome.
Corrections imply:
- full routing available with ffado-mixer whatever is the samplerate. You would have to be able to route anything in everything (care, however, with larsen like effects). I was not able to test for ADAT and SPDIF, having no such devices.
- full matrix-mixer available with ffado-mixer. Have in mind that rows are mixer inputs and columns are mixer outputs. The channel routing will appear in matrix-mixer display.
- if you are using qjackctl (why not :), the right names for jack input and output ports will appear (and part of the routing also). Moreover, jack will not crash when starting at a sample rate different than the one in the flash.
The unfair feature, until now, is that part of the display in ffado-mixer and in qjackctl will not update until restarting.
Some additional work to do.
Phil
This is fantastic news!
This is fantastic news! Routing was the one thing stopping the Pro40 from being truly usable.
I will hopefully have some time off in the next week or so, I'll grab the new code and let you know how it behaves.
Cheers!
Some new features
Hi,
since revision 2060 of the trunk, there are new features available for Pro 40 (and Pro 24):
- mixer can be managed using the "matrix" of ffado-mixer. Just recall that inputs are rows and
outputs are columns.
- routing is also available using the crossbar router of ffado-mixer. Care that there is many degrees of freedom for routing (almost everything may be routed everywhere).
- jack input and outputs ports are displayed in coherence with the router
- sample rate dependency is accounted for.
Of course, there is a need for more trials. Also, there is some limitations at this time: while modifications are accounted for immediatly, this is not true for part of the display of ffado-mixer or jack port. More work is needed for this.
Hope you willl enjoy for it.
Phil
works well with tango studio updates... except sdif issue
Hi!
I have the focusrite on loan and will decide if its right for our home studio setup. I am using Ubuntu Studio 10.04 LTS and had not managed to get the device recognised by the dbus server with the ffado version in synaptic, so as advised, I got updates from Tango Studio repository. I am using the old firewire stack, and as was commented earlier, I opened the terminal and typed "ffado-dbus-server &" and turned on the focusrite, hit enter on the terminal just as the power led came on. It recognised the device this time and then I got the mixer working, although I still have to understand it better. I got Jack and then Ardour working and then managed to record an analogue signal.
The only problem is with SPDIF, it is very faint and distorted- there is a high pitched buzzing noise accompanying the piano notes of my tone generator. Other gear (such as the maudio black box with spif out as an option will not even register any sound at all!! I have had the same problem in windows XP- and the tone generator worked fine with another DAW with digital input (optical set to spdif) so I hope the focusrite isn't defective...
Re: works well with tango studio updates... except sdif issue
Have you fixed a definitively right routing using a different OS (windows or Mac) ? Did you have use of ffado-mixer ? Because routing and mixer are still questionable up to now and as you would see reading next comments, we are under reflexion for possibly modifying part of the encoding.
I have an additional question since you use the old firewire stack and used ffado-mixer. What do you see for the matrix mixer, more precisely what are the number of rows and columns and are all the values coherent ?
Reply: works well with tango studio updates... except sdif issue
hello, la-page-web-of-phil!
Only turned on the focusrite for now - I see a matrix of 0 - 17 horizontal and 0 -15 channels vertical. It seems more or less alright with channels 0-7 x 2 rows lit up -0.46 db and then the last 2 channels representing the spif (that I have plugged in at the momment?) lit up -0.011 db. I had switched the optical from adat to spdif but I don't think that works cause the routing still shows ADAT channels but there is no option for spdif channel 1.1 1.2 AND 2.1 and 2.2 as is in WinXP mixer! I also have Win7 OS as part my multiboot so I can see if there is any difference...
By the way is there a wiki or instructions on using the matrix- I am not sure what I need to change in the routing and if I just do it in jack connections? Also I have to check out Ardour manual and figure out how to use an effects bus to use as a send/return for my lexicon mpx550 effects processor which I have now plugged via stereo inputs and left output on the focusrite, we like to use older gear as well as the software plugins. I guess I should ask those questions in the Ardour forum...
*I'm trying to re-submit cause I kept getting the capcha wrong and my reply is seen as spam, lol!
Re: works well with tango studio updates... except sdif issue
hello, la-page-web-of-phil!
Only turned on the focusrite for now - I see a matrix of 0 - 17 horizontal and 0 -15 channels vertical. It seems more or less alright with channels 0-7 x 2 rows lit up -0.46 db and then the last 2 channels representing the spif (that I have plugged in at the momment?) lit up -0.011 db. I had switched the optical from adat to spdif but I don't think that works cause the routing still shows ADAT channels but there is no option for spdif channel 1.1 1.2 AND 2.1 and 2.2 as is in WinXP mixer! I also have Win7 OS as part my multiboot so I can see if there is any difference...
By the way is there a wiki or instructions on using the matrix- I am not sure what I need to change in the routing and if I just do it in jack connections? Also I have to check out Ardour manual and figure out how to use an effects bus to use as a send/return for my lexicon mpx550 effects processor which I have now plugged via stereo inputs and left output on the focusrite, we like to use older gear as well as the software plugins. I guess I should ask those questions in the Ardour forum...
I use TangoStudio too. But
I use TangoStudio too. But that don't work! (how is possible? really Saffire PRO 40?)
I first try with old stack => that cause bug to the hardware device: meters switch off and chaotic internal routing make voice 1 'larsening' (very hight frequency) .
So i would recommend to not try with old version and old stack, so.
I also test with last updates and 'unstable TS repository', with no success.
Anyway, with libffado2 | 2.0.99+svn2171-2
that work, the ffado-mixer work and correct the problem but not the hardware meters.
Note: today, Jack-ffado don't work with this device with debian wheezy packages.
I use TangoStudio too. But
For having leds working, see the indications in comment of mine above.
Phil.
Are you talking about
Are you talking about that:
"
Nevertheless, a correct initial configuration of the "router" is required. This can be obtained by running a small utility like
set-default-router-config-dice-eap --samplerate=48000 --port=fw1
at 48000 and 96000 Hz.
"
I don't understand what utility or where put this command line.
Can you please explain??
Anyway, that seem more simple to use another OS, but I don't got any, I will never, and I don't find anyone having a 1394port.
So a 'linux' solution will really help me!
Re: Are you talking about
Yes.
Just run this command line in a terminal window once your Pro 40 is plugged in
$ set-default-router-config-dice-eap --samplerate=48000 --port=fw1
(with as usual, $ symbolizing your shell prompt).
And run once more time with --samplerate=96000 if required.
This has to be done once for all, provided you use a recent subversion of ffado (greater than 2166).
saffire pro 40 routing
I downloaded the specs I could find in public and built a debug version of the library to check out the routing tables etc.
The routing table _seems_ to be right (if the values for analog etc. are correct in the headers.. couldn't find the spec where these
are defined ... according to header+code the eRS_INS0 is 4 << 4 and so analog:2 should be (4<<4)+2 = 66 = 0x42 ):
09688322413: (dice_eap.cpp)[1358] show: Router connections:
09688402755: (dice_eap.cpp)[1364] show: 1394:00 -> SPDIF:00
09688486894: (dice_eap.cpp)[1364] show: 1394:01 -> SPDIF:01
09689718848: (dice_eap.cpp)[1364] show: ADAT:01 -> 1394:01
09689801955: (dice_eap.cpp)[1364] show: ADAT:02 -> 1394:02
09689885012: (dice_eap.cpp)[1364] show: ADAT:03 -> 1394:03
09690050158: (dice_eap.cpp)[1364] show: ADAT:05 -> 1394:04
09690132787: (dice_eap.cpp)[1364] show: ADAT:06 -> 1394:05
09690216920: (dice_eap.cpp)[1364] show: ADAT:07 -> 1394:06
09690533621: (dice_eap.cpp)[1364] show: Analog:02 -> 1394:00 ;; analog:02 (which should be analog input 3 on the device, I think?) -> this is correct
09692263741: (dice_eap.cpp)[1364] show: Mute:00 -> 1394:07
09692265113: (dice_eap.cpp)[1364] show: Mute:00 -> 1394:08
09692267319: (dice_eap.cpp)[1364] show: Mute:00 -> 1394:09
09692268912: (dice_eap.cpp)[1364] show: Mute:00 -> 1394:10
09692270274: (dice_eap.cpp)[1364] show: Mute:00 -> 1394:11
09692271865: (dice_eap.cpp)[1364] show: Mute:00 -> 1394:12
09692273227: (dice_eap.cpp)[1364] show: Mute:00 -> 1394:13
09692274835: (dice_eap.cpp)[1364] show: Mute:00 -> 1394:14
09692277009: (dice_eap.cpp)[1364] show: Mute:00 -> 1394:15
09692281268: (dice_eap.cpp)[1364] show: Mute:00 -> ADAT:02
09692287891: (dice_eap.cpp)[1364] show: Mute:00 -> ADAT:06
09692289255: (dice_eap.cpp)[1364] show: Mute:00 -> ADAT:07
09692290847: (dice_eap.cpp)[1364] show: Mute:00 -> Analog:00
09692292210: (dice_eap.cpp)[1364] show: Mute:00 -> Analog:01
09692293808: (dice_eap.cpp)[1364] show: Mute:00 -> Analog:02
09692295172: (dice_eap.cpp)[1364] show: Mute:00 -> Analog:03
09692303093: (dice_eap.cpp)[1364] show: Mute:00 -> Mixer:00
09692304706: (dice_eap.cpp)[1364] show: Mute:00 -> Mixer:01
09692317650: (dice_eap.cpp)[1364] show: Mute:00 -> Mixer:09
09692319024: (dice_eap.cpp)[1364] show: Mute:00 -> Mixer:10
09692320641: (dice_eap.cpp)[1364] show: Mute:00 -> Mixer:11
09692322013: (dice_eap.cpp)[1364] show: Mute:00 -> Mixer:12
09692323630: (dice_eap.cpp)[1364] show: Mute:00 -> Mixer:13
09692325013: (dice_eap.cpp)[1364] show: Mute:00 -> Mixer:14
09692327172: (dice_eap.cpp)[1364] show: Mute:00 -> Mixer:15
09692331677: (dice_eap.cpp)[1364] show: Mute:00 -> Mute:00
In midst of the debug messages I get some warnings/errors though:
09692570621: ^[[31mError (dice_avdevice.cpp)[1668] readRegBlock: Could not read 108 quadlets from node 0xFFC0 addr 0xFFFFE0208D64
^[[0m09692579051: ^[[31mWarning (dice_eap.cpp)[1403] read: No routes found. Base 0x7, offset 0x4000
(didn't check this, but this is probably due to missing routing table for HIGH perhaps.. 192kHz)
Been reading the code and trying to understand what is going on, but so far everything seems OK, except that "dice_avdevice.cpp readRegBlock" error.
--jani;
Saffire pro/new firewire stack
Hi everybody,
I bought a Saffire Pro 40 and received it yesterday.
I'm awestruck because it was (would have been) working straightforwardly (if I would remember that, at first, I should have to root logging in), at least for the (not so) elementary functions I tested: jack interface, playback and recording. However, I didn't yet have a trial with ffado mixer, I have to learn more about it before.
Note that it was working using the new firewire stack (firewire_ohci, say) included in new kernels
(2.6.35 and 3.0.9, concerning the kernel I tested), with host controller FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 05) (as $ lspci returns).
PC is a Dell Precision M6300 laptop, 3 years old running fedora 14 and 16 (with a manually compiled 3.0.2
preempted vanilla kernel for the latter).
Especially, fully preempted 3.0.2 kernel seems to give a very good result (8ms of latency, and probably better if I would be able to solve this damned "fan" (!) dependency of large - occasional - xruns appearance).
So, many, many thanks (and a happy new year, of course) for developpers.
You have done a lot of work, guys !
Phil
Saffire pro/new firewire stack, router working?
Hi. I bought Saffire Pro 40 recently and I am trying to get it working.
So far I've been trying with the new firewire stack (with libraw1394 2.0.7).
I get the streaming working all the way to Ardour2, but the ffado-mixer router is not really working.
I have a LINE input connected to the analog input 3 port. Recording was working for a while (I suspect with
factory defaults) in Ardour, but at some point it just stopped working.
If I set the routing table so that the analog input is wired to 1394:0 (or along those lines.. the DAW output
anyway), I get a high-frequency square wave (oscillation?) in recording. If I connect all analog inputs and record
8 channels from ardour, I get similar high-frequency square wave on all channels, but nothing is responding to the
signal on LINE input. The amplitude is a bit different on each channel.
While the input was working, the matrix mixer was working properly. It seems that the router is routing something
funky to the DAW.
Should I try with the older stack, or is this a libffado or ffado-mixer issue?
I have a programming background, so my next step is to see if I can find some HW specs on Saffire Pro 40 + Dice II spec
and start figuring out what is going wrong with the router config.
I don't have access to Windows -> can't reset the device to factory defaults.
Any pointers welcome.
--jani;
Re: Saffire pro/new firewire stack, router working?
Well, I also experienced incoherent routing issues using ffado-mixer. Thus I reset to factory defaults after re-installing Windows and then the firmware of Focusrite on my computer; then I adjusted different levels in mixers (matrix-mixer) and routing.
Then, I returned back to Linux and turned to the last subversion (2019, at that time).
I listed the results of test-dice-eap and had a look:
- matrix-mixer has the right values (the ones I entered under Windows), with some uncertainty about the last column but:
* the values of the number of rows/columns are inverted in ffado-mixer; having a rapid look to the C++ code (dice-eap.cpp, if I remember well) this may probably be easily corrected but I (or you) would have to know what is the paradigm (which has also to apply to other devices) used by the developers: is a row of ffado-mixer represent one "mix" or is it the inverse (one column represents one mix).
- I was unable to recognize most of the routing with respect with the one I entered in Windows. Together with the "funky" results of modifying routing we observed, there is probably something really wrong.
* now, to go a step further, I (or you) will need to know from the ffado developers what they mean by transmitter and receiver: this is because the outputs of jack should be some of the inputs of the devices and reversely, knowing that there is additional inputs (analogic, adat, spdif) and outputs for the device.
Well, I have no much more time right now but I will follow the discussion.
Phil
My other reply is somehow
My other reply is somehow being reviewed as spam. I found out that ins1 is used instead of ins0 in case of saffire pro 40.. After I changed these lines from the driver:
saffire_pro40.cpp:
addSource("Analog", 0, 8, eRS_InS0); ==> addSource("Analog", 0, 10, eRS_InS1);
addDestination("Analog", 0, 8, eRD_InS0); ==> addDestination("Analog", 0, 10, eRD_InS1);
With those changes and very careful use of ffado-mixer (check the debug log to see what changes ACTUALLY the driver did and just retry on the ffado-mixer
until the correct changes end up going in...) I managed to get the recording stuff working.
Playback is not working yet (there is output, but it is cuts off a lot.. almost as if the streaming doesn't have a real change to get going). I wonder if my
debug stuff is slowing stuff down too much for the streaming to work.
The ffado-mixer or the driver is somehow really broken when it comes to the saffire pro 40. The UI changes sometimes are totally ignored. I think this probably
has to do with the fact that the ffado-mixer doesn't get the ACTUAL HW state as it it's initial starting point or something along those lines and then when
you try to edit routes, they are not found in the first place (so that the could be deleted for example...) => routing table gets filled with whatever.
I will look more into it to see if I can figure out what is wrong with that.
--jani;
Setting up a good config
Setting up a good config with MAC (2-channel analog recording + one monitor mix to headphones etc.) I
needed to make more modifications to the saffire_pro40.cpp so that similar config could be created in
ffado-mixer:
void SaffirePro40::SaffirePro40EAP::setupSources() {
addSource("SPDIF", 0, 2, eRS_AES);
addSource("ADAT", 0, 8, eRS_ADAT);
addSource("Analog_0", 0, 10, eRS_InS0);
addSource("Analog_1", 0, 10, eRS_InS1);
addSource("Mixer", 0, 16, eRS_Mixer);
addSource("1394_0", 0, 16, eRS_ARX0);
addSource("1394_1", 0, 16, eRS_ARX1);
addSource("Mute", 0, 1, eRS_Muted);
}
void SaffirePro40::SaffirePro40EAP::setupDestinations() {
addDestination("SPDIF", 0, 2, eRD_AES);
addDestination("ADAT", 0, 8, eRD_ADAT);
addDestination("Analog_0", 0, 10, eRD_InS0);
addDestination("Analog_1", 0, 10, eRD_InS1);
addDestination("Mixer", 0, 16, eRD_Mixer0);
addDestination("Mixer", 0, 2, eRD_Mixer1, 16);
addDestination("1394_0", 0, 16, eRD_ATX0);
addDestination("1394_1", 0, 16, eRD_ATX1);
addDestination("Mute", 0, 1, eRD_Muted);
}
Once these edits are in place, the route table looks like (in my case):
1394_0:00 -> Analog_0:00
1394_0:00 -> Mixer:02
1394_0:01 -> Analog_0:01
1394_0:01 -> Mixer:03
ADAT:00 -> 1394_1:00
ADAT:01 -> 1394_1:01
ADAT:02 -> 1394_1:02
ADAT:03 -> 1394_1:03
ADAT:04 -> 1394_1:04
ADAT:05 -> 1394_1:05
ADAT:06 -> 1394_1:06
ADAT:07 -> 1394_1:07
Analog_1:00 -> 1394_0:00
Analog_1:01 -> 1394_0:01
Analog_1:02 -> 1394_0:02
Analog_1:02 -> Mixer:00
Analog_1:03 -> 1394_0:03
Analog_1:03 -> Mixer:01
Analog_1:04 -> 1394_0:04
Analog_1:05 -> 1394_0:05
Analog_1:06 -> 1394_0:06
Analog_1:07 -> 1394_0:07
Mixer:00 -> Analog_1:04
Mixer:01 -> Analog_1:05
Mixer:01 -> Mute:00
Mute:00 -> 1394_1:08
Mute:00 -> 1394_1:09
Mute:00 -> ADAT:00
Mute:00 -> ADAT:01
Mute:00 -> ADAT:02
Mute:00 -> ADAT:03
Mute:00 -> ADAT:04
Mute:00 -> ADAT:05
Mute:00 -> ADAT:06
Mute:00 -> ADAT:07
Mute:00 -> Analog_1:00
Mute:00 -> Analog_1:01
Mute:00 -> Analog_1:02
Mute:00 -> Analog_1:03
Mute:00 -> Analog_1:06
Mute:00 -> Analog_1:07
Mute:00 -> Mixer:04
Mute:00 -> Mixer:05
Mute:00 -> Mixer:06
Mute:00 -> Mixer:07
Mute:00 -> Mixer:08
Mute:00 -> Mixer:09
Mute:00 -> Mixer:10
Mute:00 -> Mixer:11
Mute:00 -> Mixer:12
Mute:00 -> Mixer:13
Mute:00 -> Mixer:14
Mute:00 -> Mixer:15
Mute:00 -> Mixer:16
Mute:00 -> Mixer:17
Mute:00 -> SPDIF:00
Mute:00 -> SPDIF:01
SPDIF:00 -> 1394_0:08
SPDIF:01 -> 1394_0:09
59 entries in table and 59 reported "understood" by the driver.
Now.. if we could just figure out how to get that ffado-mixer to play along. Managed to get audio input/output now fully
running at 48kHz, but not at 96kHz (input works, but output doesn't...)
--jani;
Re: Setting up a good config
I tested your config but did not retrieve the correct routing. Also your config implies 20 analog inputs while only eight are available and 32 1394 connections while the saffire pro have only 20.
So I looked further to the active router config and finally tested successfully:
void SaffirePro40::SaffirePro40EAP::setupSources() {
addSource("SPDIF", 0, 2, eRS_AES);
addSource("ADAT", 0, 8, eRS_ADAT);
addSource("Analog", 16, 8, eRS_InS0);
addSource("Mixer", 0, 16, eRS_Mixer);
addSource("1394", 0, 10, eRS_ARX0);
addSource("1394", 0, 10, eRS_ARX1, 10);
addSource("Mute", 0, 1, eRS_Muted);
}
void SaffirePro40::SaffirePro40EAP::setupDestinations() {
addDestination("SPDIF", 0, 2, eRD_AES);
addDestination("ADAT", 0, 8, eRD_ADAT);
addDestination("Analog", 0, 2, eRD_InS0);
addDestination("Analog", 0, 8, eRD_InS1, 2);
addDestination("Mixer", 0, 16, eRD_Mixer0);
addDestination("Mixer", 0, 2, eRD_Mixer1, 16);
addDestination("1394", 0, 10, eRD_ATX0);
addDestination("1394", 0, 10, eRD_ATX1, 10);
addDestination("Mute", 0, 1, eRD_Muted);
}
which lead to the routing I implemented under windows:
04445633830: (dice_eap.cpp)[1355] show: Router connections:
04445721412: (dice_eap.cpp)[1361] show: 1394:00 -> Mixer:16
04445816592: (dice_eap.cpp)[1361] show: 1394:01 -> Mixer:17
04447535552: (dice_eap.cpp)[1361] show: ADAT:00 -> 1394:10
04447593600: (dice_eap.cpp)[1361] show: ADAT:00 -> Mixer:08
04447632232: (dice_eap.cpp)[1361] show: ADAT:01 -> 1394:11
04447689056: (dice_eap.cpp)[1361] show: ADAT:01 -> Mixer:09
04447727426: (dice_eap.cpp)[1361] show: ADAT:02 -> 1394:12
04447785237: (dice_eap.cpp)[1361] show: ADAT:02 -> Mixer:10
04447823673: (dice_eap.cpp)[1361] show: ADAT:03 -> 1394:13
04447881610: (dice_eap.cpp)[1361] show: ADAT:03 -> Mixer:11
04447919572: (dice_eap.cpp)[1361] show: ADAT:04 -> 1394:14
04447977157: (dice_eap.cpp)[1361] show: ADAT:04 -> Mixer:12
04448015570: (dice_eap.cpp)[1361] show: ADAT:05 -> 1394:15
04448073547: (dice_eap.cpp)[1361] show: ADAT:05 -> Mixer:13
04448112135: (dice_eap.cpp)[1361] show: ADAT:06 -> 1394:16
04448168700: (dice_eap.cpp)[1361] show: ADAT:06 -> Mixer:14
04448207249: (dice_eap.cpp)[1361] show: ADAT:07 -> 1394:17
04448265104: (dice_eap.cpp)[1361] show: ADAT:07 -> Mixer:15
04448274595: (dice_eap.cpp)[1361] show: Analog:00 -> 1394:00
04448335374: (dice_eap.cpp)[1361] show: Analog:00 -> Mixer:00
04448370681: (dice_eap.cpp)[1361] show: Analog:01 -> 1394:01
04448431576: (dice_eap.cpp)[1361] show: Analog:01 -> Mixer:01
04448466376: (dice_eap.cpp)[1361] show: Analog:02 -> 1394:02
04448527106: (dice_eap.cpp)[1361] show: Analog:02 -> Mixer:02
04448562528: (dice_eap.cpp)[1361] show: Analog:03 -> 1394:03
04448623427: (dice_eap.cpp)[1361] show: Analog:03 -> Mixer:03
04448658226: (dice_eap.cpp)[1361] show: Analog:04 -> 1394:04
04448719058: (dice_eap.cpp)[1361] show: Analog:04 -> Mixer:04
04448754500: (dice_eap.cpp)[1361] show: Analog:05 -> 1394:05
04448815266: (dice_eap.cpp)[1361] show: Analog:05 -> Mixer:05
04448850657: (dice_eap.cpp)[1361] show: Analog:06 -> 1394:06
04448911584: (dice_eap.cpp)[1361] show: Analog:06 -> Mixer:06
04448946423: (dice_eap.cpp)[1361] show: Analog:07 -> 1394:07
04449007124: (dice_eap.cpp)[1361] show: Analog:07 -> Mixer:07
04449074626: (dice_eap.cpp)[1361] show: Mixer:00 -> Analog:00
04449170668: (dice_eap.cpp)[1361] show: Mixer:01 -> Analog:01
04449266318: (dice_eap.cpp)[1361] show: Mixer:02 -> Analog:02
04449362448: (dice_eap.cpp)[1361] show: Mixer:03 -> Analog:03
04449458068: (dice_eap.cpp)[1361] show: Mixer:04 -> Analog:04
04449554051: (dice_eap.cpp)[1361] show: Mixer:05 -> Analog:05
04449649663: (dice_eap.cpp)[1361] show: Mixer:06 -> Analog:06
04449745637: (dice_eap.cpp)[1361] show: Mixer:07 -> Analog:07
04449778736: (dice_eap.cpp)[1361] show: Mixer:07 -> Mute:00
04449841717: (dice_eap.cpp)[1361] show: Mixer:08 -> Analog:08
04449937117: (dice_eap.cpp)[1361] show: Mixer:09 -> Analog:09
04450566481: (dice_eap.cpp)[1361] show: Mute:00 -> 1394:18
04450568126: (dice_eap.cpp)[1361] show: Mute:00 -> 1394:19
04450569682: (dice_eap.cpp)[1361] show: Mute:00 -> ADAT:00
04450572107: (dice_eap.cpp)[1361] show: Mute:00 -> ADAT:01
04450573474: (dice_eap.cpp)[1361] show: Mute:00 -> ADAT:02
04450575097: (dice_eap.cpp)[1361] show: Mute:00 -> ADAT:03
04450576471: (dice_eap.cpp)[1361] show: Mute:00 -> ADAT:04
04450578096: (dice_eap.cpp)[1361] show: Mute:00 -> ADAT:05
04450579655: (dice_eap.cpp)[1361] show: Mute:00 -> ADAT:06
04450581747: (dice_eap.cpp)[1361] show: Mute:00 -> ADAT:07
04450629148: (dice_eap.cpp)[1361] show: Mute:00 -> SPDIF:00
04450631378: (dice_eap.cpp)[1361] show: Mute:00 -> SPDIF:01
04450645487: (dice_eap.cpp)[1361] show: SPDIF:00 -> 1394:08
04450741413: (dice_eap.cpp)[1361] show: SPDIF:01 -> 1394:09
Could you have a test with this
Phil
Yes, more tuning needed
I wasn't sure that the config I proposed was the correct one, only that it had enough to represent the router table I had. So some fine tuning
is needed.
ffado-mixer starts to cooperate just fine when all entries in mixer table are accounted for (I think this is because before it
couldn't tell the ffado to switch from "ins1:00->1394:00" to say "ins0:00->1394:00" because "ins1" was not representable...) and I have a fully
working setup for my needs for now.
Phil: did you test all the outputs and routing on the back (1-8)? at least the monitor outputs (1-2) were connected to the eRD_InS0, so I wonder if the
rest of the outputs are connected to eRD_InS0:02-07 or are they in eRD_Ins1 instead?
I can't test now, but I will later do a routing setup that involves all analog inputs and all analog outputs, spdif input and spdif output and
see that everything gets routed with the config you provided. Actually, looking at your routing setup seems that you more or less have a full routing setup there.
After we have this 100% figured out, we would need some ffado developer to push this change to the repository.
--jani;
Re: Yes, more tuning needed
Yes, I tested all analog inputs/outputs and also played with the ffado-mixer (with a minor modification of dice_eap.cpp to make it works), but I did not modify any routing until now. I have no ADAT nor SPDIF devices, so I could'n't test for these inputs outputs.
Also, there is the so-called "loop back" which is not yet implementer.
I yet mailed to developers using the developer list. Probably you would have to join the list (ffado-devel@lists.sourceforge.net), because the discussion becomes rather too specific as comments of this page.
Phil
Re: Yes, more tuning needed
Getting changes into the repo shouldn't be a problem: I would certainly be willing to push them, but since I don't have saffire hardware I would need assurances that the changes don't mess up functionality for other saffire devices.
The changes
The changes we are talking about here are to saffire_pro40.cpp, which applies only saffire pro 40 if I understand it correctly (overloads some
functions of the generic dice eap for saffire pro 40).
We'll figure out the correct changes (the changes Phil provided might be the exact right one) and let you know when everything checks out.
Cheers,
--jani;
Focusrite and Ricoh
I have a Toshiba satellite A300 laptop with "Ricoh Co Ltd R5C592" firewire.
¿Has anyone installed Focusrite saffire pro 40 in Ubuntu/linux with ffado?
¿Is posible to do it?
¿What can I do if it isn't posible?
Thanks
Focusrite and ricoh works OK
Yes I'm using ffado and a Focusrite PRO 40 with my laptop (Asus G2S) wich has a Ricoh based firewire bus. It works OK.
But if you have installed Ubuntu ( Luicd ) you can add TangoStudio or KXStudio repositories, or compile ffado and jack from svn sources.
Re: Focusrite and Ricoh
In the absence of any other feedback I will simply say that I don't know. I don't own either a Ricoh-based interface card or a pro40 so I have no first-hand experience to draw on. We have some information about host controllers at http://subversion.ffado.org/wiki/HostControllers but your particular variant doesn't seem to be listed yet. I would suggest that the best approach in your case is to simply try it and see if it works. If it does, great! Otherwise we'll have to consider alternatives. In either case, report your findings back here so we can add to the general knowledge-base about Ricoh controllers.
Another option may be to subscribe to the ffado-users mailing list and post your question there. You'll reach a different set of people there and among those there may be people who have already tried using your particular chip with ffado.
If it turns out that this controller can't work with audio interfaces, the best approach is probably to obtain a CardBus firewire interface card and use that instead of the built-in interface. Interfaces based on Texas Instruments (TI) chipsets seem to be fairly robust, but as per the host controller page mentioned above there are chips which can work.
I apologise that this information is fairly generic in nature, but without first-hand experience it's a touch tricky to say much more.
Doesnt work
Hello,
Does anybody can work with the Saffire PRO 40 in an stable situation? Could you tell me what version of ubuntu,exactly which drivers and which linux kernel? I just got it to work without Realtime mode, and anyway i cannot start from Ardour? Somebody knows why at the Ardour starting you cannot choose "firewire driver" and why in Jack there is a firewire driver option but not a Ffado option?
Is there anybody that could help me pesonally by email? i would appreciate so much!
thanks!
Saffire Pro 40
Yesterday I did a clean install of UbuntuStudio 11.10, 64-bit version with realtime kernel and chose to install only the Audio studio and recording applications. After installation I let the Update Manager run to update the system to the latest versions of all the packages.
In order to have the Saffire Pro 40 work I switched it on BEFORE rebooting the system. After logging in I opened a terminal window and entered:
ffado-dbus-server
This produced some warnings and other messages but ended up by showing the available ports on the Saffire.
Next I started Jack Control (included in the Ubuntu Studio distro), selected firewire in the Setup window, and clicked the Start button. Immediately the synchronisation indicator led on the Saffire lit up.
I tested the system with Ardour (also part of UbuntuStudio) and everythig seems to work properly. I even have sound output from my Saffire Pro 40, something I could not get working with UbuntuSutio 11.04. All Xruns, also a problem I had with the previous release of UbuntuStudio, have disappeared as well! In short: it seems I now have a stable system running that fully supports the Focusrite Saffire Pro 40.
Next thing I need to master is the FFado Mixer in order to configure the settings of my Saffire Pro 40.
Saffire Pro 40
Care with ffado-mixer.
I experienced many strange behaviours and finally many problems with it during the last days, and presently I will try to reset the Saffire using Windows (I have first to reinstall Windows for the matter).
I am wondering about routing, especially.
Phil.
Ubuntu 11.04
Try This
1.Do a clean install of Ubuntu 11.04 with updates.
2.Goto "System Settings" then "Users and Groups" then "Advanced Settings" then the "User Privileges" Tab and check the "Use Audio Devices" tab.
3.Goto the "Ubuntu Software Center" and search "ffado" and install the FFADO-Mixer.
4.Reboot
5.Turn device on wait a couple of minutes.
6.Start "FFADO MIXER" - It should show your device at this point. (I have noticed that sometimes the mixer doesn't work on some devices.)
7. Start QjackCtl select "firewire' hit start.
I hope this helps.
Jazzman
How I got it to work
After a few days of trying, I finally have a fully working Pro 40 in Ubuntu 10.10.
First off, as many have already said - this doesn't work yet with the new stack. So, if you want to save some frustration,
then load the old stack - https://help.ubuntu.com/community/FireWire and it should be a bit easier.
The first thing I did was load the subversion ffado drivers, which are already available in synaptic, so that was easy enough.
Same thing with jack. Once you get everything loaded and verify you're running the old stack, you should be good to go.
Here is the part that took numerous tries to get right. Make sure your Pro 40 is OFF when you boot up into the desktop.
Open a terminal and type "ffado-dbus-server &" but don't hit enter yet - power on your Pro 40 and after about 3 to 4 seconds hit enter to run ffado-dbus-server &
If ffado-mixer works you're good to go, if not - power off the Pro 40 and try the same steps again. I usually get it to work by the second try.
The trick it to get it recognized before it goes into standalone mode. I believe it has something to do with the Pro 40 only sending the device id right after it boots up?
Keep an eye on the terminal and you should see something like:
(ffado-dbus-server.cpp)[ 270] main: Discovering devices...
Debug (devicemanager.cpp)[ 358] discover: Starting discovery...
Debug (Configuration.cpp)[ 163] showSetting: Group: (null)
Debug (Configuration.cpp)[ 185] showSetting: vendorid = 4878 (0x0000130E)
Debug (Configuration.cpp)[ 185] showSetting: modelid = 5 (0x00000005)
Debug (Configuration.cpp)[ 209] showSetting: vendorname = Focusrite
Debug (Configuration.cpp)[ 209] showSetting: modelname = Saffire PRO 40
[Etc....]
After you see that the device is discovered you can start jack. I don't know if it matters or not, but I created a Preset Name of firewire based on the default.
Interface hw:0 Input/Output channels = 8 each. Note: you may have to setup jack before you do the first step?
Once you start jack you will hopefully see the second green light (indicating fw) light up on the Pro 40. From there it is smooth sailing!
Install audacious and use the jack plugin to test.
I think I did all of that and yet...
And yet all I get is:
00818253238: Fatal (devicemanager.cpp)[ 191] initialize: No firewire adapters (ports) found.
00818253448: Error (ffado-dbus-server.cpp)[ 277] main: Could not initialize device manager
00818254154: Debug (ffado-dbus-server.cpp)[ 202] exitfunction: Debug output flushed...
after running 'ffado-dbus-server &' after a few seconds of turning on the Pro 40.
And:
02:32:43.048 Could not connect to JACK server as client. - Overall operation failed. - Unable to connect to server. Please check the messages window for more info.
If I try to run Jack.
I have tried with Musix 2.0, JackLab, Ubuntu Studio 10.04, Ubuntu 10.04 Netbook Remix with added jackd, ffado and RT-kernel packages compiled from svn, Ubuntu Studio 10.10 changing to old stacks and prior jack and ffado versions, PureDyne 9-11...
This stuff does NOT work guys! In May it will be two years that I am trying to make this happen and/or waiting for DICE support on a release... I wholeheartedly thank the volunteers that pull this project together, but I cannot wait another two years for a DICE support release and FireWire is dying faster as an interface than this project is moving.
I will have to part ways and think of something else. I don't like Macs because they are just doorways to using your credit card for everything new you want to do, so I guess either Windows 7 or a standalone recorder will have to do. If I can ever get all that cash together.
Thank you all again
Good bye.
Gabe.
Old stack / New stack
Working via a Texas Instruments XIO2200(A) (in a Startech Expresscard) with Linux 2.6.34.7 compiled with old Firewire stack.
New stack appears to "work", but with no actual sound I/O.
It also works in the new
It also works in the new stack, trust me.
Only issue is that playback is muted in the new stack. The device receives the stream, but it isn't routed to playback. But recording works fine.
This problem exists with all Dice-based devices that use the Extended Application Protocol (EAP) and is being worked on.
New Stack! No Output Sound!
Hello!
Device have sync, is working pretty nice for recording, but i cant hear what i recorded ... wtf!
What can i do to put it to work?? Thanks for the info.
Im running:
Linux debian 2.6.32-5-amd64 #1 SMP Sat Oct 30 14:18:21 UTC 2010 x86_64 GNU/Linux
Working output
I couldn't get the output working with the newer firewire stack and was getting xruns.
Enabled the older firewire stack and the xruns went away and the output started working.