Server Version#: 1.29.0.6244
Player Version#: N/A
This has existed for some time.
Scenario setup:
- “Scan my library automatically” enabled
- “Run a partial scan when changes are detected” enabled
- “Empty trash automatically after every scan” disabled
- “Generate intro video markers” when media added
- Have a TV Library of media with multiple source directories defined.
\NAS1\TV
\NAS2\TV
Example full media path:
\NAS1\TV\ShowA\ShowA.e01e01.mkv
\NAS1\TV\ShowA\ShowA.e01e02.mkv
\NAS2\TV\ShowB\ShowB.s01e01.mkv
\NAS2\TV\ShowB\ShowB.s01e02.mkv
etc. - Library already has video intro markers detected for ShowA and ShowB, stored start/end within xml, visible per episode.
Trigger:
The undesired behavior I see is triggered simply by relocating ShowA from NAS1 to NAS2 (re-balancing volume capacity):
Move ShowA files from NAS1 to NAS2.
\NAS1\TV\ShowA\ShowA.e01e01.mkv → \NAS2\TV\ShowA\ShowA.e01e01.mkv
\NAS1\TV\ShowA\ShowA.e01e02.mkv → \NAS2\TV\ShowA\ShowA.e01e02.mkv
This action triggers a “Part Rename detected” in the server logs. While that’s technically correct, it was just the path that changed, not the filename itself. “Detection Intros” begins immediately which seems to be because it’s “newly added”. It’s chewing through PMS Data SSD layers for no valid reason as the episode already knew intro start/end. It’s the same file, just a new storage path within the same TV Library.
Anyone else notice this and wish it was handled better?
