[timidity-talk] What does the trace option actually do?

[Philip N. <pan...@ya...>]

I am following up on my question about cpu use with the alsa server mode. In
that post I reported that with a device connected to timidiy with -iA, cpu use
jumps to 25% even with no midi activity. If I add the trace option, -iAt, the
cpu use goes down to nothing until midi events are happening. Unfortunately, I
get nasty xruns in this configuration. I get far fewer xruns without the trace
option, almost none.

So at this point I have to choose between cpu use and xruns. If I understood
better what the trace option did in alsa server mode, maybe I could figure out
how to improve that situation. Any ideas?



Philip - http://blogs.xcskiwinn.org/panmanphil
"There's a difference between righteous anger and just being crabby" - Barbara