Core ripping classical
Posted by: jon h on 17 December 2017
I have just ripped a classic classical CD.
EMI CD of Beethoven Violin Concerto, performed by Perlman, conducted by Giulini. It doesnt get simpler than this.
Core lists it as:
Artist: Ludwig Van Beethoven
Conductor: blank
Composer: Blank
Data came in from FreeDB. Neither Rovi nor MusicBrainz lists it.
What a clusterfsck.
nbpf posted:Musicmad posted:...If you keep to the Composer's name only then works such as Music for the Funeral of Queen Mary, Z.860 [Christophers/Sixteen] (1994) will be awfully brief ... Purcell's contribution was about 1/3 only of the playing time.
...
Not necessarily, it depends on the UPnP server. If you use MinimServer and search after Composer > Work you will first see only the tracks of Music for the Funeral of Queen Mary, Z.860 [Christophers/Sixteen] (1994) for which the composer is Purcell (as one would expect) but you will be also given the opportunity to select the whole album.
For me the simplest tagging scheme is to put in Album the text which is on the cover of a CD and fill in Composer, Work, Conductor, Ensemble, Artist, Period, Form, etc. with their respective values or leave them blank.
It goes without saying that a track/file can be associated to more than one artist and, in fact, to more than one conductor (parts of War Requiem are often performed with two or three conductors, for instance), to more than one composer (typical for transcriptions) and, especially in opera works, to more than one ensemble (orchestra and chor) and to more than one work ("Das Rheingold" is part of "Der Ring des Nibelungen").
This complexity implies that, if you try to compensate for the weaknesses of a UPnP server by using a clever tagging scheme you very likely will get into troubles. If you call things by name and use Composer for composers, Conductor for conductors, Work for works, etc. you can hardly make anything wrong.
I'm sure that you and I discussed this issue a few weeks ago ... and I promised to review and consider your approach which, regretfully, I have failed to do. I know the problem is that each time I look at MinimServer I get totally lost and revert back to AssetNas which is simpler to use. And the fact that this server works so well makes me question why not use it? The major issue is nominating the Album Artist v. Track Artist (when ripping).
In your reply to my example you say that you can select the whole album (and I recall checking this out last time) ... but surely, if the server knows that the Album is linked to that Composer then by default you have nominated the Composer as the Album Artist.
If I get some free time over the next week I'll give it some more thought ... thanks for the reminder.
Mitch
Musicmad posted:nbpf posted:Musicmad posted:...If you keep to the Composer's name only then works such as Music for the Funeral of Queen Mary, Z.860 [Christophers/Sixteen] (1994) will be awfully brief ... Purcell's contribution was about 1/3 only of the playing time.
...
Not necessarily, it depends on the UPnP server. If you use MinimServer and search after Composer > Work you will first see only the tracks of Music for the Funeral of Queen Mary, Z.860 [Christophers/Sixteen] (1994) for which the composer is Purcell (as one would expect) but you will be also given the opportunity to select the whole album.
For me the simplest tagging scheme is to put in Album the text which is on the cover of a CD and fill in Composer, Work, Conductor, Ensemble, Artist, Period, Form, etc. with their respective values or leave them blank.
It goes without saying that a track/file can be associated to more than one artist and, in fact, to more than one conductor (parts of War Requiem are often performed with two or three conductors, for instance), to more than one composer (typical for transcriptions) and, especially in opera works, to more than one ensemble (orchestra and chor) and to more than one work ("Das Rheingold" is part of "Der Ring des Nibelungen").
This complexity implies that, if you try to compensate for the weaknesses of a UPnP server by using a clever tagging scheme you very likely will get into troubles. If you call things by name and use Composer for composers, Conductor for conductors, Work for works, etc. you can hardly make anything wrong.
...
In your reply to my example you say that you can select the whole album (and I recall checking this out last time) ... but surely, if the server knows that the Album is linked to that Composer then by default you have nominated the Composer as the Album Artist.
...
No, I never fill in Album Artist with composer values: composer values only populate the Composer index.
The point is that the server does not actually need composer values in the Album Artist index to deduce that a certain album is linked to a certain composer: every track of an album has the same Album value by definition. This is finally what an album is: a collection of files with the same Album value. Thus, if one drills down to a certain track (file) while searching after Composer, the server can immediately deduce the album that track belongs to by looking up the Album value for that track.
In fact, if one picks a Composer value in MinimServer, one is immediately presented with all the albums and with all the tracks associated with that composer. Thus, for instance, if I select "Bach, Johann Sebastian" as a composer, the next MinimServer screen looks like the following:
47 albums
1144 items
Composer
Work
Conductor
Ensemble
Artist
Genre
Form
Period
Rec. date
Inc. date
If I further select a Work, say "Brandenburgische Konzerte BMW 1046-1051", the next screen looks like
3 albums
39 items
Work
Conductor
Ensemble
Rec. date
Notice that now certain indexes have now disappeared. This is because they do not contain any further options. In other words, all the 39 files have now the same Genre value (or values). Still, the 39 tracks have different recording dates, ensemble values, conductor values and, perhaps surprisingly, work values. Can you see why this can happen?