It seems the intro detection feature is at the very least time intensive and potentially resource intensive?
It would make sense that it is only done once.
As mentioned here there a a few things that trigger it that could be prevented.
Some suggestion are keeping a record of the file hash in the database may be enough to save redoing.
I’m currently about to move my media to a new storage volume so I can sperate its snapshot and backup plan and schedule.
Would be great to see this implemented. I’ve had to turn intro detection off as I use cloud storage. It can be a bit iffy at times and shows/movies are redownloaded which triggers intro detection.
Seriously - something needs to be done about this Credit/Intro detection as turns into a processing nightmare for people with large media collections that move files around.
I just finished adjusting file paths within my Library and… Boom - here we go with scanning all my files again for like the 5 or 6 time.
Is there a reason why the Credit/Intro detection isn’t storing this in metadata to avoid constant re-scans of the same media files?
Yup, I just encountered this issue and found this thread. I migrated my plex server and meta data from a windows server to a linux docker server. I migrated the 22gb meta data library to the new server but the media is all still on the same nas drive. Once I remapped the library folders, it started re-detecting intros on 12 terabytes of media. 26 hours later it’s still grinding away!
Same issue here. Migrated plex meta data along with cash and rescan of intros kicked in. Would expect this wouldn’t be necessary. Would gladly see a more handsome resolution to the case.
I would love to see this implemented. I have a couple big library moves in my future planned out and intro/credits detection is pretty much one of the longer steps in the library migration process. Other than read/write speeds on the HDDs. It’ll be the same media in a similar folder structure, following the library migration process exactly as per Plex instructions, but will still trigger intro and credit detection. I feel like it could be much smarter than that, especially for such an intensive and time consuming process.
In the other linked thread, you mentioned an engineer was working on this (3/2023). Do you know if this is still a planned feature? Even a “I’m just migrating my data, I promise I’m not making any changes to the files themselves” manual hack would be great. Editing the database directly isn’t a great workaround for me as I’m making quite a few changes to the naming scheme (adding more info about the files to the filenames as some guides recommend).
So i have a large library and sometimes i might need to move some files about, or data loss that then gets re-added to plex, bulk file renames etc. Plex then needs to rescan everything even though the actual files are identical. Could something be put in place like hash values to prevent having to rescan these files.
