getting sound to work

The problems I was having seemed to be the soundcard. I bought a
sblive, and got the drivers to load:

#on -n 14 deva-sblive
Attaching to irq: 11
0 - Sound Blaster Live! EMU10k1 at 0xe800, irq 11


But now what? I want to test this via a wav or mp3. I don’t see a
/dev/dsp, or even a //14/dev/dsp

#ls //14/dev
cd1.0 con3 con6 kbd null pcm01
shmem con1 con4 hd1.0 midi00 par1
ser1 sndctl0 con2 con5 hd1.0t77 mixer00
pcm00 ser2

So, whats next? catting the wav to and of those pcm or sndctl devices
results in the driver exiting.

-Aaron

Aaron,
The sound blaster drivers you are using are ALSA based. There’s no
“cat” you can do to make them work (that I know of) but you can use “aplay”
or “mpg123” to test the sound. I use another ALSA based sound chip driver,
and aplay works for testing (only problem I have is after playing a sound,
the driver will crash if I try to play another). But that’s a driver
related issue for me…

Here’s some info for sound drivers in QNX:
http://qdn.qnx.com/support/bok/solution.qnx?9617

Hope that helps,
Ron

“Aaron Solochek” <aarons@ai.mit.edu> wrote in message
news:3B3B803B.1040406@ai.mit.edu

The problems I was having seemed to be the soundcard. I bought a
sblive, and got the drivers to load:

#on -n 14 deva-sblive
Attaching to irq: 11
0 - Sound Blaster Live! EMU10k1 at 0xe800, irq 11


But now what? I want to test this via a wav or mp3. I don’t see a
/dev/dsp, or even a file://14/dev/dsp

#ls file://14/dev
cd1.0 con3 con6 kbd null pcm01
shmem con1 con4 hd1.0 midi00 par1
ser1 sndctl0 con2 con5 hd1.0t77 mixer00
pcm00 ser2

So, whats next? catting the wav to and of those pcm or sndctl devices
results in the driver exiting.

-Aaron

I get the following errors with aplay. Also, mpg123 doesn’t work. Is
there anything else to check?



#on -n 14 aplay test.wav
Aplay: version 0.0.8 by Jaroslav Kysela <perex@jcu.cz>
Error: audio open error: No such file or directory

#on -n 14 aplay -l
Aplay: no soundcards found…

-Aaron


Ron Cococcia wrote:

Aaron,
The sound blaster drivers you are using are ALSA based. There’s no
“cat” you can do to make them work (that I know of) but you can use “aplay”
or “mpg123” to test the sound. I use another ALSA based sound chip driver,
and aplay works for testing (only problem I have is after playing a sound,
the driver will crash if I try to play another). But that’s a driver
related issue for me…

Here’s some info for sound drivers in QNX:
http://qdn.qnx.com/support/bok/solution.qnx?9617

Hope that helps,
Ron

“Aaron Solochek” <> aarons@ai.mit.edu> > wrote in message
news:> 3B3B803B.1040406@ai.mit.edu> …

The problems I was having seemed to be the soundcard. I bought a
sblive, and got the drivers to load:

#on -n 14 deva-sblive
Attaching to irq: 11
0 - Sound Blaster Live! EMU10k1 at 0xe800, irq 11


But now what? I want to test this via a wav or mp3. I don’t see a
/dev/dsp, or even a file://14/dev/dsp

#ls file://14/dev
cd1.0 con3 con6 kbd null pcm01
shmem con1 con4 hd1.0 midi00 par1
ser1 sndctl0 con2 con5 hd1.0t77 mixer00
pcm00 ser2

So, whats next? catting the wav to and of those pcm or sndctl devices
results in the driver exiting.

-Aaron
\

First question that I have, are you trying to run this on a different node,
or is your unit’s node number 14? (from the usage of “on” my guess is you’re
trying to run aplay on another node).

If you are trying to run it on another node, I’m not quite sure how aplay
will react. If you go to that node however (physically use the machine),
start the sound driver, and do “aplay -l”, does it do anything?


“Aaron Solochek” <aarons@ai.mit.edu> wrote in message
news:3B3BB765.4020407@ai.mit.edu

I get the following errors with aplay. Also, mpg123 doesn’t work. Is
there anything else to check?



#on -n 14 aplay test.wav
Aplay: version 0.0.8 by Jaroslav Kysela <> perex@jcu.cz
Error: audio open error: No such file or directory

#on -n 14 aplay -l
Aplay: no soundcards found…

-Aaron


Ron Cococcia wrote:

Aaron,
The sound blaster drivers you are using are ALSA based. There’s no
“cat” you can do to make them work (that I know of) but you can use
“aplay”
or “mpg123” to test the sound. I use another ALSA based sound chip
driver,
and aplay works for testing (only problem I have is after playing a
sound,
the driver will crash if I try to play another). But that’s a driver
related issue for me…

Here’s some info for sound drivers in QNX:
http://qdn.qnx.com/support/bok/solution.qnx?9617

Hope that helps,
Ron

“Aaron Solochek” <> aarons@ai.mit.edu> > wrote in message
news:> 3B3B803B.1040406@ai.mit.edu> …

The problems I was having seemed to be the soundcard. I bought a
sblive, and got the drivers to load:

#on -n 14 deva-sblive
Attaching to irq: 11
0 - Sound Blaster Live! EMU10k1 at 0xe800, irq 11


But now what? I want to test this via a wav or mp3. I don’t see a
/dev/dsp, or even a file://14/dev/dsp

#ls file://14/dev
cd1.0 con3 con6 kbd null pcm01
shmem con1 con4 hd1.0 midi00 par1
ser1 sndctl0 con2 con5 hd1.0t77 mixer00
pcm00 ser2

So, whats next? catting the wav to and of those pcm or sndctl devices
results in the driver exiting.

-Aaron

\

Aaron Solochek <aarons@ai.mit.edu> wrote:

I get the following errors with aplay. Also, mpg123 doesn’t work. Is
there anything else to check?



#on -n 14 aplay test.wav
Aplay: version 0.0.8 by Jaroslav Kysela <> perex@jcu.cz
Error: audio open error: No such file or directory

#on -n 14 aplay -l
Aplay: no soundcards found…

try “on -f 14 aplay test.wave”

-xtang

-Aaron



Ron Cococcia wrote:

Aaron,
The sound blaster drivers you are using are ALSA based. There’s no
“cat” you can do to make them work (that I know of) but you can use “aplay”
or “mpg123” to test the sound. I use another ALSA based sound chip driver,
and aplay works for testing (only problem I have is after playing a sound,
the driver will crash if I try to play another). But that’s a driver
related issue for me…

Here’s some info for sound drivers in QNX:
http://qdn.qnx.com/support/bok/solution.qnx?9617

Hope that helps,
Ron

“Aaron Solochek” <> aarons@ai.mit.edu> > wrote in message
news:> 3B3B803B.1040406@ai.mit.edu> …

The problems I was having seemed to be the soundcard. I bought a
sblive, and got the drivers to load:

#on -n 14 deva-sblive
Attaching to irq: 11
0 - Sound Blaster Live! EMU10k1 at 0xe800, irq 11


But now what? I want to test this via a wav or mp3. I don’t see a
/dev/dsp, or even a file://14/dev/dsp

#ls file://14/dev
cd1.0 con3 con6 kbd null pcm01
shmem con1 con4 hd1.0 midi00 par1
ser1 sndctl0 con2 con5 hd1.0t77 mixer00
pcm00 ser2

So, whats next? catting the wav to and of those pcm or sndctl devices
results in the driver exiting.

-Aaron
\

excellent. That did the trick. Thanks.

-Aaron

Xiaodan Tang wrote:

Aaron Solochek <> aarons@ai.mit.edu> > wrote:

I get the following errors with aplay. Also, mpg123 doesn’t work. Is
there anything else to check?




#on -n 14 aplay test.wav
Aplay: version 0.0.8 by Jaroslav Kysela <> perex@jcu.cz
Error: audio open error: No such file or directory


#on -n 14 aplay -l
Aplay: no soundcards found…


try “on -f 14 aplay test.wave”

-xtang


-Aaron



Ron Cococcia wrote:


Aaron,
The sound blaster drivers you are using are ALSA based. There’s no
“cat” you can do to make them work (that I know of) but you can use “aplay”
or “mpg123” to test the sound. I use another ALSA based sound chip driver,
and aplay works for testing (only problem I have is after playing a sound,
the driver will crash if I try to play another). But that’s a driver
related issue for me…

Here’s some info for sound drivers in QNX:
http://qdn.qnx.com/support/bok/solution.qnx?9617

Hope that helps,
Ron

“Aaron Solochek” <> aarons@ai.mit.edu> > wrote in message
news:> 3B3B803B.1040406@ai.mit.edu> …


The problems I was having seemed to be the soundcard. I bought a
sblive, and got the drivers to load:

#on -n 14 deva-sblive
Attaching to irq: 11
0 - Sound Blaster Live! EMU10k1 at 0xe800, irq 11


But now what? I want to test this via a wav or mp3. I don’t see a
/dev/dsp, or even a file://14/dev/dsp

#ls file://14/dev
cd1.0 con3 con6 kbd null pcm01
shmem con1 con4 hd1.0 midi00 par1
ser1 sndctl0 con2 con5 hd1.0t77 mixer00
pcm00 ser2

So, whats next? catting the wav to and of those pcm or sndctl devices
results in the driver exiting.

-Aaron

\