From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0001061]: can't test audio with aplay using 16-bit signed LE format; 1.0.7 however works
Date: Sat, 23 Apr 2005 02:08:04 +0200 [thread overview]
Message-ID: <97bc31869627bd23037fae79fc094227@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1061>
======================================================================
Reported By: ukr
Assigned To:
======================================================================
Project: ALSA - driver
Issue ID: 1061
Category: PCI - intel8x0
Reproducibility: always
Severity: minor
Priority: normal
Status: new
Distribution: Fedora Core 3
Kernel Version: Linux 2.6.11
======================================================================
Date Submitted: 04-18-2005 03:24 CEST
Last Modified: 04-23-2005 02:08 CEST
======================================================================
Summary: can't test audio with aplay using 16-bit signed LE
format; 1.0.7 however works
Description:
I usually test my speakers with aplay using
aplay -t raw -f S16_LE -c 6 -r 48000 -Dsurround51
With 1.0.8, when I do this, nothing goes to any of the speakers. However,
when I revert to alsa-driver 1.0.7, it works correctly. I have Intel ICH5
audio with Realtek ALC650F chip with 5.1 channel audio.
Thanks,
Uday.
======================================================================
----------------------------------------------------------------------
ukr - 04-19-05 18:45
----------------------------------------------------------------------
Okay, I now have 1.0.9rc2 versions of both alsa-driver and alsa-lib. I
found that the custom output devices in my .asoundrc are what that are
giving strange noises with 1.0.9rc2 but not with older versions. Here is
my .asoundrc:
pcm.intel8x0 {
type hw
card 0
}
ctl.intel8x0 {
type hw
card 0
}
pcm.ch51dup {
slave.pcm surround51
slave.channels 6
type route
ttable.0.0 1
ttable.1.1 1
ttable.0.2 0.5
ttable.1.2 0.5
ttable.0.3 0.5
ttable.1.3 0.5
ttable.0.4 1
ttable.1.5 1
}
pcm.ch40dup {
type route
slave.pcm surround41
slave.channels 4
ttable.0.0 1
ttable.1.1 1
ttable.0.2 0.5
ttable.1.2 0.5
ttable.0.3 1
ttable.1.4 1
}
Both ch51dup and surround51 give strange noises with xmms; however, when I
changed my output device to "hw:0,0", I get correct output on the two
channels. I have uploaded /etc/asound.state and
/proc/asound/card0/codec97#0/ac97* files (all three concatenated) after I
had set to surround51 and when I was getting that strange noise.
Also when I tested with speaker-test the following way:
speaker-test -D surround51 -c 6 -s <number>
I found that Rear Left and Rear Right were interchanged with Center and
LFE respectively i.e. for 5 and 6, output was on rear left and right, but
speaker-test was showing them as center and lfe respectively. I am using
1.0.9rc2 version of alsa-utils too.
----------------------------------------------------------------------
ukr - 04-23-05 02:08
----------------------------------------------------------------------
I would like to add that surround51 is working correctly but not ch51dup
and ch41dup (which I had set up using the route plug-in in .asoundrc).
Issue History
Date Modified Username Field Change
======================================================================
04-18-05 03:24 ukr New Issue
04-18-05 03:24 ukr Distribution => Fedora Core 3
04-18-05 03:24 ukr Kernel Version => Linux 2.6.11
04-19-05 02:30 ukr Issue Monitored: ukr
04-19-05 17:39 tiwai Note Added: 0004524
04-19-05 17:52 ukr Note Added: 0004530
04-19-05 17:58 tiwai Note Added: 0004531
04-19-05 18:45 ukr Note Added: 0004538
04-19-05 18:46 ukr File Added: debug.output
04-23-05 02:08 ukr Note Added: 0004562
======================================================================
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next reply other threads:[~2005-04-23 0:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-23 0:08 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-03-01 0:05 [ALSA - driver 0001061]: can't test audio with aplay using 16-bit signed LE format; 1.0.7 however works bugtrack
2005-12-30 3:24 bugtrack
2005-04-19 16:45 bugtrack
2005-04-19 15:58 bugtrack
2005-04-19 15:52 bugtrack
2005-04-19 15:39 bugtrack
2005-04-18 1:24 bugtrack
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=97bc31869627bd23037fae79fc094227@bugtrack.alsa-project.org \
--to=bugtrack@alsa-project.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox