AudioFire 4

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

ffado d-bus not working

Hi,

I'm completely new with linux, I installed ubuntu 12.04 recently and I spent hours and hours this week trying to make my Audiofire pre8 work with jack and now I'm quite desperate, I feel like I tried it all.

I think my pre8 is recognized by my computer, which is a good thing:

~$ ffado-test ListDevices
Cannot create thread 1 Operation not permitted
-----------------------------------------------
FFADO test and diagnostic utility
Part of the FFADO project -- www.ffado.org
Version: 2.1.0-
(C) 2008, Daniel Wagner, Pieter Palmers
This program comes with ABSOLUTELY NO WARRANTY.
-----------------------------------------------

=== 1394 PORT 0 ===
Node id GUID VendorId ModelId Vendor - Model
0 0x001486a28ef9a10e 0x00001486 0x00000AF9 Echo Digital Audio - AudioFirePre8

BUT when typing
~$ ffado-dbus-server
I get:
Cannot create thread 1 Operation not permitted
-----------------------------------------------
FFADO Control DBUS service
Part of the FFADO project -- www.ffado.org
Version: 2.1.0-
(C) 2008, Pieter Palmers
This program comes with ABSOLUTELY NO WARRANTY.
-----------------------------------------------

ERROR: messagebuffer not initialized: Discovering devices...
ERROR: messagebuffer not initialized: DBUS service running
ERROR: messagebuffer not initialized: press ctrl-c to stop it & exit

Also, it seems that I don't have the raw1394 thing on my computer:
with "sudo modprobe raw1394", I get:
FATAL: Module raw1394 not found.

Same thing when I type ls -al /dev/raw1394, there is no such file.

Here is my lspci
00:00.0 Host bridge: Intel Corporation Ivy Bridge DRAM Controller (rev 09)
00:01.0 PCI bridge: Intel Corporation Ivy Bridge PCI Express Root Port (rev 09)
00:14.0 USB controller: Intel Corporation Panther Point USB xHCI Host Controller (rev 04)
00:16.0 Communication controller: Intel Corporation Panther Point MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation Panther Point USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation Panther Point High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation Panther Point PCI Express Root Port 1 (rev c4)
00:1c.1 PCI bridge: Intel Corporation Panther Point PCI Express Root Port 2 (rev c4)
00:1c.2 PCI bridge: Intel Corporation Panther Point PCI Express Root Port 3 (rev c4)
00:1c.3 PCI bridge: Intel Corporation 82801 PCI Bridge (rev c4)
00:1d.0 USB controller: Intel Corporation Panther Point USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation Panther Point LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation Panther Point 6 port SATA Controller [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation Panther Point SMBus Controller (rev 04)
01:00.0 VGA compatible controller: NVIDIA Corporation GF116 [GeForce GTX 550 Ti] (rev a1)
01:00.1 Audio device: NVIDIA Corporation GF116 High Definition Audio Controller (rev a1)
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06)
04:00.0 PCI bridge: Texas Instruments XIO2213A/B/XIO2221 PCI Express to PCI Bridge [Cheetah Express] (rev 01)
05:00.0 FireWire (IEEE 1394): Texas Instruments XIO2213A/B/XIO2221 IEEE-1394b OHCI Controller [Cheetah Express] (rev 01)
06:00.0 PCI bridge: ASMedia Technology Inc. ASM1083/1085 PCIe to PCI Bridge (rev 03)

Could someone please help?? I know it's Christmas and everything so I don't expect a lot of replies right now, but I hope this will get fixed soon. Thanks in advance!

Merry Christmas!

FFADOO problem after upgrade

Details posted to the other forum :

http://www.linuxmusicians.com/viewtopic.php?p=33601#p33601

Can anyone help me please?

Thanks!

Re: FFADOO problem after upgrade

Welcome to FFADO.

On the other site you wrote:
I've just migrated to KXStudio from UbuntuStudio(on 12.10) but I cannot make my AudioFire 4 to work. Can anyone help me to sort this problem out please?

We need some details clarified. Did your AudioFire4 used to work prior to your upgrade to KXStudio? According to the logs, you're currently running a very recent svn snapshot of FFADO (which is good). If the device used to work, do you happen to recall which version of FFADO you were using back then?

For the benefit of others following this comment thread, here is the non-verbose jackd output reported in the linuxmusicians forum:

jackd -R -d firewire
jackdmp 1.9.9.5
:
JACK server starting in realtime mode with priority 10
1354645518789771: (ffado.cpp)[ 92] ffado_streaming_init: libffado 2.1.9999-2256 built Dec 2 2012 00:13:40
1354645518985302: Warning (fireworks_session_block.cpp)[ 257] loadFromMemory: size not correct: got 13392, should be -4 according to data
firewire ERR: Could not start streaming threads
Cannot start driver
JackServer::Start() failed with -1
Failed to start server

I'll have to search the ffado-devel and ffado-user mailing list archives, but I have a vague recollection that this particular error (the loadFromMemory line) comes about due to an incompatibility between the FFADO driver and the latest AudioFire firmware versions. Consequently, if you have had this AudioFire4 working before, are you aware of any firmware update which might have been done to it in the time since? Even so, the verbose log you posted (as discussed below) indicates that this did not cause a fatal problem, so for the moment it may be safe to overlook this.

Details reported by ffado-diag on linuxmusicians look reasonable. All library versions are fine and the kernel is lowlatency. I note that the firewire host is an NEC chip:

04:02.0 FireWire (IEEE 1394) [0c00]: NEC Corporation uPD72874 [Firewarden] IEEE1394a OHCI 1.1 Link/3-port PHY Controller [1033:00f2] (rev 01) (prog-if 10 [OHCI])
Subsystem: NEC Corporation Device [1033:00ce]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: ...
Latency: 32, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 18
Region 0: Memory at f7900000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [60] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME+
Kernel driver in use: firewire_ohci
Kernel modules: firewire-ohci

Some NEC chips aren't good for audio under any OS, but I don't know if this is one of them and I can't check right now because the FFADO developer wiki is down for some reason. I'll just flag this as something to keep an eye on since the verbose log (see below) does seem to indicate that there's a streaming problem. Having said that, if you've successfully used this hardware in the past then this is unlikely to be the problem either.

The firewire interface does not share it's IRQ with anything else: that's good.

Finally, a "-v 6" FFADO debug output was provided at pastebin. Despite the loadFromMemory warning I discussed earlier, it seems that device discovery did in fact work just fine - so we probably aren't looking at a firmware problem after all. The device seems to be set up correctly and we are well on the way to starting the audio streams when the pastebin ends prematurely. Based on this, it seems that there was some problem with setting up the audio stream but we don't know what it was because the log on pastebin has been truncated. If possible, could you attempt post this log again (probably to pastebin for the moment - it'll make the forum unreadable if it goes here), but start at the line which reads

Debug (ffado.cpp)[ 218] ffado_streaming_start: ------------- Start -------------

This should capture the entire setup of the audio streaming, and may give us a clue as to what's going wrong.

Sorry for such a late

Sorry for such a late response.

I thought I would get a notification if there was a reply so I assumed my question was ignored and never came back to see.

Anyway, here's the log you requested :

http://dev.eyeq.co.kr/doc/fender/jackd.txt

Thanks!

Xavier

Re: Sorry for such a late

No problem on the delay - I understand how it might have happened. It may be worth keeping an eye on the "recent comments" section of the website's front page. Since forum traffic is fairly low, you should be able to see any replies crop up if you check once every few days.

I should also note here that I have not dealt directly with AudioFire devices up to now. While I do work with other FFADO drivers (RME, MOTU) I have not worked on the AudioFire drivers up to now and don't have an AudioFire unit myself. Therefore some of my comments will be of a general nature.

Having said that, thanks for the reposted log file. There are a number of different error conditions flagged, but latter ones could be side effects of the earlier ones. Therefore we probably need to concentrate on the first few errors initially and then move to the later ones if they are still observed after dealing with the first ones.

The first warnings we see are these:

Warning (StreamProcessor.cpp)[ 479] putPacket: Instantanous samplerate more than 1% off nominal. [Nom fs: 48000.000000, Instantanous fs: 192000.000000, diff: -144000.000000 ( -3.000000)]
Debug (StreamProcessor.cpp)[ 491] putPacket: cy 0002 rather large TSP difference TS=01695751026 => TS=01695752050 (1024, nom 4096)
1362291141069644: Warning (StreamProcessor.cpp)[ 479] putPacket: Instantanous samplerate more than 1% off nominal. [Nom fs: 48000.000000, Instantanous fs: 27432.398493, diff: 20567.601507 ( 0.428492)]
Debug (StreamProcessor.cpp)[ 491] putPacket: cy 0005 rather large TSP difference TS=01695756146 => TS=01695763313 (7167, nom 4096)

For the moment we can put these to one side because they can occur during start up as the computer and audio interface synchronise to each other.

The first real indication of trouble comes via these messages:

Debug (IsoHandlerManager.cpp)[1516] putPacket: (0x20bead0) dropped 1 packets on cycle 9, 'dropped'=0, cycle=9, m_last_cycle=7
Debug (StreamProcessor.cpp)[ 534] putPacket: (0x20beec0) Correcting timestamp for dropped cycles, discarding packet...
Debug (IsoHandlerManager.cpp)[1516] putPacket: (0x20bead0) dropped 1 packets on cycle 25, 'dropped'=0, cycle=25, m_last_cycle=23
Debug (StreamProcessor.cpp)[ 534] putPacket: (0x20beec0) Correcting timestamp for dropped cycles, discarding packet...
Debug (IsoHandlerManager.cpp)[1516] putPacket: (0x20bead0) dropped 1 packets on cycle 41, 'dropped'=0, cycle=41, m_last_cycle=39
Debug (StreamProcessor.cpp)[ 534] putPacket: (0x20beec0) Correcting timestamp for dropped cycles, discarding packet...
Debug (IsoHandlerManager.cpp)[1516] putPacket: (0x20bead0) dropped 1 packets on cycle 57, 'dropped'=0, cycle=57, m_last_cycle=55
Debug (StreamProcessor.cpp)[ 534] putPacket: (0x20beec0) Correcting timestamp for dropped cycles, discarding packet...
Debug (IsoHandlerManager.cpp)[1516] putPacket: (0x20bead0) dropped 1 packets on cycle 97, 'dropped'=0, cycle=97, m_last_cycle=95
Debug (StreamProcessor.cpp)[ 534] putPacket: (0x20beec0) Correcting timestamp for dropped cycles, discarding packet...
Debug (IsoHandlerManager.cpp)[1516] putPacket: (0x20bead0) dropped 1 packets on cycle 105, 'dropped'=0, cycle=105, m_last_cycle=103
Debug (StreamProcessor.cpp)[ 534] putPacket: (0x20beec0) Correcting timestamp for dropped cycles, discarding packet...

Several hundred such messages are seen, but they are not strictly periodic: the time between them does vary a little. What they do indicate is that some packets are going missing - that is, presumedly the interface is sending them but the computer is not receiving them. The warning is based on the assumption that the interface does send one packet per "cycle"; since there's a skip in the cycle number it's assumed that a packet went missing. Unless for some reason the Audiofire is withholding packets every so often, this would be a situation which would need to be solved before reliable operation of the interface can be carried out.

What's of particular note is that it's always exactly one cycle that's being skipped. Given this, it could be that the interface is simply not sending a packet in those cycles. The problem I have with that idea is that if the interface was prone to do this then I would have expected the AudioFire driver to take this into account. For that reason (and only that reason) I would err on the side of thinking that this is a fault condition of some kind.

If it is assumed that there is a fault causing these skipped cycles, the next question is "what?". As previously suggested, there may be an issue with the NEC firewire chipset in use. Our page noting good and bad host controllers does indicate that the NEC chipsets can be problematic. However, yours is a "Firewarden" chipset which isn't explicitly mentioned on the page so it's hard to draw any conclusions from this.

Another possibility is a bad cable. Bad Firewire cables can show many different symptoms, many of which are hard to logically equate with cable trouble. Is it feasible for you to try your interface out with a different firewire cable?

Is the AudioFire interface the only device on the firewire bus at the time you run these tests?

What I think we can rule out at this point is an issue with the firmware. The incompatibilities I mentioned in my earlier response have quite different symptoms to what we're seeing in your logs.

I doubt it would be the

I doubt it would be the cable issue, since it's working fine when I boot into the Windows partition. However, I'll just buy another firewire controller and see if it resolves the problem.

Thanks very much for taking your time to share your insight of the problem with me!

support

How do the mic inputs work, for anyone using this(does the phantom power turn on?) and about Hi-Z.. will the guitars power up?

yes, read your manual

the hi-z need is autodetected by the preamps, the phantom power has a button to set in ffado-mixer which though is largely unlabeled, but is quite complete. Haven't tested it but am willing to.

message and xruns

Hi everybody

Thank you for your great work.

I have the audiofire4 on an ubuntustudio10.04 and when i run 'ffado-dbus server' (I do it to run ffado-mixer and it's OK) I have this message:

00447257687: Warning (fireworks_session_block.cpp)[ 257] loadFromMemory: size not correct: got 13392, should be -4 according to data

I have also xruns every minutes. Is there a link between these two events and what can I do ?

Thank you for your help.

ffado mixer cant connect to dbus server ffado ( ubuntu 10.04 )

been using this device on xp,7,osx, ubuntustudio 9.04, 9.10, and now on 10.04. on ubuntu 10.04 , when launching ffado mixer, i get " a cant connect dbus mssg ", with a retry button below, so i cant access the mixer to adjust settings on the echo audiofire4, i have'nt had any problems until ubuntu 10.04. it works fine on 9.10 and 9.04. thx todd(fedexnman)

If hitting the retry-button

If hitting the retry-button doesn't actually help, start "ffado-dbus-server" in a konsole/xterm, watch its output and then start "ffado-mixer" from another konsole/xterm.

If that fails, please contact us via the mailing list and attach the output of these two commands...

Hi there

I just purchased this device. I have been running the layla 24 on linux for the past few years with no problems. Jack starts fine but I do get the odd xrun which i was really hoping to avoid. Every couple of minutes there is an odd xrun. System is not under any strain really.
Any ideas ? Is it my version of Jack and/or FFADO ?

Conor