From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - lib 0000565]: Bug reported to gnomemeeting team
Date: Mon, 18 Oct 2004 18:03:37 +0200 (CEST) [thread overview]
Message-ID: <20041018160337.E07CF11030@server.perex-int.cz> (raw)
A BUGNOTE has been added to this bug.
======================================================================
https://bugtrack.alsa-project.org/alsa-bug/bug_view_page.php?bug_id=0000565
======================================================================
Reported By: mirko
Assigned To:
======================================================================
Project: ALSA - lib
Bug ID: 565
Category: pcm - digital audio
Reproducibility: always
Severity: crash
Priority: normal
Status: new
======================================================================
Date Submitted: 10-04-2004 14:35 CEST
Last Modified: 10-18-2004 18:03 CEST
======================================================================
Summary: Bug reported to gnomemeeting team
Description:
http://bugzilla.gnome.org/show_bug.cgi?id=153770
D. Sandras says it's a big-endian/little-endian problem and suggested to
report it here.
======================================================================
----------------------------------------------------------------------
jcdutton - 10-04-2004 15:01 CEST
----------------------------------------------------------------------
Summary of bug:
S16_BE format fails.
The following works:
arecord -f S16_LE -c 1 -r 8000 -D plughw:0 >test1.wav
The following fails:
arecord -f S16_BE -c 1 -r 8000 -D plughw:0 >test1.wav
arecord: begin_wave:1617: Wave doesn't support S16_BE format...
As this is a plug device, it should work.
----------------------------------------------------------------------
tiwai - 10-04-2004 15:58 CEST
----------------------------------------------------------------------
WAV format doesn't support big-endian. That's independent from plug
layer.
----------------------------------------------------------------------
jdthood - 10-17-2004 15:13 CEST
----------------------------------------------------------------------
What is probably the same bug was reported to the Debian BTS:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=245040
----------------------------------------------------------------------
tiwai - 10-18-2004 18:03 CEST
----------------------------------------------------------------------
Hmm, too little info. Can't you get a bt with symbols?
At least, we need to know the h/w information and hw_params,
sw_params setting running in GM.
Bug History
Date Modified Username Field Change
======================================================================
10-04-04 14:35 mirko New Bug
10-04-04 15:01 jcdutton Bugnote Added: 0002010
10-04-04 15:58 tiwai Bugnote Added: 0002011
10-17-04 15:13 jdthood Bugnote Added: 0002192
10-18-04 18:03 tiwai Bugnote Added: 0002198
======================================================================
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
next reply other threads:[~2004-10-18 16:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-18 16:03 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-07-08 8:35 [ALSA - lib 0000565]: Bug reported to gnomemeeting team bugtrack
2005-02-14 15:20 bugtrack
2005-02-13 10:03 bugtrack
2004-10-17 13:13 bugtrack
2004-10-04 13:58 bugtrack
2004-10-04 13:01 bugtrack
2004-10-04 12:35 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=20041018160337.E07CF11030@server.perex-int.cz \
--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