You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Firstly, many thanks to Rob & Co for sharing caption-inspector with the open source community. I've been using caption-inspector for a few years for field 1 data.
However, recently I have been attempting to decode SCC files containing field 2 (CC3/4) data with caption-inspector.
Test Case - Field 1(CC1/2) only
Below is a test case containing.
CC1: AAAAAAAA
CC2: aaaaaaaa
❌ The field 2 SCC file does not decode as expected. The PAC codes {R1:White}9140 and 1940 are interpreted as always belonging to field 1, and instead of producing a decode containing CC3/4, caption-inspector extracts the PAC and payload as if they belong in field 1/CC1&2.
Decoded Line 21 / CEA-608 for Asset: ./captioninspector/field2-C1 - Channel: 1 {R1:White} "XXXXXXXX
Decoded Line 21 / CEA-608 for Asset: ./captioninspector/field2-C2 - Channel: 2 {R1:White} "xxxxxxxx
Decoded Line 21 / CEA-608 for Asset: ./captioninspector/field2-C3 - Channel: 3
00:00:00:00 - {RCL} {ENM}
00:00:00:07 - {EOC}
Decoded Line 21 / CEA-608 for Asset: ./captioninspector/field2-C4 - Channel: 4
00:00:00:08 - {RCL} {ENM}
00:00:00:15 - {EOC}
I believe that PAC codes {R1:White}9140 and 1940 codes are correct, even when used in Field 2. I have cross referenced against McPoodle's 7 bit parity tables, which although is not anything near a reference implementation of SCC/608, but is at least an independent 3rd party interpretation of CTA-608 / Title 47.
✅ Removing the PAC codes from a field 2 SCC file results in an expected decode on channels 3 & 4
Decoded Line 21 / CEA-608 for Asset: ./captioninspector/field2-without-pac-C3 - Channel: 3
00:00:00:00 - {RCL} {ENM} "XXXXXXXX"
00:00:00:06 - {EOC}
Decoded Line 21 / CEA-608 for Asset: ./captioninspector/field2-without-pac-C4 - Channel: 4
00:00:00:07 - {RCL} {ENM} "xxxxxxxx"
00:00:00:13 - {EOC}
Although it is noted that even this final example without PAC codes, caption-inspector reports Channel/Field Mismatch on an SCC file containing Field 2 data.
Question: Does caption-inspector support field 2(CC3/4) input from SCC/SC2 files or does it assume that all SCC files (and PAC codes therein) are field 1? Or have I misinterpreted how field 2(CC3/4) should be included within an SCC/SC2 file. Thanks!
The text was updated successfully, but these errors were encountered:
Firstly, many thanks to Rob & Co for sharing caption-inspector with the open source community. I've been using caption-inspector for a few years for field 1 data.
However, recently I have been attempting to decode SCC files containing field 2 (CC3/4) data with caption-inspector.
Test Case - Field 1(CC1/2) only
Below is a test case containing.
CC1: AAAAAAAA
CC2: aaaaaaaa
✅ This successfully decodes to CC1/2 as expected.
Test Case - Field 2(CC3/4) only, containing PAC codes
If I take a field 2 CC3/4 equivalent test case containing:
CC3: XXXXXXXX
CC4: xxxxxxxx
❌ The field 2 SCC file does not decode as expected. The PAC codes
{R1:White}
9140
and1940
are interpreted as always belonging to field 1, and instead of producing a decode containing CC3/4, caption-inspector extracts the PAC and payload as if they belong in field 1/CC1&2.I believe that PAC codes
{R1:White}
9140
and1940
codes are correct, even when used in Field 2. I have cross referenced against McPoodle's 7 bit parity tables, which although is not anything near a reference implementation of SCC/608, but is at least an independent 3rd party interpretation of CTA-608 / Title 47.✅ Removing the PAC codes from a field 2 SCC file results in an expected decode on channels 3 & 4
Although it is noted that even this final example without PAC codes, caption-inspector reports
Channel/Field Mismatch
on an SCC file containing Field 2 data.Question: Does caption-inspector support field 2(CC3/4) input from SCC/SC2 files or does it assume that all SCC files (and PAC codes therein) are field 1? Or have I misinterpreted how field 2(CC3/4) should be included within an SCC/SC2 file. Thanks!
The text was updated successfully, but these errors were encountered: