jackd + libffado + echo audiofire 2

[hiro]

I was able to compile libffado and jackd and have already set my permissions for /dev/raw1394.
My echo audiofire 2 soundcard has 4 inputs and 6 outputs, ffado-mixer has this right.
But when I start jackd with the firewire plugin I think something with the inputs/outputs is wrong.
In qjackctl I see under "readable Clients/output ports" four microphones named system/dev0_unknown, dev0_unknown0, dev0_unknown1 and dev0_unknown2.
On the right side it shows again 5 microphones and one speaker: dev0_unknown4.
For testing I tried few simple clients, but none of them produced any sound. (They all automatically connected to dev0_unknown4 though.
How do I go on from here?

[thorgal]

hi, welcome here

don't know how to fix your firewire issue or whether this is an issue at all. But have you tried to disconnect and reconnect the test clients to all playback ports (not only system:dev_unknown4) ?

[hiro]

With playback ports you mean input ports, right?
When I connect anything to these input ports which show the mic icon I always get this error message:

Destination port in attempted (dis)connection of system:dev0_Unknown and system:dev0_Unknown3 is not an input port
JackAudioDriver::ProcessAsync: read error, skip cycle
JackPosixMutex::Unlock res = 1

[thorgal]

the left hand side port window shows system inputs (microphone, etc, anything that can transfer audio to your firewire device),

the right and side port window shows system outputs (probably your speakers, headphones, whatever device can receive audio).

In general, a working system will have ports named like:

Code: Select all

system:capture_x  | system:playback_x

your system is just weird. Why would that be named like this ? and why h/w ports seem to be confused, i have no clue (probably a ffado issue with your h/w device).

[hiro]

It's a jackdmp issue. 1.9.6 from svn doesn't have this problem any more.

[garybryan]

Hey,

I've been having the same problem. I had the problem on Arch Linux, then I installed Ubuntu Studio and it was fine, but after not using the inteface for a couple of months and going through some system updates in that time, it's broken again.

I've tried installing jackdmp from SVN and I'm still having the same issue. I've also tried to downgrade to Jack 1 as it always worked OK with FireWire, but Ubuntu makes that downgrade practically impossible as a ton of packages now depend on jack2.

Any advice? I'm almost at the point of installing Windows, which I really do hate but it seems like the only way I'll ever be able to get a working music production setup.

[garybryan]

Actually I seem to have fixed it by enabling Synchronous Mode (-S on the Jack command line), after reading about it being used to solve an unrelated problem.

Now I just need to figure out the secret of the below 10ms latencies without Xruns (or even below 100ms latencies without Xruns would be nice!) that everyone else here seems to experience...