In this post you will learn how to use custom preset for Azure Media Service Encoding. But before that let's look at a case study or issue which I faced. When I uploaded a 55.5 MB mp4 file and encoded with "H264AdaptiveBitrateMP4Set720p" encoder preset, I received following output files: Look into green rectangular highlighted video files in the image, this looks good according to input file size. But if you look at red rectangular highlighted video files, these are *improved* files for adaptive streaming, which looks useless if you compare with my example "a dark line on my face in video can't be removed by system automatically...make sense". Here I'm trying to understand Azure Media Services encoding permutations but increasing file size 2-3 times larger than input file is never a acceptable deal. Why I should pay more for bandwidth and storage on these large files, how I convince my clients? On this issue I thought to under
In this quick code you will learn how to initialize var so that it works like null or empty. Technically, this is not possible.