Mackie Onyx-i series

Reported to work with svn r1956.

Support Status: 
Reported to work


After 6 month working with a Onyx 1620i I wanted to report that all works well and with nearly no xruns.
I personally consider it as stable;-)

Wow, I'm interested if the latency is lower as 2-3 ms =)

So just to clarify is the Mackie 820i going to work on my Linux box? Will I need to mess with the ffado driver or will it now just work out of the box. Can you reccomend settings? Its really great news if the i-series mixers now work.

I'm planning to get a 1640 Onyx-i mixer . I hesitate between this one and a Presonus Studiolive 16/4/2 with a preference for the Mackie . But reading posts on the Onyx Serie make me be not sure for the Onyx-i serie working capacities with ffado . What about that in fact ?


you should decide, which mixer better fits your needs. When I was looking for a mixer a year ago, I decides to buy a Mackie - although I had read that it was not working with ffado - because I liked the sound, the price was ok and it was exactly what I was looking for.
It took me two month to figure out, (with the help of the ffado developers) what had to be done to get it working.
Then it took some more time until everything was stable. But now it works - with the new stack.


That works with ubuntu Tango studio. But not the mixer FFADO "This panel is merely placeholder for devices that don't have a mixer panel (yet)".
An idea?

No, 8ms latency is possible (4 core AMD) at my side

Yes, it should work without any problems.
My Jack Settings is /usr/bin/jackd -S -v -P89 -dfirewire -r48000 -p128 -n3#
I use the new FireWire stack


And what about the FFADO mixer for you?
I use the new FireWire stack i too.



I can record 8 tracks simultaneously on my Gentoo system using jack-0.121.3, libffado-2.0.1, libraw1394-2.0.8 (the stable version 2.0.3 didn't work) and the new firewire stack on kernel 3.3.4.

Is there anything I can provide to fix the ffado-mixer tool? Is there anything else that I can help the FFADO project with regards to this mixer?

If anyone has any other questions about my setup, feel free to ask. Thanks for all your work!

It's good news that you've been able to use the Onyx with FFADO. Thanks for letting us know.

Regarding libraw1394, version 2.0.8 is the latest stable version. If gentoo's system claims that 2.0.3 is the latest then that indicates that their repositories need to be updated. Since you're using the new kernel stack it's little surprise that 2.0.3 didn't work for you; there were vital changes and bugfixes which went in to libraw1394 after that version was released which are required for use with the new stack.

It's very interesting that libffado 2.0.1 worked for you. This code base is now nearly 18 months old. While it's certainly true that it's the last officially released version, development has been progressing since that time. The lack of a release for such a long time is a problem, but was unavoidable since several key developers have had other issues to deal with over that time. This is, however, a problem which we are actively working towards resolving in the next few months. You could of course check out a recent subversion revision and give that a go if you feel like it in the meantime.

Is there anything I can provide to fix the ffado-mixer tool?

In the first instance it would be interesting to know what exactly is missing or malfunctioning in the mixer for this device. If there is no mixer for this device then we should probably at least enable the generic bebob mixer for this interface in the "configuration" file and see what happens.

I will by a 1620i soon.

Thanks for all detail.

About latency: i can be interested by working with very few latency, two.

@dehnhardt: you report 8ms with: jackd -S -v -P89 -dfirewire -r48000 -p128 -n3#

So with only 2periods (buffer), you are nearly 5ms??

Tanks all for informations!

Hey Guys, first of all I want to tell that I am thankfull to be able to get help and informations here, keep up the good work.

Unluckylie I was not able to get my Mackie 1220i to worke with my Kubuntu.
I installed FFADO and can launch it, but no device shows up. I got to admit, that I am new to Linux
(Not that I am a bloddy beginner, but it´s the first time I really want to use it as an OS).

So could you please tell me what I need to do to get it work ?
I´m affraid I couldn find a how to or something.


We'll need a few more details before we can work out what might be going on. First up, could you tell us which version of kubuntu you are running?

Secondly, could you run "ffado-test ListDevices" and post the result? This command will tell us whether your Onyx can be seen by the operating system and point us closer to the location of the problem.

Finally, it would be good to know which version of FFADO is in use on your system. Your package manager can probably tell you this.


I'm running kxstudio 12.04 64.
I had my mixer working with ffado and after a update it has stopped.

Mixer shows in ffado-test ListDevices
ffado-diag shows the new stack is loaded

I get these errors with ffado-test Discover or when starting ffado-dbus-server

Discovering devices...
1390585825960834: Error (ieee1394service.cpp)[ 797] doFcpTransaction: FCP transaction didn't succeed in 2 tries
1390585825960897: Warning (ieee1394service.cpp)[ 772] transactionBlock: FCP transaction failed
1390585825960906: Error (bebob_avdevice.cpp)[ 99] probe: Number of channels command failed
1390585825999528: Error (ieee1394service.cpp)[ 797] doFcpTransaction: FCP transaction didn't succeed in 2 tries
1390585825999555: Warning (ieee1394service.cpp)[ 772] transactionBlock: FCP transaction failed
1390585826039611: Error (ieee1394service.cpp)[ 797] doFcpTransaction: FCP transaction didn't succeed in 2 tries
1390585826039639: Warning (ieee1394service.cpp)[ 772] transactionBlock: FCP transaction failed
1390585826039667: Error (avc_avdevice.cpp)[ 89] probe: Subunit info command failed

I'm really confused because this all worked before, now I have been reconfiguring for two days and can't get past this point.

Any Help would be appreciated much.


I had my mixer working with ffado and after a update it has stopped.

What did you update: FFADO, your operating system or the firmware of your StudioLive? Whatever was updated, what was the previous version number and the one currently in use?

The errors are a little odd: the FCP transactions are the primary means by which FFADO communicates with the device. Such errors would occur if, for example, we sent FCP commands to a device which didn't understand them. However, as you noted it used to work, so something has become confused. Clearly the mixer can be made to work so the trick will be to work out what might have gone wrong.

That is the peculiar thing, I had been trying to fix an annoying problem where jack would suddenly stop after a few hours of operation, I had been running jackd1 so i switched to jackd2 to see if it might fix that problem, but I couldn't get it to stay running but for a few minutes, so I went back to jackd1 and everything quit working altogether.

I rebooted the machine to clear out any daemons that might have been running and that's when this started. As far as I know the only other thing that was done in this period was a update of some system files to 12.04 "security update".

I didn't do anything to the ffado configuration. Since then I have gone back through the step by step for 12.04 to make sure all config files etc are correct.

By the way I am running the stock low-latency kernel that is loaded by kxstudio not real time.

Use to the mixer would show that the firewire connection was there as soon as you booted up the machine, now it doesn't. ffado-diag shows the interface to be working and as I said Listdevices shows the mixer.


You are right - this is extremely peculiar. Based on the steps you have outlined it doesn't appear that the configuration of anything now is different to what it was initially. And yet it worked earlier and now does not.

I am wondering whether the original problem "jack stopping suddenly after hours of operation" might not be a clue. It is possible that this was an early failure symptom of a problem which was getting progressively worse as time went on. Although it would amount to unfortunate timing, it is possible that whatever was failing happened to get significantly worse around the time you made the change to jackd2.

It is possible that a "security update" could influence things negatively. However, I think it is unlikely in this case.

Using stock low-latency kernel should be fine.

If you happen to have access to another firewire cable it is probably worthwhile trying it to see if the symptoms are altered. If your firewire card has multiple firewire sockets it would also be useful to try using the other one (and the same at the audio interface end if applicable). These tests would determine whether the problem is due to a degradation of the mechanical aspects of the system: firewire plugs, sockets and cables. They are also the easiest things to test.

If the above tests indicate that there is no cable/socket fault then we have to start considering other things. But let's rule out the easy things first.

I recently purchased a 1640i and am trying to use it in Fedora 20. I too get the exact same errors. I am using Fedora 20, but am considering trying 18 or 19 to see if it's a regression in newer versions of FFADO.

I am happy to do testing for the devs, just need to know what they need.

A number of others have reported similar errors under somewhat different conditions on the ffado-devel mailing list over the last couple of months. A check through the list archives might reveal some useful suggestions, but my immediate recollection is that the true cause has remained elusive. If you do have the ability to easily try the older distributions (or just older FFADO versions) then this would certainly tell us something. We need to keep in mind that having success with an older distribution version doesn't necessarily mean the problem is in FFADO: it could be due to an interaction with older FFADO with older libraries and an older kernel. In any case, the more data we get on this the better.

sorry for my bad English.

mackie 1620 i do not appear in qtjackctrl ubuntu studio 14.04
ffado latest version svn install.

if someone just m help, thank you very much.

For people browsing the comments, "dephazz" also posted a contact message which is being followed up on the ffado-user mailing list in the "[I'm a user and need support] MACKIE ONYX 1620i" thread. This should be accessible via the mailing list archives.

FFADO diagnostic utility 2.1.9999-2493
(C) 2008 Pieter Palmers
2009-2010 Arnold Krille

=== CHECK ===
Base system...
kernel version............ 3.13.0-17-lowlatency
Preempt (low latency)... True
RT patched.............. False
old 1394 stack present.... False
old 1394 stack loaded..... False
old 1394 stack active..... False
new 1394 stack present.... True
new 1394 stack loaded..... True
new 1394 stack active..... True
/dev/raw1394 node present. False
/dev/fw* permissions:
crw------- 1 root root 251, 0 mars 13 10:08 /dev/fw0
User IDs:
uid=1000(eddy) gid=1000(eddy) groupes=1000(eddy),0(root),4(adm),24(cdrom),27(sudo),29(audio),30(dip),44(video),46(plugdev),108(lpadmin),123(sambashare)
Prerequisites (dynamic at run-time)...
gcc ............... gcc (Ubuntu 4.8.2-16ubuntu6) 4.8.2
g++ ............... g++ (Ubuntu 4.8.2-16ubuntu6) 4.8.2
PyQt4 (by pyuic4) . Python User Interface Compiler 4.10.3 for Qt version 4.8.4
jackd ............. jackd version 0.121.4 tmpdir /dev/shm protocol 24
path ............ /usr/bin/jackd
flags ........... Package jack was not found in the pkg-config search path.
Perhaps you should add the directory containing `jack.pc'
to the PKG_CONFIG_PATH environment variable
No package 'jack' found
libraw1394 ........ 2.1.0
flags ........... -lraw1394
libavc1394 ........ 0.5.4
flags ........... -lavc1394 -lrom1394 -lraw1394
libiec61883 ....... 1.2.0
flags ........... -liec61883 -lraw1394
libxml++-2.6 ...... 2.36.0
flags ........... -I/usr/include/libxml2 -I/usr/include/glibmm-2.4 -I/usr/lib/x86_64-linux-gnu/glibmm-2.4/include -I/usr/include/sigc++-2.0 -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libxml++-2.6 -I/usr/lib/libxml++-2.6/include -lxml++-2.6 -lxml2 -lglibmm-2.4 -lgobject-2.0 -lsigc-2.0 -lglib-2.0
dbus-1 ............ 1.6.18
flags ........... -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -ldbus-1
Prerequisites (static at compile-time)...
gcc ............... gcc (Ubuntu 4.8.2-16ubuntu6) 4.8.2
g++ ............... g++ (Ubuntu 4.8.2-16ubuntu6) 4.8.2
PyQt4 (by pyuic4) . Python User Interface Compiler 4.10.3 for Qt version 4.8.4
jackd ............. no message buffer overruns
path ............ /usr/bin/jackd
flags ........... Package jack was not found in the pkg-config search path.
libraw1394 ........ 2.1.0
flags ........... -lraw1394
libavc1394 ........ 0.5.4
flags ........... -lavc1394 -lrom1394 -lraw1394
libiec61883 ....... 1.2.0
flags ........... -liec61883 -lraw1394
libxml++-2.6 ...... 2.36.0
flags ........... -I/usr/include/libxml2 -I/usr/include/glibmm-2.4 -I/usr/lib/x86_64-linux-gnu/glibmm-2.4/include -I/usr/include/sigc++-2.0 -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libxml++-2.6 -I/usr/lib/libxml++-2.6/include -lxml++-2.6 -lxml2 -lglibmm-2.4 -lgobject-2.0 -lsigc-2.0 -lglib-2.0
dbus-1 ............ 1.6.18
flags ........... -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -ldbus-1
uname -a...
Linux eddy-Satellite-A350 3.13.0-17-lowlatency #37-Ubuntu SMP PREEMPT Mon Mar 10 22:12:11 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
Host controllers:
20:00.0 FireWire (IEEE 1394) [0c00]: JMicron Technology Corp. IEEE 1394 Host Controller [197b:2380] (prog-if 10 [OHCI])
Subsystem: Toshiba America Info Systems Device [1179:ff00]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR-
Kernel driver in use: firewire_ohci

CPU info:
Architecture: x86_64
Mode(s) opératoire(s) des processeurs :32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 2
On-line CPU(s) list: 0,1
Thread(s) par cœur : 1
Cœur(s) par socket : 2
Socket(s): 1
Nœud(s) NUMA : 1
Identifiant constructeur :GenuineIntel
Famille de processeur :6
Modèle : 23
Révision : 6
Vitesse du processeur en MHz :1600.000
BogoMIPS: 3990.23
Cache L1d : 32K
Cache L1i : 32K
Cache L2 : 3072K
NUMA node0 CPU(s): 0,1
IRQ information
Hardware Interrupts:
IRQ 0: PID: None, count: [3649, 2799], Sched None (priority None), drivers: ['timer']
IRQ 1: PID: None, count: [101, 83], Sched None (priority None), drivers: ['i8042']
IRQ 8: PID: None, count: [1, 0], Sched None (priority None), drivers: ['rtc0']
IRQ 9: PID: None, count: [219, 220], Sched None (priority None), drivers: ['acpi']
IRQ 12: PID: None, count: [70, 72], Sched None (priority None), drivers: ['i8042']
IRQ 16: PID: None, count: [0, 0], Sched None (priority None), drivers: ['uhci_hcd:usb3']
IRQ 17: PID: None, count: [2, 0], Sched None (priority None), drivers: ['mmc0', 'firewire_ohci', 'jmb38x_ms:slot0']
IRQ 18: PID: None, count: [0, 0], Sched None (priority None), drivers: ['uhci_hcd:usb8']
IRQ 19: PID: None, count: [3428, 3408], Sched None (priority None), drivers: ['ata_piix', 'ata_piix', 'ehci_hcd:usb1', 'uhci_hcd:usb5', 'uhci_hcd:usb7']
IRQ 21: PID: None, count: [0, 0], Sched None (priority None), drivers: ['uhci_hcd:usb4']
IRQ 23: PID: None, count: [243, 201], Sched None (priority None), drivers: ['ehci_hcd:usb2', 'uhci_hcd:usb6']
IRQ 45: PID: None, count: [0, 0], Sched None (priority None), drivers: ['eth0']
IRQ 46: PID: None, count: [273, 3740], Sched None (priority None), drivers: ['iwlwifi']
IRQ 47: PID: None, count: [236, 235], Sched None (priority None), drivers: ['snd_hda_intel']
IRQ 48: PID: None, count: [183, 211], Sched None (priority None), drivers: ['radeon']
IRQ 49: PID: None, count: [43, 41], Sched None (priority None), drivers: ['snd_hda_intel']

Software Interrupts:

=== REPORT ===
FireWire kernel drivers:

The new FireWire kernel stack is loaded.
If running a kernel earlier than 2.6.37 and problems are experienced, either
try with the old Firewire kernel stack or upgrade to a newer kernel
(preferrably 2.6.37 or later).

Here I have solved my problem, thanks in party Damien.DX.
how? All simply by installing KXSTUDIO 12.04.

put more installation day, and it is, the table is detecteée.
works very well with ardor.

256, 48000 Hz, 5.8 ms