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
I recently discovered the original_year field for tracks and albums, and would like to show it instead of (release) year in query results. However, I'm having some trouble with getting the field to show up correctly, and I'm getting increasingly confused about the expected behaviour. The confusion stems from me trying to deal with a number of (supposedly) incorrectly set original_year fields for some library items, and not understanding how they should be set / unset / emptied. The underlying bigger plan would be to unset/empty out the (supposedly) incorrectly set fields, and possibly setup a logic for showing year instead of original_year in query results when the latter field is unset / empty. See the use case below for details.
Use case
My album_format and item_format configurations are as follows:
However, querying for the track still shows original_year as before, as shown below. This might have to do with no logic setup so far for dealing with unset fields.
> beet ls album:"5XOD"
Five Times Of Dust - 5XOD - Negativ Terminal Data | [Domestica, 0000] Synth/Wave | MP3
Also, checking for the value of original_year using the edit command shows:
> beet edit --all album:"5XOD"
(in text editor)
...
original_year: 0
...
.... which was the value it was set to before running the Zero Plugin. This makes me somewhat confused, not having the big picture (is it a placeholder flag for an unset field?).
Finally, as I'm more interested in albums, the Zero plugin doesn't seem to handle the -a flag, and thus I can't modify the album at all:
> beet zero -a album:"5XOD"
Usage: beet zero [options]
beet zero: error: no such option: -a
... and as such, my original problematic query output remains:
beet ls -a album:"5XOD"
Five Times Of Dust - 5XOD | [Domestica, 0000] Synth/Wave | MP3
At this point, I'm already feeling stuck and confused, and would like to have some external feedback on what is going on.
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.
-
I recently discovered the
original_yearfield for tracks and albums, and would like to show it instead of (release)yearin query results. However, I'm having some trouble with getting the field to show up correctly, and I'm getting increasingly confused about the expected behaviour. The confusion stems from me trying to deal with a number of (supposedly) incorrectly setoriginal_yearfields for some library items, and not understanding how they should be set / unset / emptied. The underlying bigger plan would be to unset/empty out the (supposedly) incorrectly set fields, and possibly setup a logic for showingyearinstead oforiginal_yearin query results when the latter field is unset / empty. See the use case below for details.Use case
My
album_formatanditem_formatconfigurations are as follows:An example of a correctly rendering item looks as follows:
Notice the existence of both
yearandoriginal_yearproperties as a detail:However, some items have something off with the
original_yearfield, making them look as follows:The relevant fields are set to:
And for the singular track in the album
I can remove the seemingly incorrectly set
original_yearfield for the singular track using Zero Plugin byAfter this, the field is not shown any more:
However, querying for the track still shows
original_yearas before, as shown below. This might have to do with no logic setup so far for dealing with unset fields.Also, checking for the value of
original_yearusing the edit command shows:.... which was the value it was set to before running the Zero Plugin. This makes me somewhat confused, not having the big picture (is it a placeholder flag for an unset field?).
Finally, as I'm more interested in albums, the Zero plugin doesn't seem to handle the
-aflag, and thus I can't modify the album at all:... and as such, my original problematic query output remains:
At this point, I'm already feeling stuck and confused, and would like to have some external feedback on what is going on.
Thanks for your input!
Beta Was this translation helpful? Give feedback.
All reactions