All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: Doug McLain <doug@nostar.net>
Cc: alsa-devel@alsa-project.org, clemens@ladisch.de
Subject: Re: plans for fireworks driver
Date: Sun, 10 Mar 2013 19:37:11 +0900	[thread overview]
Message-ID: <513C6257.8050306@sakamocchi.jp> (raw)
In-Reply-To: <513C52C7.7010101@nostar.net>

Doug,

 >> Then I hope you to try playback.I reccomend below process:
 >> 1. use alsamixer to change sampling rate that you hope
 >> 2. use jackd in usual way, or aplay with plughw interface
 >> 3. hear 1/2ch or not
 >
 > Alsamixer successfully changes SR and clock source.  I started jack and
 > played back and edited an ardour session with no problems.  As you said
 > earlier, capture doesn't work.  the ports are there but no signal.  Once
 > that works Ill start using this driver full time.

I'm glad to hear it. I believe you can playback with any sampling rate, 
32.0 - 96.0 kHz for AudioFire2, 32.0 - 192.0 kHz for AudioFire12.

But I cannot hear all of channels which I send. My AudioFirePre8 can 
playback 16ch (differed in current sampling rate). When I playback 16ch 
with aplay or jackd, I can hear only 1/2ch physical output...

I hope you to confirm this on your devices.


Currently my driver fully utilize ALSA's snd-firewire-lib.ko to 
transmitting (and receiving) stream. But snd-firewire-lib.ko has no 
codes for receiving (=PCM capturing). I'm under working for this.

Thanks


Takashi Sakamoto
o-takashi@sakamocchi.jp

(Mar 10 2013 18:30), Doug McLain wrote:
>> I note that your system cannot communicate to your device via FFADO
>> because the device is already used by my module. You can execute
>> "modprobe -r snd-fireworks" if you want to use FFADO.
>
> That's not true.  The ffado tools (the mixer, the discovery & diagnostic
> tools, etc) work fine whether or not the alsa module is loaded, and
> whether or not jack is running on the device.  The problem with the AF12
> and your driver was whatever the problem is with ffado and AF firmware >
> 4.8.  Somehow the Clemens snd-fireworks driver was unaffected.  I dont
> know enough about the driver and hardware to understand why, but I'm
> sure you will figure it out.  I'm glad to see progress on this driver so
> do not hesitate to ask for anything.
>
>> Then I hope you to try playback.I reccomend below process:
>> 1. use alsamixer to change sampling rate that you hope
>> 2. use jackd in usual way, or aplay with plughw interface
>> 3. hear 1/2ch or not
>
> Alsamixer successfully changes SR and clock source.  I started jack and
> played back and edited an ardour session with no problems.  As you said
> earlier, capture doesn't work.  the ports are there but no signal.  Once
> that works Ill start using this driver full time.
>
> -D

      reply	other threads:[~2013-03-10 10:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-08 21:49 plans for fireworks driver Doug McLain
     [not found] ` <513B2B62.9040307@sakamocchi.jp>
2013-03-09 20:52   ` Doug McLain
     [not found]     ` <513BEBE6.6030708@sakamocchi.jp>
2013-03-10  7:28       ` Doug McLain
2013-03-10  9:04         ` Takashi Sakamoto
2013-03-10  9:30           ` Doug McLain
2013-03-10 10:37             ` 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=513C6257.8050306@sakamocchi.jp \
    --to=o-takashi@sakamocchi.jp \
    --cc=alsa-devel@alsa-project.org \
    --cc=clemens@ladisch.de \
    --cc=doug@nostar.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 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.