alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Takashi Sakamoto <o-takashi@sakamocchi.jp>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	Jay Fenlason <fenlason@redhat.com>
Subject: Re: Griffin FireWave stream format information
Date: Fri, 28 Feb 2014 10:56:32 +0100	[thread overview]
Message-ID: <20140228105632.1a436d21@stein> (raw)
In-Reply-To: <530EB782.6090205@sakamocchi.jp>

On Feb 27 Takashi Sakamoto wrote:
> Stefan or Jay,
> 
> Could I request you to get outputs against command in this message with
> FireWave?

Jay already responded, but 

[...]
> Based on this guess and according to its manual, FireWave should have 7
> entries:
> $ firewire-request /dev/fw8 fcp 0x01ffbfc100000000ffff01ff
> 0c ff bf c1 00 00 00 00 ff 00 01 90 40 02 02 01 06 06

$ firewire-request /dev/fw8 fcp 0x01ffbfc100000000ffff01ff
response: 000: 0c ff bf c1 00 00 00 00 ff 00 01 90 40 02 02 01 ............@...
response: 010: 06 06                                           ..

> $ firewire-request /dev/fw8 fcp 0x01ffbfc100000000ffff02ff
> 0c ff bf c1 00 00 00 00 ff 00 02 90 40 03 02 01 06 06

$ firewire-request /dev/fw8 fcp 0x01ffbfc100000000ffff02ff
response: 000: 0c ff bf c1 00 00 00 00 ff 00 02 90 40 03 02 01 ............@...
response: 010: 06 06                                           ..

> $ firewire-request /dev/fw8 fcp 0x01ffbfc100000000ffff03ff
> 0c ff bf c1 00 00 00 00 ff 00 03 90 40 04 02 01 06 06

$ firewire-request /dev/fw8 fcp 0x01ffbfc100000000ffff03ff
response: 000: 0c ff bf c1 00 00 00 00 ff 00 03 90 40 05 02 01 ............@...
response: 010: 06 06                                           ..

> $ firewire-request /dev/fw8 fcp 0x01ffbfc100000000ffff04ff
> 0c ff bf c1 00 00 00 00 ff 00 04 90 40 05 02 01 06 06

$ firewire-request /dev/fw8 fcp 0x01ffbfc100000000ffff04ff
response: 000: 0c ff bf c1 00 00 00 00 ff 00 04 90 40 02 02 01 ............@...
response: 010: 02 00                                           ..

> (These four is for 6ch sound for usual 5.1ch surround)
> $ firewire-request /dev/fw8 fcp 0x01ffbfc100000000ffff05ff
> 0c ff bf c1 00 00 00 00 ff 00 05 90 40 02 02 01 02 06

$ firewire-request /dev/fw8 fcp 0x01ffbfc100000000ffff05ff
response: 000: 0c ff bf c1 00 00 00 00 ff 00 05 90 40 03 02 01 ............@...
response: 010: 02 00                                           ..

> $ firewire-request /dev/fw8 fcp 0x01ffbfc100000000ffff06ff
> 0c ff bf c1 00 00 00 00 ff 00 06 90 40 03 02 01 02 06

$ firewire-request /dev/fw8 fcp 0x01ffbfc100000000ffff06ff
response: 000: 0c ff bf c1 00 00 00 00 ff 00 06 90 40 04 02 01 ............@...
response: 010: 02 00                                           ..

> $ firewire-request /dev/fw8 fcp 0x01ffbfc100000000ffff07ff
> 0c ff bf c1 00 00 00 00 ff 00 07 90 40 04 02 01 02 06

$ firewire-request /dev/fw8 fcp 0x01ffbfc100000000ffff07ff
response: 000: 0a ff bf c1 00 00 00 00 ff ff 07 ff             ............

> (These three is for 2ch stereo sound for Dolby Pro Logic II)
> 
> Would you please confirm these output?

So this seems to be the same as from Jay's FireWave specimen.
Here are results of the other requests from your subsequent mail:

$ firewire-request /dev/fw8 fcp 0x01ffbfc000000000ffffffff
response: 000: 0c ff bf c0 00 00 00 00 ff 00 90 40 04 02 01 06 ...........@....
response: 010: 06                                              .

$ firewire-request /dev/fw8 fcp 0x00ffbfc100000000ff0090400202010200
response: 000: 08 ff bf c1 00 00 00 00 ff 00 90 40 02 02 01 02 ...........@....
response: 010: 00                                              .

$ firewire-request /dev/fw8 fcp 0x00ffbfc100000000ff0090400302010200
response: 000: 08 ff bf c1 00 00 00 00 ff 00 90 40 03 02 01 02 ...........@....
response: 010: 00                                              .

$ firewire-request /dev/fw8 fcp 0x00ffbfc100000000ff0090400402010200
response: 000: 08 ff bf c1 00 00 00 00 ff 00 90 40 04 02 01 02 ...........@....
response: 010: 00                                              .

-- 
Stefan Richter
-=====-====- --=- ===--
http://arcgraph.de/sr/

       reply	other threads:[~2014-02-28  9:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <530EB782.6090205@sakamocchi.jp>
2014-02-28  9:56 ` Stefan Richter [this message]
2014-02-28 11:06   ` Griffin FireWave stream format information Takashi Sakamoto
2014-02-28 13:34     ` Stefan Richter
2014-02-28 13:51       ` Takashi Sakamoto
2014-02-28 14:09         ` Stefan Richter
2014-02-28 14:39           ` Takashi Sakamoto

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=20140228105632.1a436d21@stein \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=fenlason@redhat.com \
    --cc=o-takashi@sakamocchi.jp \
    /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).