# mpv-Yaozhi: a Windows-only mpv bundle with Blu-ray menus and Dolby Vision P7 > mpv-Yaozhi packages a self-built Windows mpv core with a Chinese-language uosc front end, disc navigation and a configuration assistant. It is a convenience distribution for Windows 10 and 11, not a portable mpv config you can drop onto Linux or macOS. **Yaozhil/mpv-Yaozhi** — mpv-Yaozhi 自制整合包 -重构mpv播放内核 - 自制 UI 优化、可视化配置脚本、弹幕、中文 stats - Repository: https://github.com/Yaozhil/mpv-Yaozhi - Stars: 756 · Forks: 29 - Language: Unknown - License: NOASSERTION - Published: 2026-09-17 · Updated: 2026-09-17 · Language: en - Canonical page: https://hysenlabs.com/projects/yaozhil-mpv-yaozhi ## What mpv-Yaozhi actually is, and who the bundle is for mpv-Yaozhi is a third-party Windows distribution of mpv, described in its README as "面向 Windows 的高画质、原盘导航、沉浸声与中文交互一体化 mpv 播放方案". The README states plainly that it is a community-maintained third-party release scheme and not an official mpv version. It builds on mpv and on dyphire/mpv-config, and it adds a self-compiled Windows x86-64 core, a portable configuration, and a Chinese-language interaction layer. The target user is narrow and specific. The system requirements list Windows 10 or 11 64-bit, a graphics card that supports Direct3D 11 with a reasonably recent driver, and for HDR, passthrough or 5.1.4 to 9.1.6 output, a matching display, sound card, Windows audio interface, HDMI/eARC device or amplifier. Nothing in the README mentions Linux, macOS, ARM or a headless build. If your media box runs Linux, this project is not aimed at you at all. The problem it solves is assembly work. A stock mpv install gives you a player and a config language; getting Blu-ray disc navigation, Dolby Vision profile handling, PGS subtitle brightness control and a Chinese track picker means collecting scripts, a Java runtime for BD-J menus, and a core built with the right patches. The README frames the result as an out-of-the-box package: the full archive already contains the player core, the portable config and the BD-J Java runtime, so the README says ordinary users do not need to install mpv or Java separately. ## How the self-built core, uosc front end and disc navigation fit together The architecture is a bundle rather than a service. A self-maintained Windows x86-64 mpv core sits at the root, with D3D11, gpu-next, Schannel and libcurl, plus a custom patch chain. Around it sits portable_config, and on top of that a heavily customized uosc provides the unified main menu, right-click menu, playlist, track list and subtitle search. The README describes the root mpv-Atmos.exe as a separate experimental entry point for object-audio software decoding and status display; it does not replace the main mpv.exe, and when its components are unavailable the project falls back to the normal playback path. Disc navigation is wired into playback chain construction. The README says local Blu-ray directories, optical drives and ISO files enable disc navigation when the playback chain is built, and if First Play jumps straight to the feature, the player requests the disc main menu once at an appropriate moment. Both HDMV and BD-J Java menus are supported, and the full package bundles a Java runtime matched to the player core. Remote Blu-ray ISO over AList/OpenList is deliberately different: it stays in main-title mode and does not start a menu VM, to avoid extra network random reads and startup delay. Dolby Vision handling is described as internal decoding, reshaping and display adaptation for P5, P7 MEL/FEL, P8.1 and P8.4. For P7/FEL the README states that the base layer, enhancement layer and RPU stay associated, and that fast precise seeking filters damaged enhancement-layer recovery frames so they do not briefly blend into the picture. The gpu-next path separates UHD HDR/DV embedded PGS from external or SDR graphical subtitles: the former can follow the video into the HDR mapping chain, the latter is handled conservatively as SDR/sRGB. That is a design decision with a visible consequence, and it is the kind of split that matters more than any single toggle. ## Installing mpv-Yaozhi and running a first Blu-ray folder There is no package manager route. The README points to the Releases page for the latest integrated package, and the repository layout confirms it: LICENSE.md, README.md, docs/ and portable_config/ at the top level, with binaries distributed through releases rather than committed. The install steps in the README are four actions: download the latest integrated package from Releases, extract the archive completely into a writable directory (do not run it from inside the compression tool), double-click mpv.exe or drag a media file onto the player, and optionally run the configuration assistant that sits next to mpv.exe so it can detect your hardware and pick a suitable configuration. If you want double-click playback from Explorer, the README mentions a "注册视频文件关联" script in the root directory; it says file association is written only for the current user. No command-line install is documented, so the only concrete artefact to handle is the extracted folder containing mpv.exe and portable_config. The first real use is to open a local Blu-ray folder or ISO. The README states that local Blu-ray directories, optical drives and ISO files enter disc navigation when the playback chain is built, and that if First Play goes directly to the feature the player requests the main menu once at a suitable moment. In practice you drag the disc root or the ISO onto mpv.exe, or pass it as the file argument. The README gives keyboard entry points for the menu once you are inside: Home or Ctrl+m returns to the Blu-ray menu root, and Ctrl+M shows or hides the pop-up menu. It also notes that menu artwork, language, animation, pop-up menus and optional items come from the disc itself, and that an image without an authored menu will not have one generated by the player. That last sentence is the honest boundary of the feature: the player drives a menu that exists, it does not invent one. ## Where the bundle stops being the right tool The clearest limitation is the platform. Windows 10 and 11 64-bit only, with Direct3D 11 required. A user on Linux who wants the same disc-menu behaviour gets nothing from this project; the README does not offer a Linux build, and the self-built core is described as Windows x86-64. Similarly, the 9.1.4 and 9.1.6 speaker layouts are only covered for software channel order and PCM ordering, while the README says 5.1.4 and 7.1.4 have been covered for Windows device opening and real-device channel routing. Final speaker output still depends on the sound card, driver, Windows audio interface, HDMI/eARC chain and the end device. If your receiver chain is the weak link, the player cannot fix it. Audio passthrough has a documented recovery path rather than a guarantee. The README says that when a device rejects the current bitstream the player exits the incompatible state and returns to PCM, to avoid silent or stuck playback afterwards. That is a sensible fallback, but it also means the four passthrough modes (all, Dolby only, DTS only, off) can silently degrade to PCM on a picky HDMI path. The AI upscaling and interpolation features are off by default and conditional. RIFE builds an AI 2x chain only when it can preserve the source resolution and existing upscaling quality; when it cannot run in real time it falls back automatically rather than downsampling first. HDR10 and HDR10+ can use a path that keeps PQ, BT.2020 and per-frame information, but Dolby Vision, HLG, HDR Vivid, disc playback and VFR scenarios keep the original colour chain and native smoothing. In other words, the more exotic your source, the less the enhancement stack does. Anyone buying this for frame interpolation on Dolby Vision discs should read that as a no. Finally, the releases carry an internal label. The three most recent are named v1.0.5-internal, v1.0.5-2-internal and v1.0.3-internal, each described as 内测更新. The README does not document a stable channel, a rollback procedure or a changelog beyond the 近期更新 list, so a user who needs predictable behaviour has to decide whether internal builds are acceptable. ## How it differs from a plain mpv plus mpv-config setup The obvious alternative is mpv itself with dyphire/mpv-config, which the README names as one of the two foundations of this project. The difference is in what you supply. With upstream mpv you install the player, choose a build, write or copy a configuration, add scripts for menus and track selection, and source a Java runtime if you want BD-J menus. The README of mpv-Yaozhi states that the full package already contains the core, the portable config and the BD-J Java runtime, and that ordinary users do not need to install mpv or Java separately. That is the entire trade: you accept a fixed, opinionated bundle in exchange for skipping the assembly. The second difference is the interaction layer. Upstream mpv ships a minimal OSC and a command interface; this project replaces that with a customized uosc and adds Chinese menus for track selection, key binding management, format badges, danmaku, intro and outro marking, music mode and playback history. The README notes that key binding management under 杳知 > 快捷键绑定列表 lets you search, modify and restore shortcuts in Chinese without directly rewriting the original input.conf. That is a real behavioural difference from editing input.conf by hand, and it also means your edits live in the project's layer rather than in the file you may already know. A third difference is the release model. Upstream mpv is a general-purpose player for many platforms; this is a Windows x86-64 distribution with its own patched core and its own release cadence. Choosing it means tracking this project's releases for core updates rather than following mpv upstream directly. ## Maintenance, licence and what to check before upgrading The repository is not archived, and the last push was on 2026-09-16, so the project is being worked on right now. The three most recent releases all fall in September 2026, and the newest, v1.0.5-2-internal, carries the same timestamp as the last push. That tells you the release train is active, but it also tells you the visible releases are internal builds rather than a numbered stable line. Upgrade cost is mostly re-extraction. The README's install steps are download, extract fully, run mpv.exe, optionally run the configuration assistant. There is no documented in-place updater, no documented migration of an existing portable_config, and no documented rollback to a previous release. Because the archive contains the core, the portable config and the Java runtime together, replacing it wholesale is the path the README describes, and any local edits inside portable_config are the thing at risk. The README does not say how those are preserved across versions. On licensing, the repository ships a LICENSE.md at the top level, and the README's badge reads "License: See details" with a link to a 来源与许可 section. The project is a redistribution that bundles mpv, a Java runtime and third-party scripts, so the licence that binds you is a combination rather than a single identifier, and the repository metadata itself reports NOASSERTION. That is a signal to read LICENSE.md and the 来源与许可 section before redistributing or shipping the package inside another product. This is not legal advice; it is a note that the licence question here has more than one component. ## Conclusion Adopt it if you watch UHD Blu-ray rips, ISO images or Dolby Vision P7 content on a Windows 10 or 11 x86-64 machine and want the Chinese menus, disc navigation and format badges without assembling an mpv config yourself. Do not adopt it for Linux, macOS, ARM or a headless HTPC, and do not treat it as a drop-in replacement for a hand-written mpv.conf you already understand. Before you rely on it, verify that your GPU driver exposes Direct3D 11 and that the release you download is a full package rather than an internal build, because the recent releases are labelled 内测更新 and the full archive is the only distribution the README describes. ## FAQ ### What does MPV stand for? The README does not expand the acronym. It only identifies mpv as the upstream player that mpv-Yaozhi is based on, and states that this project is a third-party distribution rather than an official mpv version. ### What is mpv on Linux? The README does not describe mpv on Linux. It describes mpv-Yaozhi as a Windows 10 and 11 64-bit distribution with a self-built Windows x86-64 core, so nothing in it covers a Linux build or Linux behaviour. ### Does mpv-Yaozhi need Java or a separate mpv install? The README says the full integrated package already contains the player core, the portable config and the BD-J Java runtime, and that ordinary users do not need to install mpv or Java separately. It adds that no environment variable changes are needed for disc menus. ### Which platforms does mpv-Yaozhi support? The README lists Windows 10 and 11 64-bit, a Direct3D 11 capable graphics card and a reasonably recent driver. HDR, audio passthrough and 5.1.4 to 9.1.6 output additionally require matching display, sound card, Windows audio interface, HDMI/eARC or amplifier support. ### Does mpv-Yaozhi upscale or interpolate every video? No. The README says the upscaling and interpolation features are off by default and enabled independently. RIFE builds an AI 2x chain only when it can keep the source resolution and existing upscaling quality, and falls back automatically otherwise; Dolby Vision, HLG, HDR Vivid, disc and VFR content keep the original colour chain and native smoothing. ### How do I get back to the Blu-ray menu while a disc is playing? The README states that Home or Ctrl+m returns to the Blu-ray menu root during feature or segmented playback, and Ctrl+M shows or hides the pop-up menu. It also lists Chinese entries under 杳知 > 蓝光圆盘菜单 for the menu root, title menu, play shortcut menu and one level up. ## Sources - [Issues](https://github.com/Yaozhil/mpv-Yaozhi/issues) - [README](https://github.com/Yaozhil/mpv-Yaozhi/blob/main/README.md) - [Releases](https://github.com/Yaozhil/mpv-Yaozhi/releases) - [Yaozhil/mpv-Yaozhi on GitHub](https://github.com/Yaozhil/mpv-Yaozhi) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/yaozhil-mpv-yaozhi