-
|
I want to import and move an old and very badly tagged big bunch of mp3 files into beets. I often have the situation that files are in a folder called and there is no further subfolders, and no good tagging to what albums those files belong. Files belong to random albums of this artist but most of those albums would be incomplete if ordered back together. Something like 3 tracks from and ablum out of 15 tracks is a rough standard here. I played around with the "group_albums: yes" option but I am not sure if it does what I want / if I understand correctly. After endless tries of reimports with one single "artist folder" I realized that the only way to get beets halfway to recognize tracks on the same album was to initially manually moving files to "album folders" before starting Before I am posting my rather lengthy already beets config file I'd like to ask what would be the essential settings to achieve the following:
Thanks for any workflow and config hints, I can certainly post my config here but at the moment I am not sure if it adds to clarity of what I want to achieve, thus let's wait until someone asks for set options explicitely. |
Beta Was this translation helpful? Give feedback.
Replies: 8 comments 2 replies
-
|
This would be my configuration: |
Beta Was this translation helpful? Give feedback.
-
|
Ok, I guess I now understand what singleton import really is which brings me to a new question: It's based on a musicbrainz recording entry, alright - but sometimes there is multiple albums available on MB for this recording and thus none of them is written into beets db, the imported item is left without an album tag. Sometimes I realize later that actually I have part of this album already in my collection and now want these newly added items to add to this existing album. How would I do this? |
Beta Was this translation helpful? Give feedback.
-
|
I figured it should work like this: Note: I don't have a separate singleton directory, they just go to Seems nothing is done at all. What am I doing wrong? |
Beta Was this translation helpful? Give feedback.
-
|
I think I have a related concern in that singleton import does not write |
Beta Was this translation helpful? Give feedback.
-
|
After almost 1 year of beets usage and contributing experience I still don't understand singletons. Is it just me or is it true that a track that was initially imported as a singleton can't be changed to a regular album track. I forgot about this issue already but still what I wrote in that post #4211 (comment) seems to be a fact. Singletons can't be reimported to add them to an album. Period? Please correct me if I'm wrong! I tried using beet modify to set singleton to false but that doesn't work. It's not a regular database field nor is it a flexible attribute if I understand correctly. A flexible attr named "singleton" was added to the db but still beet info shows that the modified track is a singleton! |
Beta Was this translation helpful? Give feedback.
-
|
I think you can reimport. I just use -I flag to reimport and provide the full path again. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks!!! Will anwer in new thread, so I can mark as answer. |
Beta Was this translation helpful? Give feedback.
-
|
-I is --noincremental. I tried that but thought that it didn't work either. I think I did not come up with the idea that providing the full path of the imported file could help. Ok so here is the final "solution" or at least the way it works right now: Reimporting via a library search does not work. Reimporting via the full path of the singleton file already in the library, does work! |
Beta Was this translation helpful? Give feedback.
-
|
Is there a reason why a library based reimport of as singleton does simply return "nothing"? Should this be considered a bug? IMHO it would ease the retagging workflow a lot if an |
Beta Was this translation helpful? Give feedback.
-
|
Anyway, I'd like to share what works best for me and what is my answer to the first question from the headline of this thread. "Importing incomplete albums" I import in regular "album mode" but loop through each and every file and import them one by one: I have my config set to automatically try to merge into other albums: To prevent false positives while finding duplicates, respecting the catalog number of releases helps a lot: With each round in the shell loop I would keep on supplying release ID's ( Now one would argue: Isn't that option of import excatly ment for that purpose: Well, yes.....but in the end, with a badly tagged folder like this, often you would end up stuck after merging 5 tracks into an album already to find out that at this point a track would be added with a wrong track position, which is the worst thing that could happen and difficult to fix later on. You would quit the importer, NOTHING would be saved and you would have to start all over again! That is why, in my opinion it is better to import each track one by one. Get it into the correct album, the importer quits and it is saved and tagged properly. Then move on to the next file! |
Beta Was this translation helpful? Give feedback.
-I is --noincremental. I tried that but thought that it didn't work either. I think I did not come up with the idea that providing the full path of the imported file could help. Ok so here is the final "solution" or at least the way it works right now: