From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Stefan Richter <stefanr@s5r6.in-berlin.de>,
Jay Fenlason <fenlason@redhat.com>
Subject: Re: PCM rules for FireWave in speaker.c
Date: Fri, 28 Feb 2014 20:28:33 +0900 [thread overview]
Message-ID: <531072E1.6060603@sakamocchi.jp> (raw)
In-Reply-To: <53105DA8.1090607@ladisch.de>
Clemens,
> The current rules in speakers.c disallow rates less than 48 kHz if there
> are less than six channels, and disallow two channels if the rate is
> less than 48 kHz. This means that the allowed parameter combinations
> are 2ch at 48/96 kHz, and 6ch at 32/44.1/48/96 kHz.
Oh, I misunderstood it...
>> Recently, with Jay Fenlason's help, I got some information about its
>> stream format. I'll show them in the end of this message.
>>
>> As a result, I realized FireWave has stream formats below:
>> - 6ch PCM at 32.0/44.1/48.0/96.0kHz
>> - 2ch IEC 60958-3 at 32.0/44.1/48.0kHz
>>
>> Although there are no stream formats for 2ch PCM at 48.0/96.0kHz, the
>> driver has it. Do you know the reason? Are there any model quirks?
>
> I don't have any of the AV/C audio specifications; these rules were
> determined experimentally. In other words, when the sample rate is set
> to 48 or 96 kHz, sending a stream with two PCM channels appears to work.
OK. You confirmed it.
> If you wanted to support these undocumented formats in your driver, you
> would have to add some kind of quirk.
Exactly. For PCM, I need to add hard-coded rule. On the other hand, I
want to omit IEC 60958-3 mode because I don't know whether ALSA has
proper interfaces for it. It will not be PCM.
# I wonder why this mailman sometimes don't deliver my mail...
Thanks
Takashi Sakamoto
o-takashi@sakamocchi.jp
prev parent reply other threads:[~2014-02-28 11:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <530FFF88.1040606@sakamocchi.jp>
2014-02-28 9:58 ` PCM rules for FireWave in speaker.c Clemens Ladisch
2014-02-28 11:28 ` Takashi Sakamoto [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=531072E1.6060603@sakamocchi.jp \
--to=o-takashi@sakamocchi.jp \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.de \
--cc=fenlason@redhat.com \
--cc=stefanr@s5r6.in-berlin.de \
/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