Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: ORIGYEAR auto tagging? (Read 1195 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

ORIGYEAR auto tagging?

I'm looking for any automation to populate ORIGYEAR data for **individual** tracks.
e.g. get the actual (or first) release date of the individual tracks of a compilation

My current best method is to manually update after strongarming ChatGPT into providing years (not sustainable nor likely accurate).

Re: ORIGYEAR auto tagging?

Reply #1 –
I'm getting the dates of the non-comp releases from Discogs and foo_discogs and the dates are then mapped to these fields:

%RELEASE_YEAR%
%MASTER_RELEASE_DATE% (best)
%RELEASE_DATE_RAW%
%RELEASE_MONTH%
%RELEASE_DAY%

Of course, compilations of tracks all released on different dates are a different matter however. The singles should provide this info.
Quis custodiet ipsos custodes?  ;~)

Re: ORIGYEAR auto tagging?

Reply #2 –
Quote from: 2tec on
Of course, compilations of tracks all released on different dates are a different matter however

Thanks yes, I'm using foo_discogs as well, but specifically looking for each track.

I'm open to any other apps or methods

Re: ORIGYEAR auto tagging?

Reply #5 –
sadly the MusicBrainz tagger is no better at this

see ~ https://marc2k3.github.io/component/musicbrainz64/

however, someday one of the devs might look into tagging compilations with the original release date of that single

just begging

I end up doing this manually (manfully)

also see: https://community.metabrainz.org/t/how-to-get-picard-writing-the-original-release-date-year-of-a-recording/355388/2
Quis custodiet ipsos custodes?  ;~)

Re: ORIGYEAR auto tagging?

Reply #7 –
This isn't going to happen for tracks, it's insane.

The comment linked by 2tec is absolutely relevant. It's from an MB dev (also goes by phw on this forum)

The whole point of original release date in MusicBrainz land is for albums that may have many versions. These are categorised as releases and they all belong to a common release group.

As an example, Hounds of Love has a 1997 re-release (one of many on the site)

https://musicbrainz.org/release/464753da-e92e-42c6-958e-f94d2d5ed224

But the original release was in 1985 determined from the first release in the parent release group.

https://musicbrainz.org/release-group/017f2a37-a78f-3578-9611-fa40408e5d90

So this is the original date that various MusicBrainz taggers write fully working as intended.
 

Re: ORIGYEAR auto tagging?

Reply #8 –
Quote from: marc2k3 on
This isn't going to happen for tracks, it's insane.



Whether it goes in ORIGYEAR or a custom tag, is irrelevant (to me at least).

The concept of accurate track tagging is clearly not insane, what is insane is that 25+ years on, there's still no tool for the job.