From: Takashi Iwai <tiwai@suse.de>
To: Bernard Urban <Bernard.Urban@meteo.fr>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: CMI8330: success !
Date: Mon, 20 Jan 2003 10:56:16 +0100 [thread overview]
Message-ID: <s5hadhw5em7.wl@alsa2.suse.de> (raw)
In-Reply-To: <8765skqhq7.fsf@merceron.meteo.fr>
At 20 Jan 2003 10:43:28 +0100,
Bernard Urban wrote:
>
>
> Bernard Urban <Bernard.Urban@meteo.fr> writes:
> >
> > Notice that I have deleted the controls with false or zero values to
> > save some place. For card0, the SB controls are absent. There are also
> > some differences between controls for card0 and CARD_0, why ?
> > I get the CARD_0 controls when using alsamixer.
> > The important thing to notice is that the SB
> > controls need not to be unmuted (as I first believe was necessary) !
> > So to have playback it is not needed
> > to define these SB controls in routine cmi8330_add_sb_mixers().
> > But the SB initialization step is probably mandatory (I will test it).
>
> Actually, the cmi8330 card works when undefining ENABLE_SB_MIXER.
> So the init step in snd_sbdsp_create() is sufficient. This is good, as
> you can get rid of these additional and dysfunctional controls.
thanks, nice to know that.
does it work w/o ENABLE_SB_MXIER even after rebooting (i mean, after
resetting the hardware) ?
> >
> > Actually, this is somehow curious, as PLAYBACK_ON_SB is defined, and
> > so playback should go through SB ??? It is apparently not the case.
> >
> > Only one application did not work correctly, namely the old libc5
> > based xquake (yes, I have done
> > echo "xquake.real 0 0 direct" >/proc/asound/card0/pcm0p/oss).
> > There is sound, but extremely noisy.
> >
> > Some words about the behaviour of the SB controls in alsamixer:
> > "SB" control follows the "SB Capture" control value.
> > "SB Synth", "SB PCM" and "SB Speaker" do not respond to commands.
> > "SB CD", "SB Line" and "SB Mic" cannot have values above 10%.
> >
> > I have also tried both "SB Mic" and "Mic" controls in alsamixer,
> > but capture did not work at all (only noise is registered and I have
> > Larsen effect when the volume is pushed too high). Nevertheless,
> > as "SB Mic" cannot have values above 10%, here lies perhaps the
> > problem.
> >
> > I will now try to use #undefine PLAYBACK_ON_SB.
>
> This works also, with ENABLE_SB_MIXER defined,
> but some .wav files played on events in the desktop
> are scratchy (sometimes, not always). So the original
> #define PLAYBACK_ON_SB
> is better.
ok.
> > Concerning the SB16 driver, I could not record either
> > (arecord is blocking indefinitly). Changing the 16 bits DMA control
> > did not help.
>
> No, this works. The blocking occurs when some application has an open
> file descriptor for playback (in my case, esd for gnome, even in the
> state "suspended"). But you must MANUALLY assign 16 bits DMA to
> "Playback" to obtain a successful capture (and conversely
> assign it to "Capture" for playback). The "Auto" value does not work.
> I recall my card is a SB 16 Vibra X PNP, if you want to put a warning
> in the README file about that.
then we can set "playback" as default for Vibra X PnP.
i'm not sure whether it's a general problem for all SB16 Vibra
models, or Vibra X only. does anyone know that?
> Capture for cmi8330: no success at all, with or without
> PLAYBACK_ON_SB, and ENABLE_SB_MIXER defined.
> But I noticed that I cannot capture (mic recording) with DOS or
> Windows either on this machine. The microphone is ok, it is the same
> used for the successful SB16 test. So it is not out of possibility there is
> a hardware problem on my mainboard (the chip is on it, not on an add-on
> card). I have not currently the possibility to test the "line in" entry.
> I will perhaps test the CD one if it makes sense ?
yes, but make sure that you connected the CD-cable :)
ciao,
Takashi
-------------------------------------------------------
This SF.NET email is sponsored by: FREE SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en
next prev parent reply other threads:[~2003-01-20 9:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-16 15:15 Requested: CMI8330 testers? Takashi Iwai
2002-12-27 9:19 ` Bernard Urban
2003-01-08 13:00 ` Takashi Iwai
2003-01-08 16:17 ` Takashi Iwai
2003-01-09 10:55 ` Takashi Iwai
[not found] ` <873cnxz8pz.fsf@merceron.meteo.fr>
[not found] ` <s5hel7hwf4p.wl@alsa2.suse.de>
[not found] ` <87ptqy3ij6.fsf_-_@merceron.meteo.fr>
2003-01-17 13:54 ` CMI8330: success ! Bernard Urban
2003-01-20 9:43 ` Bernard Urban
2003-01-20 9:56 ` Takashi Iwai [this message]
2003-01-21 10:11 ` Bernard Urban
2003-01-21 10:16 ` Takashi Iwai
2003-01-09 15:00 ` Requested: CMI8330 testers? Bernard Urban
2003-01-10 13:29 ` SB 16 driver OSS emulation Bernard Urban
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=s5hadhw5em7.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=Bernard.Urban@meteo.fr \
--cc=alsa-devel@lists.sourceforge.net \
/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