Server Version#: 1.19.1.2645
Player Version#: 4.32.1
Running Plex on a Synology DiskStation NAS.
I am at my wit’s end with subtitles. I have 2 separate issues. #1 Plex won’t search of or download English subtitles from opensubtitles. I have read thru all the instructions from Plex, plus some in other forum threads & posts elsewhere, I have everything set exactly as it’s supposed to be set, but it simply doesn’t work.
#2 in my main/original movie folder Plex will not recognize subtitle files I add to the folder. Here again all my settings are correct and I’ve checked & tried all the directions including several force refreshes with no luck. The only solution I didn’t try was removing everything from my folder & starting over, since I have almost 800 films and the loss of custom posters, collection tags, etc would be huge.
I DID make a second movies library & folder as a test, and files I put in THAT library/folder DO correctly read subtitle files I download myself and add, so I know my settings are correct. But I can’t get my main folder to refresh/accept it for some reason. (I did have to reorder my agents.) If no one can help me figure out how to get my main library to accept it I’ll just put anything I have to add a sub to in that library, but it’s not ideal.
However, that file still will NOT download subs for me. I have tried it both with & without my opensubs login creds entered, and made sure all the settings are perfect, but no luck.
Already did all of that. Like I said, everything works in the NEW Library I created, I just can’t get them to work in the ORIGINAL library. See here, it works in movies2 but not movies. And yes, after I moved Local Assets to the top (per the directions) I rescanned AND did a total meta refresh. More than once.
As I said, my concern it’s what’s described here Subtitles not working - RESOLVED where you do everything right BUT it still won’t work until you reload everything. Which loses my tags, collections, etc.
Also, any clue on the whole “won’t download subtitles” thing?
Yeah, you shouldn’t have to go as far as the post you referenced.
And your naming is spot on. A lot of people’s naming is not.
Let’s try this: Plex Dance one movie and gather logs.
Set your system for debug logs only (Settings -> General -> Show Advanced). Do not enable verbose logs. Verbose captures too much info and wraps too quickly (and is much harder to read).
Pick one movie that doesn’t work and Plex Dance it. Move everything associated with the movie - subtitles, extras, etc. This will lose any custom collections, artwork, etc, so pick one where it won’t hurt too much.
Did Plex recognize the movie and the subtitles?
After you put the movie back and all the scanning and metadata downloading is complete wait one more minute for everything to get logged, then pull the log files. Settings -> Manage -> Troubleshooting. Attach the entire zip file to the thread.
I’m hoping the logs will show something.
I’m not sure what else to try. If the two libraries are configured exactly the same the files should work in either one. The logs should show what is happening.
Thanks for your patience.
Also, not sure why downloads from opensubtitles.org are not working. Noticed a couple of other posts from others on same subject. I configured it on my PMS and not working for me either.
FYI, Local Media Assets doesn’t have to be at the top. It just has to be enabled in both Movies/Plex Movie and Movies/The Movie Database in Agents config. Putting it at the top can cause issues with MP4 files as Plex will look to the metadata in the MP4 before matching with any external sources.
Ok, there WAS actually a naming issue with the file I used as an example (I left an “l” out), BUT that wasn’t the whole issue as it was also happening with other files.
However, I got a notification for a Plex server update and once I ran the update everything started to work.
The only issue I found is that it looks like if I have OpenSubtitles enabled it overrides uploaded subs, and sometimes the ones that Plex picks are off & I have to fidget like heck with the adjustments.
Regardless, thanks for the help but running the update seems to have fixed it. (My only guess is it forced a database refresh,)