Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>, alsa-devel@alsa-project.org
Cc: clemens@ladisch.de, linux1394-devel@lists.sourceforge.net,
	fenlason@redhat.com, ffado-devel@lists.sf.net
Subject: Re: [RFC][PATCH 00/15 v4] OXFW driver, a succesor to firewire-speakers
Date: Sun, 26 Oct 2014 23:15:24 +0900	[thread overview]
Message-ID: <544D01FC.6000408@sakamocchi.jp> (raw)
In-Reply-To: <20141026130032.593f268a@kant>

Hi Stefan,

On Oct 26 2014 21:00, Stefan Richter wrote:
> Conclusion:
> -----------
> 
> In my tests, the patch set does not regress with LaCie FireWire Speakers,
> does not regress with Griffin FireWave + Jack, and it fixes FireWave for
> stereo playback through ALSA client applications.  Therefore and for the
> much extended device support and features (which I could not test myself
> due to lack of hardware), I would be glad if these patches were to be
> queued up for mainline merge and am offering a
> 
> Tested-by: Stefan Richter <stefanr@s5r6.in-berlin.de> (Speakers, FireWave)
> 
> tag. Thank you,

Thanks for your test and report. And I'm sorry to notice your message
after I posted my patches to alsa-devel...

[alsa-devel] [PATCH 00/29 v2] ALSA: Enhancement for existed FireWire drivers
http://mailman.alsa-project.org/pipermail/alsa-devel/2014-October/082844.html


> Stock, i.e. snd-firewire-speakers:     Patched, i.e. snd-oxfw:
>     Card: FireWire Speakers                Card: FWSpeakers
>     Chip: OXFW970                          Chip: FWSpeakers
...
> Alsamixer displays different chip names.
> Stock, i.e. snd-firewire-speakers:     Patched, i.e. snd-oxfw:
>     Card: FireWave                         Card: FireWave
>     Chip: OXFW970                          Chip: FireWave

This is due to second parameter for snd_pcm_new().

[alsa-devel] [PATCH 18/29] ALSA: oxfw: Split PCM functionality to a new file
http://mailman.alsa-project.org/pipermail/alsa-devel/2014-October/082857.html

In my patchset, the parameter refers to 'struct snd_card.driver'. For
these two models, this member refers to 'struct device_info.driver_name'
and it's hard-coded. This may be a bit meddling.

>     There is distortion on channel 2 (R) channel.  The type of
>     distortion depends on the audio which is played back.  It can be
>     pops, buzzing, or a high continuous hissing tone (I guess a 22.05
>     kHz tone).

I heard it.

I understand it's due to the difference of stream format.
$ cat /proc/asound/FireWave/firewire/formation
Input Stream to device:
	Rate	PCM	MIDI
 	48000	6	0
 	32000	6	0
 	44100	6	0
 	96000	6	0
 	32000	2	0
*	44100	2	0
 	48000	2	0

Old snd-firewire-speakers just change sampling rate without changing
stream format. If the device wait for 6ch PCM samples in a data block of
AMDTP packet but the driver transfer 2ch PCM samples in a data block of
AMDTP packet (or vice versa), the device handles the samples badly and
sounds hiss noise.

>     This is the same behavior as I remember it from the time when
>     snd-firewire-speakers was merged into the mainline in 2.6.39.

If so, you and Clemens should have mentioned about it anywhere (maybe in
commit message). It brings a new device to my home ;)

Anyway, thanks for your and Clemens' work. Enjoy playing music!


Regards

Takashi Sakamoto
o-takashi@sakamocchi.jp

      reply	other threads:[~2014-10-26 14:15 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-13 14:27 [RFC][PATCH 00/15 v4] OXFW driver, a succesor to firewire-speakers Takashi Sakamoto
2014-05-13 14:27 ` [PATCH 01/15] speakers: Rename to oxfw and rename some members Takashi Sakamoto
2014-05-13 14:27 ` [PATCH 02/15] oxfw: Move to its own directory Takashi Sakamoto
2014-05-13 14:27 ` [PATCH 03/15] oxfw: Split stream functionality to a new file and add a header file Takashi Sakamoto
2014-05-13 14:27 ` [PATCH 04/15] oxfw: Split PCM functionality to a new file Takashi Sakamoto
2014-05-13 14:27 ` [PATCH 05/15] oxfw: Split control " Takashi Sakamoto
2014-05-13 14:27 ` [PATCH 06/15] oxfw: Change the way to name card Takashi Sakamoto
2014-05-13 14:27 ` [PATCH 07/15] oxfw: Change the way to make PCM rules/constraints Takashi Sakamoto
2014-05-13 14:27 ` [PATCH 08/15] oxfw: Add proc interface for debugging purpose Takashi Sakamoto
2014-05-13 14:27 ` [PATCH 09/15] oxfw: Change the way to start stream Takashi Sakamoto
2014-05-13 14:27 ` [PATCH 10/15] oxfw: Add support for AV/C stream format command to get supported stream formation Takashi Sakamoto
2014-05-13 14:27 ` [PATCH 11/15] oxfw: Add a quirk for Griffin FireWave Takashi Sakamoto
2014-05-13 14:27 ` [PATCH 12/15] oxfw: Add support for Behringer/Mackie devices Takashi Sakamoto
2014-08-10 15:54   ` [alsa-devel] " Clemens Ladisch
2014-08-11 23:48     ` Takashi Sakamoto
2014-08-12  7:33       ` [alsa-devel] " Clemens Ladisch
2014-08-12 23:21         ` Takashi Sakamoto
2014-08-13  6:41           ` Clemens Ladisch
2014-08-13  7:00             ` Takashi Sakamoto
2014-08-13  7:07               ` Clemens Ladisch
2014-08-13  7:57                 ` Takashi Sakamoto
2014-05-13 14:27 ` [PATCH 13/15] oxfw: Add support AMDTP in-stream and PCM capture Takashi Sakamoto
2014-05-13 14:27 ` [PATCH 14/15] oxfw: Add support for capture/playback MIDI messages Takashi Sakamoto
2014-05-13 14:27 ` [PATCH 15/15] oxfw: Add hwdep interface Takashi Sakamoto
2014-05-13 17:43 ` [RFC][PATCH 00/15 v4] OXFW driver, a succesor to firewire-speakers Stefan Richter
2014-05-14 14:15   ` Takashi Sakamoto
2014-08-10 15:54 ` Clemens Ladisch
2014-08-11 23:55   ` Takashi Sakamoto
2014-08-12  7:09     ` Clemens Ladisch
2014-08-12 22:45       ` Takashi Sakamoto
2014-08-13  7:06         ` Clemens Ladisch
2014-08-13 22:55           ` Takashi Sakamoto
2014-10-16 14:31       ` Takashi Sakamoto
2014-10-26 12:00 ` Stefan Richter
2014-10-26 14:15   ` 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=544D01FC.6000408@sakamocchi.jp \
    --to=o-takashi@sakamocchi.jp \
    --cc=alsa-devel@alsa-project.org \
    --cc=clemens@ladisch.de \
    --cc=fenlason@redhat.com \
    --cc=ffado-devel@lists.sf.net \
    --cc=linux1394-devel@lists.sourceforge.net \
    --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