Changelog
Transcoding per user/player
Transcoding profiles can be created in the new Transcodings settings in the WebUI. Then players detected automatically by Navidrome can be configured to use one of these profiles (using the new Players settings). Users can only configure their own players. Admins can configure all players from all users.
Note that If no profile is set for a player, it will receive the original audio file, even if maxbitrate is set in the stream request.
Transcoded files are cached in the $ND_DATAFOLDER/cache folder. By default the cache size is 100MB, but can be configured using the ND_TRANSCODINGCACHESIZE environment variable.
All changes
5b40ec4 build: go mod tidy
29e661e docs: update README
b466ec7 build: always add latest tag to version
c8cd755 feat: use human readable sizes in cache size configuration
faac303 feat: allow session timeout to be configurable. closes #101
ced87be fix: when searching player by id, create new player if client name does not match the one found
811703a fix: create default transcodings on existing installations
bc1f767 docs: Update README
7055dc5 docs: update basic transcoding info
e02f3d3 refactor: clean up unused config options
68a49be feat: allow regular users to change their players' configuration
c8b0d2b feat: select correct transcoding for streaming
3999381 feat: add transcodedSuffix to Subsonic API responses
4518011 feat: player CRUD
353c48d refactor: rename player to audioplayer
da36941 feat: better getPlayer middleware setup
8ec7890 feat: transcoding and player datastores and configuration
a0e0fba build(deps): bump @testing-library/react from 9.5.0 to 10.0.1 in /ui
75e7ba8 build(deps): bump github.com/go-chi/cors from 1.0.0 to 1.0.1
74c30b5 docs: add list of tested clients
e67bdbb docs: add link to transcoding issue