The Media Packager command line tool can generate a .header and a .metadata file when packaging content. The .metadata file can be used to initiate a license request from the player -- the .metadata file alone is sufficient to perform a license request.
For information on the FLV/F4V file formats, you can download the video file format specification from http://www.adobe.com/devnet/f4v.html.
To get familiarize with Flash access for mp4, i have created a manifest file which includes DRMAdditionalHeader tag.
i have encoded .mp4.metadata content and included in DRMAdditionalHeader tag. And requested that manifest file.i got that manifest file, but it didnt do license request.
And player showed as DRM Protected: No.
1. Does encoded(base64) .metadata is equal to drm additional header?
2. is there any other data(content) also needed to do license request?
No, the .metadata is not the same as the DRM Additional Header. For the DRMAdditionalHeader tag in the manifest, you need to use the contents of .header file (base-64 encoded) that was generated by the Media Packager command line tool.
Thanks katherine .
I have included total .header file content (base-64 encoded) in DRMAdditionalHeader tag in the manifest.
But still i didnt see any license request from player and
showed as DRM Protected: No
DRM Error: 3309[CorruptedFLV] in player
Do i need to give partial content of .header file?
can you provide me info on this..
I am doing conversion from mp4 to f4m for HDS.
I have requirement which needs to make a license request from the f4m we generate , irrespective of mp4/f4f
For the DRMAdditionalHeader tag in the manifest(f4m), used the contents of .header file (base-64 encoded) that was generated by the Media Packager command line tool
I used Media Packager command line tool that ships with the Flash Access SDK.
But license request is not generated from f4m file. Can some one help on this?