2017-09-28, 09:28
Vendors should not announce capabilities they don't implement.
Quote:Vendors should not announce capabilities they don't implement.They don't via getEncodings method. Are you sure that checking the constants in AudioFormat is supposed to tell you the HW capabilities? I would assume that every Nougat defines the IEC constant for example. It is like checking the API level...
Quote:It it this log that tell me that IEC API is chosen?Exactly. That's where things start to fail.
"DEBUG: AESinkAUDIOTrack: Using IEC PT mode: 13"
(2017-09-28, 20:19)CiNcH Wrote: I totally agree that it is sad that MediaTek is not adapting to public APIs.
But it is still a Kodi bug that it uses IEC even though the HW API clearly states that it does not support it. Making a decision based on those constants is just wrong. And you know that.
(2017-09-28, 20:31)CiNcH Wrote: Yes. I know this approach of making an API call with a certain encoding and fall back in case it fails... I am still on Marshmallow so IEC is a non-issue for me...
(2017-09-27, 18:55)Nednil Wrote: I have a Philips 55pus6561 and I received android 7.1.2 a couple of days ago.
Philips version QM163E.0.15.176.3
And now No passthrough seems to working anymore, with the same settings as before and kodi 17.4
Have anyone else received this version?
and have the same issues´?
(2017-10-16, 14:29)CiNcH Wrote: Won't happen. Kodi only follows standard APIs for the very reason of code maintainability. Manufacturers need to fix this stuff. If they don't, people should not buy it.
Quote: Not sure about Sony tho.