mirror of
https://github.com/CCExtractor/ccextractor.git
synced 2026-04-25 15:40:02 +00:00
Corrupted SRT Text Output from HDHomeRun Prime Stream #111
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 @cyburgee on GitHub (Feb 2, 2016).
Hello,
I'm writing to investigate an issue where the SRT output of CCExtractor displays garbled text when run on particular video output from an HDHomeRun Prime. I seem to be getting extra "X"s, "@"s, and "■"s. This happens on the output of some channels, however most seem to work just fine. Also, VLC is able to display the subtitles without the extraneous characters.
Here's the SRT output: https://www.dropbox.com/s/lphfdzzkyrj05f9/captions_default.srt?dl=0
and the video file: https://www.dropbox.com/s/am93sn9i4x084tl/ad3ef288-fc07-4405-8670-5d13aa6a5eaf.ts?dl=0
Here's the output with the CEA-608 debug information:
I get the same output when CCExtractor is running in stream mode or otherwise.
Are there any command line options or anything else that I'm missing? Let me know and I can share any other information or debug output with you.
Thanks,
Collin
@canihavesomecoffee commented on GitHub (Feb 2, 2016):
Hello,
could you please try it on 0.79? 0.78 was a rather buggy version unfortunately, and 0.79 fixed most of the introduced errors. That way we can determine if it's the version, of if it's a more persistent issue.
@cyburgee commented on GitHub (Feb 2, 2016):
Thanks for the quick reply. I just tried it on 0.79 and the output appears unchanged. Would you like me to attach the debug output from the newer version?
@canihavesomecoffee commented on GitHub (Feb 2, 2016):
That would be nice.
@cyburgee commented on GitHub (Feb 2, 2016):
Here's the CEA-608 debug from 0.79:
@canihavesomecoffee commented on GitHub (Feb 2, 2016):
Thanks. Did you run any < .78 versions with similar videos that did not produce any errors? That might give us additional clues if it's been introduced more recently, or if it's an older bug.
I've tested it on my Windows version, and I can confirm the bug.
@cyburgee commented on GitHub (Feb 2, 2016):
I haven't used ccextractor prior to version .78. If you'd like I can try. Do you have an idea of what which version I should start with?
@canihavesomecoffee commented on GitHub (Feb 2, 2016):
Hello,
It's no problem if you didn't. I have some tools which will allow me to test rather fast, so it's no problem if you can't 👍
@canihavesomecoffee commented on GitHub (Feb 3, 2016):
Small follow up: I've most likely pinned down the issue to a commit that was made between .69 and .70, and It'll be looked at.
@cyburgee commented on GitHub (Feb 3, 2016):
Awesome. Thanks a lot.
@cyburgee commented on GitHub (Feb 19, 2016):
Hello,
Just wanted to check in on this.
Has there been any progress on this issue or are there any plans to make some?
Thanks,
Collin