2016-02-04, 14:28
One could argue, both versions suck in a way, cause the shield's v5 android version sucks. Refreshrate switching is not optimal implemented ...
I personally don't like either - it's a long way to go on this platform.
v17 speaks non IEC passthrough in the engine, therefore things like delay / pausing are solved in a more optimal way, e.g. no clock moving, better possibilities to maintain sync after seek and so on.
As of now go with amlogic :-) they support IEC passthrough frames and from what I read it works really nice. Android's Audiotrack api has a long way to go and the implementation of the vendors also.
I personally don't like either - it's a long way to go on this platform.
v17 speaks non IEC passthrough in the engine, therefore things like delay / pausing are solved in a more optimal way, e.g. no clock moving, better possibilities to maintain sync after seek and so on.
As of now go with amlogic :-) they support IEC passthrough frames and from what I read it works really nice. Android's Audiotrack api has a long way to go and the implementation of the vendors also.
