01-18-2023, 12:17 PM
(01-18-2023, 10:16 AM)richo Wrote: I have also noticed something, which is sort of logical. If you made any changes to the MPD settings from the web interface it will remove earlier manually added line:
format "44100:16:1"
I think this is to be expected, as the web interface takes care of writing such configuration file, that is: you're not encouraged to write it yourself.
Maybe we could write the file in a more intelligent way: overwrite only the values the UI is aware of, and leave the rest unchanged... it's a bit challenging, though, to be done in a proper (data-agnostic way) way: read all, take unknown as granted, replace all known, save all.
I may have a look into it, but... let's consider WHY we shouldn't:
we have, ATM, two options: FLAC and MP3 (that is: hi-quality lossless vs lossy low quality). At this point, IMHO, it should be clear that for MP3 streaming we do deliberately want a low-quality, and hence force such line automatically in the config. file. It's easier, and there is no meaning for streaming MP3 at 24/96 => shrinked down to 320kbs, right?!?
@Tim Curtis, am I right in my assumptions? This is a one-liner, and could make a lot of people happy, at least @richo. But looking at the bigger picture... shall I decide to stream my library over the internet, to reduce bandwidth, and costs, and depending on the situation, I would prefer to have MP3 streaming over FLAC. Problem is: I would lose roughly 25% of my music availability without this easy fix.
I could take care of implementing it, of course, shall it be the case.
Nice day everybody, now back to some silly and annoying database work-duties
