Jump to content

PlaySessionId is ignored for live tv channels


pünktchen

Recommended Posts

pünktchen

@Luke this is not new, but i've always wondered why the PlaySessionId is ignored for live tv channels? Multiple simple requests to 

http://127.0.0.1:8096/videos/{ChannelId}/stream?Static=true&PlaySessionId=123456789&api_key={Key}

opens multiple seperate streaming sessions. I can see this because multiple ts files are created in the transcoding folder.
In contrary to live tv, normal library videos behave differently.

http://127.0.0.1:8096/videos/{Id}/stream.ts?PlaySessionId=123456789&api_key={Key}

There an existing stream is used if the following requests have the same PlaySessionId. Only one ts file is created in the transcoding folder.

This strange live tv behaviour is the main reason why it makes it so difficult to use Emby's live tv as a m3u playlist in Kodi's Simple PVR addon.
Kodi sends up to four request before the actual playback happens. That means also up to four ts files in Emby in a very short time frame, which strains the server.

Link to comment
Share on other sites

That's not what playsession is used for. Truthfully, it's incorrectly named. It should have been called StreamSessionId, because it is only meant to manage a single video stream.

What you want is LiveStreamId, in which case, you need to use the api to open a live stream, which our apps generally do as part of their /playbackinfo calls. Then from there you get a url that you can hit as many times as you need, and then finally, you use the api to close the live stream.

Link to comment
Share on other sites

pünktchen
4 hours ago, Luke said:

What you want is LiveStreamId, in which case, you need to use the api to open a live stream, which our apps generally do as part of their /playbackinfo calls. Then from there you get a url that you can hit as many times as you need, and then finally, you use the api to close the live stream.

I know about this. But this is not suitable for a simple iptv client/player. Those apps want a single url to open a stream and cannot make a request to something that returns a json response beforehand. Also as you've mentioned the way with a LiveStreamId explicitely needs a stop request to close the live stream which those apps will never do.
By using the single request from my start post, the live stream will be closed automatically when the client disconnects, but there the PlaySessionId is not used.

So why you are making live tv so difficult? Why are there two different concepts for more or less the same thing - video and live tv streaming?
Is there a technical reason behind it or is it just grown historically?

It would be so easy to use Emby's live tv streams in Kodi without all those limitations and the solution you've have promised 16 month ago has never seen the light of the day: https://emby.media/community/index.php?/topic/64827-get-live-tv-channel-stream/&do=findComment&comment=812427

 

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...