Here at Ziggeo we always liked to be sure that we bring you all the best things. We would do that to various features as well as improvements. Now sometimes the best thing might not be the latest available, so how do you choose?
Well, easy and if you read further you will see just how.
Some browser vendors provide a way for you to select what to be used. They also provide different ways of doing things. Such example is Google Chrome and their encoding engine.
There are 2 flavors of it available. One is great for CPU. This one is also used by Firefox and most other browser vendors. Chrome however also offers a newer one, which is a bit more CPU intensive.
Now why would they do that?
Good question. The reality is that there is a choice between 2 different options. Make the encoding better for CPU (requiring smaller amount of encoding), or make video better for mobile data.
When it comes to internet and more specifically mobile data, less you need it, the better. To pack 10mb into some smaller size, well you need to process it. The more you process the same, the smaller it can get and this is what you would generally use CPU.
Should you always use it?
Well most your customers on mobile devices will love using the best there is. If you want to do that, just leave it as is. If your customers are generally utilizing older mobile devices, then CPU power might not be great. In such cases, you would be better off using the new parameter.
So how does this work?
cpu-friendly boolean parameter as true to your recorder and that is it. No further action is needed on your side.
Which encoding is used when?
Well, we stayed clear of mentioning exactly what is used because that is something browser vendors will change over time. Historically this is also often different from browser to browser. Instead we plan to have this parameter constantly up to date.
What that means is that as the time goes we will always keep it to provide you with the encoding that uses less CPU, or by excluding it to use the latest.
Have any questions? Reach out to us through our friendly support team at firstname.lastname@example.org.