[PR #12173] [MERGED] Add support for reading and storing Recording MBIDs from file metadata #12925

New issue

Closed

opened 2025-12-22 09:34:19 +01:00 by backuprepo · 0 comments

backuprepo commented

2025-12-22 09:34:19 +01:00

Owner

📋 Pull Request Information

Original PR: https://github.com/jellyfin/jellyfin/pull/12173
Author: @lyarenei
Created: 6/25/2024
Status: ✅ Merged
Merged: 3/1/2025
Merged by: @crobibero

Base: master ← Head: recording-mbid-support

📝 Commits (10+)

ef67ca2 Add recording metadata provider
1a983fd Add recording MBID
014182c Save recording MBID during probing
9dd18c8 Set recording ID in probe result normalizer
4d949d5 Add recording external media type
15410d1 Reimplement after changes in upstream
482b4a9 Rename variable
6366088 Rename variable
9a5b5f8 Revert "Set recording ID in probe result normalizer"
f891021 Fix setting provider ID

📊 Changes

4 files changed (+58 additions, -2 deletions)

View changed files

📝 MediaBrowser.Model/Entities/MetadataProvider.cs (+6 -1)
📝 MediaBrowser.Model/Providers/ExternalIdMediaType.cs (+6 -1)
📝 MediaBrowser.Providers/MediaInfo/AudioFileProber.cs (+19 -0)
➕ MediaBrowser.Providers/Plugins/MusicBrainz/MusicBrainzRecordingId.cs (+27 -0)

📄 Description

Changes

Add support for reading and storing MusicBrainz Recording IDs if they are present in the file metadata.

Issues

I'm not aware of any. It'll make the recording MBID conveniently accessible within Jellyfin (and editable from Jellyfin UI).

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/jellyfin/jellyfin/pull/12173 **Author:** [@lyarenei](https://github.com/lyarenei) **Created:** 6/25/2024 **Status:** ✅ Merged **Merged:** 3/1/2025 **Merged by:** [@crobibero](https://github.com/crobibero) **Base:** `master` ← **Head:** `recording-mbid-support` --- ### 📝 Commits (10+) - [`ef67ca2`](https://github.com/jellyfin/jellyfin/commit/ef67ca2abe15b82f3669f9af6e5b7a945b216633) Add recording metadata provider - [`1a983fd`](https://github.com/jellyfin/jellyfin/commit/1a983fdc9069ee400311e32a3193d00b12258e34) Add recording MBID - [`014182c`](https://github.com/jellyfin/jellyfin/commit/014182c162a4f7a292dd616af218928e213a9b24) Save recording MBID during probing - [`9dd18c8`](https://github.com/jellyfin/jellyfin/commit/9dd18c8aba3f970a5816a13a33acf3d58b0e440f) Set recording ID in probe result normalizer - [`4d949d5`](https://github.com/jellyfin/jellyfin/commit/4d949d588dcb228a51732af64423729c7711f586) Add recording external media type - [`15410d1`](https://github.com/jellyfin/jellyfin/commit/15410d1255d8951449f90cf89ddcc342c66f0ded) Reimplement after changes in upstream - [`482b4a9`](https://github.com/jellyfin/jellyfin/commit/482b4a96a8c070052841dbeda155fdb982498e32) Rename variable - [`6366088`](https://github.com/jellyfin/jellyfin/commit/6366088e5949878e56c6183209b90f4083e45f43) Rename variable - [`9a5b5f8`](https://github.com/jellyfin/jellyfin/commit/9a5b5f81e779765ebb8accfd285131a1e9eb01f2) Revert "Set recording ID in probe result normalizer" - [`f891021`](https://github.com/jellyfin/jellyfin/commit/f8910217482ff242a59d869c5d7d66a1b606ff30) Fix setting provider ID ### 📊 Changes **4 files changed** (+58 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `MediaBrowser.Model/Entities/MetadataProvider.cs` (+6 -1) 📝 `MediaBrowser.Model/Providers/ExternalIdMediaType.cs` (+6 -1) 📝 `MediaBrowser.Providers/MediaInfo/AudioFileProber.cs` (+19 -0) ➕ `MediaBrowser.Providers/Plugins/MusicBrainz/MusicBrainzRecordingId.cs` (+27 -0) </details> ### 📄 Description **Changes** Add support for reading and storing MusicBrainz Recording IDs if they are present in the file metadata. <img width="882" alt="image" src="https://github.com/jellyfin/jellyfin/assets/26324629/272ffa0b-c858-405a-97ac-a5d603cc1ee5"> **Issues** I'm not aware of any. It'll make the recording MBID conveniently accessible within Jellyfin (and editable from Jellyfin UI). --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>