From: Henry Worth <haworth@ncal.verio.com>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: CDDA playback on Pismo (and other newer models)
Date: Sun, 06 Aug 2000 01:09:41 -0700 [thread overview]
Message-ID: <398D1D45.9A5BA852@ncal.verio.com> (raw)
In-Reply-To: 200008040916.KAA26622@hyperion.valhalla.net
Iain Sandoe wrote:
>
>
> I've been using the xmms CVS tree (www.xmms.org and follow the links). It
> works fine with .wavs of different sample rates etc. [xmms --version ==
> 1.2.1].
>
Which output plugin do you use? And was that on a Pismo?
Looking at eSound and the XMMS ESD output plugin, they simply can't work
with little endian formats like .wav on a big endian machine. The esd
daemon
uses, and sets the output device to, native endiness (there isn't even a
parm to indicate endiness of the incoming data buffer). The XMMS ESD
output plugin completely ignores endiness of the incoming data stream
and
passes it through unchanged (versions 0.9.5, 1.2.1, 1.2.2). A quick hack
to swap bytes in the ESD plugin fixed playback of .wav files. The small
files that had worked before were all 8-bit mono format.
OTOH, the OSS output plugin appears to correctly pass the data stream's
endiness to the sound device, but a quick hack to swap data bytes also
fixed its playback problems. I need to dig into the code some more, but
are we sure the AWACS Screamer in the Pismo isn't one of those variants
that only supports big-endian data? A quick test forcing the
AFMT_*_[LB]E
value to either value for the IOCTL doesn't make a difference.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-08-06 8:09 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-04 9:16 CDDA playback on Pismo (and other newer models) Iain Sandoe
2000-08-04 20:40 ` Henry Worth
2000-08-04 21:03 ` Benjamin Herrenschmidt
2000-08-06 8:09 ` Henry Worth [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-08-08 22:19 Henry Worth
2000-08-07 19:35 Iain Sandoe
2000-08-07 21:49 ` Henry Worth
2000-08-07 9:03 Iain Sandoe
2000-08-07 19:18 ` Henry Worth
2000-08-08 5:02 ` Takashi Oe
2000-08-08 7:01 ` Henry Worth
2000-08-06 21:07 Henry Worth
2000-08-06 9:38 Iain Sandoe
2000-08-06 13:26 ` Takashi Oe
2000-08-06 18:36 ` Henry Worth
2000-08-07 1:25 ` Takashi Oe
2000-08-07 5:02 ` Henry Worth
2000-08-04 13:05 Iain Sandoe
2000-08-04 12:57 Benjamin Herrenschmidt
2000-08-04 5:18 Henry Worth
2000-08-04 9:50 ` Michel Dänzer
2000-08-04 15:56 ` Nelson Abramson
2000-08-04 19:45 ` Henry Worth
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=398D1D45.9A5BA852@ncal.verio.com \
--to=haworth@ncal.verio.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).