Content inputs
Select source videos or prepared tracks. Include the audio languages and subtitles required by your audience.
6.0Content packaging
DRM Content Packaging Encoding and Encryption
Prepare protected streaming content with DRM-X 6.0 Desktop Packager and CLI. Encode H.264 or H.265 video, package HLS, MPEG-DASH, and CMAF output, apply Common Encryption, validate the result, and publish to supported cloud storage.
01 / DRM-X 6.0
DRM content packaging from source to publication
Encoding and adaptive streaming
Encode H.264/AVC or H.265/HEVC renditions for an adaptive bitrate ladder. Match source quality and target-device decoding support.
Packaging and validation
Create streaming manifests and encrypted segments. Check track, key, and DRM signaling consistency before publishing.
Publishing
Upload the encrypted output to a supported destination and connect its Content ID to your application.
02 / DRM-X 6.0
Desktop operation and CLI automation
Desktop Packager and CLI provide two interfaces to the content-processing workflow. Use the CLI for repeatable encoding, packaging, and publishing jobs.
| Interface | Platform | Use |
|---|---|---|
| Desktop Packager | Windows | Configure processing jobs and manage batches through the desktop interface. |
| CLI Packager | Windows and Linux | Automate the same processing workflow on your computer or content server. |
03 / DRM-X 6.0
Formats, codecs, and tracks
| Category | Supported workflow |
|---|---|
| Streaming output | HLS, MPEG-DASH, and CMAF packaging profiles |
| Video | H.264/AVC and H.265/HEVC encoding |
| Audio and subtitles | Prepare the required tracks and validate their support in the selected player. |
| Playback compatibility | Select the package profile for the device’s DRM, codec, and encryption support. |
04 / DRM-X 6.0
Common Encryption and quality-tier keys
| Option | Meaning |
|---|---|
| cenc | AES-CTR encryption for compatible Common Encryption workflows. |
| cbcs | Pattern encryption based on AES-CBC for compatible workflows, including FairPlay HLS. |
| Single Video Key Protection | All video renditions share one video key. Encrypted audio uses a separate audio key. Audio-only content uses one audio key. |
| Multi-key | Use separate audio, SD, HD, and UHD keys. A policy can permit HD playback while requiring stronger hardware protection for UHD. |
05 / DRM-X 6.0
CPIX key exchange and PSSH signaling
CPIX
CPIX exchanges content keys and protection metadata between compatible processing systems. Keep the exchange within your trusted packaging integration.
PSSH boxes
PSSH boxes carry DRM initialization data for applicable formats. The initialization data, content key IDs, and license configuration must match.
Protected key storage
DRM-X manages protected content-key storage. Packaging access and playback authorization have separate roles and credentials.
06 / DRM-X 6.0
Validate and publish the protected output
For live broadcasting, use the separate AWS SPEKE workflow described on the Live DRM page.
- Check manifests, media tracks, key IDs, and DRM initialization data.
- Test playback and policy behavior on the intended devices.
- Publish through documented 1AICLOUD, AWS S3, Microsoft Azure, Google Cloud Storage, Alibaba Cloud OSS, and Tencent Cloud COS integrations.
- Use the registered Content ID to request playback from your backend.
Questions
Common questions
Can I encode and encrypt in one workflow?
Yes. Desktop Packager and CLI combine encoding, DRM encryption, validation, and publishing in supported workflows.
Can protected media stay in my cloud account?
Yes. Use registered AWS S3, Microsoft Azure, Google Cloud Storage, Alibaba Cloud OSS, and Tencent Cloud COS storage, or choose managed 1AICLOUD hosting. DRM licensing remains separate from media delivery.
Which packager platforms are available?
Windows supports Desktop Packager and CLI. Linux supports CLI processing. macOS packaging is planned and is not part of the current release.
Your next step
Download the packager
Use the relevant guide or contact our team to plan your supported workflow.