Comment on An Opensubsonic server in Rust
lyoko@lemm.ee 2 months agoIs Rust that much better than Go?
IMHO, rust and go have two differents things. The reason I choose Rust is because it is fast and calling C code from rust is supported really well since Rust’s goal is to become a system language. Navidrome is just calling the ffmpeg binary. While in my project, I’ve compiled the neccessary parts of ffmpeg myself (thanks to vcpkg) and call the function directly from Rust. It leads to smaller and full static final binary (because no ffmpeg bin) as well as faster transcoding time since we don’t have to wait for the ffmpeg binary to finish transcoding the whole file before load the result from the filesystem to the memory.
Would it have been impossible to submit your changes to Navidrome as pull requests?
You can see here. This is the biggest reason why I’ve decided to start my own implementation. Beside, I share my server with several friends so I want a mechanism to prevent mixing musics from different people.
Does this import the Navidrome database?
This could be a feature request in the future. I could add a python script to import users/songs/playlists/playcount/etc from Navidrome.
sabreW4K3@lazysoci.al 2 months ago
Thank you for taking the time to answer. I actually am subscribed to that thread and the upcoming new scanner that fixes that problem. Though now with your new server, you wouldn’t need to worry about that.
I truly wish you luck though. The more awesome subsonic servers around, the better. I hope your project can be just as much of a household name as Navidrome.
lyoko@lemm.ee 2 months ago
Thank you very much for your kind word! I’ve seen that scanner already but decided to reimplement anyway because I want to choose a different design from the start and have the flexibility to add some new features myself (some kind of ML integration like immich and S3 integration). As worse case, I will still use this so no problems :D