All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benny Sjostrand <gorm@cucumelo.org>
To: Friedrich Ewaldt <friedrich.ewaldt@gmx.de>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: cs46xx -> Terratec DMX XFire 1024 4channel output success
Date: Mon, 07 Apr 2003 23:27:07 +0200	[thread overview]
Message-ID: <3E91ED2B.3020902@cucumelo.org> (raw)
In-Reply-To: 3E91C251.8020405@gmx.de

> Yep, 0x592d works perfectly and I also find that "0x592d" as last 
> output of /proc/asound/card0/ac97#0regs. 


Great!

> Just to get sure you didn't misunderstand me :)
> Volume control of the second output DOES work (using the 'headphones' 
> slider), but the 'PCM' slider only controls the first output's volume.
>
> I think I'm beginning to understand why:
> The second output is a pure PCM output, i.e. no mixing of CD, line-in, 
> mic-in, ... as for the first output. Therefore, there is only *one* 
> mixer element to control the second output. Only the name "headphones" 
> is misleading.
> In the new 4 channel configuration this control could have been named 
> "PCM2" or "rear PCM" or ...
> ... or isn't "headphones" sometimes the correct name?

Yeah that make sense, I was about to ask you if did'nt have a 
"Headphone" control in your mixer.

About the "Headphone" maybe a more correct name could be "Alternate 
Output", well, dont know, as that is done in the ac97 layer.

>
> That leads to the next point:
> Is it possible to switch back to the oly behaviour at run time? (seem 
> like the decision in which mode to initialize the codec is done while 
> starting alsa). Using the second output as a headphone output of the 
> first PCM device is not completely wrong: On the XFire there are 
> jumpers which you can use to select the output type (amplified for 
> loudspeakers -or- line level) of the *first* output only. The second 
> output is always at line level, i.e. suitable for 600Ohm headphones.
> I don't know whether it's a good idea to allow switching back to the 
> 2channel ("front-back-always-the-same-sound") for using headphones to 
> hear at the first output.
> I think there is an alternative: It should be possible to copy the 
> data from the first output to the second output by some .asoundrc 
> magic. But: how much CPU time will alsa eat for this (keeping in mind 
> that the codec itself can do the same without any CPU cost)? If it's 
> not too much, I wouldn't see any reason for switching back to the old 
> codec configuration.
> What do you think? (I know, you don't have the XFire, but anyway ;-) )
>  fe

To get back to the previous mode, it's just to unset the EAM bit. Maybe 
we could have a control in the mixer for that like "4 channel 
duplicate", or something that just unset/set the EAM bit when desired.

/Benny




-------------------------------------------------------
This SF.net email is sponsored by: ValueWeb: 
Dedicated Hosting for just $79/mo with 500 GB of bandwidth! 
No other company gives more support or power for your dedicated server
http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/

      reply	other threads:[~2003-04-07 21:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-30 18:51 [PATCH] cs46xx: Center-LFE channel support + a lot of hacking Benny Sjostrand
2003-04-02 14:47 ` Takashi Iwai
2003-04-02 20:30 ` Friedrich Ewaldt
2003-04-05 22:45   ` Benny Sjostrand
2003-04-06 12:29     ` cs46xx -> Terratec DMX XFire 1024 4channel output success Friedrich Ewaldt
2003-04-06 22:23       ` Benny Sjostrand
2003-04-07 18:24         ` Friedrich Ewaldt
2003-04-07 21:27           ` Benny Sjostrand [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=3E91ED2B.3020902@cucumelo.org \
    --to=gorm@cucumelo.org \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=friedrich.ewaldt@gmx.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 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.