Marcus Weseloh

Even though this is a very old issue, I tried to find out what exactly is going on here. The problem can be recreated with current FluidSynth, playing the attached...

> Not having a default tuning on each channel does have some performance benefits for the usual case where no MTS tuning is needed, though. I think that thought was...

I think we should change FluidSynths behaviour and have an active tuning 0 / 0 on all channels by default. As explained above, I don't think it will have any...

Some more notes about the implementation: It is obviously not a fool-proof auto-suspend. With a very short timeout value, there is the chance that audio from long-running effects (like a...

> So I would be interested: Can you confirm that turning off reverb and chorus significantly reduces CPU usage for the fluidsynth-server-background process? Of course it does. But that's not...

For plain ALSA things look a bit better. "Normal" idle (i.e. without auto-suspend) uses around 6% CPU time. If I comment out the rendering function from the alsa driver and...

> I'm just a bit cautious, trying to understand things step by step, this feels like a potential premature optimization issue to me. Yes, very valid point. What really triggered...

In 38e6fff is a very simple mmap-based ALSA driver format and handler. First analysis shows no improvement with regard to CPU consumption, quite the contrary (as expected).

> In [38e6fff](https://github.com/FluidSynth/fluidsynth/commit/38e6fff9e039f386435a1cf8509ee0d44f01e45e) is a very simple mmap-based ALSA driver format and handler. First analysis shows no improvement with regard to CPU consumption, quite the contrary (as expected). And now...

Ok... I think I understand why PulseAudio has such high CPU load with default FluidSynth settings. Default settings are sample-rate 44100, period-size 64 and enabled adjust-latency mode. This will configure...