07-23-2020, 12:05 PM
Right @TheOldPresbyope and @the_bertrum. Perhaps we should try to define the logic for how this input_cache ought to work and then append it to this issue on Github: https://github.com/MusicPlayerDaemon/MPD/issues/603
I checked for the largest file on my server and it was almost 1GB. Users with wifi connection to their NAS would under the above mentioned scheme have to wait for some time before playback starts, but I suppose that just can’t be helped, unless there is a fall-back functionality to loading in chunks, which I suppose is better than no caching at all.
Thoughts?
- Files should be loaded fully into the cache before playback starts, so that there is no network activity during playback.
- If the playlist contains more files than can fit the cache, then the loading of continuous album tracks should be prioritised (to enable gapless playback). Otherwise cache pruning and loading can be done between tracks.
I checked for the largest file on my server and it was almost 1GB. Users with wifi connection to their NAS would under the above mentioned scheme have to wait for some time before playback starts, but I suppose that just can’t be helped, unless there is a fall-back functionality to loading in chunks, which I suppose is better than no caching at all.
Thoughts?
