[PR #14716] feat: add option to require file size change for media refreshes #14077

Open
opened 2026-02-07 07:24:02 +03:00 by OVERLORD · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/jellyfin/jellyfin/pull/14716
Author: @tam1m
Created: 8/28/2025
Status: 🔄 Open

Base: masterHead: feature/file-change-setting


📝 Commits (1)

  • 95b35af feat: add option to require file size change for media refreshes

📊 Changes

3 files changed (+22 additions, -3 deletions)

View changed files

📝 MediaBrowser.Controller/Extensions/ConfigurationExtensions.cs (+5 -0)
📝 MediaBrowser.Model/Configuration/ServerConfiguration.cs (+5 -0)
📝 MediaBrowser.Providers/MediaInfo/ProbeProvider.cs (+12 -3)

📄 Description

This adds new system setting FileChangeRequireSizeChange that allows users to control how Jellyfin detects changes in media files. When enabled, the server will require both the modification time and the file size to have changed before triggering a metadata refresh.

This is based on the discussions in #13839 and #14674 and makes the behavior reintroduced in #14674 configurable.

With #14674, Jellyfin only checks the modification time of a file to determine if it has changed, which can lead to unnecessary metadata refreshes when a file's timestamp is updated without any actual change to its content. This is problematic for users with remote filesystems that may not provide stable timestamps, aswell as just copying files around without changing anything.

I do recognize that this feels a bit hacky and would be fixed properly by hashing the files instead of relying on their timestsamps and size, but it's worth it in my opinion as this workaroud will prevent a lot of unnecessary rescans and especially uninented trickplay regeneration for a lot of users.


🔄 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/14716 **Author:** [@tam1m](https://github.com/tam1m) **Created:** 8/28/2025 **Status:** 🔄 Open **Base:** `master` ← **Head:** `feature/file-change-setting` --- ### 📝 Commits (1) - [`95b35af`](https://github.com/jellyfin/jellyfin/commit/95b35afb6b9c5bfde6f8c76bd3459590a235ee6b) feat: add option to require file size change for media refreshes ### 📊 Changes **3 files changed** (+22 additions, -3 deletions) <details> <summary>View changed files</summary> 📝 `MediaBrowser.Controller/Extensions/ConfigurationExtensions.cs` (+5 -0) 📝 `MediaBrowser.Model/Configuration/ServerConfiguration.cs` (+5 -0) 📝 `MediaBrowser.Providers/MediaInfo/ProbeProvider.cs` (+12 -3) </details> ### 📄 Description This adds new system setting `FileChangeRequireSizeChange` that allows users to control how Jellyfin detects changes in media files. When enabled, the server will require both the modification time and the file size to have changed before triggering a metadata refresh. This is based on the discussions in #13839 and #14674 and makes the behavior reintroduced in #14674 configurable. With #14674, Jellyfin only checks the modification time of a file to determine if it has changed, which can lead to unnecessary metadata refreshes when a file's timestamp is updated without any actual change to its content. This is problematic for users with remote filesystems that may not provide stable timestamps, aswell as just copying files around without changing anything. I do recognize that this feels a bit hacky and would be fixed properly by hashing the files instead of relying on their timestsamps and size, but it's worth it in my opinion as this workaroud will prevent a lot of unnecessary rescans and especially uninented trickplay regeneration for a lot of users. --- <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:24:02 +03:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/jellyfin#14077