dan-online
commented
22 hours ago So here's kinda why I decided to not take that direction with autopulse. My major issue with autoscan was that it didn't refresh files, so a transcoded file wouldn't update and would have incorrect media information. Sending a scan to a directory like autoscan does, doesn't really do much (only checking for a new file). autopulse only sends a scan as a fallback if it can't find the "Item" attributed to the file, which would let it run an analyze or refresh command on.
However, if you're okay with not having an analyze/refresh then I could add an option to use the directory path at the trigger level so it will always fallback on the scan. Otherwise I'd have to do maybe some sort of recursive method to find every item under that directory and send an analyze/refresh to, however to me that seems like a waste of resources if the only files that actually changed is 1 or 2
mvanbaak
Description
One reason why I started using autoscan (and now want to move to autopulse as its actually maintained) is that it groups updates to a movie/season directory instead of handling multiple updates, each for every file etc. When sonarr imports a new episode, autopulse should store and handle a scan event for the directory where the episode file was imported to, and not for the whole file. This will make updates sent from other tools, touching the same path, group able with the initial sonarr update.
I'm not sure if I manage to explain what I mean, I'll leave a screenshot in the Additional Information.
Additional Information
In my ideal world, all these updates would be grouped into 1 scan event, for the Season02 directory, like the top most record.