CCextractor behaves unexpectedly when processing both CEA-608 fields. #274

New Issue

claunia · 2026-01-29T16:39:37Z

claunia commented

2026-01-29 16:39:37 +00:00

Originally created by @OmegaVVeapon on GitHub (Feb 15, 2017).

For CEA-608 extraction, the helpstates that:

Options that affect what will be processed:
          -1, -2, -12: Output Field 1 data, Field 2 data, or both
                       (DEFAULT is -1)

The -1 and -2 options both create a <media_name>.srt file with the correct CEA-608 CC's according to the specified field. However, specifying both fields (-12), will create <media_name>_1.srt and <media_name>_2.srt files. However, the first file will contain interleaved CCs from both fields inside of it, leaving the second file empty. For example, this is what occurs when trying to extract both the english and french CEA-608 CCs from a media:

media_1.srt

00:00:36,746 --> 00:00:40,205
 <i> [boy]</i>
 <i> If you must blink, do it now.</i>

4
00:00:36,704 --> 00:00:40,581
  (garçon):<i> Si tu dois cligner</i>
<i>des yeux, fais-le tout de suite.</i>

media_2.srt

Originally created by @OmegaVVeapon on GitHub (Feb 15, 2017). For CEA-608 extraction, the `help`states that: ``` Options that affect what will be processed: -1, -2, -12: Output Field 1 data, Field 2 data, or both (DEFAULT is -1) ``` The `-1` and `-2` options both create a `<media_name>.srt` file with the correct CEA-608 CC's according to the specified field. However, specifying both fields (`-12`), will create `<media_name>_1.srt` and `<media_name>_2.srt` files. However, the first file will contain interleaved CCs from both fields inside of it, leaving the second file empty. For example, this is what occurs when trying to extract both the english and french CEA-608 CCs from a media: _media_1.srt_ ``` 00:00:36,746 --> 00:00:40,205 [boy] If you must blink, do it now. 4 00:00:36,704 --> 00:00:40,581 (garçon): Si tu dois cligner des yeux, fais-le tout de suite. ``` _media_2.srt_ ``` ```

claunia closed this issue

2026-01-29 16:39:37 +00:00

claunia commented

2026-01-29 16:39:38 +00:00

@Izaron commented on GitHub (Feb 15, 2017):

Can you please attach your video file here? For example, as link to Dropbox file.

@Izaron commented on GitHub (Feb 15, 2017): Can you please attach your video file here? For example, as link to Dropbox file.

claunia commented

2026-01-29 16:39:38 +00:00

@OmegaVVeapon commented on GitHub (Feb 15, 2017):

I'm afraid I can't share the media that repro'd the issue (NDA), and I don't seem to have any other medias with 2 CEA-608 fields. If I do find something to share, what address should I send the Dropbox link to? carlos (at) ccextractor.org?

@OmegaVVeapon commented on GitHub (Feb 15, 2017): I'm afraid I can't share the media that repro'd the issue (NDA), and I don't seem to have any other medias with 2 CEA-608 fields. If I do find something to share, what address should I send the Dropbox link to? carlos (at) ccextractor.org?

claunia commented

2026-01-29 16:39:39 +00:00

@cfsmp3 commented on GitHub (Feb 15, 2017):

Just write it here in a comment.

Basically you have two options

Work with us publicly, meaning samples and code are available for
everyone to use as needed.
Work with us privately. Privately always means under contract. You can
hire me or anyone else in the team you like. I'll be happy to sign a NDA if
needed.

What is not going to happen is that we work on anything private without
payment :-)

On Wed, Feb 15, 2017 at 1:42 PM, Alan Silva notifications@github.com
wrote:

I'm afraid I can't share the media that repro'd the issue (NDA), and I
don't seem to have any other medias with 2 CEA-608 fields. If I do find
something to share, what address should I send the Dropbox link to?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/CCExtractor/ccextractor/issues/687#issuecomment-280148802,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFrJ2aFKXIQpVfYHi9MDFdFaZspbxwPtks5rc3FEgaJpZM4MB4ZA
.

@cfsmp3 commented on GitHub (Feb 15, 2017): Just write it here in a comment. Basically you have two options 1) Work with us publicly, meaning samples and code are available for everyone to use as needed. 2) Work with us privately. Privately always means under contract. You can hire me or anyone else in the team you like. I'll be happy to sign a NDA if needed. What is not going to happen is that we work on anything private without payment :-) On Wed, Feb 15, 2017 at 1:42 PM, Alan Silva <notifications@github.com> wrote: > I'm afraid I can't share the media that repro'd the issue (NDA), and I > don't seem to have any other medias with 2 CEA-608 fields. If I do find > something to share, what address should I send the Dropbox link to? > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <https://github.com/CCExtractor/ccextractor/issues/687#issuecomment-280148802>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AFrJ2aFKXIQpVfYHi9MDFdFaZspbxwPtks5rc3FEgaJpZM4MB4ZA> > . >

claunia commented

2026-01-29 16:39:39 +00:00

@cfsmp3 commented on GitHub (Jan 11, 2018):

Closing since user didn't reply to last post and we don't have a sample.

@cfsmp3 commented on GitHub (Jan 11, 2018): Closing since user didn't reply to last post and we don't have a sample.

claunia commented

2026-01-29 16:39:39 +00:00

@harrynull commented on GitHub (Jan 12, 2018):

Is this a common issue that can be reproduced in all medias with 2 CEA-608 fields?

@harrynull commented on GitHub (Jan 12, 2018): Is this a common issue that can be reproduced in all medias with 2 CEA-608 fields?

claunia referenced this issue

2026-01-29 16:59:45 +00:00