Setting max_output_buffer is not added to config file and causes MPD start failure

[ceejayemm]

I setup a new installation (RPi 3A+, i20260216 and update 20260407) and configured as I normally do for a wireless system. When I set Player / Buffer - Output (max_output_buffer) to 8192 (normal for me) the value was not written to the file /srv/http/data/mpdconf/outputbuffer.conf leaving the value blank. This caused the MPD Player not to start. Editing the correct value into the file allowed MPD to be restarted.

Chris

[Sagnasty]

I also ran into this issue with 20260407

[klassikmann]

Things are a little different for me. I reinstalled on my RPi 3B 1.2, restored a recent backup conatining max_output_buffer_size "16384" and updated to version 20260407. The value for max_output_buffer_size was retained in /srv/http/data/mpdconf, and mpd starts up as well.
What I didn't do was try to set max_output_buffer_size to a new value.

[ceejayemm]

Yes, it seems to happen when changing from the original value, whatever it is, to another value. The entry in the file, in my case, became:

max_output_buffer_size ""

Chris