All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: James Courtier-Dutton <James@superbug.demon.co.uk>
Cc: ALSA development <alsa-devel@alsa-project.org>
Subject: Re: [PATCH] AudigyLS updates.
Date: Wed, 30 Jun 2004 18:39:13 +0200	[thread overview]
Message-ID: <s5hzn6l9f0u.wl@alsa2.suse.de> (raw)
In-Reply-To: <40E0117D.6010503@superbug.demon.co.uk>

At Mon, 28 Jun 2004 13:39:25 +0100,
James Courtier-Dutton wrote:
> 
> Takashi Iwai wrote:
> > 
> >>2) Add a CAPUTRE source switch for switch between "MIC", "Line in", 
> >>"SPDIF in", "TAD in", "AUX in" and "What u hear". Currently, one cannot 
> >>switch to capture "SPDIF in" or "What u hear", but all the other inputs 
> >>are possible via switches in the AC97.
> > 
> > 
> > This will need better control on user-space.
> > ac97 mixer will provide the generic capture source only...
> > 
> > 
> > Takashi
> > 
> > 
> 
> I am adding better controls as I find out what does what.
> How is the userspace mixer controls status? (Using a lisp .conf file to 
> control how the mixer behaves).

Jaroslav has been working on this, but I think it's not ready yet...

> What shall I call the AC97 capture controls?
> 1) AC97 Master CAPTURE.
> 2) AC97 MIC CAPTURE.
> 3) AC97 Line in CAPTURE.
> 4) AC97 TAD in CAPTURE.
> 5) AC97 AUX CAPTURE.
> option (1) to (5) can act together, so one can record some from MIC and 
> also some from Line in at the same time.

In the case of SB16, it's simply like 'Mic Capture Switch'.

> 6) Feedback into PLAYBACK from CAPTURE.

Isn't it 'what u hear'?  What's different from 'master capture'?

> There is also another capture source register I have found out about.
> 0 - Selects SPDIF CAPTURE.
> 1 - What you hear CAPTURE.
> 2 - Unknown
> 3 - AC97 CAPTURE. (See 1) to 5) above)
> If this register is not set to 3, all the AC97 inputs are muted.
> 
> I think I will add some new control renaming/deleting code, so that only 
> the controls I know about are displayed to the user. I can put an #if 1 
> ... #endif round it, so that I can disable the renaming when I am testing.

The simplest way would be to implement enum as the capture source as
an exclusive capture source.  Of course the only drawback is that one
cannot choose Line and CD at the same time in this case, but I don't
think not many people will complain against this restriction.


> Is there a document somewhere for alsa-driver developers that states 
> what one should set things to as the default, the "on start up" settings?

No, it's up to the device.
In general, we choose the mute as default, but I think not all volumes
have to be muted (e.g. only PCM and Master).

> E.g.
> Initial Analog volume controls.
> Should digital out be enabled at startup, or analog outputs.
> 
> I think we should have the following (although the audigyls.c does not 
> follow this yet!):-
> Analog volume controls muted.
> Default to Analog output.
> 
> In windows the defaults are:
> I don't know what the analog defaults are.
> digital out is disabled at start up.

IMO, these initial state can be handled better from the user-space,
once when we have dB-based volume controls.

> The windows driver controls digital output using a on/off switch called 
> "SPDIF Out"
> 
> I think it might be a good idea to change the "Audigy Analog/Digital 
> Output Jack"  to instead say "SPDIF Out", with it defaulting to off for 
> Analog.

Well, this is a switch for the shared output jack, so "SPDIF Out"
would be too ambiguous for its purpose.  But I agree with the renaming
to a more reasonable one.

> The "Audigy Analog/Digital Output Jack" being an on/off switch was 
> confusing, because it was not clear to a casual user what [off] meant. 
> Does that mean "Analog off", or "Digital off".

Yes.


Takashi


-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com

  reply	other threads:[~2004-06-30 16:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-25 21:37 [PATCH] AudigyLS updates James Courtier-Dutton
2004-06-28 10:48 ` Takashi Iwai
2004-06-28 12:39   ` James Courtier-Dutton
2004-06-30 16:39     ` Takashi Iwai [this message]
2004-07-01 12:34       ` James Courtier-Dutton
2004-07-01 13:30         ` Takashi Iwai

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=s5hzn6l9f0u.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=James@superbug.demon.co.uk \
    --cc=alsa-devel@alsa-project.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.