All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: need help for PCM constraint/rules
Date: Wed, 27 Mar 2013 01:58:29 +0900	[thread overview]
Message-ID: <5151D3B5.50301@sakamocchi.jp> (raw)
In-Reply-To: <514F5010.5000707@ladisch.de>

Clemens,

Thank you for your advice. The PCM rules in your Dice module also 
matches Fireworks. I apply your solution into my Fireworks module and my 
target device seems to work correctly in any sampling rate.

On this occasion, I have a question to you about your 
firewire-kernel-streaming branch in alsa-kprivate.git. There is no 
commit since last year and I'm anxious about the reason. If it's due to 
your personal, there is no matter (of cource!). But it's due to some 
technical issues or strategies against FFADO project, there is a large 
possibility that I may soon face them. If it's the latter, would you 
please inform me the details?

Regards


Takashi Sakamoto
o-takashi@sakamocchi.jp

Now my Fireworks module can playback PCM stream in any sampling rates.
(Mar 25 2013 04:12), Clemens Ladisch wrote:
> Takashi Sakamoto wrote:
>> My device (AudioFirePre8) changes its channels according to sampling rate. For example:
>> 32.0  - 48.0kHz  : 16ch: efw->channels_sets[0]
>> 88.2  - 96.0kHz     : 12ch: efw->channels_sets[1]
>> 176.4 - 192.0kHz : 10ch: efw->channels_sets[2] (but not available)
>>
>> I managed to write this rule refering to rme9652.c but I cannot achieve my purpose.
>
> These functions should be essentially identical with dice_*_constraint().
>
>
> Regards,
> Clemens

  reply	other threads:[~2013-03-26 16:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-24 13:58 need help for PCM constraint/rules Takashi Sakamoto
2013-03-24 19:12 ` Clemens Ladisch
2013-03-26 16:58   ` Takashi Sakamoto [this message]
2013-03-26 18:24     ` Clemens Ladisch
2013-03-27 12:11       ` 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=5151D3B5.50301@sakamocchi.jp \
    --to=o-takashi@sakamocchi.jp \
    --cc=alsa-devel@alsa-project.org \
    --cc=clemens@ladisch.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.