Open phw opened 10 months ago
It looks like since a while merged recordings in MB don't get followed up on the AcoustID side. There are now many instances of unresolved merges. Some examples:
https://acoustid.org/track/b1eb0783-f5f3-4428-9733-2fbfd8e30d93 https://acoustid.org/track/91684050-2987-48e9-807a-4f7354305511 https://acoustid.org/track/1cc7cd8a-50c7-4951-a8fa-557c6b2b41e6
Maybe there is some issue with running the merge code from https://github.com/acoustid/acoustid-server/blob/5c05072a01571b6a13f971bfcac2184936967549/acoustid/data/track.py#L149 .
See also the discussion at https://community.metabrainz.org/t/why-does-acoustid-sometimes-not-show-merged-recordings/659454
Thousands of people are waiting for it.
See also the discussion at https://community.metabrainz.org/t/worse-results-in-picard-2-10/663668
See also the discussion at https://community.metabrainz.org/t/picard-scan-still-returning-new-acoustid-submissions-as-standalone-recordings/603676
It looks like since a while merged recordings in MB don't get followed up on the AcoustID side. There are now many instances of unresolved merges. Some examples:
https://acoustid.org/track/b1eb0783-f5f3-4428-9733-2fbfd8e30d93 https://acoustid.org/track/91684050-2987-48e9-807a-4f7354305511 https://acoustid.org/track/1cc7cd8a-50c7-4951-a8fa-557c6b2b41e6
Maybe there is some issue with running the merge code from https://github.com/acoustid/acoustid-server/blob/5c05072a01571b6a13f971bfcac2184936967549/acoustid/data/track.py#L149 .
See also the discussion at https://community.metabrainz.org/t/why-does-acoustid-sometimes-not-show-merged-recordings/659454