Skip to content
sannies edited this page Oct 25, 2014 · 1 revision

The most simple of using DASH.encrypt is to create DASH file sets from pre-encoded media files. See Preparing Content for instructions on that topic.

Creating "Single 'sidx'" Adaptation Sets

Single 'sidx' adaptation sets are easy to handle as they only consist of one file per representation. A drawback of this way of dashing is that your web server and your client needs to support range request. Be aware that all Flash based clients need workarounds for performing range requests on the server. For details have a look at the .htaccess example in DASH.as.

java -jar dash.fragmencrypter-1.1.7-exe.jar dash vid_rep_1.mp4 vid_rep_2.mp4 vid_rep_3.mp4 sou_rep_1.mp4

Creating "One File per Segment" Adaptation Sets

These DASH file sets are easiest to serve but a bit unpractical to handle as it produce one file per segment. For 60min of movie with 10 representation this easily creates more than >10000 single files. The good thing is that you can use any HTTP server and any client without workarounds. The command line switch -x triggers this mode:

java -jar dash.fragmencrypter-1.1.7-exe.jar dash -x vid_rep_1.mp4 vid_rep_2.mp4 vid_rep_3.mp4 sou_rep_1.mp4