# Italic AcoustID

**URL:** <https://community.metabrainz.org/t/italic-acoustid/734798>\
**Category:** AcoustID\
**Tags:** recordingmerge\
**Created:** [December 30, 2024, 9:27am UTC](https://community.metabrainz.org/t/italic-acoustid/734798 "2024-12-30T09:27:09Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![jesus2099](https://community.metabrainz.org/user_avatar/community.metabrainz.org/jesus2099/32/36_2.png) [@jesus2099](https://community.metabrainz.org/u/jesus2099)\
**Post date:** [December 30, 2024, 9:27am UTC](https://community.metabrainz.org/t/italic-acoustid/734798/1 "2024-12-30T09:27:09Z")

</div>

Anyone knows what does it mean, this italic recording (2nd one)?

> [https://acoustid.org/track/b847e16e-d9ed-4aeb-bc4d-cabe7f16a914](https://acoustid.org/track/b847e16e-d9ed-4aeb-bc4d-cabe7f16a914)
> 
> ### Linked MusicBrainz recordings
> 
> | Title | Artist | Length | Sources |
> | --- | --- | --- | --- |
> | [Tu es folle](https://musicbrainz.org/recording/fd416d42-3d40-4a4f-9673-ca1a51fdedab) | Christophe | 2:34 | 1 |
> | _[Tu es folle](https://musicbrainz.org/recording/fa9c940c-408b-41f0-b746-997e50e36d72)_ | Christophe | 2:30 | 1 |

On MusicBrainz, this recording shows no fingerprints!

> _Tu es folle_ / [fingerprints](https://musicbrainz.org/recording/958820ff-ec99-4aec-8df3-737d699e796e/fingerprints)
> 
> ### Associated AcoustIDs
> 
> This recording does not have any associated AcoustIDs

* * *

### Update

Without userscript, the italic AcoustID is actually shown as:

> [https://acoustid.org/track/b847e16e-d9ed-4aeb-bc4d-cabe7f16a914](https://acoustid.org/track/b847e16e-d9ed-4aeb-bc4d-cabe7f16a914)
> 
> | Title Artist Length | Sources |
> | --- | --- |
> | [_fa9c940c-408b-41f0-b746-997e50e36d72_](https://musicbrainz.org/recording/fa9c940c-408b-41f0-b746-997e50e36d72) | 1 |

---

<div class="post-metadata">

**Author:** ![PacCeggowk9oc](https://community.metabrainz.org/letter_avatar_proxy/v4/letter/p/b9e5f3/32.png) [@PacCeggowk9oc](https://community.metabrainz.org/u/PacCeggowk9oc)\
**Post date:** [December 30, 2024, 2:37pm UTC](https://community.metabrainz.org/t/italic-acoustid/734798/2 "2024-12-30T14:37:41Z")

</div>

Probably a merge in progress that’s not finished yet, because the AcoustID server is lagging behind in submissions. I see the second one as an id only, but the two recordings still exist instead of being merged and one redirecting to the other.

---

<div class="post-metadata">

**Author:** ![jesus2099](https://community.metabrainz.org/user_avatar/community.metabrainz.org/jesus2099/32/36_2.png) [@jesus2099](https://community.metabrainz.org/u/jesus2099)\
**Post date:** [December 30, 2024, 4:30pm UTC](https://community.metabrainz.org/t/italic-acoustid/734798/3 "2024-12-30T16:30:26Z")

</div>

Indeed, there is [a recording merge](https://musicbrainz.org/edit/119730001) (queued today) in progress, including these 2 recordings, but I don’t think we see that 2nd italic recording because of that: The same merge includes a 3rd recording that is not visible, in [AcoustID.org](http://AcoustID.org).

@lukz  
I’d like to know what is the meaning of italic in [AcoustID.org](http://AcoustID.org). A [legend](https://www.wikidata.org/wiki/Q1200435) is missing. 😉

---

<div class="post-metadata">

**Author:** ![agatzk](https://community.metabrainz.org/user_avatar/community.metabrainz.org/agatzk/32/44684_2.png) [@agatzk](https://community.metabrainz.org/u/agatzk)\
**Post date:** [December 30, 2024, 4:54pm UTC](https://community.metabrainz.org/t/italic-acoustid/734798/4 "2024-12-30T16:54:47Z")

</div>

Yes, I think it means the AcoustID was linked to a source recording which was merged into this target recording. An AcoustID fingerprint will not move from the source recording to the target recording during a ‘Merge recordings’ edit (in MB). However, the AcoustID track will still have this (now re-directed) recording ID for the original source recording.

[https://musicbrainz.org/recording/fa9c940c-408b-41f0-b746-997e50e36d72](https://musicbrainz.org/recording/fa9c940c-408b-41f0-b746-997e50e36d72) re-directs to [https://musicbrainz.org/recording/958820ff-ec99-4aec-8df3-737d699e796e](https://musicbrainz.org/recording/958820ff-ec99-4aec-8df3-737d699e796e) so it is this recording (fa9…d72) which is the recording that received the AcoustID, which was then lost (from the MB view) during the merge into 958…96e.

---

<div class="post-metadata">

**Author:** ![jesus2099](https://community.metabrainz.org/user_avatar/community.metabrainz.org/jesus2099/32/36_2.png) [@jesus2099](https://community.metabrainz.org/u/jesus2099)\
**Post date:** [December 30, 2024, 7:30pm UTC](https://community.metabrainz.org/t/italic-acoustid/734798/5 "2024-12-30T19:30:57Z")

</div>

Oh thanks!!

I forgot I have a WIP modified version of @loujin’s [acoustid-merge-recordings.user.js](https://github.com/loujine/musicbrainz-scripts/pull/113) that resolves italic MBID into their merged title and artist…  
I have updated the OP.

**Merged recordings really lose their AcoustID, forever?**

This `fa9c940c-408b-41f0-b746-997e50e36d72` recording was merged into [958820ff-ec99-4aec-8df3-737d699e796e](https://musicbrainz.org/recording/958820ff-ec99-4aec-8df3-737d699e796e), already [more than two years ago](https://musicbrainz.org/edit/92853437).

---

<div class="post-metadata">

**Author:** ![agatzk](https://community.metabrainz.org/user_avatar/community.metabrainz.org/agatzk/32/44684_2.png) [@agatzk](https://community.metabrainz.org/u/agatzk)\
**Post date:** [December 30, 2024, 9:26pm UTC](https://community.metabrainz.org/t/italic-acoustid/734798/6 "2024-12-30T21:26:32Z")

</div>

> [@jesus2099](#):
>
> **Merging recordings really loses their AcoustID, forever?**

Unfortunately it seems this is the case, but it isn’t widely known as I’ve informed a number of regulars on some edits. The original question (as far as I know) was posed by @IvanDobsky in [Edit #95328271 - MusicBrainz](https://musicbrainz.org/edit/95328271). I’ve mentioned it in a few edits similar to [Edit #107685644 - MusicBrainz](https://musicbrainz.org/edit/107685644).

---

<div class="post-metadata">

**Author:** ![jesus2099](https://community.metabrainz.org/user_avatar/community.metabrainz.org/jesus2099/32/36_2.png) [@jesus2099](https://community.metabrainz.org/u/jesus2099)\
**Post date:** [December 31, 2024, 3:17am UTC](https://community.metabrainz.org/t/italic-acoustid/734798/7 "2024-12-31T03:17:57Z")

</div>

> <https://github.com/acoustid/acoustid-server/issues/114>
>
> 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

---

<div class="post-metadata">

**Author:** ![fmera](https://community.metabrainz.org/user_avatar/community.metabrainz.org/fmera/32/4492_2.png) [@fmera](https://community.metabrainz.org/u/fmera)\
**Post date:** [January 3, 2025, 8:25am UTC](https://community.metabrainz.org/t/italic-acoustid/734798/8 "2025-01-03T08:25:23Z")

</div>

it’s been an issue much further back than that; talk then that those in the source recordings would _eventually_ show up in the target has little evidence (afaict) to show for it. it’s why one should make sure the target in a recording merge has at least one (if not more, or fingerprint-comparable) common acoustid with the others, even if it might not be the one with the oldest mbid. also good practice imo to add the referenced acoustid(s) to your edit note, for future reference in recordings’ edit histories.

---

<div class="post-metadata">

**Author:** ![IvanDobsky](https://community.metabrainz.org/user_avatar/community.metabrainz.org/ivandobsky/32/11785_2.png) [@IvanDobsky](https://community.metabrainz.org/u/IvanDobsky)\
**Post date:** [January 3, 2025, 9:14am UTC](https://community.metabrainz.org/t/italic-acoustid/734798/9 "2025-01-03T09:14:43Z")

</div>

> [@fmera](#):
>
> it’s been an issue much further back than that;

I agree that this is a very old issue. I added my edit note as a test so I could literally track it from a live example. Many years before then I had been doing a number of merges using AcoustID as a guide and had a feeling there was an issue, but never traced it.

---

<div class="post-metadata">

**Author:** ![jesus2099](https://community.metabrainz.org/user_avatar/community.metabrainz.org/jesus2099/32/36_2.png) [@jesus2099](https://community.metabrainz.org/u/jesus2099)\
**Post date:** [January 3, 2025, 9:25am UTC](https://community.metabrainz.org/t/italic-acoustid/734798/10 "2025-01-03T09:25:31Z")

</div>

> [@fmera](#):
>
> those [AcoustID] in the [merge] source recordings would _eventually_ show up in the target has little evidence (afaict) to show for it.

In the beginning of AcoustID it was working, at least.

Now it feels like the supposedly nightly batch in charge of resolving MB merges (following MBID redirects and update AcoustID database accordingly) is either no longer running at all, or unable to go through all pending MBID. 😢

Wouldn’t it be nice to have a status on this long standing issue?

If AcoustID are just disappearing from MB sight, it makes them quite vain.

---

<div class="post-metadata">

**Author:** ![fmera](https://community.metabrainz.org/user_avatar/community.metabrainz.org/fmera/32/4492_2.png) [@fmera](https://community.metabrainz.org/u/fmera)\
**Post date:** [January 3, 2025, 6:16pm UTC](https://community.metabrainz.org/t/italic-acoustid/734798/11 "2025-01-03T18:16:42Z")

</div>

couldn’t find this post earlier, but yeah, since at least late 2017: [Acoustids not transferring to targets in recording merges](https://community.metabrainz.org/t/acoustids-not-transferring-to-targets-in-recording-merges/334528)

and to @jesus2099’s point, yes, acoustids used to be aggregated upon merges, irrespective of which target you picked.
