CCExtractor / ccextractor

CCExtractor - Official version maintained by the core team
https://www.ccextractor.org
GNU General Public License v2.0
727 stars 429 forks source link

[BUG] stdout argument not respected when multiple CC track found. #1453

Closed Adityashaw closed 1 year ago

Adityashaw commented 2 years ago
ccextractor --version
CCExtractor 0.94, Carlos Fernandez Sanz, Volker Quetschke.
Teletext portions taken from Petr Kutalek's telxcc
--------------------------------------------------------------------------
CCExtractor detailed version info
    Version: 0.94
    Git commit: Unknown
    Compilation date: 2022-09-06
    CEA-708 decoder: Rust
    File SHA256: Could not open file
Libraries used by CCExtractor
    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

PS: I downloaded and renamed below file.

Video links

Additional information

Expected: Output on stdout/terminal Actual: Output on multiple srt files

How can I get all/one CC output on stdout instead of creating multiple files?

abhi-kr-2100 commented 2 years ago

I'm working on this.

I've successfully built the latest checkout from source and reproduced this bug. Currently, I'm exploring the codebase to get familiar with it. I'll post here as I make progress towards identifying and fixing this issue.

abhi-kr-2100 commented 2 years ago

I've made a pull request fixing this issue for the particular case of .mkv or Matroska input files with multiple CC tracks.

cfsmp3 commented 1 year ago

@Adityashaw is the bug still there?

Adityashaw commented 1 year ago

@Adityashaw is the bug still there?

I do not see any new version on Arch User Repository since I posted this issue. I won't be able to compile myself this month due to timing constraints.

Hence, I won't be able to confirm the existence of the issue as of now.

cfsmp3 commented 1 year ago

Hence, I won't be able to confirm the existence of the issue as of now.

Closing for now. Feel free to reopen when you have a chance to verify.