Ticket #182 (reopened defect)

Opened 3 months ago

Last modified 3 months ago

jack2: strange port names with FFADO backend

Reported by: artfwo Assigned to:
Priority: major Milestone: Jack 2.0
Version: jack2 unknown Keywords: ffado firewire
Cc: artfwo@gmail.com

Description

After upgrading to a development release of Ubuntu 10.10 (which includes jackdmp 1.9.6), I get strange port names with FFADO backend. Here they are:

$ jack_lsp firewire_pcm:dev0_Unknown_in firewire_pcm:dev0_Unknown0_in firewire_pcm:dev0_Unknown1_in firewire_pcm:dev0_Unknown2_in firewire_pcm:dev0_Unknown3_in firewire_pcm:dev0_Unknown_out firewire_pcm:dev0_Unknown0_out firewire_pcm:dev0_Unknown1_out firewire_pcm:dev0_Unknown2_out firewire_pcm:dev0_Unknown3_out firewire_pcm:dev0_Unknown4_out firewire_pcm:dev0_Unknown5_out

This introduces some annoyances in applications, which expect port names like "system:playback_XX" for autoconnecting, etc.

My soundcard is Echo Audiofire 2. Everything worked in Jack 0.118.0. Please fix!

Change History

05/27/10 05:40:46 changed by artfwo

  • keywords set to ffado.

05/27/10 05:41:35 changed by artfwo

  • keywords changed from ffado to ffado firewire.

05/27/10 05:42:24 changed by artfwo

  • cc set to artfwo@gmail.com.

05/27/10 06:45:48 changed by artfwo

  • status changed from new to closed.
  • resolution set to duplicate.

Oh, sorry. That seems already been fixed in r3968 (ticket 163)

05/27/10 08:25:14 changed by artfwo

  • status changed from closed to reopened.
  • resolution deleted.

Sorry, I have to reopen this again. The bug is still present even with fixes from ticket 163.

Upgrading to FFADO svn1813 gives the following output: 

$ jack_lsp 
firewire_pcm:0014860a68bca89d_Unknown_in
firewire_pcm:0014860a68bca89d_Unknown0_in
firewire_pcm:0014860a68bca89d_Unknown1_in
firewire_pcm:0014860a68bca89d_Unknown2_in
firewire_pcm:0014860a68bca89d_Unknown3_in
firewire_pcm:0014860a68bca89d_Unknown_out
firewire_pcm:0014860a68bca89d_Unknown0_out
firewire_pcm:0014860a68bca89d_Unknown1_out
firewire_pcm:0014860a68bca89d_Unknown2_out
firewire_pcm:0014860a68bca89d_Unknown3_out
firewire_pcm:0014860a68bca89d_Unknown4_out
firewire_pcm:0014860a68bca89d_Unknown5_out

$ jack_lsp -A
firewire_pcm:0014860a68bca89d_Unknown_in
   system:capture_1
firewire_pcm:0014860a68bca89d_Unknown0_in
   system:capture_2
firewire_pcm:0014860a68bca89d_Unknown1_in
   system:capture_3
firewire_pcm:0014860a68bca89d_Unknown2_in
   system:capture_4
firewire_pcm:0014860a68bca89d_Unknown3_in
   system:capture_5
firewire_pcm:0014860a68bca89d_Unknown_out
   system:playback_1
firewire_pcm:0014860a68bca89d_Unknown0_out
   system:playback_2
firewire_pcm:0014860a68bca89d_Unknown1_out
   system:playback_3
firewire_pcm:0014860a68bca89d_Unknown2_out
   system:playback_4
firewire_pcm:0014860a68bca89d_Unknown3_out
   system:playback_5
firewire_pcm:0014860a68bca89d_Unknown4_out
   system:playback_6
firewire_pcm:0014860a68bca89d_Unknown5_out
   system:playback_7

05/28/10 07:40:08 changed by adi

  • status changed from reopened to closed.
  • resolution set to invalid.

The output is completely valid and looks exactly as expected. The "unknown" is caused by a missing name vector in FFADO and can only be fixed there.

jackd2 also provides port aliases (system:playbackXX, system:captureXX), so no app should fail.

06/22/10 10:45:37 changed by das

  • status changed from closed to reopened.
  • resolution deleted.

Sorry for reopening this bug again, but I also find this problem really annoying.

First off, the portnames are simply too long and cumbersome to type and use. Why would I even care about the GUID when I, like the majority of FFADO users, have only one firewire interface? And what kind of useful information does "Unknown" convey? If you don't know the port's name, you might as well just assign a number and nothing else.

Another issue is the "numbering" of the ports, which is basically off by two compared to what JACK 1 and most applications use (starting at 1).

To make things even worse, Qjackctl sorts ports in lexicographical order so that the port with no numerical suffix is listed last. As a result, to route a stereo signal to outputs 1 and 2 of my Audiofire 4, I have to connect it to the sixth and first output port shown in Qjackctl...

06/23/10 08:35:46 changed by adi

Have you updated to jackdmp trunk? If not, please do so. If you still experience this behaviour, then you need to understand that portnames come from FFADO, not from JACK, at least the suffix in question.

In other worlds, if latest jackdmp gives you trouble, then file a ticket at subversion.ffado.org and close this one.