Prevent updated media from showing up as new again

[rawlwear]

Evening,

 Is there a way for Jellyfin to ignore media that's already been created in its database from showing up again like new if the media file gets changed? With sonarr radarr etc updating quality of media I don't want it showing as new files added when its already in my library and only the quality changed.

Thanks to whom replies.

[Efficient_Good_5784]

Jellyfin uses absolute paths. As long as the filenames all remain the same, maybe you'll achieve what you want.
Jellyfin doesn't provide support for those applications however. You'll have to figure out how to get them to work for Jellyfin.

Also, please read the forum rules regarding this topic for future reference: https://forum.jellyfin.org/t-jellyfin-forum-rules

[koenlol]

This was bothering me too. I found a solution that has been working well for me, and I figured I'd post it in case someone comes across this thread looking for an answer like I did.

I configured Jellyfin to use file creation date in the 'Date added behavior for new content' setting. Then, I set up a custom script that:

• On 'Grab' looks for existing versions of the media in the library folders. If found, it extracts the file's creation date and saves it to a temporary file.
  
• On 'Import'/'Upgrade' changes the newly imported file's creation date to match the original, and deletes the temporary file.
  
• Triggers a Jellyfin library rescan after importing if an API key is provided.
  
  

I'll share the script I've been using, but be warned, it's AI-generated: https://pastebin.com/jem4Yf6B
You'll need to change the variables at the top of the script. After that, set it to run on 'Grab' and 'Upgrade' events in Radarr/Sonarr (Settings > Connect > Custom Script).

It's been working well on my server (ubuntu), but I don't know how it will work in other environments. I think the way your folder structure and naming schemes are set up is important. A log file should be created next to the script that might help with trouble-shooting.

[randomdude]

This was bothering me too. I found a solution that has been working well for me, and I figured I'd post it in case someone comes across this thread looking for an answer like I did.

I configured Jellyfin to use file creation date in the 'Date added behavior for new content' setting. Then, I set up a custom script that:

• On 'Grab' looks for existing versions of the media in the library folders. If found, it extracts the file's creation date and saves it to a temporary file.
  
• On 'Import'/'Upgrade' changes the newly imported file's creation date to match the original, and deletes the temporary file.
  
• Triggers a Jellyfin library rescan after importing if an API key is provided.
  
  

I'll share the script I've been using, but be warned, it's AI-generated: https://pastebin.com/jem4Yf6B
You'll need to change the variables at the top of the script. After that, set it to run on 'Grab' and 'Upgrade' events in Radarr/Sonarr (Settings > Connect > Custom Script).

It's been working well on my server (ubuntu), but I don't know how it will work in other environments. I think the way your folder structure and naming schemes are set up is important. A log file should be created next to the script that might help with trouble-shooting.

I think I've found a way to make this work easier. If you enable the .nfo saver for the library, Jellyfin will save all of the metadata alongside the media file. Then for 'Date added behavior for new content', select 'Use date scanned into library'.
It will then use the created date of the .nfo file, which will persist across upgrades.