Server Version#: 1.28.2.6151-914ddd2b3
Player Version#: (All… macOS, tvOS, iOS, Amazon Firestick)
Nothing to log really… I have been seeing file names corrupted after upload. All players see it. On the server, you can sometimes see the file name has been actually changed (FileNameRegular → WBEGF~1, etc.).
Do a search on the odd file name and it’s not physically on the server but the original file is. Delete it, force library scan, wait for it to go away, add it back in, scan again, comes back with the bad info.
Sounds like you have enabled the prefer local metadata option and got some files with very bad embedded metadata… it’s not necessarily corrupted; just somebody decided to put that garbage into the files.
You are blurring out the file path but that shows that the underlying file has the same name. If you provided the full path (you can censer C:\Users\<UserID> ) it might help
So please share more details here, since what I could digest from the VERY LIMITED INFO YOU PROVIDED is that you access a share on a NAS, and it presents it’s filenames as windows short names (8.3)
I did find 1 instance like that (local metadata) and changed it back. Thanks.
Yes it’s a NAS. No it’s not an 8.3 Windows file name. It (DSM) supports long file names as well as text cases and (some) special characters.
The path is nothing but s:/[shared path]/filename in the Plex edit screen. If you search the NAS for that file name, sometimes (rarely) it really has been changed to that but usually you just can’t find it because the original name is still out there. BUT if you hit play on the mixed-up file “poster” in Plex, it still plays. So even though nothing in the Plex Edit screens reflect the real file name, clearly Plex has it mapped to the original file in some way.
How exactly are you sharing your media from the Syno? The problem dane22 had described is not limited to 8.3 Windows/DOS based file systems but can impact certain file transfer protocols if the two endpoints fail to communicate properly.
I suppose it’s not Plex that’s mismatching your file names but that’s how they show up on your server’s host system?
Interesting question and I’ll admit to being a little vague on xfer protocols in use. NAS is a Synology, running DSM (current). Server is Wintel (Win10) and maps a drive to the NAS.
I know the NAS shows the Plex server connection using Samba (SMB2).
It’s been running like this for years (drive upgrades IAW Syn’s approved list along the way) and this is a recent issue. I first thought it was an issue with something on the cusp of failing (drive of the NAS controller itself). All drives pass deep deep SMART tests as well as a monthly “data scrub” within Syn scheduler. All logs and stats show healthy drives at normal op temps.
So I came here when I saw nothing seemed to be changing the file name itself but some way the Plex plugged in an odd name while some way keeping a connection that played the un-renamed file.
As mentioned somewhere above, the direct file (file expolrer) USUALLY looks normal. On rare occasions the target file name has also been renamed… say 1 in 20.
