Thanks for the link.
After some more experimentation, I found out (correct me if I am wrong) that Nightingale does not manage its own library. When you import music to it, you are simply adding the songs to the Nightingale database, and no files are moved or copied in the process.
Nightingale does have a watch folder function where it will add/remove songs from the Nightingale library as you add or delete files in the specified folder. With this, I have cobbled together a library management setup that I am testing now:
- Set up an empty folder and have Nightingale watch it for changes, e.g. ~/Music/
- Set up beets so that the beets config file (~/.beetsconfig) has its music directory also as ~/Music/
- Add files to your library by importing them through beets (not with Nightingale!) with the beets import command. Those songs will appear in your Nightingale library in real time since the ~/Music/ folder is being watched.
- Metadata can be changed during import with beets, or after import with Nightingale. If you change metadata with Nightingale, run the beets update command so beets will be aware of the changes.
- Beets (when you run the update command) will re-organise the folder structure inside ~/Music/ if metadata like artist or album changes, Nightingale seems to be OK with this.
- If you use the Nightingale "Delete from disk" addon to delete the actual music file, also run the beets update command to make beets aware of it.
So far this is the closest I've come to semi-automated library file/folder management that is in sync with the Nightingale library.
I will mark the thread as SOLVED, but please let me know if you have a better solution! Thanks.
P.S. the beets documentation (for config file setup and common commands) is here
P.S.2 Later I got my Nightingale forums activation email and was able to ask the question there
. I've also posted my solution there, and maybe someone will think of something better and post it there.