I haven’t been using beets for some years now, but I’d like to test some features out and probably even contribute a little.
I have a collection of nearly 150,000 songs, built during the past few decades and carefully fine-tuned using MusicBrainz Picard and some special plugins and tools. This amounts to roughly 2 TB of data.
All this is used productively, so I can’t simply “do a backup and restore” that easily (albeit doing backups almost every day).
Is there any easy way to set up beets in a fashion that
- would never ever change any tag in any file (without my manual consent)?
- would not change any file names or paths?
- would still allow me testing many plugins and probably own changes?
With this “main music broadcasting machine”, I’m unfortunately still on Ubuntu Studio 14.04, so not everything might work. I do have some virtual machines (Linux Mint 19, Manjaro 18, MacOS 10.14 Mojave) running on this machine, so I could probably use one of those for testing. They would still access my original music folders, though.
Any recommendations, please?
N.B.: I don’t wish to “work on a smaller subset” by copying a few albums, if anyhow possible, and avoid using virtual machines if possible, because I plan to see how fast it is on a collection as big as this one, probably find some old/forgotten errors in my collection, and try out some special features like complicated selections from weird tags (like “give me the paths of all 1990s songs sung in Swedish by female-fronted Norwegian hard rock groups where the bass guitar was played by artist xy”).