All Activity

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

Could you please give a step-by-step for going back to the previous version, thanks

While creating a lock around every connection WILL solve the problem, it 100% will cause pauses and a less that ideal user experience In my page, its a JS page that makes about 25 API calls to the server. When the long running call hit, with a lock on every db call, the page would stop loading at that call. Its only about 600ms but it was long enough to be frustrating. There are two changes that I had to make to fix this correctly. Every DB connection gets its OWN db connection. Dont share a global one. Before I had 1 instance that was shared. Make sure you open it in with PRAGMA journal_mode=WAL. This allows sqlite3 to be reentrant which also fixed my random crash issue, and the user experience is much better. The combination of these two changes, the page fills in the faster calls and sometime later fills in the one long running (its only about 600ms, but its enough to feel slow when holding up everything. Since there are enough calls, you dont really feel like you are waiting at all

Integrating with sonarr/radarr is a good way to get your plugin banned.

When you add a home screen section, you can choose to have it appear as Cards or as a Spotlight.

TV Show Status 2.5.110.0 Nothing you have saved changes — every setting keeps its name and default. New Settings page rewritten: grouped into sections, clearer labelling. Upcoming: show Season Finale — per-episode, lands only on the finale. Web browser only Flag a premiere or finale this many days ahead (default 7) — stops badges appearing weeks early Say 'Airing' for a show that is mid-season, with its own colour Fixed The badge position setting now applies to the web badge as well as the drawn one No finale flagged on a season that has not started yet Web badge colours now match the drawn badge for mid-season and finale Known limitation In the Emby apps, a premiere or finale badge appears on every Upcoming card of that show, not just the episode it refers to. Unaired episodes have no artwork of their own, so every card requests the same series image and the server cannot tell them apart. Only a browser can, which is why the per-episode badges are web-only To mark those episodes on TV and phone apps, the companion plugin Trakt Air Dates can put the words in front of the episode title instead EmbyTVShowStatus.dll TV-Show-Status-settings-2.5.110.pdf

I have a Roku device that I used to be able to change the default tab when you open the "movies" or "TV Shows" folder from My Media to Genres instead of always opening in Suggestions. Is that still possible with the new version ? Am I missing something? I have it working fine on all the other platforms... Anyone? @ebr

Had a quick go with .92 and scrolling is a major improvement. Thanks very much.

Where is this? I don't see it in the user Settings > Home Screen.

It uses this same system so you can try and set that in Emby and see what happens. But unless they changed it since last i tried my self, then i don't think it will work. Sadly out of my hands since it's an Emby limitation. You can make a feature request post, that will inform the developers that there are users who want it.

Te envío lo solicitado. embyserver.txt

I would recommend avoiding AV1. The support for it is almost none existing outside PCs. So if you want to stream to your TV, or what ever box you have connected to it, Emby would have to transcode. That will cause lower picture quality and cause your Emby server to work hard transcoding (if you don't have a modern GPU). TL:DR. AV1 is trash outside PC use.