mirror of
https://github.com/CCExtractor/ccextractor.git
synced 2026-02-13 13:35:37 +00:00
[BUG] dvb subtitles with depth 2 get wrong colors #435
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @atrottmann on GitHub (May 30, 2018).
Please prefix your issue with one of the following: [BUG], [PROPOSAL], [QUESTION].
CCExtractor version (using the --version parameter preferably) : 0.87
Git commit:
52707267fcIn raising this issue, I confirm the following (please check boxes, eg [X] - and delete unchecked ones):
My familiarity with the project is as follows (check one, eg [X] - and delete unchecked ones):
Necessary information
**Video links (replace text below with your links) **
original video: https://gfguardian.werft22.net/public/dvbsub-issue/dvbsub.ts
correct subtitle image: https://guardian.werft22.net/public/dvbsub-issue/sub-correct.png
incorrect subtitle image: https://guardian.werft22.net/public/dvbsub-issue/sub-incorrect.png
Additional information
When I use ccextractor to convert video with dvb subtitles of depth 2 into spupng format, the colors are very wrong: in this example, I get red text with yellow outlines on a green background, even though it should be black text with bright yellow outline on a dark yellow background.
Apparently, the bug is in /src/lib_ccx/dvb_subtitle_decoder.c in the switch statement starting line 1595: The case for a depth of 2 is handled, but then falls through to case 8.
Inserting a "break" before the "case 8" fixes the problem for me.
@thealphadollar commented on GitHub (May 30, 2018):
Hey @atrottmann, it's amazing that you have found the solution to your
problem. That's a hacker spirit there :D
You can anytime send a PR with the required changes, and it'll be reviewed
and merged if need be.
@atrottmann commented on GitHub (May 31, 2018):
Ok, that's now done as pull request #987 - thank you very much!
@cfsmp3 commented on GitHub (Sep 20, 2018):
Closing since it was fixed ages ago. Thanks @atrottmann !