(2017-01-19, 21:10)fritsch Wrote: [ -> ]lol
Well, most likely I dump debug log and you can then tell me, what the fuck did Philips screw up this time (Interestingly there were no updates meanwhile)...
As I don't think it is Kodi's fault...hence I don't even see that "new hacked GUI setting" anymore.
No AC3, no transcoding option, no EAC...nothing under audio settings.
Meanwhile 6.0.1 is rolling out in Sweden for Philips.
EDIT: I'm an complete idiot...forgot to switch settings to "Expert"
And erything seems to be in sync again, so culprit was either corrupt install (caused by testing x+1 different apk's and installing those on top of eachother) or corrupt settings.
Transcoding AC3 448Kbit/s tself works fine...
Are you sure you test a version that worked formerly? Sounds like something Analog is plugged into the TV :-) Headphones?
(2017-01-19, 21:13)Etzi Wrote: [ -> ] (2017-01-19, 21:10)fritsch Wrote: [ -> ]lol
Well, most likely I dump debug log and you can then tell me, what the fuck did Philips screw up this time (Interestingly there were no updates meanwhile)...
As I don't think it is Kodi's fault...hence I don't even see that "new hacked GUI setting" anymore.
No AC3, no transcoding option, no EAC...nothing under audio settings.
Meanwhile 6.0 is rolling out in Sweden for Philips.
EDIT: I'm an complete idiot...forgot to switch settings to "Expert"
lol, been there done that
(2017-01-19, 21:42)fritsch Wrote: [ -> ]Are you sure you test a version that worked formerly? Sounds like something Analog is plugged into the TV :-) Headphones?
It was that "not so shity AC3 448Kbit/s" build, then suddenly I noticed (decided to actually watch movie, not only test audio) audio sync issues which I could not fix, so I decided to reinstall from scratch.
Currently works fine, after I fixed "human error" with settings.
I cannot plug headphones to it, it is on the wall, so only headphones which can be "plugged in" are BT ones, another option is plug them into receiver.
Also, got confirmation from other user (via PM) with Sony TV with same chipset, that this build works fine (no sync problems), hence why I started to suspect my installation.
Also I checked Jenkins to see actual changes in this build and there were none, except that AC3 bitrate change as you said later.
So currently running: kodi-20170117-13f39e2-shitty-armeabi-v7a and after complete clean re-install there are no sync issues or other audio issues.
(Except of course issues and limitations of this MTK chipset itself, which you obviously cannot fix, only workaround with AC3 bitrate change.)
Oki - so Krypton is more or less fine for you? (And if you are honest you don't hear the difference between 384 kbit/s AC3 and 448 kbit/s one ?)
Edit: Making you a build with only 448 kbit/s and the livetv workaround that is too intrusive for general android:
http://jenkins.kodi.tv/job/Android-ARM/10724/ <- will have "not so shitty" in its name :-)
(2017-01-19, 22:22)fritsch Wrote: [ -> ]Oki - so Krypton is more or less fine for you? (And if you are honest you don't hear the difference between 384 kbit/s AC3 and 448 kbit/s one ?)
If I'am fully honest, on Movies I don't hear the difference... (Denon AVR-X1200W + Magnat Monitor Supreme 200 so it is quite medicore audio system)
I just feel somewhat better (as you usually would, if you have maxxed out all the possible quality settings, that your device can provide)...
Krypton itself seems pretty ready for the prime time to me, I had no serious audio issues, since you implemented that "less than 640Kbit/s" into your special builds.
And I have watched lots of movies, with DTS or AC3...
After I learned that "sync to display" option can be used to force transcoding on all formats, it fixed problem with movies which have 5.1 AC3 640Kbit/s audio track too.
.
Have not noticed or bumped into any serious bugs on other areas on my TV.
Oki - will wait until others report back if 448 works for them too and then bump android's default.
I have been trying some of the "firetv" labeled test builds that have the PCM pass-through enabled, and as usual pass-through does not work.
In another post that I had made about early Krypton beta builds that pass-through did work, their was mention of a "correct pause burst".
Is this something that could be enabled or adjusted through the advancedsettings.xml?
kodi 17 rc3 20170104 firetv test build log
v17 already has correct pause bursts. If the IEC pcm hack builds and the normal builds don't produce PT sound for you, you have another issue. Something not related to kodi.
Edit: In your case, you have enabled "Adjust refreshrate" which causes issues and is therefore not suggested on Android at all. Second the log shows mediacodec issues after refreshrate switching. Try with a sample that works without mediacodec, e.g.:
https://dl.dropboxusercontent.com/u/5572...20Test.avi (disable mediacodec and mediacodec (surface)) try with
that build:
http://mirrors.kodi.tv/test-builds/andro...bi-v7a.apk
and with a normal kodi v17 build with the proper API
(2017-01-19, 22:22)fritsch Wrote: [ -> ]Edit: Making you a build with only 448 kbit/s and the livetv workaround that is too intrusive for general android: http://jenkins.kodi.tv/job/Android-ARM/10724/ <- will have "not so shitty" in its name :-)
Will test it on weekend, planning to watch some movies...
Not sure about LiveTV testing as I don't use it, I have separate STB provided by ISP and they use encryption so you cannot watch those streams without it.
For reference it is:
http://mirrors.kodi.tv/test-builds/andro...bi-v7a.apk
(2017-01-19, 22:34)fritsch Wrote: [ -> ]Oki - will wait until others report back if 448 works for them too and then bump android's default.
448 works on sony also. But...... I also (and most likely nobody) can't hear the difference so if you think that 384 is better option for wider compatibility I'm fine with that.
(2017-01-19, 22:56)fritsch Wrote: [ -> ]v17 already has correct pause bursts. If the IEC pcm hack builds and the normal builds don't produce PT sound for you, you have another issue. Something not related to kodi.
Edit: In your case, you have enabled "Adjust refreshrate" which causes issues and is therefore not suggested on Android at all. Second the log shows mediacodec issues after refreshrate switching. Try with a sample that works without mediacodec, e.g.: https://dl.dropboxusercontent.com/u/5572...20Test.avi (disable mediacodec and mediacodec (surface)) try with
that build: http://mirrors.kodi.tv/test-builds/andro...bi-v7a.apk
and with a normal kodi v17 build with the proper API
Please clarify on what situations adjust refresh rate should be enabled? I set to always adjust refresh rate , is it wrong setting?