DRM Services and Chromium runtime setup

What this feature does—and does not do

Settings → DRM Services keeps supported device/runtime inventory and saved service/account preferences together. It is not a content subscription, an entitlement override or a promise that every service accepts every runtime. Use only material, accounts and content you are authorized to use.

No Chromium browser/CDM bundle is installed merely by enabling a source account. Runtime preparation is explicit. Provider behavior, account region and source capabilities still determine availability.

1. Manage device provisions carefully

1. Open the relevant Widevine or PlayReady tab and inspect the existing inventory before adding a preference.
2. Import only a supported provision you are authorized to use through the offered upload control. Do not post device files or secrets in support tickets.
3. Review parsed details, enabled state, existing references and active uses. Parsed metadata is not a successful provider playback test.
4. Use Set preference for a service/account only when the adapter supports the managed selection.
5. Test one authorized source. Keep working defaults unless you have a reason to change them.

Account preferences take priority over service preferences. Existing provider-specific device choices have priority over the fallback default. A broad fallback setting is not a command to replace every adapter’s working profile.

2. Prepare a Chromium/CDM runtime

1. Open the Chromium tab. Read the supported-host and workflow message shown by your installed version.
2. Choose a listed supported bundle and click Prepare runtime. Follow the preparation phase/progress; this downloads/verifies a runtime and does not log in to a provider.
3. When a complete installation is detected, choose Register runtime. Wait for host verification; an incomplete/detected browser is not ready.
4. Inspect its enabled state and runtime details. Use Set preference to bind the intended supported service or account.
5. Configure an enabled Transcode profile, then test one supported on-demand/VOD title on the same host.

3. Distinguish adapter coverage from qualification

The v2.0 release records scoped qualification for supported Netflix controller-local Chromium VOD workflows up to 1080p with optional transcoding. That is not a universal statement about every Netflix title, host, account or provider. Other adapters retain their own supported DRM and copy-mode paths. Read service-specific status and test the actual account rather than switching all services to Chromium.

Chromium runtime preparation on the main server does not provision every worker. Host platform, runtime availability, file access, processing policy and capacity must match the job placement.

4. Change preferences without breaking active work

• Inspect active uses and affected saved preferences before disabling/removing a device/runtime.
• Use the offered replacement/acknowledgement workflow; clearing a preference is different from deleting the runtime.
• Do not delete an active runtime folder manually or replace vendor binaries behind a registered identity.
• Restore through the supported UI when available; revalidate host readiness after changes.
• Existing references and provider defaults deserve deliberate migration, not blind rotation.

5. Diagnose the correct layer

Share only redacted diagnostics. Never upload account tokens, device material or real signed playback URLs into public bug reports.