2018-08-15, 19:45
(2018-08-15, 17:51)brazen1 Wrote: Been running it through its paces for a while and am no where close to done:Nice to hear that aosp for you the fix is working.
The main problem with the PCF honoring rules for defaulting to the correct player is fixed. YiPpY! So is player selection via the 'Play using' menu. YeEhAw! Alt + F4 command to the focused external player quits and returns to KODI in focus with resolution and frame rate correctly applied just as it did using 17.6. All is perfect including engaging/disengaging HDR etc.
However, there is a new problem and if memory serves me correct, it too was always present in my past tests with v.18 so it's not exactly new or caused by your fix imo. Again, going by distant memory.
When I play 3D with any player, the correct player opens, the resolution switches from 2160 to 1080 correctly and 3D frame packed mode engages. The 3D playback is all perfect as it was in 17.6. Quitting the player is where the problem begins. The external player closes and 3D disengages on the panel but the return to focused KODI results in it no longer in fullscreen. It appears windowed in the top left corner and the image of the GUI is not complete (mostly just a black box although some images are present when scrolling the distorted tiny GUI). Alt + F4 kills KODI and the Windows desktop returns to the correct resolution and frame rate.
I windowed KODI instead of the required fullscreen for external players and the results were the same. Fullscreening the windowed KODI in the top left corner after the error resulted in a fullscreened black window with a tiny KODI still in the top left corner.
Not sure a debug log would do any good and no idea what else I can supply should you or another decide to try and tackle it? It would require 3D capability and understand most no longer have it. Uhg...
Regarding the resolution issue, I also had this when using MPC and kodi. The issue was that I had to set the desktop and kodi resolution to 4k (2160p) and disable kodis resolution switching.
Since then, the issue disappeared.
pOpY