mirror of
https://github.com/CCExtractor/ccextractor.git
synced 2026-02-16 21:23:35 +00:00
[BUG] or [QUESTION] : Hardsubx didn't extract burn-in subs exactly as expected #680
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 @brebetez on GitHub (Feb 1, 2022).
Originally assigned to: @shashwat1002 on GitHub.
Please prefix your issue with one of the following: [BUG], [QUESTION].
CCExtractor version: 0.94
CCExtractor detailed version info
Git commit:
290e2f10f9Compilation date: 2021-12-27
Libraries used by CCExtractor
Tesseract Version: 4.1.1
Leptonica Version: leptonica-1.79.0
libGPAC Version: 1.0.1
zlib: 1.2.11
utf8proc Version: 2.4.0
protobuf-c Version: 1.3.1
libpng Version: 1.6.37
FreeType
libhash
nuklear
libzvbi
In raising this issue, I confirm the following:
Necessary information
myVideo.mp4 -ocrlang fra -hardsubx -ocr_mode frame -subcolor white -min_sub_duration 0.01 -detect_italics -whiteness_thresh 97 -conf_thresh 75Video links
Additional information
{I have several issue:
I don't know if it is an issue or if I didn't use correctly the parameters, but as I said, I tried a lot of different ways...with all the time the same result. That is why, I'm opening an Issue.
Thanks for your feedback and help.}
@PunitLodha commented on GitHub (Jun 1, 2022):
Please share the videos, so that we could look into this issue
@shashwat1002 commented on GitHub (Jun 2, 2022):
On investigating, at least on the files I have there are subtitles extracted with duration less than a second.
So I guess the second point is not entirely general, either it has changed since the issue or it's an artefact of the files used.
@brebetez please consider sharing the file you used
cc: @PunitLodha
@cfsmp3 commented on GitHub (Dec 20, 2025):
@brebetez We do need a sample and exact instructions to reproduce the problem.
@cfsmp3 commented on GitHub (Jan 1, 2026):
Closing since we didn't hear back from @brebetez - @brebetez , feel free to reply if you still have problems.