izderadicka

3 ms·

1.
by izderadicka 4y ago
MPD is definitely much more sophisticated and bigger project. MPD is primarily client-server music player with streaming support. Audioserve is more about serving audio files over HTTP protocol with couple of utilities/enhancements lik
2.
by izderadicka 4y ago
"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 responsibi
3.
by izderadicka 4y ago
Concerning audiobookshelf, I see it other way around, because I think audiobookshelf came after - so it's contender to audioserve. But it is definitely nice app. I tried and did like some things (especially turning books into HLS strea
4.
by izderadicka 4y ago
Adding not so common audio formats to audioserve will not be so different. We'll just need to add mime types (and extensions), that are recognized as audio. Also we will need to enforce mandatory transcoding for such formats. Anything,
5.
by izderadicka 4y ago
Looks like Amazon is retiring Alexa? Audioserve has generic web client - but not sure if it works on Alexa. If there are problems try with transcoding set to None.
6.
by izderadicka 4y ago
No unless somebody will make plugin for it - audioserve has it own API. I though about implementing Subsonic API, but it's design is much different from how audioserve works, so it'll require too much "interface code",
7.
by izderadicka 4y ago
Thanks for nice words, though I do suffer from above average affinity to beer (and Rust) I consider myself decent person. As I'm using audioserve myself, I try to evolve it continuosly, however my view of good simple audiobooks streami
8.
by izderadicka 4y ago
Apple platforms has by default problem with Auddioserve - my choice of default audio codec is opus (in ogg container) and Apple support of opus is not very good, to put it mildly (I think one can make Safari on MacOS to support opus, but n