From: matt@proweb.co.uk
To: 9fans@cse.psu.edu
Subject: Re: [9fans] how to listen to .wav files?
Date: Mon, 21 Jun 2004 12:07:33 +0100 [thread overview]
Message-ID: <65d199b21ba9fa66d2c581808d399a48@juice.thebigchoice.com> (raw)
In-Reply-To: <ee9e417a04061909184869ebbb@mail.gmail.com>
As Russ said, .wav is just an extension, it doesn't in any way determine the binary contents
.wav (and .avi) are RIFF files, the header of which will tell you the *real* content type of the file (and I don't even think they *have* to be RIFF files, the first few bytes tag it as a RIFF file, I imagine Microsoft's Windows applications would be able to discern other types of media.
So, if your files are not the required 16 bit little-endian two's complement integer required for /dev/audio then you'll need to change them
In my estimate your best bet for portability would be converting them to mp3 format (and you can choose lossless encoding if that is important to you) and then you are free to use them on any platform.
My decoder of choice is Nemo's port of MAD
http://plan9.escet.urjc.es/usr/nemo/export/mad.tgz
It even works on the bitsy!
Matt
prev parent reply other threads:[~2004-06-21 11:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-19 15:24 Brantley Coile
2004-06-19 16:18 ` Russ Cox
2004-06-21 11:07 ` matt [this message]
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=65d199b21ba9fa66d2c581808d399a48@juice.thebigchoice.com \
--to=matt@proweb.co.uk \
--cc=9fans@cse.psu.edu \
/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).