VLCKit is a generic multimedia library for any audio or video playback needs on macOS, iOS and tvOS.
When will you need VLCKit?
Frankly, you will need it whenever you need to play media not supported by QuickTime / AVFoundation or if you require more flexibility.
Here are some other common use-cases:
CocoaPods is a dependency manager for Cocoa projects. You can install it with:
gem install cocoapods
To integrate the latest VLCKit into your project, specify it in your Podfile:
source 'https://github.com/CocoaPods/Specs.git'
target '<macOS Target>' do
platform :macos, '10.9'
pod 'VLCKit', '~>3.3.0'
end
target '<iOS Target>' do
platform :ios, '8.4'
pod 'MobileVLCKit', '~>3.3.0'
end
target '<tvOS Target>' do
platform :tvos, '10.2'
pod 'TVVLCKit', '~>3.3.0'
end
Then run pod install.
Carthage can also pull in VLCKit. Install it with brew install carthage, then add the appropriate binary line to your Cartfile:
binary "https://code.videolan.org/videolan/VLCKit/raw/master/Packaging/MobileVLCKit.json" ~> 3.3.0binary "https://code.videolan.org/videolan/VLCKit/raw/master/Packaging/VLCKit.json" ~> 3.3.0binary "https://code.videolan.org/videolan/VLCKit/raw/master/Packaging/TVVLCKit.json" ~> 3.3.0Then run carthage update.
API documentation of VLCKit is available online and within both the source code as well as binary downloads. Except as indicated, all the APIs are the same on macOS, iOS and tvOS.
You can find more documentation on the VideoLAN wiki.
VLCKit is under the LGPLv2.1 license. See COPYING for more license info.
The LGPLv2.1 allows our software to be included in proprietary apps, as long as you follow the license. Some key points:
For further details, please read the license and consult your lawyer with any questions you might have.
VLCKit is an open-source project hosted by VideoLAN, and we happily welcome all kinds of contributions.
Pull requests are more than welcome — please use a descriptive title and description. You can also look through the currently open issues on GitLab and pick one that interests you. If you prefer the classic approach, you can submit patches; see the wiki page on how to send patches.
If you ever need help, the forum is always there for you.
Did you find a bug? Create an issue on GitLab or on the bug tracker.
For matters related to the VLCKit and LibVLC APIs, join the LibVLC bindings community on Discord.