Assistance debugging live tv playback - same provider, diff client

[jaybird2203 20]

Hi all, 

Been having a bit of an issue as of the stable 4.8.3 roll out. Using the official docker on unraid and live tv playback used to be stable for my use case but seems that since moving to the 4.8.3 release that the server is not releasing the streams when the client stops/changes channels. To recover it requires a server restart to reset the play counts and enable playback again. The clients are using Kodi 20.4 and the Emby for Kodi next gen 9.2.14 and about to try the latest releases. 

Been hitting this a few times as of late with no change to the setup other than updating the server to 4.8.3, using the previous stable release didn't see this issue with the same client configurations above. 

logs of the playback are attached but only from once the issue is encountered.

If there's a specific entry/steps to replicate/commands to run to see the streams that are not released please let me know and I'll try to recreate then provide logs for when that specific stream is stopped. 

2024-03-12 213716.022 Error Server .txt

[jaybird2203 20]

Hi all, 

Apologies for the rapid topic creation, been digging into 2 scenarios with live tv and was looking for some assistance. 

For this situation I'm a bit stumped so here's the background - I'm in the process of changing the setup used (moving from xteve to another) and on the new backend when using the web client I am able to playback the stream "without issue" so the playback starts and can view the content. While when attempting to playback using Kodi the playback immediately fails. Same stream playing back at the same time the web client is watching or different stream makes no difference - immediately fails on kodi client.

In the logs I see what appear to be start of transcode related messages since I would assume the webclient can't playback the stream which makes sense but for the kodi client playback to immediately fail doesn't. I've attached the log entries for both scenarios - web client playing back the stream first, the the kodi client playing back the same stream after the web client stopped playback. 

Web intial playback start.txt

[jaybird2203 20]

Would appear that when some streams fail/error out (like my other thread) that the stream remains counted and increments against total play count until the container is restarted. 

Will need specific details on what else to provide here, my other thread here, has an example of an immediate stream crash that does not appear to be caught so stream removed from playback counts. 

[Luke 40083]

Hi there, please attach the complete emby server log file. thanks.

[jaybird2203 20]

Hi Luke,

Restarted server after adjusting from xteve to the new so these are just isolated to playback entries. Logs show playing back the channel with the web browser to show the backend functions, stopping the playback in the web browser, then a few moments later starting the same channel through Kodi and immediate failure. 

embyserver.txt

Not sure if this will be asked but I use the same epg setup for both the xteve backend and the new. Playing back the channels through Kodi on xteve has no issues like this where the stream immediately fails. 

Edited March 15, 2024 by jaybird2203

[Luke 40083]

14 hours ago, jaybird2203 said:

Hi Luke,

Restarted server after adjusting from xteve to the new so these are just isolated to playback entries. Logs show playing back the channel with the web browser to show the backend functions, stopping the playback in the web browser, then a few moments later starting the same channel through Kodi and immediate failure. 

embyserver.txt 77.43 kB · 0 downloads

Not sure if this will be asked but I use the same epg setup for both the xteve backend and the new. Playing back the channels through Kodi on xteve has no issues like this where the stream immediately fails. 

Hi, thanks for this. I think I will need a debug server log. Can you temporarily enable debug server logging, then repeat the process and provide the debug log? Thanks.

[jaybird2203 20]

Hi Luke, 

As requested. 

embyserver.txt

Just to rule this out - confirmed that the same channel when played direct in Kodi with the same m3u file used in Emby also has no issue so its only this backend/emby/kodi pairing specifically. 

Edited March 16, 2024 by jaybird2203

[jaybird2203 20]

Hi @LukeJust realized that the 2 topics I created were combined into one.

These are two distinct scenarios with different setups - the 4.8.3 server not thinking streams are stopped when they are, or crashed, until the container is rebooted vs debugging the different backend that immediately fails on Kodi playback. 

The server not releasing the stream when the client stops/shuts off should not be an issue in my setup specifically - I have 2 clients only and 2 concurrent streams available from my provider hence setting 2 in the server. When this situation happens the primary client is the only one that is attempting to watch the streams but immediately fails with the max stream count being hit. 

Should they not be two different threads or are they both actually related? 

[jaybird2203 20]

Hi @Lukeany further information required? Looking to keep this moving, and at least pointed to the correct team, in the correct direction if possible. 

[Luke 40083]

On 4/1/2024 at 1:06 PM, jaybird2203 said:

Hi @Lukeany further information required? Looking to keep this moving, and at least pointed to the correct team, in the correct direction if possible. 

So you're saying it plays successfully but just doesn't clean up afterwards? 

[jaybird2203 20]

I have two scenarios since the threads were combined so I'll outline each. 

Client playback immediate failure scenario - using my "test" backend it plays fine on Emby web/android app and transcodes as needed, immediately crashes on client start of the same channel. Playing the channel direct on client, not through Emby, and the client can playback without issue. I restart the server container once transitioned back to my "production" backend to resume standard operations. Debug logs were attached Mar 16.

Stream not cleaning up thus hitting max stream count scenario - using the xteve backend which works on my client and web, the playback over the day(s) appears to be fine (may have a crash or two but haven't checked the full logs). Eventually the error regarding max stream limit reached is encountered by the client yet no streams are active in the "now playing" section. Requires a server restart to restore/clean out. To workaround this I set the stream limit to 0. Logs attached on the first post. 

Edited April 5, 2024 by jaybird2203

[Luke 40083]

OK can you temporarily enable debug logging, then recreate the issue and attach the debug server log? Thanks.

[jaybird2203 20]

Already posted above on Mar 16, link below.

https://emby.media/community/index.php?/topic/127362-assistance-debugging-live-tv-playback-same-provider-diff-client/&do=findComment&comment=1340760

[jaybird2203 20]

Issue still present on 4.8.4

[Luke 40083]

HI, have you updated to Emby Server 4.8.6? Has that helped?

[jaybird2203 20]

Issue still present on 4.8.7 - web can playback from the new backend but client cannot

[Luke 40083]

2 hours ago, jaybird2203 said:

Issue still present on 4.8.7 - web can playback from the new backend but client cannot

OK can you please attach a new server log? 

@quickmicare you able to reproduce?

[quickmic 1610]

10 hours ago, jaybird2203 said:

Issue still present on 4.8.7 - web can playback from the new backend but client cannot

Did you try enable transcoding for live tv in the plugin config options?

I see in your logs, the webclient requests hls streams (master.m3u8) while the plugin queries the native stream (static=true)

[jaybird2203 20]

Just opened to check the plugin settings and noticed the plugin updated to 10.0.23 so can't say what the exact settings were prior - playback I usually leave as default though. See below as they're set currently. I'll see about getting new logs though - hopefully in the next few hours. 

 

[quickmic 1610]

Try enable Transcode livetv.

[jaybird2203 20]

@quickmicTranscoding solely video allows Kodi to playback. Is there any idea why the stream needs to be transcoded in the first place?

New backend direct to kodi plays without issue, so same initial stream that Emby would request. Only when going through Emby does it immediately crash unless the plug-in enables transcoding so seems a bit off. 

Edited May 22, 2024 by jaybird2203

[quickmic 1610]

I haven't read the complete thread, I just check your "Web intial playback start.txt"

I got the impression, you are saying direct play works on web playback but not on Kodi.

That's not true, you did NOT use direct play in web playback. You tansencoded the stream.

http://host2:8096/emby/videos/1861364/master.m3u8?DeviceId=b273efaa-f25a-4f98-ad9a-1bab624a515a&MediaSourceId=0dcfd6112774e0cdb52a2f8b108eacc6&PlaySessionId=5920491661664071b623abc1fd45a423&api_key=x_secret1_x&LiveStreamId=06044cf0e6f93cdae5f285c9ecfaaeb4_01413a525b3a9622ce6fdf19f7dde354_0dcfd6112774e0cdb52a2f8b108eacc6&VideoCodec=h264,h265,hevc,av1&AudioCodec=mp3,aac&VideoBitrate=159903322&AudioBitrate=96678&MaxWidth=3840&AudioStreamIndex=1&VideoSideDataSubs=100&TranscodingMaxAudioChannels=2&SegmentContainer=ts&MinSegments=1&BreakOnNonKeyFrames=True&SubtitleStreamIndexes=-1&ManifestSubtitles=vtt&h264-profile=high,main,baseline,constrainedbaseline,high10&h264-level=62&hevc-codectag=hvc1,hev1,hevc,hdmv&TranscodeReasons=ContainerNotSupported.

-> TranscodeReasons=ContainerNotSupported

 

while Kodi did use direct play:

http://host2:8096/emby/videos/1861364/stream?static=true&LiveStreamId=06

Now as you enabled transcoding, Kodi does the same as Web UI and it works.

Before you ask, I don't know why. It depends on your stream sources.

[jaybird2203 20]

@quickmic

Apologies, I wasn't saying that Emby was providing the stream direct when the web client was playing but that Kodi is able to play the source stream direct without involving Emby. 

@Lukeis there any documentation on what the best native stream formatting is preferred for the least amount of conversion/transcoding? 

The new backend has some FFMPEG functionality so I can transcode there to reduce the amount the server needs to transcode for each client.

[quickmic 1610]

13 hours ago, jaybird2203 said:

@quickmic

Apologies, I wasn't saying that Emby was providing the stream direct when the web client was playing but that Kodi is able to play the source stream direct without involving Emby.

got you, must be something on the pass though Emby server.

[Luke 40083]

On 5/23/2024 at 10:14 AM, quickmic said:

got you, must be something on the pass though Emby server.

@quickmichave you tried this?