I switched recently from Airsonic to Gonic, mainly due to how resource-heavy Airsonic was. I primarily use 2 clients: Clementine/Linux and play:Sub/iOS. I also tested a audiobook-only-installation against BookSonic/Android.

Notes:

- Gonic doesn't support many routes. The *sonic protocol supports special routes for Podcasts/Audiobooks/Radio Stations for eg. [0] details missing routes

- It heavily uses `folder.jpg` as the album art. Doesn't work well always. I used sacad[1], but it wasn't perfect.

- Not all players will work perfectly with Gonic. I use play:Sub and it had some issues with album names being blank because Gonic used `name` field in album info while keeping title blank (I think). This is now fixed mostly, but I still have a few blank albums that I need to investigate

- I liked the transcoding options on the server side. You can set it per-client and that client will forever get MP3 for eg.

- It doesn't do artist art. Not sure why

I haven't faced any breaking-issues other than the blank album names so far (and that was fixed).

[0]: https://github.com/sentriz/gonic/issues/7

[1]: https://pypi.org/project/sacad/

Do you mean it doesn't automatically fetch album art? It does serve it to the client in my experience.

Other players would use images embedded in cover-arts. Gonic only works with folder.jpg. I had cover.png files which Gonic ignored, so I had to hack around things.

See https://github.com/sentriz/gonic/issues/11

hey thanks for your feedback! though it's strange that the scanner missed your artwork files. it should support lots of filetypes

https://github.com/sentriz/gonic/blob/master/server/scanner/...

Will check and create an issue.

Been using it for about 6 months running on a PI. Very happy with it and I just opened a PR to add rating support(which was the only thing I wanted that it lacked).