You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
all of my compilations (comp=True) have their year, genre and albumartist_sort tags treated as album-level tag. In contrast, all the other albums (Comps=False or empty) seems to have those tags managed as track level tag, allowing for the same album different values for years.
This is very problematic for compilations, given the fact that is very common for them to have tracks originally released in different years, or belonging to different genres (i.e. live recordings of music festival).
The huge issue is that beets stores in the db only a single value - usually from the first track - and when i run write that value overwrites the individual track tags, resulting in wrong metadata.
Is this the intended behavior ?
I built the library with: beet import -A ~/my/music/folder && beet update
my config is
import:
copy: no
write: no
incremental: yes
ui:
color: yes
pluginpath: ~/beets/myplugins
plugins: edit info
max_filename_length: 16
paths:
default: %left{$albumartist,16}/$album%aunique{}/$track.%left{$title,5}...%right{$title,5}
singleton: non.album/$artist/$title
comp: compilations/$album%aunique{}/$track.$title
asciify_paths: yes
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
all of my compilations (comp=True) have their year, genre and albumartist_sort tags treated as album-level tag. In contrast, all the other albums (Comps=False or empty) seems to have those tags managed as track level tag, allowing for the same album different values for years.
This is very problematic for compilations, given the fact that is very common for them to have tracks originally released in different years, or belonging to different genres (i.e. live recordings of music festival).
The huge issue is that beets stores in the db only a single value - usually from the first track - and when i run
writethat value overwrites the individual track tags, resulting in wrong metadata.Is this the intended behavior ?
I built the library with:
beet import -A ~/my/music/folder && beet updatemy config is
Beta Was this translation helpful? Give feedback.
All reactions