From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Takashi Sakamoto <o-takashi@sakamocchi.jp>
Cc: tiwai@suse.de, alsa-devel@alsa-project.org, clemens@ladisch.de,
ffado-devel@lists.sf.net
Subject: Re: [PATCH 06/13] speakers: Change the way to make PCM rules/constraints
Date: Sun, 2 Feb 2014 16:45:04 +0100 [thread overview]
Message-ID: <20140202164504.20523579@stein> (raw)
In-Reply-To: <52EC94CF.2010306@sakamocchi.jp>
On Feb 01 Takashi Sakamoto wrote:
> Hi Stefan,
>
> Thanks to get these logs. It's really helpful to me.
>
> >> 1.They have both iPCR/oPCR.
>
> They have no oPCRs, against my guess.
>
> I wrote snd-oxfw with an assumption that devices have iPCR/oPCR. So I
> must write some patches for my last RFC:
Neither LaCie FireWire Speakers nor Griffin FireWave have physical
recording inputs. It is therefore sensible that they present
OUTPUT_MASTER_PLUG.output_plugs == 0.
By the way, while LaCie FireWire Speakers is a stereo playback device,
Griffin FireWave is a 6-channel playback device with six physical outputs
(three 3.5 mm stereo receptacles). It also contains a "Dolby™ Digital
decoder and a Dolby Pro Logic II adaptive matrix surround decoder"
according to the user's manual. I have no idea how much of that is
implemented in the FireWave itself and how much is done in the FireWave
driver for OS X.
Apple' OS X built-in FireWire audio driver presents the FireWave as a
output-only device without any control besides the global joint
volume control. I don't know whether it works as a 6-channel device
with the stock driver; it evidently does work at least as a 2-channel
device with stereo sound. In order to use Dolby features on OS X, a
custom driver from Griffin needs to be installed. I haven't tried that
driver myself yet, but I have heard from somebody else that this driver
emits vendor-specific (FCP?) requests to the FireWave to set up 5.1
playback.
I do have a Mac which dual-boots to Apple OS X, and a PCILynx card which
I can put into a Linux box, so I could attempt to analyze those vendor-
specific requests that enable 5.1 output. Though currently, live seems
too short to bother.
Just in case it tells anything useful, here are some parts of alsa-info's
output (from alsa-info.sh version 0.4.63 and kernel 3.13-rc5 without your
patches; I haven't tried your patches yet):
!!Soundcards recognised by ALSA
!!-----------------------------
[...]
2 [FireWave ]: FireWave - FireWave
Griffin FireWave Surround (OXFW970 0104), GUID 0012920600520991 at fw6.0, S400
3 [Speakers ]: FWSpeakers - FireWire Speakers
LaCie FireWire Speakers (OXFW970 0105), GUID 00d04b21010212c8 at fw7.0, S400
!!Aplay/Arecord output
!!--------------------
APLAY
**** List of PLAYBACK Hardware Devices ****
[...]
card 2: FireWave [FireWave], device 0: OXFW970 [FireWave]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 3: Speakers [FireWire Speakers], device 0: OXFW970 [FireWire Speakers]
Subdevices: 1/1
Subdevice #0: subdevice #0
ARECORD
**** List of CAPTURE Hardware Devices ****
[...of course nothing from cards 2 and 3....]
!!Amixer output
!!-------------
[...]
!!-------Mixer controls for card 2 [FireWave]
Card hw:2 'FireWave'/'Griffin FireWave Surround (OXFW970 0104), GUID 0012920600520991 at fw6.0, S400'
Mixer name : 'OXFW970'
Components : ''
Controls : 2
Simple ctrls : 1
Simple mixer control 'PCM',0
Capabilities: pvolume pswitch pswitch-joined
Playback channels: Front Left - Front Right - Rear Left - Rear Right - Front Center - Woofer
Limits: Playback -32768 - 0
Mono:
Front Left: Playback 0 [100%] [on]
Front Right: Playback 0 [100%] [on]
Rear Left: Playback 0 [100%] [on]
Rear Right: Playback 0 [100%] [on]
Front Center: Playback 0 [100%] [on]
Woofer: Playback 0 [100%] [on]
!!-------Mixer controls for card 3 [Speakers]
Card hw:3 'Speakers'/'LaCie FireWire Speakers (OXFW970 0105), GUID 00d04b21010212c8 at fw7.0, S400'
Mixer name : 'OXFW970'
Components : ''
Controls : 2
Simple ctrls : 1
Simple mixer control 'PCM',0
Capabilities: pvolume pvolume-joined pswitch pswitch-joined
Playback channels: Mono
Limits: Playback -11538 - 0
Mono: Playback -3137 [73%] [on]
!!Alsactl output
!!--------------
[...]
state.FireWave {
control.1 {
iface MIXER
name 'PCM Playback Switch'
value true
comment {
access 'read write'
type BOOLEAN
count 1
}
}
control.2 {
iface MIXER
name 'PCM Playback Volume'
value.0 0
value.1 0
value.2 0
value.3 0
value.4 0
value.5 0
comment {
access 'read write'
type INTEGER
count 6
range '-32768 - 0'
}
}
}
state.Speakers {
control.1 {
iface MIXER
name 'PCM Playback Switch'
value true
comment {
access 'read write'
type BOOLEAN
count 1
}
}
control.2 {
iface MIXER
name 'PCM Playback Volume'
value -3137
comment {
access 'read write'
type INTEGER
count 1
range '-11538 - 0'
}
}
}
--
Stefan Richter
-=====-====- --=- ---=-
http://arcgraph.de/sr/
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2014-02-02 15:45 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-05 11:13 [RFC][PATCH 0/8] A new driver for OXFW970/971 based devices Takashi Sakamoto
2014-01-05 11:13 ` [PATCH 1/8] oxfw: Add skelton " Takashi Sakamoto
2014-01-05 11:13 ` [PATCH 2/8] oxfw: Read firmware version to name card Takashi Sakamoto
2014-01-05 11:13 ` [PATCH 3/8] oxfw: Add some AV/C commands for channel formation of AMDTP stream Takashi Sakamoto
2014-01-05 11:13 ` [PATCH 4/8] oxfw: Add connections and streams management Takashi Sakamoto
2014-01-05 11:13 ` [PATCH 5/8] oxfw: Add proc interface for debugging purpose Takashi Sakamoto
2014-01-05 11:13 ` [PATCH 6/8] oxfw: Add MIDI interface Takashi Sakamoto
2014-01-05 11:13 ` [PATCH 7/8] oxfw: Add PCM interface Takashi Sakamoto
2014-01-05 11:13 ` [PATCH 8/8] oxfw: Add hwdep interface Takashi Sakamoto
2014-01-05 19:46 ` [RFC][PATCH 0/8] A new driver for OXFW970/971 based devices Takashi Iwai
2014-01-06 8:33 ` Takashi Sakamoto
2014-01-07 10:07 ` Takashi Iwai
2014-01-10 15:29 ` [RFC][PATCH v2 00/13] speakers: Add support for capture/playback of PCM/MIDI Takashi Sakamoto
2014-01-10 15:29 ` [PATCH 01/13] speakers: move to its own directory Takashi Sakamoto
2014-01-10 15:29 ` [PATCH 02/13] speakers: Split stream functionality to a new file and add a header file Takashi Sakamoto
2014-01-10 15:29 ` [PATCH 03/13] speakers: Split PCM functionality to a new file Takashi Sakamoto
2014-01-10 15:29 ` [PATCH 04/13] speakers: Split control " Takashi Sakamoto
2014-01-10 15:29 ` [PATCH 05/13] speakers: Change the way to name card Takashi Sakamoto
2014-01-10 15:29 ` [PATCH 06/13] speakers: Change the way to make PCM rules/constraints Takashi Sakamoto
2014-01-12 12:18 ` Stefan Richter
2014-01-12 14:44 ` Takashi Sakamoto
2014-01-30 14:21 ` Stefan Richter
2014-02-01 6:31 ` Takashi Sakamoto
2014-02-02 15:45 ` Stefan Richter [this message]
2014-02-03 3:07 ` Takashi Sakamoto
2014-01-10 15:29 ` [PATCH 07/13] speakers: Add proc interface for debugging purpose Takashi Sakamoto
2014-01-10 15:29 ` [PATCH 08/13] speakers: Change the way to start stream Takashi Sakamoto
2014-01-10 15:29 ` [PATCH 09/13] speakers: Add some AV/C commands to get stream formation and supported sampling rates Takashi Sakamoto
2014-01-10 15:29 ` [PATCH 10/13] speakers: Add support for Behringer/Mackie devices Takashi Sakamoto
2014-01-10 15:29 ` [PATCH 11/13] speakers: Add support AMDTP in-stream and PCM capture Takashi Sakamoto
2014-01-10 15:29 ` [PATCH 12/13] speakers: Add support for capture/playback MIDI messages Takashi Sakamoto
2014-01-10 15:29 ` [PATCH 13/13] speakers: Add hwdep interface Takashi Sakamoto
2014-01-10 15:45 ` [RFC][PATCH v2 00/13] speakers: Add support for capture/playback of PCM/MIDI Clemens Ladisch
2014-01-10 15:57 ` Takashi Iwai
2014-01-10 16:18 ` Takashi Sakamoto
2014-01-12 12:35 ` Stefan Richter
2014-01-12 14:53 ` Takashi Sakamoto
2014-01-10 15:59 ` 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=20140202164504.20523579@stein \
--to=stefanr@s5r6.in-berlin.de \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.de \
--cc=ffado-devel@lists.sf.net \
--cc=o-takashi@sakamocchi.jp \
--cc=tiwai@suse.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