waveOutOpen fails with MMSYSERR_ALLOCATED

[Sandra Thiel]

Hi,

I'm writing a little app that monitors the hardware status of an installed
TVTuner card and plays a wav file in case a certain event occurs. Everything
works fine till I want to play the wav file over a phone line instead of the
speakers.

When I get the LINECALLSTATE_CONNECTED event, I evaluate the deviceID for
waveOutOpen with lineGetID and use this ID instead of the WAVE_MAPPER
constant. But then waveOutOpen always returns with error number 4
(MMSYSERR_ALLOCATED). As soon as I change the ID back to WAVE_MAPPER
everything works fine again (via the speakers). This is my first project, so
maybe it's a real stupid error ...

I tried everything and are running out of ideas what can be wrong ... Any
ideas where I can take a look at are welcome !

My system is a Win2k machine and I use TAPI 2.0.

thanks in advance,
Sandra

[Grant Schenck]

Check the information about the specified wave ID (waveGetDevCaps).
Does it match the provider?

I've seen situation where due to buggy TSPs/Wave Drivers that some
time you get bad associations from TAPI.

If this is the problem then what I have found is that playing with the
load order of the wave drivers in the registry will sometimes fix
this.
--
Grant Schenck
Grant Schenck Software
grants...@home.com
http://members.home.net/grantschenck/

"Sandra Thiel" <STh...@Pinnaclesys.com> wrote in message
news:e1ucZlMUBHA.2256@tkmsftngp03...

[Michael Dunn]

If you are receiving calls: Did you open the line in AUTOMATEDVOICE?

If you placing calls: Did you use AUTOMATEDVOICE in the lineMakeCall()?

Sandra Thiel wrote:

> When I get the LINECALLSTATE_CONNECTED event, I evaluate the deviceID for
> waveOutOpen with lineGetID and use this ID instead of the WAVE_MAPPER
> constant. But then waveOutOpen always returns with error number 4
> (MMSYSERR_ALLOCATED). As soon as I change the ID back to WAVE_MAPPER
> everything works fine again (via the speakers). This is my first project, so
> maybe it's a real stupid error ...
>
> I tried everything and are running out of ideas what can be wrong ... Any
> ideas where I can take a look at are welcome !
>
> My system is a Win2k machine and I use TAPI 2.0.
>
> thanks in advance,
> Sandra

--
Michael Dunn is a TAPI Developer and Tester for Tri-Link Technologies
My TAPI web page: http://members.home.net/tapifaq/tapi.htm
All opinions are my own, and do not reflect those of my employer.
"When all else fails, read the directions."

[Sandra Thiel]

Hi Grant,

thanks for answering so quickly!

I'm not sure if I completely understood what you mean with "Does it match
the provider?" I checked lineGetDevCaps and it supports
LINEMEDIAMODE_AUTOMATEDVOICE (dwMediaModes contains 30).

waveOutGetDevCaps returned 0 in dwFormats (WAVE_INVALIDFORMAT) -> to me it
looks like the modem driver doesn't support any wave at all, but when I use
the WAVE_MAPPER as the device ID in waveoutopen and set the preferred Audio
device in the control panel to the phone line, I can hear the sound via the
phone ?!?!?!

Sandra

"Grant Schenck" <grants...@home.com> wrote in message
news:#XRGBVPUBHA.1792@tkmsftngp07...

[Grant Schenck]

Every vendor I work with returns 0 for dwFormats in
waveOutGetDevCaps() so I don't think that means a whole lot.

What I meant was to waveOutGetDevCaps() and see if the szPname member
of the WAVEOUTCAPS matches the TSP you think you are using.

--
Grant Schenck
Grant Schenck Software
grants...@home.com
http://members.home.net/grantschenck/

"Sandra Thiel" <STh...@Pinnaclesys.com> wrote in message

news:uR2r5dbUBHA.1740@tkmsftngp07...

[Sandra Thiel]

now i understood ... the TSP is correct :-(

"Grant Schenck" <grants...@home.com> wrote in message

news:erg4lNmUBHA.2084@tkmsftngp03...

[Sandra Thiel]

just if someone is interested:

I couldn't find a solution for my problem with the waveoutput via mmio. Now
I implemented the audio output with DirectSound and and it works fine :-)

Sandra

"Sandra Thiel" <STh...@Pinnaclesys.com> wrote in message
news:e1ucZlMUBHA.2256@tkmsftngp03...