mirror of
https://github.com/CCExtractor/ccextractor.git
synced 2026-02-03 21:23:48 +00:00
MPEG2 Transport streams no longer processed #106
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 @workflowsguy on GitHub (Jan 30, 2016).
When trying to open MPEG2 Transport stream files, ccextractor now fails with "Unable to open" & error code 6.
By comparison, telxcc has no problem extracting teletext subtitles from such a file.
CCExtractor 0.78 CLI installed on OS X through Homebrew.
@canihavesomecoffee commented on GitHub (Jan 30, 2016):
Hello,
could you try running
.80.79, which is the latest version released a week ago?@workflowsguy commented on GitHub (Jan 30, 2016):
I do not know how to build ccextractor, so I will have to wait until the version becomes available through Homebrew on the Mac. Then I can try it out.
@canihavesomecoffee commented on GitHub (Jan 31, 2016):
I don't own a mac myself, but from what I see in the mac folder of the repository, all you need to do is perform these steps:
cd ~/Downloads/ccextractor0.79/mac)./build.command)If all goes well and there are no errors, you should have a ccextractor executable in the same folder. If an error occurs, it would be nice if you could open a new issue for this, so we can update the mac build command (as @cfsmp3 noted, none of us contributors owns a mac, so we can't test it every time we release unfortunately).
If you don't want to do this, would it be possible to make a small sample available, so we can test it on Linux with the current version (and with 0.78 as well) to confirm the issue?
@workflowsguy commented on GitHub (Jan 31, 2016):
Thanks for the instructions,
unfortunately it fails to build on my Mac, so I have created a new issue as per your suggestion.
@workflowsguy commented on GitHub (Feb 1, 2016):
I have tested this with a build of 0.79. However, it still produces the error message
@cfsmp3 commented on GitHub (Feb 1, 2016):
That means it can't find or open the input file.
On Feb 1, 2016 8:25 AM, "workflowsguy" notifications@github.com wrote:
@workflowsguy commented on GitHub (Feb 2, 2016):
Sorry, this was caused by an error in my extraction script.
However, it would be great if in the case of such an error the name of the file were listed.
I mistakenly thought that CCExtractor could not open the video file; instead the path to the srt file to be created was incorrect.
With a more verbose error message, I would have spotted my error immediately.
@cfsmp3 commented on GitHub (Mar 18, 2016):
Solved in current github, please reopen if a new sample that fails proper detection appears