alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Jozsef <daniel.jozsef@gmail.com>
To: Daniel Jozsef <daniel.jozsef@gmail.com>,
	ffado-user@lists.sourceforge.net,  alsa-devel@alsa-project.org
Subject: Re: [alsa-devel] Toneweal / Trigaudio FW66 device
Date: Tue, 4 Feb 2020 17:40:05 +0100	[thread overview]
Message-ID: <CAK5Eu=sQFzQe45CyHzEmEe1bs3xwdfH0HeZpHErGJqsqtF3XQg@mail.gmail.com> (raw)
In-Reply-To: <20200129031652.GA2629@workstation>

Hey,

Thanks a lot. That does sound pretty strange. Thankfully, I'm in no hurry
as I'm still mainly using an older Mac for audio stuff, but I'd like to
replace it sooner or later, and getting an upgradable Linux machine sounds
better than paying 1.5 to 2 times as much for a Mac with the same specs
(and no extensibility).

I'll try to do some testing around on my current Linux box. Unfortunately
it's an old machine with a "known problematic" Firewire implementation,
though I doubt that should play a part in device discovery.

Daniel

On Wed, Jan 29, 2020 at 4:16 AM Takashi Sakamoto <o-takashi@sakamocchi.jp>
wrote:

> Hi,
>
> On Tue, Jan 28, 2020 at 10:28:20PM +0000, Daniel Jozsef wrote:
> > I'm a little baffled by what my device just did. :P
> >
> > $ ./firewire-request /dev/fw1 fcp 0x016002c0000100ffff00
> > response: 000: 0c 60 02 c0 00 01 00 ff ff 00 00
> .`.........
> > $ ./firewire-request /dev/fw1 fcp 0x016002c0000101ffff00
> > response: 000: 0c 60 02 c0 00 01 01 ff ff 00 00
> .`.........
> > (<- didn't fail)
> > $ ./firewire-request /dev/fw1 fcp 0x016002c0000102ffff00
> > response: 000: 0c 60 02 c0 00 01 02 ff ff 00 00
> .`.........
> > $ ./firewire-request /dev/fw1 fcp 0x016002c0000103ffff00
> > response: 000: 0c 60 02 c0 00 01 03 ff ff 00 00
> .`.........
> > $ ./firewire-request /dev/fw1 fcp 0x016002c0000104ffff00
> > response: 000: 0c 60 02 c0 00 01 04 ff ff 00 02
> .`.........
> > (<- didn't fail)
> >
> > In fact...
> >
> > $ ./firewire-request /dev/fw1 fcp 0x016002c0000105ffff00
> > response: 000: 0c 60 02 c0 00 01 05 ff ff 00 03
> .`.........
> > $ ./firewire-request /dev/fw1 fcp 0x016002c0000106ffff00
> > response: 000: 08 60 02 c0 00 01 06 ff ff 00                   .`........
> > (<- shorter)
> > $ ./firewire-request /dev/fw1 fcp 0x016002c0000107ffff00
> > response: 000: 08 60 02 c0 00 01 07 ff ff 00                   .`........
> > $ ./firewire-request /dev/fw1 fcp 0x016002c00001ffffff00
> > response: 000: 08 60 02 c0 00 01 ff ff ff 00                   .`........
> > (<-srsly?)
> >
> > As for the second batch:
> >
> > $ ./firewire-request /dev/fw1 fcp 0x016002c0010100ffff00
> > response: 000: 0c 60 02 c0 01 01 00 ff ff 00 00
> .`.........
> > $ ./firewire-request /dev/fw1 fcp 0x016002c0010101ffff00
> > response: 000: 0c 60 02 c0 01 01 01 ff ff 00 00
> .`.........
> > (<- didn't fail)
> >
> > So again...
> >
> > $ ./firewire-request /dev/fw1 fcp 0x016002c0010102ffff00
> > response: 000: 0c 60 02 c0 01 01 02 ff ff 00 00
> .`.........
> > $ ./firewire-request /dev/fw1 fcp 0x016002c0010103ffff00
> > response: 000: 0c 60 02 c0 01 01 03 ff ff 00 02
> .`.........
> > $ ./firewire-request /dev/fw1 fcp 0x016002c0010104ffff00
> > response: 000: 0c 60 02 c0 01 01 04 ff ff 00 03
> .`.........
> > $ ./firewire-request /dev/fw1 fcp 0x016002c0010105ffff00
> > response: 000: 08 60 02 c0 01 01 05 ff ff 00                   .`........
> > (<- shorter)
> > $ ./firewire-request /dev/fw1 fcp 0x016002c0010106ffff00
> > response: 000: 08 60 02 c0 01 01 06 ff ff 00                   .`........
> > $ ./firewire-request /dev/fw1 fcp 0x016002c001010fffff00
> > response: 000: 08 60 02 c0 01 01 0f ff ff 00                   .`........
> >
> > Honestly I have no idea what is going on. :D
>
> It looks to work well.
>
> You tried for input plugs of audio subunit, thus the shorter
> response with 0x08 in the first byte (=NOT IMPLEMENTED) is
> expected for inquiry to 6th input plug.
>
> Hm. I guess your issue is a kind of Heisenbugs[1]. It seems to
> depend on case. To drill down the case in which the issue
> appears, I'd like you to investigate whether you can see the
> same log every time you run with libffado (jackd with Firewire
> backend, or ffado-dbus-server) or not:
>
> > Error (bebob_avplug.cpp)[ 237] discoverPlugType: Plug does not implement
> extended plug info plug type info command
> > Error (bebob_avplug.cpp)[ 120] discover: discover: Could not discover
> plug type (1,1,0,0,1)
>
>
> Additionally, I write a patch for ALSA bebob driver to support
> your device[2]. If you need a prompt solution to use the device in
> Linux-based system, it's available in topic branch of my remote
> repository. But it's required for you to study the way to update
> installed driver modules...
>
> I note that ALSA bebob driver supports transmission of audio frames
> and MIDI messages, thus it's not available to control internal DSP.
>
> [1] https://en.wikipedia.org/wiki/Heisenbug
> [2]
> https://github.com/takaswie/snd-firewire-improve/commit/1c9fabb7dd9de36ea829700df7eb13a40393a679
> [3] https://github.com/takaswie/snd-firewire-improve/tree/topic/fw66
>
>
> Regards
>
> Takashi Sakamoto
>
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel

      reply	other threads:[~2020-02-04 16:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAK5Eu=tVQjBn+YvsHOLqSEir5aV8Q0hA1OgFiJZYdqnspdMz-Q@mail.gmail.com>
     [not found] ` <CAK5Eu=snx3s9r9hoeF4Th0V0YXJYa=7PKUqDn3W4NdWZben-zg@mail.gmail.com>
     [not found]   ` <CAK5Eu=v2x+zFhCygKq8DPWd+CH5JTpZEayg=k2NvaTY7DUNA9g@mail.gmail.com>
     [not found]     ` <CAK5Eu=ucuW6Pp=+j7afPoYgPUdFXjh+PZ-PK6mc+m61M80ZndA@mail.gmail.com>
2020-01-19 16:43       ` [alsa-devel] [FFADO-user] Toneweal / Trigaudio FW66 device Takashi Sakamoto
2020-01-20 11:42         ` Daniel Jozsef
2020-01-20 14:19           ` [alsa-devel] " Takashi Sakamoto
2020-01-24 22:16             ` Daniel Jozsef
2020-01-25  3:18               ` Takashi Sakamoto
2020-01-28 22:28                 ` Daniel Jozsef
2020-01-29  3:16                   ` Takashi Sakamoto
2020-02-04 16:40                     ` Daniel Jozsef [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAK5Eu=sQFzQe45CyHzEmEe1bs3xwdfH0HeZpHErGJqsqtF3XQg@mail.gmail.com' \
    --to=daniel.jozsef@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=ffado-user@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).