All Activity

Which app specifically? Android TV app or the newer standard Android app? If the latter, have you configured the app to not hide the transport buttons? Select 'No' here in the App Settings under 'Playback'

server "emby Version 4.10.0.40" via docker on "Kubuntu 26.04 LTS" Client - "LG TV LG 32LN613V LED" with android stick "realme 4K Smart Google TV Stick" both "Emby for Android TV" version 2.1.55g (tv.emby.ambyatv) and "Emby for Android" version 3.5.55 (com.mb.android) (separate thanks to similar names for both app!) I checked "use external player" when i try to open any video it tries to open VLC but quickly closes VLC window. And it seems that episode is finished and then it tries to play next and again and again.. How to use external player? I've got on installed VLC, Vimu.. Logs from emby server embyserver.txt hardware_detection-63924713369.txt

That was why I said do not use the national lineup but use the one for your post code - either Local Over The Air Broadcast or Freeview - then 700 would be BBC R1 and would auto match to the channel from the tuner during initial setup On the National lineup BBC R1 is 181 and channel with callsign KISSRDO is 700 - so please delete that lineup and use Freeview or the Local Over the air Broadcast The standard OTA lineups to use would show like these highlighted one in the green boxes - The Freeview one would show the relevant one for your post code The initial response from Gracenote was positive and they are looking into getting the airings for Radio 1's New Music Show with Jack Saunders and Charlie and Jerry corrected. The bad news is that each show/series that has issues needs to be investigated and reported separately. I will look into Matt and Mollie next

I'm also not opposed to change, but for me the Android app has massive compression artifacts when streaming from tvheadend whereas the ATV app does not. See attached comparison.

It seems multi word search on the latest Unified Emby Android release causes the entire server to hang which will interrupt other users. I cannot repeat this behaviour using the Android for TV app, web browser or the exact same unified Android APK on my phone. it only seems to be affecting the last unified Emby app installed on Google TV's Very strange. I've attached a log, according to claude: What's actually happening: Every time you search, the mobile Emby app fires several parallel queries behind the scenes to populate different result sections (movies, shows, episodes, people, etc.). One of those is: IncludeItemTypes=Person&Recursive=true&SearchTerm=<your query> That's a recursive search across your entire library for matching cast/crew — not a lookup of "people whose name matches," but a scan checking every item's Person associations against the search term. On a 1PB library, this single query takes 29–31 seconds to complete, every time (How I Met Your Mother: 29380ms, 30995ms, 30001ms; Breaking Bad: 29993ms, then 10351ms on a retry). embyserver.txt

Ye, i hope it comes soon. I did the user config to copy the home sections to all my users, but apparently it also did the notifcations and I got spammed with alot of watch reports on my discord. Is it possible to have a list of all the things copied instead of just "etc."?

For the next Beta as well?

I removed dotnet-9.0.14 and dotnet-host-9.0.14, but when I reinstall dotnet8-8.0.20 it installs dotnet-host-9.0.14.

Congrats! Incredibly faster! But using the multiword search via Firefox (Webclient) seams to work. When trying to create a shuffle play on my music repo via the Webclient - it takes around 2 minutes and 5 seconds until the player starts. The CPU load then is around 100% (but on one core only - I have attached 4 to the VM). When using the Windows App - the search terminates on the server after nearly exactly 60 seconds, but the circle in the App is still turning. Sound a bit like a timeout to me, memory on the server is at 11%.

Live TV channels are now excluded from the global search. My family and myself really loved that feature. How can we get it back? I don't know why it was taken away. Could someone please instruct me on how I can get emby to include live tv channels in the global search when searching for content.

Set everything up again on the desktop and it works fine streaming to the TV. Whatever the issue was, it looks like it was something to do with the laptop itself, but since (as said) it's completely broken now, it's probably not something that would've been easy to diagnose and / or fix anyhow.

Hi, we'll do some testing on this. Thanks.

Hi Luke and Emby Team, I recently experienced a critical cascading issue due to an accidental path selection, and I would like to propose a safety guardrail to prevent other users from running into the same problem. ### What Happened: 1. I already have existing libraries configured with specific child paths, e.g.: - `/mnt/media/movies` - `/mnt/media/tvshows` 2. When creating a new library, I accidentally selected the **parent folder** `/mnt/media` instead of `/mnt/media/new_subfolder`. 3. Emby immediately executed a **Rebase**: `Rebasing 121614 /mnt/media/tvshows to be underneath 122603 /mnt/media` 4. Realizing the misclick seconds later, I went back and clicked "Delete" on the `/mnt/media` path. 5. **The Cascade Disaster**: Because the parent was deleted, Emby cascaded and deleted the database entries and metadata caches for all existing child libraries (`Deleting path /config/metadata/library/...`), then recreated them with **brand-new Folder IDs** (`122604`, `122605`...). 6. As a result, Emby treated all existing thousands of files as brand-new first-time imports, triggering an unexpected 7+ minute full library scan, TMDB scraping, and media info extraction across the entire server. --- ### Proposed Feature Requests / Solutions: #### Option 1: Path Validation & Warning Dialog (Immediate UI Guardrail) When a user adds a path in the library setup, please add a simple path-hierarchy check: * Check if the selected path **contains (is a parent of)** or **is contained by (is a child of)** an existing configured library path. * If a conflict is detected, display a warning modal before applying: > *"Warning: The path `/mnt/media` is a parent folder of existing library `/mnt/media/tvshows`. Adding this path will alter existing library structures. Are you sure you want to proceed?"* #### Option 2: 'Staged Changes / Draft Mode' for Path Editing (Best Root-Cause Prevention) Currently, adding or deleting a path immediately fires a live API call that instantly mutates the database. * If Emby simply staged path changes in the UI and only committed them when the user explicitly clicks a final **'Save & Apply'** button (similar to OpenWrt or enterprise router configs), any accidental path misclicks corrected within seconds would never touch the live SQLite database at all. * This would eliminate the entire cascade disaster at the root with minimal backend architectural disruption. --- Even experienced users can make a simple misclick in a folder picker. Adding either a warning check or a staging step would protect users (especially cloud mount / large NAS users) from accidental destructive rescans. Thank you for considering this usability improvement!

Search is broken on this release. Multi word searches from Android tv apps hang the server for everyone else.

The latest stable has now introduced this problem to me.

Oh my, it's also unavailable in my PM. Thanks for the link, in fact I did not see this until now...

i like alot of these new ui features even if i very rarely find any of them useful. the main gripe i have is that during payback i used to be able to hit the down arrow and hit the skip to next episode button to get quickly to the next ep. now thats missing and its alot more steps to do the same thing. is there a way to re-enable this back into the playback ui? thanks

OK, please attach the ffmpeg log as well. Thanks.

Thanks Luke

Thank you. I did eventually reproduce. I've got it resolved.

I see this in the debug console.

I can try.

Nice work. Few scenarios falling through the cracks and/or need additional logic implemented, though: 1) Last episode in the last season does not get "Season Finale" badge for Returning Series that has next season data already available. Example: Silo (itemid=1180641), S03E10: "1180641": { "Status": "Returning Series", "NextAirDate": "2027-07-08", "LastAirDate": "2026-09-03", "NextEpisodeNumber": 1, "NextSeasonNumber": 4, "NextSeasonEpisodeCount": 1 2) Last episode in the last season present on the server for Returning Series gets "Season Finale" badge even though there are missing/to-be-added episodes. Example: The UnXplained (itemid=1348049), S08E17 "1348049": { "Status": "Returning Series", "NextAirDate": null, "LastAirDate": "2026-08-28", "NextEpisodeNumber": null, "NextSeasonNumber": null, "NextSeasonEpisodeCount": null

HI there, are you having a problem that we can help you with? We are very happy to help.

Hello ax37x, ** This is an auto reply ** Please wait for someone from staff support or our members to reply to you. It's recommended to provide more info, as it explain in this thread: Thank you. Emby Team