All Activity

Around 30-40 seconds.

I'll hope this discussion can be kept up in an good way in another thread. Because there are some good points and things to take care of. So to my question. If I have understood this right, I need to have my Shield set to 4K in the GUI. To be certain I can watch 4K in 4K? For most streaming (NRK, HBO, Disney+ etc), I don't need 4K. So I think my Shield generally perform better in 1080p for the GUI. But if I must have it in 4K to be SURE 4K is shown in 4K, so be it. But I don't think it is the right way to solve it.

I will add this feature in the next update

Could you introduce additional category/toggle: "Airing" for "When a show is still running and the current season next episode's date is known'" so it shows that instead of "Returning" for running shows and Next air date OFF, so there's distinction between currently in-progress and actually returning shows? Thanks. Edit: And ofc color picker for it.

Carplay would be great!

Emby for Android? Same thing happens on the Android TV version. My client is a NVIDIA shield displaying on a LG OLED TV.

Hi vdatanet The "spotlight" on the home page images are cut off on the top on my screen . was not sure if this is an issue on my end since no one else reported it.

What client are you playing with? Paul

As far as I know, the background of Emby will be chosen from the Screensaver set in Apple TV. I like to use the Snoopy one, but this will turn the background in Emby to brown, which I don't like. Could we get regular themes to choose from within the app itself? The same ones you can choose on the Android app like Dark, Light, Blue Radiance or even the Apple TV Theme. Any possibility of this?

It's on my list

I sent you a message.. Also, please tell me your location.. England, United States East Coast.. Thank you

That is against the Emby TOS so nobody can or will help you with that, sorry.

sorry, the weather postponed my visit. I will reply here when I try it - should be in the next few days though.

Seems the issue was the emby server, i updated it to the latest version and doesnt heat up anymore.

I attach the file that causes the problem. If I rename it to xxx.ell.srt the playback hangs. If I leave it as xxx.gre.srt the playback starts fine I also attach a screenshot of files related info Novak Djokovic - The Wolf in Winter (2026) 1080p AC3.gre.srt

Sadly wife and kid use it too so i can’t :[

Your options are (1) install a server. Quick Start (2) ask a friend who runs a server to let you use theirs. (3) access an illegal server ( Paid service ) (no further instructions here). If someone else's have a talk with them. Emby does not host your server and do not supply media files.

it's a little overkill. If you want to save money, just do what I did and grab a laptop off eBay with a smashed screen. 12th gen or higher is all that's really needed. I have mine being fed by a 24 bay UNRAID server.

I got it configured and it reported it found the user and media library. But when I ask alexa to have ear wax play some music, as soon as it trys to hand off it reports "Sorry I had trouble finding music in your library". Don't know if this is a Wmby config issue or what. I used to use the Plex service till it was disabled. Then switched to Emby and trying to get it to play my music on Alexa devices.

Sample attached, 50 MB. It's synthetic — no copyrighted frames — but it's an arithmetic twin of the episode from my first post: declared duration 1326.336 s (RunTimeTicks 13263360000) last video frame 1325.324 s -> the video track is 1325.365 s long last audio packet 1326.304 s (AC-3, 32 ms frames) h264 1080p 23.976 + AC-3 192k stereo, no subtitle tracks, keyframe every 2 s So the segment list should come out identical to the one in the thread: ceil(1326.336 / 6) = 222 segments, 0..221, 1332.000 s promised for 1326.336 declared. 220 starts at 1320.000 and is real media; 221 starts at 1326.000, which is after the last video frame. Segmenting it at 6 s should stop SegmentComplete at Index=220 with End=1325.365 — the same line as the log I posted. To reach the 220 case: play to the end and let 221 fail, so the player steps back to 220; or, equivalently, open a fresh session and ask for 220 on its own. It's the jumped request that returns 500, not the segment. I ran it against 4.10.0.29 in a clean container before sending, with Emby Web on Safari: seek to 35 seconds from the end and let it play out. It ends in the same place my first post did — frozen on the last frame, session still open: 05:55:22.209 GET .../hls1/main/220.ts -> 200 (2 ms) 05:55:22.215 GET .../hls1/main/221.ts 05:55:22.216 Starting transcoding because currentTranscodingIndex=null 05:55:22.220 ProcessRun 'StreamTranscode 06922e' ... -ss 00:22:06.000 -noaccurate_seek ... SegmentComplete=video:0 Index=221 ... Frames=32 filename=D7DD1C_221.ts FfRunException: Error starting ffmpeg 05:55:22.276 Response 500. Time: 60ms 05:56:22.222 PlaySession has gone idle while playing. Position: 1325390 ms. IsPaused: False Same -ss 00:22:06.000 as the production log in my first post, and again the segment is written and announced before the 500 comes back. Two things worth knowing before you spend time on it. With fMP4 segments the same file doesn't 500 at 221 — the request just never returns (45 s, until the client gives up), which is the hang I reported on the .29 beta. And requesting segments out of the blue with a script does not reproduce either symptom: jumped on their own, 220 and 221 both answer 200. It needs a player actually arriving there. Built with ffmpeg, if you'd rather make your own: ffmpeg -f lavfi -i "testsrc=size=1920x1080:rate=24000/1001" -frames:v 31777 \ -c:v libx264 -preset veryfast -crf 30 -pix_fmt yuv420p -profile:v high \ -force_key_frames "expr:gte(t,n_forced*2)" video.mkv ffmpeg -f lavfi -i "sine=frequency=440:sample_rate=48000" -ac 2 -t 1326.336 \ -c:a ac3 -b:a 192k audio.mka ffmpeg -i video.mkv -i audio.mka -map 0:v:0 -map 1:a:0 -c copy sample.mkv Cua HLS - mostra sintetica 22 min (2026).mkv

@SamES

Webstream me met le message "Unable to détermine the type of source list"

Yes, the file is UTF-8 text, with CRLF line terminators. The problem does not appear in the web app or in the ios app.

As far as I’m concerned And what does that mean? Making yet another empty promise that you won’t keep? You promised me that SMB thing years ago, but you never actually did it.

Did you try following the steps in the OP?