Some channels live stream not working.

[GaryG 5]

This is a weird one. I used a third party app to test example channels (TV Land).
My Provider gives us three.
One is TV Land UHD and works but its latent in Emby.
One is TV Land West, it works fine in Emby.
Lastly is TV Land East, local to me, and it will not play at all in Emby, I get the "no compatible stream" popup.

I tested all three channels in another application, and they all streamed normally.
I monitored my memory usage when trying to run TV Land EAST in Emby, and memory usage was normal.
Also, I got the same result different browser. Chrome and Firefox.

My provider offeres hundres of channels and 98% work fine, Just a handful are problematic. TV Land is one of them.

Since all three channels work fine  in a different application,  I chose to post this here for expert opinion.

This is from the log.

2026-04-17 21:27:51.239 Info SessionManager: Playback stopped reported by app Emby Web 4.9.3.0 on Chrome Windows playing USA TV Land. Position: 0 ms. PlaySessionId: 524d44a8f6574e648ec0e5a2d724f934. IsPaused: False
2026-04-17 21:27:51.272 Info MediaSourceManager: Live stream 3c026c8d36242664d8fbca6608f2c206 consumer count is now 2
2026-04-17 21:27:51.273 Info SessionManager: Removed playSession 524d44a8f6574e648ec0e5a2d724f934 from session 1a0bddefe80a12ba441639bb73eba010
2026-04-17 21:27:51.273 Info DynamicHlsService-0HNKN7UQTEFA3:0000001A: ProcessRun 'StreamTranscode 93d7ab': Stopping ffmpeg process with q command for /var/packages/EmbyServer/var/transcoding-temp/0BDEC2/0BDEC2_0.ts
2026-04-17 21:27:51.273 Info PlaystateService-0HNKN7UQTEFA2:0000002D: http/1.1 Response 204 to host1. Time: 35ms. POST http://192.168.*.***:8096/emby/Sessions/Playing/Stopped?X-Emby-Client=Emby Web&X-Emby-Device-Name=Chrome Windows&X-Emby-Device-Id=59f135b1-da7a-4663-afe1-78c6ceda7ab1&X-Emby-Client-Version=4.9.3.0&X-Emby-Token=x_secret2_x&X-Emby-Language=en-us&reqformat=json.
2026-04-17 21:27:51.341 Info DynamicHlsService-0HNKN7UQTEFA3:0000001A: ProcessRun 'StreamTranscode 93d7ab': Stopping ffmpeg process with q command for /var/packages/EmbyServer/var/transcoding-temp/0BDEC2/0BDEC2_0.ts
2026-04-17 21:27:51.343 Info LiveStreamService-0HNKN7UQTEFAC:00000001: http/1.1 Response completed after client disconnected to 127.0.0.1. Time: 10089ms. GET http://127.0.0.1:8096/LiveTv/LiveStreamFiles/0a93eec644a745449ed97c1da649af71/stream.ts. Headers: Connection=close, Content-Type=video/mp2t, Date=Sat, 18 Apr 2026 01:27:41 GMT, Server=UPnP/1.0 DLNADOC/1.50, Transfer-Encoding=chunked, Cross-Origin-Resource-Policy=cross-origin, Private-Network-Access-Name=****_*******, Private-Network-Access-Id=7ff3c510313945559f288ad81e3ebac3
2026-04-17 21:27:51.344 Info DynamicHlsService-0HNKN7UQTEFA3:0000001A: AppendExtraLogData - Read graph file: /var/packages/EmbyServer/var/logs/ffmpeg-transcode-93d7abd2-3543-48ec-90fa-ad0835de773b_1graph.txt
2026-04-17 21:27:51.344 Warn DynamicHlsService-0HNKN7UQTEFA3:0000001A: AppendExtraLogData: Unable read graph output file: /var/packages/EmbyServer/var/logs/ffmpeg-transcode-93d7abd2-3543-48ec-90fa-ad0835de773b_1graph.txt
2026-04-17 21:27:51.345 Info DynamicHlsService-0HNKN7UQTEFA3:0000001A: ProcessRun 'StreamTranscode 93d7ab' Process exited with code 137 - Failed
2026-04-17 21:27:51.346 Info DynamicHlsService-0HNKN7UQTEFA3:0000001A: http/1.1 Response completed after client disconnected to host1. Time: 10126ms. GET http://192.168.1.167:8096/emby/videos/11140117/live.m3u8?DeviceId=59f135b1-da7a-4663-afe1-78c6ceda7ab1&MediaSourceId=3c026c8d36242664d8fbca6608f2c206&PlaySessionId=524d44a8f6574e648ec0e5a2d724f934&api_key=x_secret2_x&LiveStreamId=06044cf0e6f93cdae5f285c9ecfaaeb4_01413a525b3a9622ce6fdf19f7dde354_3c026c8d36242664d8fbca6608f2c206&VideoCodec=h264,av1&AudioCodec=mp3,aac&VideoBitrate=199904276&AudioBitrate=95724&AudioStreamIndex=1&VideoSideDataSubs=100&TranscodingMaxAudioChannels=2&SegmentContainer=ts&MinSegments=1&BreakOnNonKeyFrames=False&SubtitleStreamIndexes=-1&ManifestSubtitles=vtt&h264-profile=high,main,baseline,constrainedbaseline,high10&h264-level=62&TranscodeReasons=ContainerNotSupported,DirectPlayError&allowVideoStreamCopy=false&allowAudioStreamCopy=false.

Is this some type of memory issue?

Thanks in advance.

Edited April 18 by GaryG
Spelling

[GaryG 5]

Entire log attached, just tried again, same result @ 2026-04-20 16:35:55

embyserver.txt

[GaryG 5]

Alsio attached ffmpeg-transcode-6ee7962b-c252-4f94-84f4-4e86e257da1c_1.txt

ffmpeg-transcode-6ee7962b-c252-4f94-84f4-4e86e257da1c_1.txt

[GaryG 5]

Is this a provider issue? Should I close it out? Havent heard anyhting. Thanks

[GaryG 5]

Ive been looking at this a few days. Totally lost. CHannels in question stream fine using an IPTV app.
Emby  same issue. I cant figure out why.

Any opinions?

[Chillout 117]

I get this on some IPTV livetv channels too where it wont play in Safari or the Emby windows app but will play in Chrome.  Sounds like your issue it wont play in Chrome.  

I'm not sure , I think it has something to do with the video or audio codec that is being streamed some emby apps dont like.   I hope it gets resolved at some point but for now I have a work around.

[GaryG 5]

Its strange, Ive tested the specific URL for the problematic channel in VLC Media player, and other apps.
The stream is fine. Emby however it just times out. What is your workaround? Thanks

Edited April 23 by GaryG
Added text

[GaryG 5]

Ive compared the streams in VLC, the only difference I can see between the stream that works in EMBY vs the one that doesnt, are color references.
3 Items in attachment, strating with "Color Primaries".

The stream that does work in emby doesnt have these references. Maybe a red Herring?

Edited April 23 by GaryG
Spelling

[GaryG 5]

Can anyone from the EMBY team  explain what this means?
2026-04-23 13:14:18.310 Info MediaSourceManager: Live stream 3c026c8d36242664d8fbca6608f2c206 consumer count is now 6

This number is increasing daily I think. Was 5 yesterday

 

[Chillout 117]

My workaround is switching apps or I go to my backup provider.  The codec on the left does not work in Safari but works in Chrome.  The codec on the right works in Safari.

Something similar was happening in the Roku app but they have fixed in the beta. Maybe whatever they did to fix it in Roku would work across different apps. @ebr

edit: our "problem streams" have identical footprint.  Possibly we use the same source content. 

 

Edited April 23 by Chillout

[GaryG 5]

29 minutes ago, Chillout said:

My workaround is switching apps or I go to my backup provider.  The codec on the left does not work in Safari but works in Chrome.  The codec on the right works in Safari.

Something similar was happening in the Roku app but they have fixed in the beta. Maybe whatever they did to fix it in Roku would work across different apps. @ebr

edit: our "problem streams" have identical footprint.  Possibly we use the same source content. 

 

Interesting, The two codecs look identical except for those color references.
Just like my screenshot, H264 - MPEG_4 AVC (part 10) (h264). Resolution issue maybe? A mystery.

Edited April 23 by GaryG

[GaryG 5]

Ive tried  playing with every setting I can think of, transcoding, resolution, trailers off/on, subtitles off/on, hardware acceleration off/on.
Unless Emby team has anyhting to add, I'm at a loss.

[GaryG 5]

Ive tried different browsers as well. Same reult Firefox, Chrome, and Edge

[GaryG 5]

Some progress:
A server restart seems to fix this problem. I suspect the problem lies in the consumer count error:

"2026-04-23 13:14:18.310 Info MediaSourceManager: Live stream 3c026c8d36242664d8fbca6608f2c206 consumer count is now 6"

The server restart reset the number back to zero I presume. This is all guesswork, but the server restart did help.
 

[GaryG 5]

Update: After server restart the channel will play for a short period, and during playback there is latency. Then about 15 or 20 seconds in, it crashes, "no compatible stream".
EMBY TEAM: should I load up logs again??
 

[GaryG 5]

On 11/21/2025 at 12:27 AM, Luke said:

hi @Brian_Oblivionare you still having an issue with this using the latest versions of emby server and emby for android?

Im experiencing this similar issue currently. Thread is in "Live TV" forum

[GaryG 5]

Hopint to hear any opinion from the Emby team...

[GaryG 5]

Switched the stream on the problematic channel to 720 - 4 MBPS and it becomes more stable after server restart. Still a problem however.

Edited April 26 by GaryG

[Luke 42412]

HI, we are looking into this. Thanks.