Licensing, Codec Royalties and DRM for a Paid Corporate Course
A commercial training company is building a paid, subscription-based safety-compliance course sold to corporate clients. The producer plans to use: a commercial music track as background under narration; two clips from a stock footage library bought under a standard royalty-free licence; three diagrams from an open textbook released under CC BY-NC-SA 4.0, which will be cropped and re-annotated; and a screen recording of a third-party CAD application being used, including its logo and splash screen. Delivery is via web and iOS/Android apps. The vendor quotes two encoding options: HEVC, which carries royalties administered by several patent pools, or AV1, offered royalty-free by the alliance that develops it. The legal team has asked for a written risk assessment before the first module is published.
1. Analyse the rights position for each of the four content types, flagging what can proceed and what needs action before publication.
Read the worked answer
1. Commercial music track as background. This is synchronisation plus, if the track is a known recording, master use. A sync licence covers the composition; a separate master licence covers the recording. Subscription sale to corporate clients is commercial use; most consumer-facing "personal use" or "royalty-free" library terms do not cover it. Action: obtain sync and master licences, or replace with a track explicitly licensed for commercial/enterprise use. Do not rely on the fact that the track is only audible under narration.
2. Stock footage, standard royalty-free licence. Usually permissive, but read for: whether redistribution inside a paid product counts as permitted use, whether the licence is per-seat or per-publisher, whether attribution is required, and whether the licence survives termination (some allow the licensor to withdraw a clip for new uses). Action: archive the licence certificate and version with the asset; verify the clips are not marked editorial-only.
3. CC BY-NC-SA 4.0 diagrams. Two problems. NC - a paid subscription course is commercial use; selling access is not a borderline case, so the NC term is breached. SA - cropping and re-annotating creates an adaptation, which if distributed must be released under the same BY-NC-SA terms, potentially forcing the derivative diagram (and arguably the video segment built on it) to be openly licensed. The aggregation exception only helps if the work is included unmodified alongside other material. Action: do not use them. Find CC BY (or CC BY-SA, still awkward) sources, purchase a licence, or redraw the diagrams from scratch - facts are not protected, only their expression.
4. Screen recording of third-party software. Recording your own lawful use of the software for training is generally acceptable, but check the end-user licence, which sometimes restricts redistribution of output. Showing the logo is nominative use - you are identifying the product - and is normally defensible, but do not use the logo as branding for your course. Action: check the EULA, avoid showing licence keys, personal data or unreleased features, and keep the recording factual.
2. Compare the HEVC and AV1 options. What should the company actually choose, and on what basis?
Read the worked answer
Frame the decision as a royalty exposure question, not a compression question.
HEVC. The technical case is strong: universal hardware decode on recent phones and TVs, mature encoder support, Main10 for HDR. The commercial case is the problem. Rights are administered by multiple independent patent pools, plus unaffiliated holders, so there is no single licence to obtain and no single fee that settles the matter. Pools generally charge separately for encoder/decoder devices and, in some cases, for content or service revenue above thresholds. A subscription business should model three scenarios: fees per subscriber, fees per title, and fees per app install - the last two can be painful for a small company with a large installed base.
AV1. Royalty-free licensing from the developing alliance, better compression than HEVC at low bitrates, and broad browser support. Risks: software decode on older mobile hardware costs battery and CPU, hardware decode is present only on newer chipsets, and third-party patent holders have asserted claims against AV1 adopters even though the alliance itself grants royalty-free terms from its members. Encoding is slower and more compute-hungry.
Recommendation. Do not pick one. Publish a multi-codec ladder from a single mezzanine:
- AV1 as the primary high-efficiency rendition for web and modern Android, where decode is cheap.
- H.264 High as the universal fallback. Its patent position is old and settled, and every device decodes it; the compression penalty is offset by the fact that the fallback serves older hardware anyway.
- HEVC only if the iOS installed base demands it and the licence review clears it; Apple hardware handles HEVC cleanly, and an HEVC rendition can be limited to those clients.
Document the decision with the royalty model attached, review it annually, and keep the mezzanine masters so the ladder can be re-cut when the licensing picture changes.
3. The company wants to stop screen-recording and casual re-distribution of the paid modules. Recommend a content-protection approach, and state plainly what it cannot achieve.
Read the worked answer
What DRM actually does. A DRM system encrypts the media and delivers decryption keys only to a player that has been authenticated and whose robustness has been assessed. That raises the cost of extraction; it does not make extraction impossible.
Recommended stack:
- Encrypt with a common encryption scheme (CENC/AES-CTR or AES-CBC) so one set of packaged segments serves every DRM system, and issue per-session licences rather than long-lived keys.
- Use the platform DRM systems: Widevine on Android/Chrome, FairPlay on Apple platforms, PlayReady on Windows. Publish CMAF segments once and let the licence server serve each client.
- Bind licences to entitlement: short licence duration, device limits, concurrent-stream limits, and server-side authorisation tied to the subscription state, so cancelling revokes access.
- Choose the right robustness level. Widevine L1 (hardware TEE) versus L3 (software) determines the maximum resolution a studio or partner will allow; for your own content, L1 for HD, L3 acceptable for SD.
- Forensic watermarking with per-user identifiers, so a leaked copy can be traced to a subscriber; this is the deterrent that actually changes behaviour.
- Complementary controls: signed URLs, hotlink protection, no-store cache headers on licence endpoints, and rate limits on the licence server.
State clearly what it cannot do: it cannot stop a phone camera pointed at a screen, an analogue capture, or a rooted device with a cracked player. Anyone claiming otherwise is overselling. The realistic goal is to make piracy inconvenient and traceable, and to satisfy the contractual security requirements of corporate buyers, who often demand DRM even knowing its limits. Note also that DRM stripping and key sharing may be separately unlawful under anti-circumvention rules, which strengthens the deterrent story in your terms of service.