Skip to content

add c608 mapping #823

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
+54 −0
Open

add c608 mapping #823

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
2fecb92
add c608 mapping
dericed Apr 10, 2024
8eeee1b
add S_C608 subtitle track
dericed Apr 21, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 26 additions & 0 deletions block_additional_mappings/c608-captions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,26 @@
## c608 Captions

### c608 Captions Description

CEA-608 captions can be stored in `BlockMore Element` to associate the content of a Matroska Block (typically a video frame) with closed captioning data. Storing CEA-608 caption data requires that the corresponding Block SHALL NOT use Lacing.
Copy link
Collaborator

@robUx4 robUx4 Jan 26, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

SHALL NOT should have "**" around it.


The `BlockAdditional Element` stores the c608 data as a array of one or more octet pairs from one data channel of a CEA-608 data stream with each octet pair corresponding to a video frame. For more information about the content see [@!ANSI-CTA-608-E-S-2019].

### BlockAddIDType

The BlockAddIDType value reserved for CEA-608 captions is "608".

### BlockAddIDName

The BlockAddIDName value reserved for CEA-608 captions is "CEA-608 captions".

### BlockAddIDExtraData

BlockAddIDExtraData MAY contain a value as defined by Section 6.4.3.3 of [!@DASH-IF-IOP] that describes the caption services and language. An ABNF from [!@DASH-IF-IOP] for this value is restated here for convenience:
Copy link
Collaborator

@robUx4 robUx4 Oct 22, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

MAY should be normative

Suggested change
BlockAddIDExtraData MAY contain a value as defined by Section 6.4.3.3 of [!@DASH-IF-IOP] that describes the caption services and language. An ABNF from [!@DASH-IF-IOP] for this value is restated here for convenience:
BlockAddIDExtraData **MAY** contain a value as defined by Section 6.4.3.3 of [!@DASH-IF-IOP] that describes the caption services and language. An ABNF from [!@DASH-IF-IOP] for this value is restated here for convenience:


```
@value = (channel *3 [";" channel]) / (language *3[";" language])
2 channel = channel-number "=" language
Copy link
Collaborator

@robUx4 robUx4 Apr 13, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are the numbers at the beginning of each line expected in the ABNF description ?

Copy link
Collaborator

@robUx4 robUx4 Oct 22, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To answer myself: yes, these number are line numbers in the PDF. They should be removed here.

3 channel-number = CC1 | CC2 | CC3 | CC4
Copy link
Collaborator

@robUx4 robUx4 Apr 13, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

CC1/CC2/CC3/CC4 are missing a definition

Copy link
Collaborator

@robUx4 robUx4 Oct 22, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Given the examples in the PDF they are litteral strings.

In a more recent version of the split PDF it says:

SCTE 214-1 [5], section 7.2.3, “Signalling CEA-608 caption service metadata”

In the current version of SCTE 214-1 that's section 8.2.3 and the BNF has been fixed:

@value = language / channel 0*3 [";" channel]
channel = channel-number "=" language
channel-number = “CC1” / “CC2” / “CC3” / “CC4”
language = 3ALPHA ; language code per ISO 639-3

We should probably use that and also reference that source directly.

4 language = 3ALPHA ; language code per ISO 639.2/B
```
8 changes: 8 additions & 0 deletions codec_specs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -944,6 +944,14 @@ Codec Name: ARIB STD-B24 subtitles
Description: This is the textual subtitle format used in the ISDB/ARIB broadcasting standard.
For more information, see (#arib-isdb-subtitles) on ARIB (ISDB) subtitles.

### S_C608

Codec ID: S_C608

Codec Name: CEA-608 Captions

Description: Each Block of a S_C608 subtitle track stores the c608 data as a array of one or more octet pairs from one data channel of a CEA-608 data stream with each octet pair corresponding to a video frame. The "LABEL" Matroska tag is RECOMMENDED for storage the first channel number of the CEA-608 pair (expressed as either "CC1" or "CC2"). For more information about this format see [@!ANSI-CTA-608-E-S-2019].
Copy link
Collaborator

@robUx4 robUx4 Jan 26, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

RECOMMENDED should have "**" around it


## Button Codec Mappings

### B_VOBBTN
Expand Down
20 changes: 20 additions & 0 deletions rfc_backmatter_codec.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -141,3 +141,23 @@
<date year="2022" month="October" day="6"/>
</front>
</reference>

<reference anchor="ANSI-CTA-608-E-S-2019" target="https://shop.cta.tech/products/line-21-data-services">
<front>
<title>Line 21 Data Services ANSI/CTA-608-E S-2019</title>
<author>
<organization>ANSI/CTA</organization>
</author>
<date year="2019" month="December"/>
</front>
</reference>

<reference anchor="DASH-IF-IOP" target="https://dashif.org/docs/DASH-IF-IOP-v4.3.pdf">
<front>
<title>Guidelines for Implementation: DASH-IF Interoperability Points</title>
<author>
<organization>DASH Industry Forum</organization>
</author>
<date year="2018" month="November" day="18"/>
</front>
</reference>