Repository navigation
FAQ
Player Process Info — Kodi's own name for its playback information overlay
(the Player process info entry of the video OSD). TinyPPI is a compact,
richer replacement for it.
No. It requires CoreELEC 22 or later on Amlogic hardware: the readings come from the Amlogic driver and from the side-data InfoLabel only CoreELEC 22 publishes. On anything else the add-on refuses to open its views.
No. CoreELEC 22 introduced Player.Process(video.sidedata), which every
Dolby Vision and HDR reading depends on. Versions before 22 are rejected.
It is designed not to. The overlay reads each value once per 100 ms refresh and only writes window properties that changed; side data is parsed only when it changes; per-title facts are read once a second. The service starts its heavy work five seconds after Kodi so it does not compete with start-up. The web dashboard builds nothing while no page is connected.
TinyPPI registers two font sizes in the skin's Font.xml and asks Kodi to
reload the skin so they take effect. It happens once per skin (and again after
a skin update replaces Font.xml).
No. The overlay is laid out for 1080i; skins with a 720p folder are refused.
Anything free during fullscreen playback. A color button on the remote is a
good choice. Use NotifyAll(script.tinyppi,open_overlay) for the fastest
response — see Launching and Keymaps.
Yes. Map one key to NotifyAll(script.tinyppi,open_overlay) and another to
NotifyAll(script.tinyppi,open_dialog) (or RunScript(script.tinyppi,dialog)).
Launch mode only affects RunAddon(script.tinyppi).
Kodi reports the coded frame (a letterboxed 2.39:1 film in a 16:9 frame reads 1.78). For Dolby Vision, TinyPPI uses the RPU's L5 active area to compute the ratio of the visible picture. Without L5 data it shows Kodi's value.
The side data is captured before CoreELEC's own conversion, so TinyPPI shows
the stream as the file carries it. The converted flag in the metadata view's
Stream section tells you a conversion happened.
A full enhancement layer reconstructs a 12-bit picture. MEL and single-layer profiles are 10-bit, SDR 8-bit.
Both are Dolby Vision enhancement layers on profile 7 discs. A FEL (full enhancement layer) carries real picture data that extends the base layer to 12 bit; a MEL (minimal enhancement layer) carries next to nothing. TinyPPI colors the tag green (FEL) or orange (MEL) by default.
The VS10 engine does not accept them as inputs; the driver has no mode group for either. The same applies to Dolby Vision titles that also carry HDR10+ metadata. See VS10 Output Modes.
The driver cannot switch directly between those outputs. TinyPPI performs two complete switches through SDR, as you would by hand.
No. Everything — the page, its icons and the posters — is served by the add-on from the box. Posters come from Kodi's own texture cache.
Not directly, and you should not forward its port. Use a VPN into your home network. Under a non-home host name the dashboard asks for the token even for reading.
Yes — up to six live pages. All of them are fed by one snapshot builder, so five open tabs cost the box the same as one.
Not by reading. Only the controls (VS10 switching, remote, playback, watched marks) act on the box, and all of them need the token.
Add your own to addon_data/script.tinyppi/imax_titles.txt; propose general
additions as an issue or pull request. See IMAX Detection.
English, German, Arabic, Hungarian and Simplified Chinese. The dashboard uses the same strings. Want to add one? See Translations.
Yes — the code is AGPL-3.0-or-later. A fork needs its own name and artwork, because the TinyPPI name, logo and artwork are not covered by the code license. See License and Credits.
User guide
- Installation
- Getting Started
- Launching and Keymaps
- The TinyPPI Overlay
- Dolby Vision Metadata View
- VS10 Output Modes
- Codec Logos
- Channel Layout Graphic
- IMAX Detection
- Colors and Themes
Web dashboard
Reference
Developers
Project