Documentation › Integrations
Integrations
TinePlayer is set up so that it can be integrated as a video player for other applications. Support is included for some popular media libraries like Jellyfin and Kodi, but custom integrations can be scripted using the command line arguments.
How Applications Reach It
Two ways: something casts a video to TinePlayer over the network, or something launches TinePlayer with a video as an argument.
| Application | How it reaches TinePlayer |
|---|---|
| Jellyfin | Casts over the network. TinePlayer appears as a player in the Jellyfin app, which then acts as the remote for pausing, seeking, volume, and switching soundtracks and subtitles while the video plays. |
| Kodi | Launches TinePlayer as an external player for a selected video. TinePlayer then plays the video and when finished hands watch progress and control back to Kodi. |
| Plex | Reaches TinePlayer through Kodi integration, with its add-on set to direct paths. |
| Anything else | A shortcut, a script, a file manager, or another application launches TinePlayer with the video as an argument. It plays, and exits. |
Scripting Your Own
Everything can be passed to TinePlayer at startup via command line arguments: which video, which soundtrack on which output, which subtitles, whether to open the media page or start playback immediately, and more. It is just a matter of building the command that suits your integration.
- Command Line - every option, and how to run it on each platform
- Advanced Integration - launching TinePlayer from a script, a shortcut or another application
One Thing to Check First
Whatever hands the video over has to provide a direct path or direct stream to the original file. Something that streams a transcoded or converted version will be stripped of any additional soundtracks or subtitiles and TinePlayer will not be able to route multiple audio tracks to different outputs.
Next: Jellyfin - casting and remote control.