When I uncheck " Use standard Artist name instead of name displayed on cover" the “Album Artist” and Artist fields are modified to use the English versions of the names. Howevet the Conductor and Composer fields remain in Russian.
Songkong picking Cyrillic name for Russian artists
Yes because there is no artist credit for these relationships to use instead, I have now fixed issue for next release.
Hi. With 12.2.1 there is still a problem with the “Romanise Names” option. I have just uploaded some support files for
https://musicbrainz.org/release/5ce422e6-4a14-4961-8721-454621e38e67
Here, the ARTIST tags are still in cyrillic, despite MB using the English/Latin version.
I have looked at this and I cannot work out why it is setting Album Artist field okay but not Artist field, could you send me the the two music files please so i can test it locally.
Thanks worked it out, the issue is we were not converting relation artists only release/track and releasegroup artists. This can effect the Artist and Artists fields because we try to set Artist based on user Classical:Track Artist option making use of relations if possible instead of just the MusicBrainz Track Artist entity because they have a clearly defined role (e.g Conductor/Orchestra) instead of us having to guess - raised issue.
Fixed in SongKong 12.3 Screamadelica
Hi Paul. This is great. I have just confirmed that SK is now working well for most of my Russian composers and artists albums.
I have noticed that in a few cases it is still selecting the cyrillic version of the name of the work. I will set up support files for an example shortly. There was also one case where some additional track artists had duplicate credits, one romanised and the other in cyrillic. These were obscure russian singers and probably not in the classical artists list. Again, will check and let you know.
Hi, thanks I received the reports I think the issue maybe Discogs related but unsure, bit confusing.
It would help if you spell out to me exactly what is wrong in both Report 1 and Report 2 and provide me with the files so I can test locally.
Ah yes, I think you are correct about discogs, and it may have something to do with previously set metatata. I noticed that the Cryillic singer names were in the “Credits:” tag, which I believe is fetching from Discogs.
This does not appear to be reproducible. If I wipe all metadata except acoustids and rematch to “one album” to https://www.discogs.com/release/10455715 (without the explicit it finds an alternative version and the wrong cover art). After that the only tag in Cyrillic is “Label” and “credits”.
A subsequent “Fix Songs” corrects the label name to “Olympic”. [However it also decides the album is not classical and unsets IS_CLASSICAL (incorrectly).]
If instead I match to the Musicbrainz release https://musicbrainz.org/release/cc6b5a10-6499-49f5-9c89-e7a322830f4e, it does not find the discogs as well, and also sets IS_CLASSICAL to False.
I also notice that when wiping all metadata and starting again, that SongKong will fetch cover art from discogs but not MusicBrainz. Is this a known limitation?
So I’ll withdraw my original issue as not reproducible but I’m afraid add to others instead : the failure to determine IS_CLASSICAL and the failure to fetch cover art from discogs.
Can you upload the music files please.
I’m afraid I just found another instance where Fix Songs “corrects” English work names to Cyrillic - just sent support files, reproducible this time.
https://www.dropbox.com/scl/fo/hsf4m54x3sarp74u58nmv/AJkyfNlep-W-5yWtKcsCcJo?rlkey=fvtmkq1s66bblrk3bkn3ayy26&dl=0
https://www.dropbox.com/scl/fo/fhgnf0vlrpgfv4rta3nib/AI8UgLCIGR6nmXIIowzaC6I?rlkey=zzy3q9i88v555eo1dn4qasu0m&dl=0
Ok. so the first bug is that when getting release direct from MusicBrainz for each track it was only getting the Recording Artist Credit not the Track Artist Credit, the knock on effect was this meant IsClassical checks such as
- Recording artist differs to Track Artist and only one Track Artist (because Track Artist is Composer)
failed.
Additionally when we get direct from MusicBrainz we dont get the Works hierarchy because it requires too many queries, so other checks such as:
- At least two levels of works
- WorkType is Classical type
also failed
So that is why it wasn’t set as Classical, fixing the track artist credit issue fixes so it is now marked as Classical
This is only an issue when we have to retrieve release direct from MusicBrainz because not yet in Albunack
You are correct when retrieving release directly from MusicBrainz instead of Albunack it does not retrieve cover art, but it can be done I have raised https://jthink.atlassian.net/browse/SONGKONG-2928
Hi, are we talking about the Movement or the Work field?
If we can derive Movement from Title then we use that, if we cannot we use the linked MB Recording Work. Similarly, if we can derive Work from Title then we use that, if not we use MB Work (this is the Work that Mb Recording Work is part of)
So here are the Titles:
Capriccio espagnol, Op. 34: I. Alborada
Capriccio espagnol, Op. 34: II. Variazioni
Capriccio espagnol, Op. 34: III. Alborada
Capriccio espagnol, Op. 34: IV. Scena e canto gitano
Capriccio espagnol, Op. 34: V. Fandango asturiano
Overture “May Night”
Sadko, Op. 5
Suite “The Snow Maiden”: I. Introduction
Suite “The Snow Maiden”: II. Danse des oiseaux
Suite “The Snow Maiden”: III. Cortège
Suite “The Snow Maiden”: IV. Danse des bouffons
Suite “The Tale of Tsar Saltan”: I. Tsar’s Farewell and Departure
Suite “The Tale of Tsar Saltan”: II. Tsarina in a Barrel at Sea
Suite “The Tale of Tsar Saltan”: III. The Flight of the Bumble-bee
Suite “The Tale of Tsar Saltan”: IV. The Three Wonders
Suite “The Golden Cockerel”: I. Tsar Donon in his Palace
Suite “The Golden Cockerel”: II. Tsar Donon on Campaign
Suite “The Golden Cockerel”: III. Tsar Donon as Guest of the Queen of Shemakha
Suite “The Golden Cockerel”: IV. The Wedding and Lamentable End of Donon
Symphony No. 2, Op. 9 “Antar”: I. Largo - Allegro giocoso - Adagio - Largo - (Tempo I) - Allegretto vivace - Adagio - Allegretto vivace - Largo (Tempo I)
Symphony No. 2, Op. 9 “Antar”: II. Allegro - Molto allegro - Meno mosso, allargando - Allegro (Tempo I)
Symphony No. 2, Op. 9 “Antar”: III. Allegro risoluto alla marcia
Symphony No. 2, Op. 9 “Antar”: IV. Allegretto vivace - Andante amoroso - Animato assai - Tempo I
Russian Easter Festival Overture, Op. 36
and here are the values SongKong added to Movement
Alborada
Variazioni
Alborada
Scena e canto gitano
Fandango asturiano
Увертюра
Introduction
Danse des oiseaux
Cortège
Danse des bouffons
Tsar’s Farewell and Departure
Tsarina in a Barrel at Sea
The Flight of the Bumble-bee
The Three Wonders
Tsar Donon in his Palace
Tsar Donon on Campaign
Tsar Donon as Guest of the Queen of Shemakha
The Wedding and Lamentable End of Donon
Largo - Allegro giocoso - Adagio - Largo - (Tempo I) - Allegretto vivace - Adagio - Allegretto vivace - Largo (Tempo I)
Allegro - Molto allegro - Meno mosso, allargando - Allegro (Tempo I)
Allegro risoluto alla marcia
Allegretto vivace - Andante amoroso - Animato assai - Tempo I
Essentially we used the MusicBrainz Works Hierachy to work if a song is a movement of a work or just standalone work.
If It is a movement of work we add the Movement and Work fields (and there is also the Three Level Opera Works case). Is more complext than this but basically if the title looks like a movement and work we use this for the Movement and Work fields, if not possible we don’t use. If we can’t use we fall back to the MB Works titles. we don’t currently support Work Aliases but we already have an issue for that.
So for most tracks we could derive Movement and Work from title
But in the case of Overture “May Night”/Увертюра which itself is part of Майская ночь ( May Night , May Night) we didnt derive the work from title.
Now, Im not entirely clear why we couldnt use title Overture “May Night” as movement, it may be because its the only movement of that work on the release so I may be able to fix that.
In the case of Sadko, Op. 5 it is standalone Work so not a Movement so field is left blank
and here are the values SongKong added to Work
Каприччио на испанские темы, op. 34
Каприччио на испанские темы, op. 34
Каприччио на испанские темы, op. 34
Каприччио на испанские темы, op. 34
Каприччио на испанские темы, op. 34
Майская ночь
Sadko, op. 5
Suite from “The Snow Maiden”
Suite from “The Snow Maiden”
Suite from “The Snow Maiden”
Suite from “The Snow Maiden”
Musical Pictures from “The Tale of Tsar Saltan”, op. 57
Musical Pictures from “The Tale of Tsar Saltan”, op. 57
The Tale of Tsar Saltan: Act III
Musical Pictures from “The Tale of Tsar Saltan”, op. 57
Четыре музыкальных картины из оперы «Золотой петушок»
Четыре музыкальных картины из оперы «Золотой петушок»
Четыре музыкальных картины из оперы «Золотой петушок»
Четыре музыкальных картины из оперы «Золотой петушок»
Symphony no. 2 “Antar”, op. 9
Symphony no. 2 “Antar”, op. 9
Symphony no. 2 “Antar”, op. 9
Symphony no. 2 “Antar”, op. 9
Russian Easter Festival Overture, op. 36
Ah I forgot this issue
So because we could not derive work from title for all tracks we fall back to using MusicBrainz for all tracks for better consistency, since we couldnt derive work from for track 6 we didnt do for any.
So probably the ultimate solution is really adding support for Work Aliases
So for the first five the Mb Work is Каприччио на испанские темы, op. 34 and since we don’t yet support Work aliases that is what we have to use.
Whereas for tracks 8-11 the Work Suite from “The Snow Maiden is the title in MusicBrainz so there is no problem.
So if I disable the consistency fix then I get
Movement
Alborada
Variazioni
Alborada
Scena e canto gitano
Fandango asturiano
Увертюра
Introduction
Danse des oiseaux
Cortège
Danse des bouffons
Tsar’s Farewell and Departure
Tsarina in a Barrel at Sea
The Flight of the Bumble-bee
The Three Wonders
Tsar Donon in his Palace
Tsar Donon on Campaign
Tsar Donon as Guest of the Queen of Shemakha
The Wedding and Lamentable End of Donon
Largo - Allegro giocoso - Adagio - Largo - (Tempo I) - Allegretto vivace - Adagio - Allegretto vivace - Largo (Tempo I)
Allegro - Molto allegro - Meno mosso, allargando - Allegro (Tempo I)
Allegro risoluto alla marcia
Allegretto vivace - Andante amoroso - Animato assai - Tempo I
Work
Capriccio espagnol, Op. 34
Capriccio espagnol, Op. 34
Capriccio espagnol, Op. 34
Capriccio espagnol, Op. 34
Capriccio espagnol, Op. 34
Майская ночь
Sadko, op. 5
Suite “The Snow Maiden”
Suite “The Snow Maiden”
Suite “The Snow Maiden”
Suite “The Snow Maiden”
Suite “The Tale of Tsar Saltan”
Suite “The Tale of Tsar Saltan”
Suite “The Tale of Tsar Saltan”
Suite “The Tale of Tsar Saltan”
Suite “The Golden Cockerel”
Suite “The Golden Cockerel”
Suite “The Golden Cockerel”
Suite “The Golden Cockerel”
Symphony No. 2, Op. 9 “Antar”
Symphony No. 2, Op. 9 “Antar”
Symphony No. 2, Op. 9 “Antar”
Symphony No. 2, Op. 9 “Antar”
Russian Easter Festival Overture, op. 36
So to summarize the reason for the issues is that track six has title Overture “May Night” so there is nothing to indicate the name of the work, because of this to achieve consistency we derive the Movement and Work fields for all tracks from the Mb Works rather than from the track title
If we supported Work Aliases this would mean all movements and works on this release could have English/Latin script titles, although they may vary slightly from what is written on album cover.
Without this I’m trying to work if this is a case where we should allow SongKong to use works and movements derived from titles for the other tracks despite the failure for the one track, but I cannot work out a sensible rule that is going to work well for all releases
okay here is a potential rule that might work.
After grouping tracks by work if we have track that is the only track on the release for its particular work and the title does not seem to be of the form Work:Movement then just use Title as Movement field.
Making just this change results in track 6 now showing Overture “May Night” for Movement field, although this doesn’t help Work field which is still Майская ночь, what do you think?
Dear Paul,
Thank you for unfulding the debugging process in such detail. This does indeed help me understand the issue, and I think your workaround and proper fix to use the MB primary emglish language alias will tackle the issue robustly.
The other means might be to see if there’s a RESTful call to Google Translate available……
Yes I learnt a few things in the process, I have now created this article to better document things rather than having to parse the code from scratch again.
So I have implemented the
if we have track that is the only track on the release for its particular work and the title does not seem to be of the form Work:Movement then just use Title as Movement field
rule, logged as issue
With regards to the Work names for this album we get much better results if we remove the consistency check, but this would lead to worse results for the Messiah release that caused the change to be made in the first place, any thoughts?
The use of Work aliases is going to improve things, but even then we still want to use the titles from CD if possible, for example the CD might be in German and the MB Work title might have an English alias, and might prefer to have the German names.
Interesting idea, however it would slow things down, there are limitations on use of Google Translate so would probably need customer to create their own key, translation may be wrong and Google translate may change its translation over time leading to unexpected results. So im not going to go down this road.