So, I noticed this issue a while back and forgot about it for some time. However, the other night my wife tried to watch a couple of episodes of Chicago P.D. but they would not play.
I did some investigation today and here is what I found:
- When trying to play an episode of Chicago P.D. from the web interface the logs show:
2017/04/18 15:11:58 [HLS] Starting transcoder for file-825 at 0s (encoder=h264_videotoolbox, resolution=1080, deinterlacer=linear, bitrate=10000)
/Volumes/Channels-DVR/TV/Chicago P.D./2017-04-05-2159 Chicago P.D. 2017-04-05 S04E19 Last Minute Resistance.mpg: No such file or directory
2017/04/18 15:12:06 [HLS] Stopping transcoder session file-825 @ 0s
- On the NAS filesystem I see the directories for the episodes as:
Chicago P.D._DiskStation_Apr-05-2243-2017_TailCharacterConflict
Chicago P.D._DiskStation_Mar-21-1050-2017_TailCharacterConflict
Chicago P.D._DiskStation_Mar-22-2207-2017_TailCharacterConflict
Chicago P.D._DiskStation_Mar-29-2249-2017_TailCharacterConflict
** Note the recording in the directories appears to be normal
- Googling I found this:
If you have file or folder folder names containing a trailing dot, Synologyâs Cloud Station software will change your filenames to include âTailCharacterConflictâ, and, in my case, sync files wrongly. The same can happen when filenames or directory names have a trailing whitespace character.
** Which is exactly what I am seeing here.
Itâs worth noting that Chicago P.D. is not the only issue here. It also happens with Marvelâs Agents of S.H.I.E.L.D.
So, the question is, can the DVR preemptively construct a storage directory name that does not cause this condition? (i.e.; does not end in a trailing â.â or â ')