Hello everyone,
I have a problem with the video OSD that seems inherent to CoreElec. Indeed, when we use the Fuse 2 Skin on the PC or Android version of Kodi, the name of the chapters is displayed perfectly when we skip forward with the “Next Chapter or Big Step Forward” shortcut, as you can see here :
which is not the case with Kodi CE where only the fast forward time information “+06:17” is displayed.
Hi vpeter, first of all thank you for your valuable help.
Next, have you tried it with the Skin Fuse 2? Because as Jjd-uk explains it well “Ok so he using that area for multiple things whereas Estuary has an exclusive area for the Chapter info. So he’s probably half right in that he relies on Player.SeekOffset being empty, but personally I would always want that info displayed but currently Artic Fuse 2 limits it to only when certain conditions are met, however that will be a conscious design on his part. Code is at https://github.com/jurialmunkey/skin.arc…#L937-L960”
This is one strange skin at least for me. Presssing key i and then up button and nothing happen. How to even check it if even basic things doesn’t work as on regular skin.
On PC, when you move forward with the “Next Chapter or Big Leap Forward” shortcut (in the OSD Video), the chapter names are displayed perfectly, as you can see here:
This is not the case on CoreElec. The skin developer, Jurial, says that Player.SeekOffset is empty.
(The shortcut to move from one chapter to another is by default the up arrow on PC. And when you press the up arrow, the chapter number and name should appear.)
“The problem is that on CoreELEC, the seekoffset is set when searching by chapter, while on Windows and Android it is not set, resulting in inconsistency between platforms.”
Thank you very much for this solution, Vpeter. I’ll give it a try!
Do you know the reason for this specific feature of CoreElec that leads to this different behavior from other platforms? Is it related to a function essential to CE’s behavior? In other words, do you know if it would one day be possible to integrate a native solution into CoreELEC to permanently adjust this behavior, without requiring manual modifications with each skin update. So that the behavior is common to other platforms and the same for all users.
However, I fully understand the technical challenges this represents, as well as the resources it must require.