Re: Deadlocking problems in winmm

2005-04-09 Thread Robert Lunnon
On Sat, 9 Apr 2005 06:17 pm, Eric Pouech wrote: > Robert Lunnon a écrit : > > sounds like the callback for the wave header is not called, so > +audioio,+winmm,+mmtime would be helpful. > A+ More information, The instances of DDERR_SURFACEBUSY Begin with the section of code under. It looks suspi

Re: Deadlocking problems in winmm

2005-04-09 Thread Robert Lunnon
On Sat, 9 Apr 2005 06:17 pm, Eric Pouech wrote: > Robert Lunnon a écrit : > > sounds like the callback for the wave header is not called, so > +audioio,+winmm,+mmtime would be helpful. > A+ More insight, Perhaps the problem isn't specifically audio related even though it ONLY happens when the au

Re: Deadlocking problems in winmm

2005-04-09 Thread Robert Lunnon
On Sat, 9 Apr 2005 06:17 pm, Eric Pouech wrote: > Robert Lunnon a écrit : > > sounds like the callback for the wave header is not called, so > +audioio,+winmm,+mmtime would be helpful. > A+ I'll hunt a bit there but its not audioio specific, same thing happens when I use the arts driver. Still I'l

Re: Deadlocking problems in winmm

2005-04-09 Thread Eric Pouech
Robert Lunnon a écrit : sounds like the callback for the wave header is not called, so +audioio,+winmm,+mmtime would be helpful. A+ -- Eric Pouech

Deadlocking problems in winmm

2005-04-08 Thread Robert Lunnon
Since early this year I have been having difficulties with winmm in that my test application seems to deadlock if an audio driver is set up in the config. Without a defined audio driver or if the audio device is busy, the app works fine. For what it's worth here is a dump of +winmm +mmtime. Aft