11 Jun
2004
11 Jun
'04
8:55 a.m.
At Thu, 10 Jun 2004 15:47:07 -0400,
Dave Phillips wrote:
Greetings:
Can someone explain why TiMidity eventually hogs the CPU at 95% or
more after running for a while (like 12 hours or more) ? I'm talking
about hogging the chip while TiMidity is idling, not playing. I'm using
it as a softsynth, it works well, but even in the latest version its CPU
usage just soars. Here's how I'm invoking 2.13.0 :
timidity -iA -B2,8 -c /home/dlphilp/timidity.cfg -A100 -Oj
-EFreverb=0 -EFchorus=0
Takashi: Obviously I spoke too soon in my earlier message. I just
looked at top again and saw that TiMidity was eating up 96% of the CPU. :(
If it constantly hogs CPU even without playing noes, it must be a
bug. My rough guess is that the sample position goes back to 0 or
negative due to the integer overflow.
Are you keeping the MIDI connection for this long time?
What happens if you once disconnect from timidity?
Takashi