Archive Support

[alanpearce]

This is mentioned as being unimplemented in the readme. Firstly I thought it would be good to have a ticket to track it.

Secondly, I'm not sure when it would be useful. I'm trying to figure out if it's something that I might want to use for my collection or not. Could you describe what you're planning to do with it?

[xthursdayx]

I'm not sure if this is the right place to post this, but I'm hoping to use this plugin to get beets to recognize the fact that I archive some albums in both lossy and lossless formats (usually MP3 and FLAC) and allow me to implement this path structure:
default: %the{$albumartist}/$album%aunique{} ($original_year) (%upper{$format})/$track - $title
Where $format serves as an album level disambiguator. I'm posting here because I assume this might fall under "archive support"... Any ideas?

[geigerzaehler]

What I intended to do with “archive support” is the possibility for users to an archive of lossless files and to keep lossy files in their beets collection. For example a user would import a losslessly encoded album and then use this plugin to move the lossless files into an archive and keep only the lossy files.

@xthursdayx I think this is related to your problem. I assume you want to keep metadata between the two formats in sync. (It should be possible to have beets recognize both album versions, but this would be without syncing.) This plugin can help you achieve that with some caveats: First, only one version is in your beets library. This means you can only find that version with the ls command, etc. The alternative only exists as a file in some location, but we keep track of it. Second, the higher quality version needs to be the one in the beets library. This is something that the archive support would try to solve.