{"id":958,"date":"2012-10-30T13:40:56","date_gmt":"2012-10-30T12:40:56","guid":{"rendered":"http:\/\/www.alkannoide.com\/?p=958"},"modified":"2012-10-30T14:22:26","modified_gmt":"2012-10-30T13:22:26","slug":"packaging-adaptive-bitrate-vod-content-on-the-fly","status":"publish","type":"post","link":"https:\/\/www.alkannoide.com\/2012\/10\/30\/packaging-adaptive-bitrate-vod-content-on-the-fly\/","title":{"rendered":"Packaging adaptive bitrate VOD content on the fly"},"content":{"rendered":"

The actual market on the OTT use Adaptive Bit Rate video format over HTTP (Smooth Streaming<\/a>, HTTP Dynamic Streaming<\/a>, HTTP Live Streaming<\/a> and MPEG-DASH<\/a> soon) to deliver the content. I make this analyse without integrate the DRMs system which is a big topic itself.\u00a0Here is an overview of the different format available for each platform.<\/p>\n

[table id=1 \/]<\/p>\n

The matrix is a kind complex; all this technologies are multibitrate, so for one asset, you need to transcode for each bitrate.\u00a0Each technology is different and use his own specification :<\/p>\n

[table id=2 \/]<\/p>\n

If I follow the specifications given by the manufacturers (HLS) or if I’m basing on 4 bitrates for the others formats (Smooth Streaming, HDS), I need to transcode more than 20 times the same asset.<\/p>\n

There is an option to avoid and reduce significatively the number of transcoding tasks : the packaging on the fly. This article will only analyse the on-demand side, not the live.<\/p>\n

Packaging on the fly is possible. If you look the second table, you will see all format can be encoded in H264 and AAC, so you would streamline the number of transcoding tasks from 20 times to 8. I take 8 because this is the number of bitrate given for the iPad encoding video recommandations<\/a>.<\/p>\n

The main idea is : have one ABR streaming format in input, repack in a server the content in anyone others formats. To do that there is different solutions, I group them by type :<\/p>\n