Do I need to start over?

spinach · March 31, 2023, 1:57am

I’m about a quarter into a multi-TB import when I noticed that I made mistakes. When beets couldn’t find tracks in an album match from discogs or musicbrainz, it left those behind in the source folder rather than importing them. I probably should have imported those albums ‘As Is’.

I used copy not move during import so I still have all my original files. What’s the best way forward? Do I need to start from scratch or can I reimport from my source directory to grab all those orphaned tracks?

RollingStar · April 1, 2023, 8:49pm

Hot take-

look at duplicate_action.

https://beets.readthedocs.io/en/stable/reference/config.html#duplicate-action

there’s some way to ‘resume’ an import but IDK if it will help you:

https://beets.readthedocs.io/en/latest/reference/cli.html?highlight=import#import

spinach · April 3, 2023, 1:53am

Thanks for your reply but neither of those suggestions are going to help me. I don’t need to deal with any dupes right now. If I select ‘no’ to Resume Import it doesn’t start from the beginning.

How do I just remove all entries in beets and restart my import?

adrian · April 6, 2023, 8:07pm

I’m not entirely clear on why saying “no” to “resume import” doesn’t restart… but you can delete the ~/.config/beets/state.pickle to clear any memory of an interrupted import. You also may want to be careful about the import.incremental setting, if you’ve ever had that enabled.

jojo · April 13, 2023, 5:37am

I’m not sure if that helps but there is a log file that should tell you which folders were skipped. You can run an import from that logfile using the --from-logfile option of the import command. Maybe that helps you to not have to start over completely?

I just checked and realized that there is no default value for that log file setting, so if you haven’t set that on purpose when you’ve set up beets, my suggestions won’t help, sorry

github.com

beetbox/beets/blob/d05c34ec4e9d8fa9e34706ac2279b7315b36e1e0/beets/config_default.yaml#L19


      
          hardlink: no
          reflink: no
          delete: no
          resume: ask
          incremental: no
          incremental_skip_later: no
          from_scratch: no
          quiet_fallback: skip
          none_rec_action: ask
          timid: no
          log:
          autotag: yes
          quiet: no
          singletons: no
          default_action: apply
          languages: []
          detail: no
          flat: no
          group_albums: no
          pretend: false
          search_ids: []

spinach · June 3, 2023, 2:43pm

OK, after a hiatus from Beets I returned to the task of reimporting my Downloads. I used the --noincremental tag and that got beets to start from the beginning. Found that one on Google Groups in 2023!

https://groups.google.com/g/beets-users/c/AhWwRkszFOE

But now I’m finding that extrafiles is leaving files behind or behaving oddly when I import an already existing album As Is. This creates a second folder that contains just the extra files whereas the music files are in their own folder.

I really feel like I need to just delete all my imported albums and start fresh. Can I do that without screwing things up? Will the Update command clear out the database?