A developer says an unofficial Kodi 22 community build can play Dolby Vision FEL on Windows with NVIDIA graphics. In a post on the Kodi forum, dane-9 describes testing the build with a GTX 1080, driver 582.78, a Denon AVR-X3800H receiver and an LG C1 display. Read the developer’s account.
Dolby Vision FEL uses a full enhancement layer alongside the main video stream. The developer says the build decodes both and combines them on the GPU, using RPU metadata. That processing path is what makes this report relevant to people trying to play Profile 7 FEL video from a Windows PC.
Treat the GTX 1080 setup as the concrete test case; other GPU models belong to separate reported claims.
What the developer says the build can play
dane-9 lists Dolby Vision Profile 5, Profile 7 MEL and FEL—including polynomial and MMR FEL—and Profile 8.1. For a Profile 7 FEL 4K Blu-ray remux, the developer reports no missed enhancement-layer frames and says playback could switch among Dolby Vision, HDR10 and SDR.
The described TV-led output carries a 12-bit 4:2:2 Dolby Vision tunnel inside an 8-bit RGB signal. The developer also says the build does not require the Dolby Access app, the Dolby Vision extension or EDID changes.
The reported NVIDIA test scope
The detailed test account is specific to a GTX 1080 with NVIDIA driver 582.78, connected through a Denon AVR-X3800H to an LG C1. AVPasión’s report, published on November 18, 2026, also names the RTX 5070 and RTX 5080 as GPUs used for playback. Those model claims are reported by AVPasión; dane-9’s forum post describes the GTX 1080 setup.
The developer says a 5090 had not been tested. Driver 617.42 appears in the account as a static analysis, not a playback test.
Why the implementation changes HDMI timing
In dane-9’s explanation, the build uses NVAPI and a custom HDMI timing to signal Dolby Vision output. The custom timing assigns HDMI_VIC 3 to 3840×2160 at 23.976 Hz. The developer says the usual 3840×2160 timing is labeled CTA VIC 93, which does not prompt the NVIDIA driver to create the vendor-specific InfoFrame needed for this output path.
The account describes the timing change as part of the playback path: playback startup applies the custom timing, and stopping playback reverts it. That mechanism, like the profile support and test results, is the developer’s description of the unofficial build.