alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: alsa-devel@alsa-project.org,
	linux1394-devel@lists.sourceforge.net,
	Jay Fenlason <fenlason@redhat.com>
Subject: Re: [PATCH 1/2] ALSA: add LaCie Firewire Speakers/Griffin FireWave surround driver
Date: Tue, 8 Feb 2011 22:10:52 +0100	[thread overview]
Message-ID: <20110208221052.1c9faa9f@stein> (raw)
In-Reply-To: <4D5146FC.7050708@ladisch.de>

On Feb 08 Clemens Ladisch wrote:
> Stefan Richter wrote:
> > Next test:  Plugged the Speakers in, unloaded snd_hda_intel, loaded
> > firewire-ohci, snd_firewire_speakers now gets bound to devie right away.
> > Started xine and played a file.  No complaint.  (Hmm, I wonder whether I
> > had an operator error in my earlier session with FireWave.)  There is the
> > same problem as in the first KDE4 control panel test:  Playback starts
> > with an Autechre remix during the first few seconds. ;-)

I cannot reproduce the noise (clicks) at the start.  But clicks or pops
during playback are fully reproducible with the FireWave.  I am not 100%
sure but I think the Speakers are not affected.

These clicks or pops occur at a fast rate whenever there is a louder
passage in the sound stream.  The pitch and rate of clicks or pops
apparently depends on the spectrum of of the sound stream.  They happen
alongside the normal expected sound.

> If it is the same with both devices, the problem is probably not a wrong
> number of channels.
> 
> Choppy sound could indicate a wrong sample rate.  Jay used speaker-test,
> which uses 48 kHz by default, but most music files are 44.1 kHz, so it
> looks as if switching the sample rate does not work correctly.
> 
> > Alas the missing mixer makes the whole affair not quite usable yet:  The
> > LaCie FireWire Speakers are very loud; too loud for the desk or living
> > room.  On OS X, I had their volume pulled down to the lowest mark.
> 
> Attached are .conf files that enable software volume emulation for
> devices "default", "front", "surround40", and "surround51", but not "hw".
> Put them into /usr/share/alsa/cards/ (or wherever your distribution puts
> them).

This works indeed... most of the time.  Eventually (after device replugs
or driver reloading), somehow this software mixer/ volume control was not
found anymore.  It was back again in a later session.

But I learned that Audacious has an option to add such a software mixer/
volume control itself.

The effect of either way of volume control on the Speakers is that they
become usable (as far as desktop speakers can be considered usable).

The effect on the FireWave is that above mentioned clicks or pops are
avoided if the volume is turned down far enough.  However, at this state
the right channel puts out a high-frequency tone, close to what I suspect
is the upper frequency of the hearing capability of a well-maintained ear.
The left channel doesn't do that.

Furthermore, the muffled sound that the C/S port (the S channel) puts out
under OS X by Apple's stock driver¹ does not occur under Linux.

¹) as if it was driven as a 2.1 system, but it is probably just accidental
because it is too quiet and there are occasional pops on this channel
-- 
Stefan Richter
-=====-==-== --=- -=---
http://arcgraph.de/sr/

------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
mailing list linux1394-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux1394-devel

  reply	other threads:[~2011-02-08 21:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4D46933D.5050609@ladisch.de>
2011-02-07  9:13 ` [PATCH 0/2] LaCie Firewire Speakers/Griffin FireWave support Clemens Ladisch
2011-02-07  9:14   ` [PATCH 1/2] ALSA: add LaCie Firewire Speakers/Griffin FireWave surround driver Clemens Ladisch
2011-02-07 14:40     ` Stefan Richter
2011-02-07 14:56       ` Clemens Ladisch
2011-02-07 21:56       ` Stefan Richter
2011-02-08  8:05         ` Clemens Ladisch
2011-02-08 13:37         ` Clemens Ladisch
2011-02-08 21:10           ` Stefan Richter [this message]
2011-02-07 16:49     ` Stefan Richter
2011-02-07 16:57       ` Clemens Ladisch
2011-02-10  9:46     ` [PATCH] " Clemens Ladisch
2011-02-07  9:14   ` [PATCH 2/2] alsa-lib: add LaCie Firewire Speakers/Griffin FireWave Surround driver Clemens Ladisch

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=20110208221052.1c9faa9f@stein \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=clemens@ladisch.de \
    --cc=fenlason@redhat.com \
    --cc=linux1394-devel@lists.sourceforge.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 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).