Re: file.wav -> dsp issue

Re: file.wav -> dsp issue

[Lee Revell]

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/

Re: [Alsa-devel] Re: file.wav -> dsp issue

[Takashi Iwai]

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/

Re: [Alsa-user] file.wav -> dsp issue

[Brian L Scipioni]

[-- 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 --]

Re: [Alsa-devel] Re: file.wav -> dsp issue

[Takashi Iwai]

At Wed, 01 Dec 2004 09:56:52 -0500,
Brian L Scipioni wrote:
> 
> 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

-D option requires an argument.  In the second case, you didn't pass
it so the wav file name is parsed as the device name.

> cat /usr/share/sounds/startup3.wav > /dev/dsp
> makes no sound and hangs for 55 seconds on this 2.5 second sample.

Most likely the device is simply blocked by others.
This behavior was changed recently to be non-blocking mode, BTW.


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/

Re: [Alsa-devel] Re: file.wav -> dsp issue

[Brian L Scipioni]

[-- Attachment #1: Type: text/plain, Size: 1752 bytes --]

oops!  I meant to run
aplay  /usr/share/sounds/startup3.wav (without the -D of course, duh!)
this gives no output although
 aplay -D spdif /usr/share/sounds/startup3.wav does
In previous versions of ALSA this (without specifying spdif) worked.
Have default devices changed?

you write:
.... blocked by others
This behavior was changed recently to be non-blocking mode

What was changed to non-blocking mode? /dev/dsp or other devices.

could the legacy card that alsaconf found be my tiny 
motherboard speaker?  If so why does it get in the way now - it did not
before.

I have 
alias sound-slot-1 off
in my modules.conf
because my system log periodically complains that sound-slot-1 is not
found even though i have only one card

thanks,
sorry for the bevy of questions,
brian

On Wed, 2004-12-01 at 10:


> At Wed, 01 Dec 2004 09:56:52 -0500,
> Brian L Scipioni wrote:
> > 
> > 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
> 
> -D option requires an argument.  In the second case, you didn't pass
> it so the wav file name is parsed as the device name.
> 
> > cat /usr/share/sounds/startup3.wav > /dev/dsp
> > makes no sound and hangs for 55 seconds on this 2.5 second sample.
> 
> Most likely the device is simply blocked by others.
> This behavior was changed recently to be non-blocking mode, BTW.
> 
> 
> Takashi

-- 
Brian L Scipioni
909 Austin Ave
Atlanta, GA 30307
home:	404.525.8911
cell:	404.771.3740
brian@gaugetheory.org


[-- Attachment #2: Type: text/html, Size: 2292 bytes --]