starred/jellyfin
1
0
Fork 0
mirror of https://github.com/jellyfin/jellyfin.git synced 2026-05-04 18:09:12 +03:00
Code Issues 822 Packages Projects Releases 10 Wiki Activity

[PR #16103] Add PreferOriginalReleaseDate option for music #14526

New Issue
Open
opened 2026-02-07 07:31:12 +03:00 by OVERLORD · 0 comments
OVERLORD commented 2026-02-07 07:31:12 +03:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/jellyfin/jellyfin/pull/16103
Author: @arminius-smh
Created: 1/25/2026
Status: 🔄 Open

Base: master ← Head: music-release-date

📝 Commits (1)

  • 686a568 Add PreferOriginalReleaseDate option for Music

📊 Changes

2 files changed (+38 additions, -13 deletions)

View changed files

📝 MediaBrowser.Model/Configuration/LibraryOptions.cs (+4 -0)
📝 MediaBrowser.Providers/MediaInfo/AudioFileProber.cs (+34 -13)

📄 Description

Changes

Jellyfin right now uses only track.Date, which is trying to mainly use the recording date for the metadata: 5b19662004/ATL/Entities/MetadataHolder.cs (L130).

My changes tries to get the actual original release date: 5b19662004/ATL/Entities/MetadataHolder.cs (L222)
or the publishing date: 5b19662004/ATL/Entities/MetadataHolder.cs (L262) before then trying the normal date at the end again

It also sets the production year from the premierdate, since that is also done for albums but is kept as a last fallback as well.

So I believe overall no metadata should get lost, only the earlier dates filled for the production

Issues

The issue is that if releases have specific version info tagged, jellyfin tries to use that instead of the original date, its mostly a non issue for newer music, where there is the digital release and thats it, but especially for older music with different versions that may be released much later than the original release, it leads to these issues:

Before (basically random numbers of when the specific issue was released, which leads to odd sortings):
image

After (original release dates):
image

🔄 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/16103 **Author:** [@arminius-smh](https://github.com/arminius-smh) **Created:** 1/25/2026 **Status:** 🔄 Open **Base:** `master` ← **Head:** `music-release-date` --- ### 📝 Commits (1) - [`686a568`](https://github.com/jellyfin/jellyfin/commit/686a568f6115235b79b3c6a775e7c464a106c9a8) Add PreferOriginalReleaseDate option for Music ### 📊 Changes **2 files changed** (+38 additions, -13 deletions) <details> <summary>View changed files</summary> 📝 `MediaBrowser.Model/Configuration/LibraryOptions.cs` (+4 -0) 📝 `MediaBrowser.Providers/MediaInfo/AudioFileProber.cs` (+34 -13) </details> ### 📄 Description <!-- Ensure your title is short, descriptive, and in the imperative mood (Fix X, Change Y, instead of Fixed X, Changed Y). For a good inspiration of what to write in commit messages and PRs please review https://chris.beams.io/posts/git-commit/ and our documentation. --> **Changes** <!-- Describe your changes here in 1-5 sentences. --> Jellyfin right now uses only `track.Date`, which is trying to mainly use the recording date for the metadata: https://github.com/Zeugma440/atldotnet/blob/5b1966200449df6d3cb8d2208b9adfeaad5e69ef/ATL/Entities/MetadataHolder.cs#L130. My changes tries to get the actual original release date: https://github.com/Zeugma440/atldotnet/blob/5b1966200449df6d3cb8d2208b9adfeaad5e69ef/ATL/Entities/MetadataHolder.cs#L222 or the publishing date: https://github.com/Zeugma440/atldotnet/blob/5b1966200449df6d3cb8d2208b9adfeaad5e69ef/ATL/Entities/MetadataHolder.cs#L262 before then trying the normal date at the end again It also sets the production year from the premierdate, since that is also done for albums but is kept as a last fallback as well. So I believe overall no metadata should get lost, only the earlier dates filled for the production **Issues** <!-- Tag any issues that this PR solves here. ex. Fixes # --> The issue is that if releases have specific version info tagged, jellyfin tries to use that instead of the original date, its mostly a non issue for newer music, where there is the digital release and thats it, but especially for older music with different versions that may be released much later than the original release, it leads to these issues: Before (basically random numbers of when the specific issue was released, which leads to odd sortings): <img width="2164" height="1130" alt="image" src="https://github.com/user-attachments/assets/aaeb4d3f-1b76-41c3-b56d-be797d4ff7ec" /> After (original release dates): <img width="995" height="539" alt="image" src="https://github.com/user-attachments/assets/8518892e-14aa-4556-b0c9-be09d2f0ba19" /> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
OVERLORD added the pull-request label 2026-02-07 07:31:12 +03:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
EFjellyfin.db
area:database
awaiting-feedback
backend
blocked
breaking change: web api
bug
build
ci
confirmed
discussion needed
dotnet future
downstream
duplicate
enhancement
feature
future
github-actions
good first issue
hdr
help wanted
invalid
investigation
librarydb
live-tv
lyrics
media playback
music
needs testing
nuget
performance
platform
pull-request
Mirrored from GitHub Pull Request
 question
regression
release critical
requires-web
roadmap
security
security
stale
support
syncplay
ui & ux
upstream
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/jellyfin#14526
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?