IINA

You can get IINA through several sources. For the latest stable and beta releases, visit the GitHub release page or the IINA official website. If you want to try out the latest features and improvements before they are officially released, you can download the nightly builds from our Nightly Download Page. Nightly builds are generated by GitHub automatically for every commits, which might be buggy and unusable. If you find a bug, please follow the contributing section and file an issue. IINA uses mpv for media playback. To build IINA, you can either fetch copies of these libraries we have already built (using the instructions below) or build them yourself by skipping to these instructions. 1. Download pre-compiled libraries by running By default the shell script downloads universal binaries. You can download arch-specific binaries using --arch ( universal , arm64 or x86 64 ) Files are downloaded in parallel (5 concurrent downloads by default). You can change this using --parallel (from 1 to...) If you want to build an older IINA version you must change DYLIBS DOWNLOAD PATH in the script to download the corresponding dylibs. For example, 2. Open iina.xcodeproj in the latest public version of Xcode. IINA may not build if you use any other version. 1. Build your own copy of mpv. If you're using a package manager to manage dependencies, the steps below outline the process. 2. Copy the corresponding mpv and FFmpeg header files into deps/include/ , replacing the current ones. You can find them on GitHub (e.g. mpv), but it's recommended to copy them from the Homebrew or MacPorts installation. Always make sure the header files have the same version of the dylibs. 3. Run other/parse doc.rb . This script will fetch the latest mpv documentation and generate MPVOption.swift , MPVCommand.swift and MPVProperty.swift . Copy them from other/ to iina/ , replacing the current files. This is only needed when updating libmpv. Note that if the API changes, the player source code may also need to be changed. 6. Open iina.xcodeproj in the latest public version of Xcode. IINA may not build if you use any other version. 8. Add all the imported .dylib files into the "Copy Dylibs" phase under "Build Phases" tab of the iina target. 9. Make sure the necessary .dylib files are present in the "Link Binary With Libraries" phase under "Build Phases". Xcode should have already added all dylibs under this section. IINA is always looking for contributions, whether it's through bug reports, code, or new translations. If you're looking to contribute code, please read CONTRIBUTING.md — it has information on IINA's process for handling contributions, and tips on how the code is structured to make your work easier. If you'd like to translate IINA to your language, please visit IINA's instance of Crowdin. You can create an account for free and start translating. Please do not send a pull request to this repo directly, Crowdin will automatically sync new translations with our repo. If you want to translate IINA into a new language that is currently not on the list, feel free to open an issue.