beets VS mutagen

I was always frustrated that there is no solid source for synced lyrics that also offers decent API support. There is good ol' Crintsoft's MiniLyrics that is thankfully free software, was what I used a lot in my childhood, but unfortunately the API is highly obfuscated. Another popular choice is the Musixmatch API, which has a very large database of synced lyrics, but with "free" API that are reverse-engineered from their app, you will quickly run into rate-limit.

That's why I created LRCLIB. It's aimed to provide completely free synchronized lyrics for everyone, especially for FOSS music players, with zero profit intention. It currently has nearly 3,000,000 (not deduplicated) lyrics in database. You can also contribute to the database by adding and syncing lyrics for your favorite songs using the LRCGET client.

I'm trying my best to make LRCLIB server-side code open-source as soon as possible. But right now, full LRCLIB's database dumps have already been uploaded regularly and publicly, which are simply sqlite3 files. Feel free to download, look at or do anything you want with the database at https://lrclib.net/db-dumps.

Many open-source projects have already begun integrating LRCLIB, including:

- beets - music library metadata management (https://github.com/beetbox/beets)

I just ssh onto my server and use beets to remotely organize my navidrome collection and edit metadata. Beets has lots of auto-tagging features and I rarely need to edit anything manually. Works great if you are ok with using the command line.

You could try https://github.com/beetbox/beets but it seemed very manual and extremely slow. I had better luck with Picard.

Honestly? I use https://beets.io/ to organise all my FLAC on my NAS.

I expose the /Music directory over NFC.

I use https://kodi.tv/ to stream music to my amp. I manually pick the album I want to listen to.

Kodi also has a fairly reasonable web UI.

Keep it simple.

If you're technically inclined, there's beets.

You should check out beets.

Yes, you have the torrent client call beets.io on the folder and have beets configured.

Hey HN, I wanted to share a Docker Desktop extension that uses Mutagen (the open-source[0] file sync tool for developers) to improve bind mount performance in Docker Desktop. It allows you to create synchronized filesystem caches inside the Docker Desktop VM that can automatically replace bind mounts. This gives you ext4 filesystem performance inside the Docker Desktop VM, with low-latency synchronization to-and-from the host filesystem.

Docker themselves actually shipped this functionality in Docker Desktop back in 2020, but they decided to pivot back to virtual filesystems with gRPC FUSE and Virtiofs. While these work fairly well, there are still substantial gains to be had for workflows that are readdir(), stat(), read(), and write()-heavy. This includes things like package installs (e.g. npm and Composer), dynamic language runtimes (e.g. PHP or Node.js), and compiling code.

This new implementation is significantly more performant[1], offers a more detailed UI, and gives you the option of setting the user and group IDs for files sync'd into the VM. You can even create multiple caches of the same files with different UIDs/GIDs, allowing containers with different UIDs/GIDs to access the same files without permissions conflicts.

This extension is closed-source and requires a subscription for some functionality, but that money helps to support the corresponding open-source project.

I'd be keen to hear your feedback. There are a few minor limitations (mostly SDK limitations), but nothing too significant. The next step is probably going to be adding support for remote Docker engines, but I'd be interested to know if there are other pressing features that people would like to see.

Disclaimer: I am a Docker Captain, though this tool is not developed, sponsored, or endorsed by Docker, Inc.

---

[0]: https://github.com/mutagen-io/mutagen

[1]: The Docker Desktop EULA prevents me from publishing benchmarks, but the performance difference will be the same as the difference between gRPC FUSE or Virtiofs and a "native" ext4 volume inside the VM. This will differ between hardware and virtualization frameworks. The best option is testing your own workflow.

I can't predict ultra far into the future (who can these days... :|), but Mutagen has been under active development for about 6 years now[0]. At the moment I have enough funding to work on it full-time until at least the middle of next year, though I also do Mutagen-related contracting and consulting work to support the project. Mutagen's Docker Desktop extension is going to be a freemium product designed to support the project more directly, which will hopefully allow development to continue indefinitely.

[0]: https://github.com/mutagen-io/mutagen/graphs/contributors

It's pretty bad. The Docker for Mac team tested something called Mutagen to speed things up, but then removed it again, and the difference was drastic.