From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - utils 0001990]: aplay/arecord cannot play/capture A_LAW
Date: Mon, 24 Apr 2006 15:07:32 +0200 [thread overview]
Message-ID: <57204e6e1e71fe55ec56f08cb03b3fae@bugtrack.alsa-project.org> (raw)
The following issue has been REOPENED.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1990>
======================================================================
Reported By: Raymond
Assigned To: tiwai
======================================================================
Project: ALSA - utils
Issue ID: 1990
Category: aplay/arecord
Reproducibility: always
Severity: major
Priority: normal
Status: feedback
======================================================================
Date Submitted: 04-01-2006 04:26 CEST
Last Modified: 04-24-2006 15:07 CEST
======================================================================
Summary: aplay/arecord cannot play/capture A_LAW
Description:
aplay/arecord can play MU_LAW and the sound card support MU_LAW and A_LAW
arecord -D hw:0,0 -f MU_LAW -t au -c 1 -r 8000 test.au
aplay -D hw:0,0 test.au
Try to use -t raw but the quality of A_LAW is very bad when compare with
MU_LAW
arecord -D hw:0,0 -f A_LAW -t raw -c 1 -r 8000 test.raw
aplay -D hw:0,0 test.raw
======================================================================
----------------------------------------------------------------------
tiwai - 04-20-06 15:29
----------------------------------------------------------------------
Yes, _usually_ they are so, but the default status is not strictly
defined.
I see no real bugs, so let's close this one.
----------------------------------------------------------------------
Raymond - 04-24-06 15:07
----------------------------------------------------------------------
Do "type oss" plugin support mu-law ?
It is ok to play mu-law using au88xx driver
http://sourceforge.net/projects/aureal
play mulaw.au
au88xx, alsa-lib-1.0.11 and alsa-plugins-1.0.11 ( oss )
pcm.ossdriver {
type oss
device /dev/dsp
}
aplay -v -Dossdriver test.wav
Playing WAVE 'test.wav' : Signed 16 bit Little Endian, Rate 44100 Hz,
Mono
ALSA <-> OSS PCM I/O Plugin
Its setup is:
stream : PLAYBACK
access : RW_INTERLEAVED
format : S16_LE
subformat : STD
channels : 1
rate : 44100
exact rate : 44100 (44100/1)
msbits : 16
buffer_size : 16384
period_size : 4096
period_time : 92879
tick_time : 0
tstamp_mode : NONE
period_step : 1
sleep_min : 0
avail_min : 4096
xfer_align : 4096
start_threshold : 16384
stop_threshold : 16384
silence_threshold: 0
silence_size : 0
boundary : 1073741824
aplay -Dossdriver mulaw.au
Playing Sparc Audio 'mulaw.au' : Mu-Law, Rate 8000 Hz, Mono
*** OSS: unsupported format MU_LAW
aplay: set_params:961: Unable to install hw params:
ACCESS: RW_INTERLEAVED
FORMAT: MU_LAW
SUBFORMAT: STD
SAMPLE_BITS: 8
FRAME_BITS: 8
CHANNELS: 1
RATE: 8000
PERIOD_TIME: 128000
PERIOD_SIZE: 1024
PERIOD_BYTES: 1024
PERIODS: 4
BUFFER_TIME: 512000
BUFFER_SIZE: 4096
BUFFER_BYTES: 4096
TICK_TIME: [0 0]
aplay -Dplug:ossdriver mulaw.au
Playing Sparc Audio 'mulaw.au' : Mu-Law, Rate 8000 Hz, Mono
*** OSS: unsupported format MU_LAW
aplay: set_params:961: Unable to install hw params:
ACCESS: RW_INTERLEAVED
FORMAT: MU_LAW
SUBFORMAT: STD
SAMPLE_BITS: 8
FRAME_BITS: 8
CHANNELS: 1
RATE: 8000
PERIOD_TIME: 128000
PERIOD_SIZE: 1024
PERIOD_BYTES: 1024
PERIODS: 4
BUFFER_TIME: 512000
BUFFER_SIZE: 4096
BUFFER_BYTES: 4096
TICK_TIME: 0
Issue History
Date Modified Username Field Change
======================================================================
04-01-06 04:26 Raymond New Issue
04-03-06 07:16 Raymond Note Added: 0009085
04-03-06 07:36 Raymond Note Added: 0009086
04-07-06 19:32 tiwai Note Added: 0009152
04-08-06 07:47 Raymond Note Added: 0009171
04-10-06 16:52 tiwai Note Added: 0009199
04-11-06 07:46 Raymond Note Added: 0009229
04-11-06 07:55 Raymond Note Edited: 0009229
04-11-06 09:41 Raymond Note Edited: 0009229
04-20-06 15:29 tiwai Status new => resolved
04-20-06 15:29 tiwai Resolution open => not an issue
04-20-06 15:29 tiwai Assigned To => tiwai
04-20-06 15:29 tiwai Note Added: 0009384
04-24-06 15:07 Raymond Status resolved => feedback
04-24-06 15:07 Raymond Resolution not an issue => reopened
04-24-06 15:07 Raymond Note Added: 0009451
======================================================================
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
next reply other threads:[~2006-04-24 13:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-24 13:07 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-04-25 9:46 [ALSA - utils 0001990]: aplay/arecord cannot play/capture A_LAW bugtrack
2006-04-25 0:59 bugtrack
2006-04-24 14:50 bugtrack
2006-04-24 14:43 bugtrack
2006-04-24 13:48 bugtrack
2006-04-20 13:29 bugtrack
2006-04-11 5:46 bugtrack
2006-04-10 14:52 bugtrack
2006-04-08 5:47 bugtrack
2006-04-07 17:32 bugtrack
2006-04-03 5:36 bugtrack
2006-04-03 5:16 bugtrack
2006-04-01 2:26 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=57204e6e1e71fe55ec56f08cb03b3fae@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 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.