Tvheadend

The Kodi Plugin is using the HTSP.

I believe that HTSP is "only" an own protocol to control the stream etc.

Video / Audio is delivered like pass ... (IMHO)

Then i guess the default profile should be set to HTSP and not PASS if I use the Kodi Plugin.

HTSP is the protocol that the Kodi plugin uses to talk to Tvheadend. If you are using the "Pass" profile, Tvheadend does not additional processing, but merely sends the stream to Kodi exactly as it receives it.

What is "best" is subjective and varies based upon your setup. If your Tvheadend machine can do hardware transcoding, then perhaps you want to transcode. If you haven't purchased the MPEG2 license for the RPi, perhaps you want to transcode. Profiles are subjective, and how they're best used is dependent upon your particular setup.

Thanks for your help.
I know "best" is relative, but my logic was if HTSP is the protocol Kodi plugin uses, it is perhaps a good choice to use htsp and not pass. I use TVH backend for transcoding if I use Andoid app for watching live tv, but that uses a different profile with transcode. The Rpi2 is my main media player now, and I have all the codecs available, and I don't want any transcoding to my Rpi2. I read the HTSP protocol description, but I still can't decide if it is better and more advised to use then to simply pass the stream as is to Kodi.

If you don't want any transcoding, the just use pass. By default, Tvheadend doesn't have any profiles defined and will just pass the stream through; no configuration necessary.

i use the same setup ... tvheadend server as backend and rpi2 with kodi als frontend.
i only use HTSP ... working perfect.

If you want more Informations about HTSP read this : https://tvheadend.org/projects/tvheadend/wiki/Htsp/158

:-)

True, that page does give an overview of the API. However, it hasn't been updated in over a year, and since that page was last updated, there have been ~60+ commits/changes to the API.

Tvheadend's weak spot is its complicated/involved setup, coupled with a rather sparse and lacking documentation.