What triggers recently added?

What’s the logic behind Recently Added? I have that Library section as a “button” on the home screen and there are movies appearing there that most definitely are not recently added.

I have Plex media server running on my nas mainly for the purpose of downloading subtitle files. Infuse can’t store subtitles next to the video file so I have to use plex since I have about 10 different clients accessing my video library and I don’t want to have to download subtitles from each of them …

My guess is that when Plex reindex and possibly update subs etc, Infuse thinks the video file stored in the same folder is new …
My guess is that the Recently Added logic is very rudimentary and only looks at folder update date or something, which would be weird sine it completely disregard folders in all other aspect - when fetching meta data for instance.

Anyhow if you could look into this it would be most appreciated.

For most share types, Infuse will use the creation date information to determine which videos are newest.

Unfortunately, we don’t have access to this info when streaming via UPnP or DLNA - so currently when streaming from Plex the recently added items will simply be the items that were indexed last by Infuse.

However, for Plex users this will be dramatically improved in 5.7 when we roll out our new native Plex integration.

Ok, but what triggers Infuse to index and does it even consider if it has indexed that movie before?
If I manually add an .srt file to a movie folder, does that make Infuse re-index and consider the movie file (.mkv) as a new “recently added” movie?
It’s a rethorical question because I know the answer! :slight_smile: It does and it would be great if it didnt! :slight_smile:

Infuse will typically scan for updates when the app is first opened.

If you are using UPnP/DLNA and you move or modify files, the server may reindex these which would effectively present them as new files to Infuse. In this case, Infuse would treat the flies as new because as far as Infuse knows it is in fact a new file.

You can avoid issues like this by connecting via SMB, NFS, or the new Plex integration that was included in 5.7.