Those are not going to be deep guides but should give you a better idea of how to compliment FFmpeg in order to help improve your strategy. I have included several examples below to give you a high-level view of how you can use FFmpeg with 3 rd party tools and services. If you use the FFmpeg today in your pipeline, it mostly stays at the content preparation (encoding) side and doesn’t go beyond its comfort zone allowing other services and tools to take over the packaging and DRM application. Complimenting FFmpeg with Other Tools & Services

However, this signaling is simple Clear Key which does not provide the strong encryption specification enforced with consumer DRM and mandated by studios.ĭespite the fact that the DRM output is not yet available with FFmpeg, it can still be deployed within your workflow provided it is used in conjunction with other services and tools that will allow you to package the files with DRM. FFmpeg does allow for AES-128 encryption with HLS, for example, with the following signaling inside your manifest: While very capable, with DRM in the picture, it leaves some things to be desired. FFmpeg is one of the most powerful tools available when it comes to A/V content processing/encoding/packaging.

More recently, however, we are increasingly seeing more customers utilizing FFmpeg to produce both VOD and Live assets.Ĭustomers using existing partners enjoy the benefit of a preexisting integration, but for those using FFmpeg, a few changes must be made to implement DRM. When people come to us asking for DRM integration advice, they usually already have a video workflow that includes content encoding and packaging.Ĭustomers mostly use different 3 rd party vendors that are already integrated with BuyDRM like Wowza, AWS Media Services, Harmonic, Telestream and others.

Ffmpeg options pipe