Limitations of Native player vs. Swiftfin (VLCKit) #953
holow29
started this conversation in
Development
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
There is more information in #519, but for the sake of consolidation, I thought I would put some points of interest here in terms of comparing the Native Apple AVPlayer implementation with that of Swiftfin's VLCKit implementation. This might be hepful when MPV is implemented to look at how this changes.
The main question is why one might choose the Native player over Swiftfin VLCKit or vice versa.
Given the versatility of Jellyfin, many of these limitations can be overcome. For example, Jellyfin can transcode audio/video to suit what the player requests, including HDR->SDR tonemapping. It can also take text-based subtitles and convert them to other text-based subs like SRT to WebVTT, or it can burn-in image-based subs to the video stream. However, the goal for people is usually to avoid transcoding, so knowing these limitations might aid in that.
(This does not take into account the interface differences right now; for example, switching subtitles/audio streams is not working correctly on Native player or on Swiftfin VLCKit when transcoding.)
My general advice is the following:
Use native if all are true:
Otherwise, use Swiftfin VLCKit.
Beta Was this translation helpful? Give feedback.
All reactions