SongKong Jaikoz

SongKong and Jaikoz Music Tagger Community Forum

original Release year not filled in

#1

Hi There,

I just upgraded to the pro 10 version and noticed that the original release year isn’t filled in.

https://musicbrainz.org/release/c1f47c16-d252-38be-91a2-4e0fb7abf2c1 is a disc witch I have bought and challenges Jaikoz a lot.

It is a Various artist release.
It was released in 1992
It contains songs which where hits in my country in the year 1985

The original Release year isn’t filled in.

The Pre Historie is a Radio Program on Flemish radio station 2 dating back to the year 1984.
During a episode Music from a certain mont/decennial period is played and between music trivia/news from the same times is given. It almost literal takes you back in time…
Hence a lot of compilations cd’s came out…

Why is the original Release year not filled in automatically…

Kind Regards
Guy Forssman

#2

Hi, so it should always add something for original release date (even if not correct). So let me check a few things

  • Did it actually match to MusicBrainz release.
  • Has it added anything into Original Album field
  • Did it add to Year field
#3

I copied the album deleted the metadata but could not duplicate the faulty behaviour.
The first time it left the “Original Release Year” field blank and only filled in 1992 for the “year” field.

On a non exiting album in the MusicBrainz database https://www.discogs.com/Various-Flairs-Top-Of-The-80s-Vol-1/release/5778711
I had the following behaviour.
I saw that Original Release Year gets a date see (picture 1) but on finishing writing the metadata it changed al 3 songs to a faulty same date ( see picture2)
Because the album exist in the Discogs database I also tried this one on step 2

Step 1 tried MB --> results in not finding the album but seperate songs
Step 2 search manual on google
Step 3 used Jaikoz with release nr from Discogs.
Step 4 noticed that not all data is writen none is overwritten


What is happening here?

#4

So are you saying the date is correct, but a match to Discogs overwrites the data with incorrect data ?

#5

Hi ,

What happens when I use MusicBrainz as a tagging service is explained in picture 1 and 2.
Because Jaikoz overwrites the correct data with faulty one I used Discogs as a tagging service and then Step 4 I noticed that not all data is writen none is overwritten

so in short
Step 1 load songs from album (unknown to MB )
Step 2 choose MB as a tagging service–> results in not finding the album but separate songs https://ibb.co/N3SV1qw
Step 3 Jaikoz overwrites the found date and fills in a new one https://ibb.co/tXwz6nn

Step 4 search manual on google and found it in Discogs
Step 5 used Jaikoz with release nr from Discogs.
Step 6 noticed that not all data is written none is overwritten

Kind regards
Guy

#6

[quote=ForSSound]Hi ,

What happens when I use MusicBrainz as a tagging service is explained in picture 1 and 2.
Because Jaikoz overwrites the correct data with faulty one I used Discogs as a tagging service and then Step 4 I noticed that not all data is writen none is overwritten

so in short
Step 1 load songs from album (unknown to MB )
Step 2 choose MB as a tagging service–> results in not finding the album but separate songs https://ibb.co/N3SV1qw
Step 3 Jaikoz overwrites the found date and fills in a new one https://ibb.co/tXwz6nn
[/quote]
Okay, what triggers step 3, you run Autocorrect from MusicBrainz again and it matching wrong album or right album but wrong date ?

Okay, by default we dont overwrite existing data with data from Discogs if the songs have already been matched to MusicBrainz because we consider MusicBrainz to be the most accurate metadata source. You can modify this, by adding fields to Preferences:Remote Correct:Discogs:Always modify these fields

#7

Okay, what triggers step 3, you run Autocorrect from MusicBrainz again and it matching wrong album or right album but wrong date ?

The screenshots are from the same push on Autocorrect from MusicBrainz…
While it’s searching I see the date’s being filled in. (screenshot 1)
On completion of that search the data’s get overwritten with something else…
screenshot 2

So 1 push not 2