From: Takashi Iwai <tiwai@suse.de>
To: Lee Revell <rlrevell@joe-job.com>
Cc: "H.Haines Brown" <brownh@hartford-hwp.com>,
alsa-user@lists.sourceforge.net,
alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: [Alsa-devel] Re: file.wav -> dsp issue
Date: Wed, 01 Dec 2004 11:55:39 +0100 [thread overview]
Message-ID: <s5hk6s2nv84.wl@alsa2.suse.de> (raw)
In-Reply-To: <1101848569.10162.25.camel@krustophenia.net>
At Tue, 30 Nov 2004 16:02:48 -0500,
Lee Revell wrote:
>
> On Tue, 2004-11-30 at 15:05 -0500, Haines Brown wrote:
> > > On Tue, 2004-11-30 at 13:04 -0500, Haines Brown wrote:
> > > > # cat file.wav > /dev/dsp
> > > >
> > > > it seems to play at half speed (pitch is very low, playing speed very
> > > > slow).
> > > >
> > > > Is the command above the best way to do a simple test of sound? Why
> > > > should sending the file to dsp not play correctly?
> > >
> > > No, that is the way to do it with the deprecated OSS API. It seems like
> > > a convenient, Unixy way to play sounds but there are many problems with
> > > it.
> > >
> > > The ALSA way is "aplay file.wav". Does this work?
> >
> > Yes, that worked fine. I find that it plays WAV and VOC, but not MID
> > and WMA files (just screeches). Thanks.
>
> Hmm, my point about the OSS api notwithstanding, seems like cat foo.wav
> > /dev/dsp should work, if aplay groks the format. It seems to be
> getting the sample rate wrong. I am cc'ing alsa-devel.
"cat > /dev/dsp" itself doesn't parse the format but just handles as
if a raw PCM data. It is pretty casual that it worked somehow.
Takashi
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
next prev parent reply other threads:[~2004-12-01 10:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20041130180410.D498B187F@teufel.hartford-hwp.com>
[not found] ` <1101839935.10162.1.camel@krustophenia.net>
[not found] ` <20041130200556.9A346188C@teufel.hartford-hwp.com>
2004-11-30 21:02 ` file.wav -> dsp issue Lee Revell
2004-12-01 10:55 ` Takashi Iwai [this message]
2004-12-01 14:56 ` [Alsa-user] " Brian L Scipioni
2004-12-01 15:04 ` [Alsa-devel] " Takashi Iwai
2004-12-01 17:58 ` Brian L Scipioni
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=s5hk6s2nv84.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=alsa-user@lists.sourceforge.net \
--cc=brownh@hartford-hwp.com \
--cc=rlrevell@joe-job.com \
/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.