"bag of tricks to smooth out perceived latency and fault tolerance." Agree - audioserve is now handling this with quite simple trick - just cache ahead couple

"bag of tricks to smooth out perceived latency and fault tolerance." Agree - audioserve is now handling this with quite simple trick - just cache ahead couple of tracks/files from current folder (aka audiobook), so responsibility is move to client. Surprisingly this simple trick did work for me for years (as I'm intensive user of audioserve). It kind of depends on file/chapter duration - but for most common cases - which are beetween 5 mins to say 90 mins it did work fine. Historically only Android client was using this caching, but with new web client https://github.com/izderadicka/audioserve-web https://github.com/izderadicka/audioserve-web and broad Service Worker support in browsers it is also available in browser.