From: Paulo Marcel Coelho Aragao <pmcaragao-ag@yahoo.com>
To: alsa-devel@lists.sourceforge.net
Subject: Re: Tips on debugging ALSA driver snd_es18xx
Date: Thu, 15 Dec 2005 09:46:51 -0200 [thread overview]
Message-ID: <20051215114651.GA4263@cortazar> (raw)
In-Reply-To: <s5hd5jyvc3q.wl%tiwai@suse.de>
Takashi Iwai wrote on Dec, 15:
[...]
> > > > I recently switched from OSS to ALSA and I'm baffled by this: aplay
> > > > produces
> > > > sound when playing wav files, but gxine and xmms produce no sound when
> > > > playing streaming audio.
> > > What are the contents of /proc/asound/card0/pcm0p/sub0/hw_params and sw_params
> > > in either case?
[...]
> > This was curious: the wav files I tried with aplay ended too quickly, so I
> > looked for longer ones. My surprise: no sound from the longer ones. It gave me
> > the impression to be related to the sound source being coded for 16 or
> > 8-bits, if I'm not speaking just plain nonsense.
[...]
> Might it be depending on the sample rate?
> Try speaker-test, for example, with different sample rates.
Tried all rates from the aplay/gxine/xmms runs, and also lower and higher
rates but no sound at all, not even with 11127Hz, the rate of the aplay run
that produced sound.
I did notice this line in all speaker-test runs:
Stream parameters are 11127Hz, S16_LE, 1 channels
of course with a differen rate at each run. S16_LE is the format for all
aplay/gxine/xmms runs that didn't produce sound. I don't know precisely what
`format' is, but the aplay run that produced sound had a different value: U8.
[...]
> > PS: Would have at hand a reference to some document that describes
> > /proc/asound ?
> alsa-kernel/Documentation/Procfile.txt (in kernel tree
> linux/Documentation/sounds/alsa/Procfile.txt).
Thanks for this, and more so, thanks for taking your time with such
speed-lightning reply.
Paulo
-------------------------------------------------------
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-15 11:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-15 1:34 Tips on debugging ALSA driver snd_es18xx Paulo Marcel Coelho Aragao
2005-12-15 8:27 ` Clemens Ladisch
2005-12-15 11:12 ` Paulo Marcel Coelho Aragao
2005-12-15 11:22 ` Takashi Iwai
2005-12-15 11:46 ` Paulo Marcel Coelho Aragao [this message]
2005-12-15 12:40 ` Paulo Marcel Coelho Aragao
2005-12-15 15:25 ` Clemens Ladisch
2005-12-15 16:52 ` Paulo Marcel Coelho Aragao
2005-12-15 17:41 ` Takashi Iwai
2005-12-15 19:42 ` Paulo Marcel Coelho Aragao
2005-12-16 14:28 ` Paulo Marcel Coelho Aragao
2005-12-22 15:51 ` 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=20051215114651.GA4263@cortazar \
--to=pmcaragao-ag@yahoo.com \
--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 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.