DRM-X 6.0Package and publish content
Package and publish DRM-X 6.0 protected VOD using DASH/CENC, HLS/CBCS, single-key or multi-key quality tiers, and managed or registered cloud storage.
Encrypt and publish your video
Prepare the source video, encrypt it, publish the output, and use its Content ID when requesting playback.
- Source video
Choose the video and audio tracks you want to protect.
- Encrypt and package
Create encrypted media using CENC or CBCS, according to the target DRM system.
- Publish the output
Upload the encrypted media and register its playback URLs.
- Content ID
Use this identifier in your backend to request playback for the published video.
Package the source once, wait for Published status, test it in the DRM-X Web Player, then integrate it with your website. The Desktop and CLI tutorials use Packager 1.0.0-beta.1 and the same protected output format.
Choose the workflow#
DRM-X 6.0 Packager Desktop
Recommended for Windows. Save and test a protected profile, add source files, choose encoding and encryption settings, and start the batch. Use Copy selected command to review the equivalent CLI command. The phase indicators show encoding, encryption, verification and upload progress.
DRM-X CLI Packager
The same Windows Suite includes the complete CLI for professional automation. Linux uses CLI only with DRMX_PACKAGER_SITE_ID, DRMX_PACKAGER_ACCESS_KEY, and DRMX_PACKAGER_KMS_TOKEN supplied by a trusted environment.
CPIX integration
Integrate a controlled media pipeline while keeping content keys and provider credentials out of build logs and operator workstations.
Follow a detailed tutorial#
Prepare the source correctly#
- Desktop and CLI can encode a master source automatically before encryption. If using pre-encoded inputs, prepare the final ladder, frame rates, audio and subtitle tracks first.
- Use Single Video Key Protection when all video qualities share one security rule. Choose Multi-key Quality Tiered when AUDIO, SD, HD, UHD1 and UHD2 need separate rules. The packaging format, codec and device support also determine compatibility.
- Produce DASH/CENC for Widevine and PlayReady and HLS/CBCS for FairPlay when those platforms are enabled.
- Upload only encrypted segments, protected manifests, and intended public delivery assets.
Publication is the security boundary#
A successful packaging job is not automatically a playable catalog item. Published status means the immutable output, registered manifest variants, storage destination, key model, Content ID, and validation evidence are ready for the Playback Session API.
Validate before customers receive it#
- Open the DRM-X Web Player and sign in with the customer account that owns the content. Select the packaging environment.
- Select the exact Published protected file.
- Confirm that Single Video Key Protection or Multi-key Quality Tiered was detected correctly, keep a matching policy and press Play.
- Test every platform, promised resolution, audio language, subtitle, stop/release path, and entitlement denial.
Connect your own cloud storage#
Configure CORS and public delivery with the cloud storage guide or AWS S3 and CloudFront tutorial. Test uploads and playback using your account.
Keep UHD available and limit phones when needed#
Include lower renditions when creating a UHD ladder. A phone-only 1080p option works at playback time; it does not require a second package or remove 4K from your published content. The player cannot create 1080p from a 4K-only source. Follow mobile playback limits after your first playback test.