Hum, seems I've been working on that many months ago ... but I have absolutely no memory of it ! (getting old is ugly !).
I'll have a look. On Thu, Jan 5, 2017 at 9:13 PM, Adrian Sampson <[email protected]> wrote: > That’s not currently possible, alas—the `original_date` option overwrites > the actual release date. > > That might be a good use case for this old feature proposal: > https://github.com/beetbox/beets/issues/488 > > > On Jan 5, 2017, at 3:04 PM, Michael MacLeod <[email protected]> wrote: > > Is it possible to keep both release_year and original_year, but make $year > default to one or the other? Ie, I want the tags and paths to use > original_year, because that's how I generally think about my music, but I > want to keep release_year info in the DB in case I want to query for it. > > On Thu, Jan 5, 2017 at 2:58 PM, Adrian Sampson <[email protected]> > wrote: > >> Beets also records the “original” release date for each release group >> (original_year, etc.). If you’d like to use this for the main date tag, you >> can also do that: >> http://beets.readthedocs.io/en/v1.4.2/reference/config.html? >> #original-date >> >> Adrian >> >> > On Jan 5, 2017, at 2:55 PM, Pierre Rust <[email protected]> wrote: >> > >> > Hi, >> > >> > lately I've been doing some retagging / cleanup on old albums and I >> just realized that many of them where getting tagged with very recent dates. >> > For example, when tagging "Let It Bleed" from The Stones (initially >> released in 1968), it get a date in 2002 ! >> > When looking at the musicbrainz release (automatically) selected during >> import, it make some sense : http://musicbrainz.org/release >> /b2ca3b22-f3cc-40c0-b2d3-f4e1d6602106 >> > 2002 is the date for this specific release, so it's not completely >> wrong, yet it's definitively not what I'm looking for nor the info I want >> to be displayed in my library. >> > >> > I've experimented reimporting with the timid option and selecting >> manually the id of the original release on imdb : it works but is quite >> tedious (the orginial release is not even in the list of the proposed >> candidates) and it requires to first identify all mis-dated albums (as >> there where imported automatically with -q, I did not realize immediately >> that the previously correct date were being overwritten ...) >> > >> > I don't remember seeing this behavior before (and I've been using beets >> for some years now), is that something new, voluntary or bug ? Is there >> any way to get the date for the original release instead ? >> > >> > thanks ! >> > >> > Pierre >> > >> > >> > -- >> > You received this message because you are subscribed to the Google >> Groups "beets" group. >> > To unsubscribe from this group and stop receiving emails from it, send >> an email to [email protected]. >> > For more options, visit https://groups.google.com/d/optout. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "beets" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/d/optout. >> > > > -- > You received this message because you are subscribed to the Google Groups > "beets" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > > > -- > You received this message because you are subscribed to the Google Groups > "beets" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "beets" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
