-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Subtitles are not found / selectable #30
Comments
I can see the subtitles being identified in the logs, so I'm not sure what's happening. I'll look into it now when I have available resources to do so. |
I have had a bit of time and hobbled together some resources to look into this. I don't know what happened from when it was working to now, but it basically looks like it was unsetting the proxy reference settings internally, so it wasn't keeping the configuration. I have identified that this is related to the calls made to |
I was able to get it to detect when I enabled the |
I think I found the issue. In the Class initialization, we set several values to show what type of agent this is. The For future personal reference, I determined this via the |
This should now be fixed in v0.1.2. Please download and confirm on your side. |
FWIW, I'm running the latest I verified that the VTT files are located on the same folders as the MP4 files. and they do appear (and work) on the Tube Archivist web interface player. Anything I can do here to help investigate? |
Can you provide the |
OK, it is only picking up the LocalMedia agent. Can you go to |
Can you select and then deselect the LocalMedia agent, restart Plex, then attempt to refresh the metadata? |
That made it work now! Thanks for your help -- I would have never guessed to try these steps... |
Glad to hear it is working now! |
I've read the documentation.
Operating System
Synology
Your Bug Report
Describe the bug
When using the tubearchivist-plex scanner & agent (v0.1.1), subtitles are not being found.
Steps To Reproduce
Expected behavior
Relevant log output
Anything else?
No response
The text was updated successfully, but these errors were encountered: