From: Bryce McKinlay <bryce@waitaki.otago.ac.nz>
To: Jeff Koftinoff <jeffk@jdkoftinoff.com>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Byte order in sound drivers
Date: Sun, 02 Dec 2001 16:05:37 +1300 [thread overview]
Message-ID: <3C099A81.6040506@waitaki.otago.ac.nz> (raw)
In-Reply-To: 9A5DA94E-E647-11D5-8040-003065709198@jdkoftinoff.com
Jeff Koftinoff wrote:
> XMMS has endian problems with wav files, but not mp3 files - It is
> listed as a bug as well for sparc. The problem solely lies with
> applications that are written incorrectly.
The most recent release of XMMS (0.9.5) works correctly for me for both
MP3 and WAV files, but not CD audio for which the input plugin returns
sound in the native endian-ness.
But, since that release, the following change was made in XMMS CVS:
Thu Jul 5 12:25:51 CEST 2001 Håvard Kvålen <havardk@xmms.org>
* Output/OSS/audio.c (oss_set_audio_params): Do endian/sign
conversion if necessary.
This breaks it on LinuxPPC 2.4.14-ben0 with both the dmasound and
usb/audio drivers (but, amusingly, fixes the CD audio). Another
application, mplayer, also seems to have the same problem - it says
something like "big endian detected, byte conversion enabled" and
doesn't work, except for 8-bit sound files.
What I want to know is whether these applications are wrong to do this -
does the Linux PPC audio drivers expect audio to be little endian?
regards
Bryce.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-12-02 3:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-01 10:16 Byte order in sound drivers Bryce McKinlay
2001-12-01 10:38 ` Jeff Koftinoff
2001-12-02 3:05 ` Bryce McKinlay [this message]
2001-12-02 3:14 ` Bryce McKinlay
2001-12-02 9:56 ` Benjamin Herrenschmidt
2001-12-02 17:17 ` Benjamin Herrenschmidt
2001-12-09 18:00 ` Giuliano Pochini
2001-12-02 18:42 ` Haavard Kvaalen
2001-12-02 22:39 ` Bryce McKinlay
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=3C099A81.6040506@waitaki.otago.ac.nz \
--to=bryce@waitaki.otago.ac.nz \
--cc=jeffk@jdkoftinoff.com \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).