For the first msxml6.dll error i need the Discogs / MusicBrainz release to find the reason of the problem.thinckley wrote: ↑Tue Jun 19, 2018 12:01 pm I am seeing a couple of errors with V5.60.
MM Version 4.1.20.1864
Windows 10 Enterprise, Build 17134
"Error happened during script execution: Object required 'WebBrowser'"
"Error #-2147012744 - msxml6.dll / The server returned an invalid or unrecognized response / File: <string>\MusicBrainzWebTag.vbs, Line: 3891, Column: 5"
MusicBrainz only
Issue: Neither search includes track counts, so the first return is often wrong. For MusicBrainz it is not as much of an issue since track count is returned in the returns drop down, for Discogs you have to go through each return to find the correct disc. It would be nice if the search either compared track counts, or if the Discogs returns listed track counts.
I know the problem you describe. Discogs don't provide the track counts of the releases. If i want to compare the track counts, i have to get the data from every release, this would take a long time.