Thread: Fire HD 8 2016
View Single Post
Old 12-12-2016, 10:27 AM   #163
stumped
Wizard
stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.
 
Posts: 3,305
Karma: 10259306
Join Date: May 2016
Device: kobo forma, Kobo Libra, Huawei media Tab, fire HD10, PW3 HDX8.9,
You are making a huge assumption as to where the upscalcing is done. Can you back that up with facts?
With SD, the Amazon or Netflix server sends 70x480 pixels, that is the meaning of SD.
For that to map to a screen that has more pixels, I would expect the tablet OS to assign the task to an on-board graphics chip, aka hardware rendering, wherever possible.
Nothing to do with Amazon code. Netflix on my ten inch lenovo looked crap also.

If you use MX player, you can force HW or SW decoding. Software takes more cpu but looks exactly the same to my eyes

In your post you seem to want to have it both ways, you blame amazon for doing it badly, praise Apple for doing it well.only one of the two is managing the task.

We could Google Android upscaling ?

Last edited by stumped; 12-12-2016 at 10:31 AM.
stumped is offline   Reply With Quote