<dt><b>HTSP Streaming</b>
<dd>
- Enables access to streaming for the HTSP protocol (Showtime, XBMC etc.).
+ Enables access to streaming for the HTSP protocol (Movian, Kodi etc.).
<dt><b>Streaming Profile</b>
<dd>
<dt><b>HTSP DVR</b>
<dd>
- Enables access to video recording functions for the HTSP protocol (Showtime, XBMC etc.).
+ Enables access to video recording functions for the HTSP protocol (Movian, Kodi etc.).
<dt><b>All DVR</b>
<dd>
<p>
First line gives clients originating from 192.168.0.0 - 192.168.0.255 network
access to streaming functions. Typically you would use this for your
-local media players at home (All though Showtime can prompt for username & password
+local media players at home (All though Movian can prompt for username & password
in its HTSP client)
<p>
The second line adds a user with world wide access who might want to modify
Tags are used to define a set of channels.
Notice that nothing prohibits a channel to be a member of multiple tags.
Also, there is no requirement to configure tags for running Tvheadend
- itself. It is, however, required if you run Tvheadend together with Showtime.
+ itself. It is, however, required if you run Tvheadend together with Movian.
<p>
The tag-sets are used for:
<ul>
<li>Searches in the EPG.
- <li>Display of channel groups in the Showtime Media player.
+ <li>Display of channel groups in the Movian Media player.
</ul>
<p>
<dl>
- <dt>Why does Tvheadend deliver data over TCP to Showtime? I thought it was
+ <dt>Why does Tvheadend deliver data over TCP to Movian? I thought it was
bad to use TCP for realtime sensitive traffic?
<dd>
'HTSP' - the protocol used for streaming TV, sending meta information
- updates and RPC between Tvheadend and Showtime uses a transmission
+ updates and RPC between Tvheadend and Movian uses a transmission
scheduler with multiple queues on the Tvheadend side. This means that
Tvheadend can measure the available bandwidth between itself and the
mediaplayer and when congestion happens it's even capable of dropping
links and DSL connections with zero picture/audio artifacts.
<p>
It's possible to get view drop statistics and bitrates directly in
- Showtime. (Open the menu when watching a TV-channel and switch on
+ Movian. (Open the menu when watching a TV-channel and switch on
'Detailed Information')
</div>
<dt>Input sources
<dl>
- <dt>DVB-T, DVB-C, DVB-S, DVB-S2 and ATSC.
+ <dt>DVB-T, DVB-C, DVB-S, DVB-S2, ATSC and SAT>IP.
<dd>
Multiple adapters are supported.
Each adapter can receive all programs available on the currently
</dd>
<dt>Analog TV
<dd>
- Using the Video4Linux2 API. Currently, only PAL is supported.
+ The IPTV extension URL - pipe:// allow to process any MPEG-TS input.
+ FFMPEG or LIBAV library can be used to produce analog to digital
+ conversion.
</dd>
</dl>
<dt>Output targets
<dl>
- <dt>HTSP (Home TV Streaming Protocol), supported by Showtime Media player and <a href="http://www.xbmc.org/">XBMC</a>
+ <dt>HTTP (Web Protocol), supported by <a href="http://www.videolan.org/vlc/">VLC</a>, <a href="http://www.mplayerhq.hu">MPlayer</a>
+ <dt>HTSP (Home TV Streaming Protocol), supported by <a href="http://movian.tv">Movian Media player</a> and <a href="http://kodi.tv/">Kodi</a>
+ <dt>SAT>IP Server
<dt>The Built-in Digital Video Recorder
</dl>
All setup and configuration is done from the built in web user interface.
Even so, all settings are stored in human readable text files.
- <dt>Fully integrated with HTS Showtime Media player.
+ <dt>Fully integrated with HTS Movian Media player or Kodi HTS PVR addon.
<dd>
All channel data and their grouping, EPG and TV streaming is conducted over a
single TCP connection.
<dd>
Requires a card server (newcamd and capmt protocol is supported).
+ <dt>Hardware based CSA descrambling
+ <dd>
+ Requires the standard dvben50221 linuxdvb library.
+
<dt>Internationalization
<dd>
All text is encoded in UTF-8 to provide full international support. All major