All Activity

yup this was brought up and has been added to the 2.3.1 patch update this week, its going into testing tonight

Quick try of ATV app on Shield. One navigation thing. For the Recently Added Movies row, if I go to an item in the row i.e. its details screen, then hit the back button, it doesn't go back to the item I clicked on, it goes to the row above or below it. Seems to be just for that row. Might specifically be that row or whatever row happens to be in that position.

here is the logs from Emby. 2026-07-20 13:43:24.749 Info SessionsService-0HNN4ENRLPATS:00000001: http/2 POST https://host5/emby/Sessions/06356d41ca6e6e90cded6126cf310244/Playing/NextTrack?api_key=x_secret3_x. Source Ip: host52, UserAgent: node-fetch/1.0 (+https://github.com/bitinn/node-fetch) 2026-07-20 13:43:24.751 Info SessionsService-0HNN4ENRLPATS:00000001: http/2 Response 204 to host52. Time: 2ms. POST https://host5/emby/Sessions/06356d41ca6e6e90cded6126cf310244/Playing/NextTrack?api_key=x_secret3_x. 2026-07-20 13:43:47.630 Info SessionsService-0HNN4ENRLPATN:0000000D: http/2 POST https://host5/emby/Sessions/06356d41ca6e6e90cded6126cf310244/Playing/NextTrack?api_key=x_secret3_x. Source Ip: host52, UserAgent: node-fetch/1.0 (+https://github.com/bitinn/node-fetch) 2026-07-20 13:43:47.631 Info SessionsService-0HNN4ENRLPATN:0000000D: http/2 Response 204 to host52. Time: 1ms. POST https://host5/emby/Sessions/06356d41ca6e6e90cded6126cf310244/Playing/NextTrack?api_key=x_secret3_x.

so any update on this? or are we going to have to wait another year to get a Shrug and a "SoonTM"?

Is there any news about adding this feature?

It works for me on my android phone via the app. But it doesn't work on my fireTV, which currently is to be expected. But it does need an external browser, so maybe you don't have chrome installed? Can you provide screenshots and logs to help me debug?

Starting since last night, the Roku app has been timing out and not loading, alternating between not being able to sign in to the server on the Roku app, or displaying a generic "Error: Timeout" message before loading the home screen (see attached). Just a few minutes ago, I managed to get to the home screen and was able to send developer logs (4:20pm EST, today, 7/20/26). The Android app connects to my server just fine and plays files no problem, it's just been the Roku app for the past 18 hours or so. I tried uninstalling and reinstalling the Roku app, deleting the server and readding it, restarting the Roku system. Roku app logs already sent, also attached my server log file. embyserver.txt

https://forums.trakt.tv/t/broken-sign-in/117443/5 I'm using the latest Emby plugin.

NFO behavior: It writes its own, separate NFO file - not the media's existing/scraper NFO. Two things worth being precise about: Schema is different from Cheese's plugin - mine is <intros><introstart>...</introstart><introend>...</introend><creditsstart>...</creditsstart></intros>, whereas his used <markers><introstart>.... Filename is also different from the video's own basename - it's {SeriesName} ({TvdbId}) S{SS}E{EE} - {EpisodeTitle}.nfo, even in "save next to media" mode. So it sits alongside the video as an extra file, it doesn't touch/overwrite whatever NFO your metadata scraper (NfoMetadata plugin etc.) already writes for that episode. Migrating your situation - this is exactly the scenario I built a separate migration script for. Here's the order I'd do it in, since it matters: Back up what's currently live first. Run the "Backup Intro/Credits Markers" task now, pointed at a fresh folder. This captures the intros you set after Cheese's plugin died (the ones with no backup anywhere yet) before anything else touches them. Convert Cheese's old NFO backups separately. There's a standalone script for this (not part of the plugin, one-time tool): migrate_nfo_to_json.py (I'll attach it to the repo's Discussions/Issues if it's not obvious where to find it - let me know). Point --output at a different folder than step 1's, not the same one. Merge carefully, don't just dump both folders together. For any episode where step 1 already produced a JSON (meaning it currently has live markers), skip step 2's file for that same episode - you don't want an old Cheese backup silently overwriting a marker you set more recently. Only bring over step 2's files for episodes that have no file from step 1 (i.e. markers you'd lost entirely). Then run Restore once against the merged folder. The reason for the ordering: Restore replaces whatever intro/credit markers currently exist for an episode with whatever's in the backup file - so if you restore an old file for an episode that already has newer markers set, you'd lose the newer ones. On the version question: the prebuilt DLL in the release is only built/tested against 4.10.0.18 - I haven't verified compatibility with .17 or earlier. Building from source against your own server's SDK DLLs (steps are in the README) would be the safer bet if you don't want to wait for the full update, since it compiles against whatever version you're actually running. Happy to help further if the merge step above needs more detail once you're looking at your actual folder contents.

Have you revoked your pin, then try to get a new one?

OK I'm not sure what the issue is yet. The beta channel has a possible fix in case you'd like to try that.

Danke Lukas, das habe ich jetzt gemacht, somit ist auch der Button weg. Danke auch an @ebr für die Hilfe. So ist es erst mal angenehmer von der Bedienung. Ich habe zwar noch nicht verstanden, warum ein Banner der seit ca. Januar 2026 besteht und ohne diesen Extra Button dargestellt wurde, jetzt plötzlich diesen Button bekommen hat. Ist aber kein Problem, diesen Begrüßungsbanner wieder zu deaktivieren, wenn damit auch dieser Button wieder verschwindet. Danke Jedenfalls, ihr seid wie immer Super und sehr Hilfsbereit

I forgot to follow up on this post until now. Life has been hectic to say the least. I have enabled this setting in my beta instance, and so far everything looks good, but I haven't had the chance to fully test with various clients as of yet. I would imagine all clients should work as intended though. I've kept my primary and secondary emby instances on stable to reduce the chance of things breaking since I don't have a lot of time to troubleshoot when a regression happens on the beta. I am very much looking forward to this coming to stable though. The sooner this is released for everyone the better IMO.

The most reliable way is to setup port forwarding and then skip upnp. If your router lets you do that, then I would go that route.

@bingbong69_ now working thanks

They just lost 2 more people after this, one of them being the founder and project lead. It looks like both are leaving due to stress/life etc. on good terms. Still doesn't bode very well as there was no announcement as to who will be stepping up to fill the roles. I'm hoping the remaining team can keep everything on track after losing several key people. Regardless of how people feel about Jellyfin being forked from Emby, options/competition are a good thing for end users.

Hello, Yes, the next song plays after it ends on the echo group. Thanks for looking this.

Yes, we were going through your connection guide on the "External Connections" steps because Emby works on our home network only. It seems to be an issue setting up the UPnP. We have two routers essentially and we started with the Optimum router (the one provided by our internet provider).

Makes perfect sense, I'll get on my emby server and do some more testing then, thank you!

Even with it disabled I still get no playback and we really need live TV to direct play same as the emby client as transcoding is not the best option, if you have a couple of users

Hi @GrimEvil! I'm pretty sure the live tv woes are caused by this: go to Settings > Playback > Video > Live TV Direct - disable this toggle for live tv direct play the web client issue was just reported for some emby users yesterday and I'll have it patched for a new plugin coming out later today

And neither do I in my testing. We'll have to keep an eye on it.

Hi @graytinc! I'm pretty sure its caused by this: go to Settings > Playback > Video > Live TV Direct - disable this toggle for live tv direct play

I am having issues playing 4k channels (livetv).

Pangolin 1.21.0 release enables the possibility for persistent sessions. If I interprete this correctly, this would solve your headaches with attaching the headers to every e.g. image request. https://pangolin.net/news/1-21-release