-
-
Notifications
You must be signed in to change notification settings - Fork 20
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
PAL can't differentiate SDH and regular subtitle #106
Comments
Sadly it's not as simple as just looking at that attribute, as I was looking in the xml for some of my videos that have both |
the bad quality of subs out there should not prevent the good subs to be chosen. |
I think I agree with @gotson, looking at some of my shows XML data in Plex, Plex seems to include the I understand that maybe just looking for |
Did a little digging and I think the model plexapi.media.SubtitleStream we use in the code already offers the boolean member Similar how the code already uses the
|
Hopefully fixes RemiRigal#106
I just pushed up the change noted by @dekaidekai, so hopefully it'll work. can test by either pulling |
@JourneyOver Thanks for the quick patch 🙇 Is there any setup steps different required for your image as opposed to The image
Here's my setup:
I don't mount any |
@dekaidekai You don't need to exactly mount the config.yaml file, just the folder like you are already.. The whole data_path thing comes from this PR #89 (tbh I might revert this pr on my side though xD) It should be setting a data directory by default if one is not provided, so I'm not sure why it didn't for you but you should be able to pass the values regardless either way through the env variables but I might need to recheck all that again to make sure it's all actually working as expected. |
So I'm a moron @dekaidekai and accidentally left the data_path bit commented out when I was messing with the default.yaml file in a recent commit. That was my mistake and it should hopefully now be rectified and fixed. so feel free to test again! |
@JourneyOver You are not a moron at all 😎 thanks again for the quick replies and fixes! |
hehe it's not a problem :P Sounds good, lemme know how testing goes when you get to it so I can know if the actual main issue is fixed or not @dekaidekai :) (even if technically I won't be able to close this issue) also wish I could find fixes for some of the other issues that have been cropping up in this repo, but I sadly haven't experienced/ran into any of the ones that some people seem to be running into >.< |
@JourneyOver I have tested the Thank you so much for the patch and your hard work 🙏 |
@dekaidekai Glad to hear! and it's not a problem, Always down to try to fix something if I can, though I do have to thank you for the code as well as you are the one who posted mostly about it above :P Guess we can officially call this issue closed. @gotson Feel free to close this issue if it ends up working for you as well (if you ever read this and check it out), otherwise I guess this will remain open even though a fix is now out unless @RemiRigal decides to randomly show up and close this xD Edit: I have now officially made a new release as well (starting with version 1.3.0 since the last technical release from at least Remi was 1.2.3 and I never changed any versioning between then and now until this release). So now we have three tags for pulling from right now |
@JourneyOver Awesome thanks again! Actually doing a little more testing and I think I see some other issues, but these might be unrelated due to other things like caching (specifically the I'll be fooling around trying to make fixes for these and I might post my findings later in another issue! |
@dekaidekai sounds good, if you do just go ahead and ping me as your help in getting fixes out (especially for things I don't run into myself) is greatly appreciated. |
@JourneyOver You are a saint thank you 🙇 The new issue I found I posted here! #109 |
@dekaidekai Hmm so we need to come up with a different method for this I think, as currently what seems to be happening is that if anything is added that actually had SDH subtitles, it automatically gets forced to use those subtitles when the content gets added in and scanned just like "forced" has always done. idk if it's due to scoring or something else but I'm trying to figure it out fully and get a solution out. |
@JourneyOver Thanks for testing this out! I think then it would maybe be due to the scoring, do we know what we want for the intended behaviour? To make it pick I can take a look at the code and investigate! |
This is another issue I might have found unrelated, but if you set the subtitles to new issue tracked here! |
I think the way things should be was how it was before in a sense: If there is a If user has an SDH subtitle do not automatically select it even on initial scans and such unless the user has specified gone in and set it to be selected even if it is the only subtitle. (e.g: if user has two subs for a video one SDH and one non-SDH and user selects the non-SDH then it should go through only set the videos that has the non-SDH while leaving the rest off, if user only has one sub and it's SDH do not automatically set it and just leave it off unless the user has gone in and selected it himself) Currently from my testing where I have a video that only has one subtitle and it's SDH, it's automatically setting said subtitle to SDH even if I go in and reset the subtitle back to |
I've gone ahead and moved this issue over to my own repo as well. |
Hi ! i tried with What's the relationship between that image and |
The main difference is that Remi is no longer maintaining this repository, so there haven’t been any updates to his image. In contrast, my fork, is actively maintained, includes fixes (like one that corresponds to this issue), and is kept up to date. Essentially, I’ve taken over the project in a fork and am working on addressing issues and trying to implement fixes as they arise. If you’re okay using an outdated image without recent fixes or updates (and it’s unlikely that Remi will return to maintain the project), you can stick with |
thanks for the details. I don't know if you managed to get in touch with Remi, but maybe he could add you as a maintainer of the project ? Or somehow update the readme to say this is not maintained. I switched to your fork :) |
i have a show where there are 2 english subs: English and English SDH. When i select English, PAL sets English SDH for the whole show.
Here is what the XML contains:
It seems one has
hearingImpaired="1"
, which should be sufficient for PAL to use the other one, and not only match onlanguageTag
.The text was updated successfully, but these errors were encountered: