Eyevinn / moqlivemock / 25959742055
53%
main: 53%

LAST BUILD BRANCH: release/v0.9.0
DEFAULT BRANCH: main
Ran
Jobs 1
Files 25
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: 53.104% (-0.7%) from 53.802%
25959742055

Pull #84

github

tobbee 
docs: add 'DRM with LOCMAF' section to LOCMAF.md

The doc previously only mentioned DRM in a single Background sentence
('fed into an MSE/EME player') and in the encryption field IDs scattered
through the moof / moov reference tables. Given that DRM is LOCMAF's
primary motivation (per Hugo's thesis title), add an explicit section
that ties the wire-format pieces together.

The new ## DRM with LOCMAF section covers:

- End-to-end pipeline diagram: encrypted CMAF → LOCMAF wire →
  reconstructed CMAF → MSE / EME / CDM, calling out that the mdat is
  byte-equal end-to-end.
- Catalog DRM signalling (contentProtections + contentProtectionRefIDs
  + DRMSystem object) with a worked JSON example, plus a note that
  locmafVersion applies to DRM-protected tracks the same way.
- cenc vs cbcs trade-off on the wire (per-sample IV vs constant IV
  from tenc), with a small comparison table.
- Pointer to the CENC IV counter-prediction optimisation in Possible
  improvements.
- Why byte-lossy moof reconstruction is safe for decryption: every
  field the CDM uses (default_KID, senc IV, subsample BytesOfClear /
  BytesOfProtectedData, ciphertext mdat) is carried verbatim; the
  fields LOCMAF does drop or repack (tr_flags, redundant tfhd
  defaults, mdat header) don't participate in decryption.
Pull Request #84: docs: add DRM section to LOCMAF.md

3268 of 6154 relevant lines covered (53.1%)

1283.96 hits per line

Coverage Regressions

Lines Coverage ∆ File
36
23.58
 -8.55% internal/pub/pub.go
14
41.74
 -1.74% internal/sub/sub.go
Jobs
ID Job ID Ran Files Coverage
1 25959742055.1 25
53.1
 GitHub Action Run
Source Files on build 25959742055