Eyevinn / go-608 / 30301156747
84%
main: 84%

LAST BUILD BRANCH: release/v0.8.0
DEFAULT BRANCH: main
Ran
Jobs 1
Files 34
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 83.626%. Remained the same
30301156747

Pull #61

github

tobbee 
docs(research): reconcile the pre-AV1 notes with mp4ff v0.55.0

Three notes already in the repo described mp4ff's SEI support as parse-only and named symbols that v0.55.0 renamed. consumer-injection-points.md was the worst: its section 3 concluded mp4ff has no way to create a caption SEI and called that the encode surface go-608 must own, which is now the opposite of the truth.

Corrected with the same editorial rule as the AV1 notes: superseded claims are marked, not deleted, since these record why the design went the way it did; dead identifiers are retargeted because a dead symbol is a trap regardless of framing.

One nuance kept straight rather than blanket-corrected: mp4ff still has no cc_data() builder. Its creators take cc_data() as input, so that stays carriage.BuildCCData. What moved upstream is the T.35/GA94 wrap and both envelopes. Also records that the reusable unit across codecs is the SEI message payload, not the message or the NAL, since an SEI NAL carries an emulation-prevented EBSP that AV1 has no analog for.

Prose references to the CEA-608 standard, and descriptions of other projects that use that spelling (media-tools, SVTA, dash.js), are deliberately left alone -- only mp4ff API symbols changed. All sei4.go, avc/sei.go and hevc/sei.go line citations were re-derived against v0.55.0 and checked.
Pull Request #61: docs(research): reconcile the pre-AV1 notes with mp4ff v0.55.0

3238 of 3872 relevant lines covered (83.63%)

0.97 hits per line

Jobs
ID Job ID Ran Files Coverage
1 30301156747.1 34
83.63
 GitHub Action Run
Source Files on build 30301156747