Beet mv mystery

Help
1

I’m having a problem with beet mv. I’m trying to use a modify tag to separate a subcollection of my music. I think I have the modify and path set up correctly, but some of my files don’t move when I execute beet mv.

My files are on a synology fileserver and I have the directory mounted locally via nfs. I figure this is probably a permissions issue in how I am mounting the directory, but since I don’t get any error from beets I am at a loss for how to debug what the problem is.

directory: /media/dropbox/music_beets
library: /home/cox/musiclibrary.db
import:
    move: yes
asciify_paths: yes
plugins: discogs duplicates the embedart fetchart badfiles #chroma #autobpm
discogs:
    user_token: ilsaKMTMtLATbpZiLOYQPfXFzjLTBYtdvnhQqQYC
    index_tracks: no
embedart:
    ifempty: yes
    remove_art_file: yes
paths:
    default: $format/%the{%lower{$albumartist}}/$year %lower{$album}/$track $title
    singleton: $format/%the{%lower{$albumartist}}/$track $title
    comp: _music_compilations/$format/$year $album %aunique{}/$track $title
    dj:1: DJ/$format/%the{%lower{$albumartist}}/$year $album/$track $title
    albumtype:soundtrack: _music_soundtracks/$format/$year $album/$track $title
2

Here is a clue, beet mv seems to “move” the same 55 files over and over again:

cox@fleroviumubuntu:/media/dropbox/_inbox_process$ beet mv
Moving 55 items (52952 already in place).
cox@fleroviumubuntu:/media/dropbox/_inbox_process$ beet mv
Moving 55 items (52952 already in place).
3

Looking at my permissions everything is 777 so should work. Should I just be running beets directly on the synology instead of using NFS?

4

Ok removing the path configuration line and runing beet mv seems to have put everything back into my main directory structure. Still not sure why I wasn’t able to move everything. I am going to try out using the convert plugin to move everything I want with DJ=1 and see if that works better.

directory: /media/dropbox/music_beets
library: /home/cox/musiclibrary.db
import:
    move: yes
asciify_paths: yes
plugins: discogs duplicates the embedart fetchart badfiles autobpm edit fromfilename #chroma
discogs:
    user_token: ilsaKMTMtLATbpZiLOYQPfXFzjLTBYtdvnhQqQYC
    index_tracks: no
autobpm:
    auto: no
embedart:
    ifempty: yes
    remove_art_file: yes
paths:
    default: $format/%the{%lower{%asciify{$albumartist}}}/$year %lower{%asciify{$album}}/$track $title
    singleton: $format/%the{%lower{%asciify{$albumartist}}}/$track $title
    comp: _music_compilations/$format/$year $album %aunique{}/$track $title
    albumtype:soundtrack: _music_soundtracks/$format/$year $album/$track $title
    albumtype:other: _audiobooks/$format/%the{%lower{%asciify{$albumartist}}}/$year $album/$track $title
    albumtype:audiobook: _audiobooks/$format/%the{%lower{%asciify{$albumartist}}}/$year $album/$track $title
    #dj:1: DJ/$format/%the{%lower{%asciify{$albumartist}}}/$year $album/$track $title
5

Still no idea what isn’t working. About half of my files don’t beet convert or beet mv. I did notice a clue with beet fields. For some reason I have both a lowercase and an uppercase version of the same field (though I don’t recall ever making the lowercase, both seem to query the same files).

Item flexible attributes:
  data_source
  dj
  track_alt
  DJ
  cover_art_url
Album flexible attributes:
  data_source
6

I think the query is just not working on my tag. In my case running beet ls DJ:1 only outputs a fraction of tracks that I tagged :frowning:

7

huh, the case on my modify tag seems to have been the issue! for some reason there was a dj tag which showed up on the query and a DJ tag which did not. i am pretty sure I only ever used the uppercase version with beet modify. Anyway starting over with a new lower case tag seems to avoid the problem, though I still don’t understand what happened.

8

please go to Discussions on our GitHub repo. It’smuch more lively there :slight_smile:

1 Like