c38eb2a623
* Set up CI with Azure Pipelines [skip ci] |
||
---|---|---|
.ci | ||
deployment | ||
Jellyfin Server | ||
Jellyfin Server.xcodeproj | ||
.gitignore | ||
AUTHORS.md | ||
ffmpeg LICENSE.txt | ||
LICENSE | ||
package-lock.json | ||
package.json | ||
README.md |
Jellyfin for macOS
Part of the Jellyfin Project
Jellyfin for macOS is a launcher/wrapper built in Swift and Objective-C.
Build Process
Getting Started
The Build Process instructions need to be updated, and will be coming soon.
FFmpeg Download
It's recommended to use a static macOS build of FFmpeg, such as Zeranoe's Builds.
At the time of writing, please use ffmpeg-4.2.2-macos64-static.zip.
Troubleshooting
The project didn't build!
Please review the error inside Xcode. If a build failed, it is likely because the resources aren't in the right directory.
The project built, but Jellyfin didn't launch. Xcode shows an error.
This is because Jellyfin needs to be placed in the app bundle so it can be launched. This is currently a manual process, which will be automated for future use.
Does the console show a Failed to bind to address
message? You may already have a copy of Jellyfin running on your computer. This can happen if you did not shutdown a separate Jellyfin install, or if you clicked on "Stop" inside Xcode. Use Activity Monitor to find and quit any open Jellyfin process.
The project built, but Jellyfin didn't launch. There are no errors I can see.
This wrapper may launch the Web UI too quickly. This will eventually be configurable. In the meanwhile, you can use the Jellyfin icon in the menu bar to launch the Web UI again.