alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Clemens Ladisch <clemens@ladisch.de>
To: Stefan Richter <stefanr@s5r6.in-berlin.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, 08 Feb 2011 14:37:00 +0100	[thread overview]
Message-ID: <4D5146FC.7050708@ladisch.de> (raw)
In-Reply-To: <20110207225604.3fe43920@stein>

[-- Attachment #1: Type: text/plain, Size: 1744 bytes --]

Stefan Richter wrote:
> Xine, although configured to the alsa backend, somehow refuses to use the
> alsa backend and falls through to jack which doesn't have any devices
> present at the moment.  Kaffeine which uses xine as backend pops up a
> window that it can't open the sound device.

Unfortunately, xine doesn't have useful error messages ...

Try "aplay -D plughw:FireWave something.wav" (or -D plughw:Speakers).

> KDE4's hardware control, sound pane, shows the card and lets me play the
> test sound on it.  First few seconds are choppy. [...]
> 
> 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. ;-)

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).


Regards,
Clemens

[-- Attachment #2: FWSpeakers.conf --]
[-- Type: text/plain, Size: 516 bytes --]

#
# Configuration for the LaCie Firewire speakers
#

FWSpeakers.pcm.default {
	@args [ CARD ]
	@args.CARD {
		type string
	}
	type plug
	slave.pcm {
		type softvol
		slave.pcm {
			@func concat
			strings [ "dmix:" $CARD ",FORMAT=S32" ]
		}
		control {
			name "PCM Playback Volume"
			card $CARD
		}
	}
}

<confdir:pcm/front.conf>

FWSpeakers.pcm.front.0 {
	@args [ CARD ]
	@args.CARD {
		type string
	}
	type softvol
	slave.pcm {
		type hw
		card $CARD
	}
	control {
		name "PCM Playback Volume"
		card $CARD
	}
}

[-- Attachment #3: FireWave.conf --]
[-- Type: text/plain, Size: 1168 bytes --]

#
# Configuration for the Griffin FireWave Surround
#

FireWave.pcm.default {
	@args [ CARD ]
	@args.CARD {
		type string
	}
	type plug
	slave.pcm {
		type softvol
		slave.pcm {
			@func concat
			strings [ "dmix:" $CARD ",FORMAT=S32" ]
		}
		control {
			name "PCM Playback Volume"
			card $CARD
		}
	}
}

<confdir:pcm/front.conf>

FireWave.pcm.front.0 {
	@args [ CARD ]
	@args.CARD {
		type string
	}
	type softvol
	slave.pcm {
		type hw
		card $CARD
	}
	control {
		name "PCM Playback Volume"
		card $CARD
	}
}

<confdir:pcm/surround40.conf>

FireWave.pcm.surround40.0 {
	@args [ CARD ]
	@args.CARD {
		type string
	}
	type softvol
	slave.pcm {
		type hw
		card $CARD
	}
	control {
		name "PCM Playback Volume"
		card $CARD
	}
}

<confdir:pcm/surround41.conf>
<confdir:pcm/surround50.conf>
<confdir:pcm/surround51.conf>

FireWave.pcm.surround51.0 {
	@args [ CARD ]
	@args.CARD {
		type string
	}
	type route
	ttable [
		[ 1 0 0 0 0 0 ]
		[ 0 1 0 0 0 0 ]
		[ 0 0 0 0 1 0 ]
		[ 0 0 0 0 0 1 ]
		[ 0 0 1 0 0 0 ]
		[ 0 0 0 1 0 0 ]
	]
	slave.pcm {
		type softvol
		slave.pcm {
			type hw
			card $CARD
		}
		control {
			name "PCM Playback Volume"
			card $CARD
		}
	}
}

[-- Attachment #4: Type: text/plain, Size: 160 bytes --]

_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  parent reply	other threads:[~2011-02-08 13:36 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 [this message]
2011-02-08 21:10           ` Stefan Richter
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=4D5146FC.7050708@ladisch.de \
    --to=clemens@ladisch.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=fenlason@redhat.com \
    --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;
as well as URLs for NNTP newsgroup(s).