From: David Peroutka <david.peroutka@seznam.cz>
To: Takashi Iwai <tiwai@suse.de>
Cc: Trevor Feeney <trev@feens.org>, alsa-devel@lists.sourceforge.net
Subject: Re: Revo 5.1
Date: Thu, 08 Dec 2005 21:42:48 +0100 [thread overview]
Message-ID: <43989AC8.1020203@seznam.cz> (raw)
In-Reply-To: <s5hu0dmjn6f.wl%tiwai@suse.de>
Takashi Iwai wrote:
> At Tue, 06 Dec 2005 09:34:48 -0500,
> Trevor Feeney wrote:
>
>>Was taking a look at the source for the Revo 5.1, noticed a few things.
>>You set it up as using only 6 DACs, going by the 5.1 I figure, but when
>>you consider that it also has the headpone out, it would have the same
>>number of DACs as the 7.1 (8 DACs in all).
>>
>>Takashi - that answers your question in the last thread...from what I've
>>read, the 5.1 only uses one codec, and the headphones would just be a
>>separate channel. I tried adjusting the number of DACs to 8 in the
>>driver, and did manage to get two
>>DAC mixer sliders. I'm not really sure if that was the way to go or
>>not. I tried adjusting the asound plugin to output to 8 channels, pcm
>>device surround71, but that didn't seem to work. I wondering if it
>>needs to be setup separately thant the other 6 channels so that it would
>>be considered it's own PCM device. That goes a bit beyond my realm of
>>knowledge for driver development though...still trying to learn this.
>>Been reading a lot of the documents and such.
>
>
> [Added alsa-devel ML again]
>
> In the case of ice1724, you can open a stereo stream separately.
> The first PCM is assigned to the multi-channel, i.e. 2-8 channels
> interleaved format. The secondary PCM is for SPDIF. The third PCM is
> the "independent" streams. This may have up to 3 substreams, each of
> which is a 2-channel one. If you change num_dacs = 8, you'll be able
> to access plughw:0,2,3 (suppose the card# is 0) for the last two
> channels individually:
>
> % aplay -Dplughw:0,1,3 foo.wav
>
> And you have to raise the corresponding DAC mixer values, of course.
>
>
> Takashi
I've enabled all 8-channels of AK4358 in the driver, but I was unable to
access the 4-th substream, because (as you noted) there are max 3
substreams per PCM, so "plughw:0,2,3" is actually not available (the
other substreams work fine).
I'd really like to try the 4-th substream because there is a good chance
that it is used to drive the headphone output (I see no other chip on
the board for headphone out).
Is there any other way to access the 4-th substream of PCM#2? Looking at
ice1724.c I see no easy way to do that, so I'm again asking you for help :)
Thanks in advance,
David
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
next prev parent reply other threads:[~2005-12-08 20:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <43948A9F.6020009@feens.org>
[not found] ` <43948F9E.50407@seznam.cz>
[not found] ` <4395A188.7060307@feens.org>
2005-12-06 14:49 ` Revo 5.1 Takashi Iwai
2005-12-07 18:36 ` Trevor Feeney
2005-12-08 20:42 ` David Peroutka [this message]
2005-12-09 11:07 ` Takashi Iwai
2005-12-09 14:20 ` Trevor Feeney
2005-12-09 14:47 ` Takashi Iwai
2005-12-09 15:31 ` Trevor Feeney
2005-12-09 15:47 ` Takashi Iwai
2005-12-09 16:04 ` Trevor Feeney
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=43989AC8.1020203@seznam.cz \
--to=david.peroutka@seznam.cz \
--cc=alsa-devel@lists.sourceforge.net \
--cc=tiwai@suse.de \
--cc=trev@feens.org \
/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.