From: Brian L Scipioni <brian@gaugetheory.org>
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-user] file.wav -> dsp issue
Date: Wed, 01 Dec 2004 09:56:52 -0500 [thread overview]
Message-ID: <1101913012.13435.37.camel@radium.gaugetheory.org> (raw)
In-Reply-To: <1101848569.10162.25.camel@krustophenia.net>
[-- Attachment #1: Type: text/plain, Size: 2902 bytes --]
I have this problem too - but probably others causing it.
aplay -D spdif /usr/share/sounds/startup3.wav works fine.
aplay -D /usr/share/sounds/startup3.wav gives the following error:
ALSA lib pcm.c:1975:(snd_pcm_open_noupdate) Unknown PCM
/usr/share/sounds/startup3.wav
aplay: main:508: audio open error: No such file or directory
cat /usr/share/sounds/startup3.wav > /dev/dsp
makes no sound and hangs for 55 seconds on this 2.5 second sample.
They both worked before I installed 1.0.7. However, I also installed
the OSS compatibility libs this time.
Also when I run alsaconf now it finds 2 cards even though I only have 1.
emu10k1 Creative ...
legacy Probe legacy ISA chips
I suspect this second device is the tiny speaker on my motherboard, no?
Is it getting all the attention?
Except for when I specify spdif on the command line "alsaplayer -d spdif
..." none of my audio apps work.
What gives here? Anybody know? Everything USED to work.
my .asoundrc is as suggested for my card (Audigy2 Platinum):
pcm.emu10k1 {
type hw
card 0
}
ctl.emu10k1 {
type hw
card 0
}
thanks guys,
brian
On Tue, 2004-11-30 at 16:02, 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.
>
> What's the sample rate of your .wav file? Do you get the same results
> with other sample rates?
>
> This could be a bug in the OSS emulation layer.
>
> Lee
>
>
>
> -------------------------------------------------------
> 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/
> _______________________________________________
> Alsa-user mailing list
> Alsa-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/alsa-user
[-- Attachment #2: Type: text/html, Size: 4307 bytes --]
next prev parent reply other threads:[~2004-12-01 14:56 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 ` [Alsa-devel] " Takashi Iwai
2004-12-01 14:56 ` Brian L Scipioni [this message]
2004-12-01 15:04 ` 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=1101913012.13435.37.camel@radium.gaugetheory.org \
--to=brian@gaugetheory.org \
--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.