Reply to thread

Message

<blockquote data-quote="rtv" data-source="post: 80040" data-attributes="member: 12309">I absolutely agree with you on this - but to make things &quot;right&quot; MP's code to parse the CDDB answer would have to be changed as I only query the gui properties and cannot even distinguish if a various artist tag was added to the track or artist field..Of course something like your pseudocode could be applied there. It would help in maybe 75% of all cases then..I've already investigated ways to support Musicbrainz as my plugin would be ready for this. Unfortunately they rely on a libmusicbrainz which could only be included if the source would be published..Nevertheless I'm keeping my eyes open since this would also solve some other problems (like our database submitting &quot;Rasmus&quot; for &quot;The Rasmus&quot; - a fan told me this is really disgusting <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink&nbsp; &nbsp; ;)" loading="lazy" data-shortname=";)" /> )</blockquote>

[QUOTE="rtv, post: 80040, member: 12309"] I absolutely agree with you on this - but to make things "right" MP's code to parse the CDDB answer would have to be changed as I only query the gui properties and cannot even distinguish if a various artist tag was added to the track or artist field.. Of course something like your pseudocode could be applied there. It would help in maybe 75% of all cases then.. I've already investigated ways to support Musicbrainz as my plugin would be ready for this. Unfortunately they rely on a libmusicbrainz which could only be included if the source would be published.. Nevertheless I'm keeping my eyes open since this would also solve some other problems (like our database submitting "Rasmus" for "The Rasmus" - a fan told me this is really disgusting ;) ) [/QUOTE]

Verification