Aha. So now the question is why does it stop sending bytes in the first
place.
A (possibly) unrelated issue: I have an ancient version of TiMidity. I
don't remember where the executable came from, probably RedHat 5.1. When
I run midi files through it, it essentially plays the whole file in
about 1 second. I've never tried to figure out why this happens, but I'm
beginning to suspect there is something about my hardware and how it
handles interrupts. Has any one ever seen this behavior or know perhaps
even know the cause?
Thanks,
Allen
Hans Meine wrote:
>
> Allen Barnett <[EMAIL PROTECTED]> writes:
>
> > I'm not having a lot of success tracking this down. I'm trying to trace
> > where the command to send bytes to /dev/dsp is dispatched from. If I put
> > a print statement in AudioSubSystem::handleIO() or
> > Synth_PLAY_impl::notifyIO(), I get an infinite loop when artsd starts
> > up. Normally, artsd starts by sending a 16kb buffer of zeros to /dev/dsp
> > (for calibration purposes?). With the print statements present, however,
> > artsd never stops sending zero bytes to /dev/dsp.
> This is the intended behaviour - artsd is constantly "mixing" sound into
> /dev/dsp unless it suspends. And when there's nothing to play, it sends
> zeros. So in fact, it is working!
>
> Now I wish you success with trying why it stops working after playing
> sound! (IIRC, that was your problem?)
>
> --
> Ciao, / /
> /--/
> / / ANS .,* Hamburg, Germany *,.
