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 15:09:16 +0100 [thread overview]
Message-ID: <20140228150916.07416202@stein> (raw)
In-Reply-To: <5310945B.90805@sakamocchi.jp>
On Feb 28 Takashi Sakamoto wrote:
> > To recover to 5.1ch surround, please execute this command:
> > (for 32.0kHz)
> > $ firewire-request /dev/fw8 fcp 0x00ffbfc000000000ff0090400202010200
> > (for 44.1kHz)
> > $ firewire-request /dev/fw8 fcp 0x00ffbfc000000000ff0090400302010200
> > (for 48.0kHz)
> > $ firewire-request /dev/fw8 fcp 0x00ffbfc000000000ff0090400402010200
> > (for 96.0kHz)
> > $ firewire-request /dev/fw8 fcp 0x00ffbfc000000000ff0090400502010200
>
> The last two bytes should be 0x0606.
>
> Within this two bytes, the first byte means the number of data channels
> and the second byte means type of the data channel. So in FireWave, 6ch
> PCM data channel is expressed by 0x0606, 2ch IEC 60958-3 data channel is
> expressed by 0x0200.
$ for n in 2 3 4 5; do echo $n; firewire-request /dev/fw8 fcp 0x00ffbfc000000000ff0090400${n}02010606; sleep 1; firewire-request /dev/fw8 fcp 0x01ffbfc000000000ffffffff; sleep 1; done
2
response: 000: 09 ff bf c0 00 00 00 00 ff 00 90 40 02 02 01 06 ...........@....
response: 010: 06 .
response: 000: 0c ff bf c0 00 00 00 00 ff 00 90 40 02 02 01 06 ...........@....
response: 010: 06 .
3
response: 000: 09 ff bf c0 00 00 00 00 ff 00 90 40 03 02 01 06 ...........@....
response: 010: 06 .
response: 000: 0c ff bf c0 00 00 00 00 ff 00 90 40 03 02 01 06 ...........@....
response: 010: 06 .
4
response: 000: 09 ff bf c0 00 00 00 00 ff 00 90 40 04 02 01 06 ...........@....
response: 010: 06 .
response: 000: 0c ff bf c0 00 00 00 00 ff 00 90 40 04 02 01 06 ...........@....
response: 010: 06 .
5
response: 000: 09 ff bf c0 00 00 00 00 ff 00 90 40 05 02 01 06 ...........@....
response: 010: 06 .
response: 000: 0c ff bf c0 00 00 00 00 ff 00 90 40 05 02 01 06 ...........@....
response: 010: 06 .
--
Stefan Richter
-=====-====- --=- ===--
http://arcgraph.de/sr/
next prev parent reply other threads:[~2014-02-28 14:09 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 ` Griffin FireWave stream format information Stefan Richter
2014-02-28 11:06 ` Takashi Sakamoto
2014-02-28 13:34 ` Stefan Richter
2014-02-28 13:51 ` Takashi Sakamoto
2014-02-28 14:09 ` Stefan Richter [this message]
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=20140228150916.07416202@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).