All Activity

Don't worry about this, it will be fixed. Do you see any other issues in this area?

That's definitely a bug. The toggle should always be rightmost.

Hi @softworkz Button reordering on genericitemlists Heres a video showing what i think is an issue. The rows below a removed genericlistitem change their button order (same for added). Hopefully i am not embarrassing myself with a coding mistake (code attached).. but i dont think i have control over button order so hopefully i am in the clear. 2026-07-04 15-41-17.mp4 ai thinks theres an issue in createListButton in the client side ManageComingSoon.zip \UI\AddMovie

In another post I mentioned I attempted to write an XML script for Emby Live-TV in an attempt to give me finer control over the EGS feeds I am using, populate program ICONs and control new programs are recorded but reruns not recorded. I am not sure if what I discovered are true bugs, or if Emby just handles them differently. I hope it is just me not having the proper understanding of how Emby Live-TV handle EPG XML and I can be educated on where I went wrong. Live TV / XMLTV: programme-level <icon>, <category>, <new>, and <previously-shown> are ingested but appear to have no effect Summary When using a third-party XMLTV guide source (merged from an XMLTV backend, not Emby's own Guide Data service), Emby's Live TV importer appears to read <title>, <desc>, and <start>/<stop> from <programme> elements, but does not appear to act on several other standard/documented elements: <icon src="..."> on <programme> never populates artwork for the corresponding Live TV "Shows" item, even though channel-level <icon> (on <channel>) works correctly and displays channel logos as expected. <category>movie</category> — using the exact, case-sensitive value configured in Dashboard → Live TV → Setup → XmlTV → Movie categories — does not appear to trigger the movie classification/internet-lookup behavior implied by that settings page, and does not affect artwork population either. <new/> and <previously-shown start="..."> do not appear to affect DVR "record new episodes only" behavior. Reruns are still scheduled for recording even when the programme is correctly tagged <previously-shown start="..."> referencing an earlier, correct original air date, and the true first airing is correctly tagged <new/>. Tested both self-closing (<new/>) and explicit open/close (<new></new>) syntax for all of the above elements, in case a non-standard internal parser was missing self-closing tags specifically. No difference in behavior was observed between the two forms. Environment Emby Server version: 4.10.0.17 (beta) Platform: Docker on QNAP NAS Running QuTS Hero. Guide Data Source: XmlTV (Dashboard → Live TV → Setup → Guide Data Sources), pointed at a self-hosted, merged XMLTV URL (not "Emby Guide Data") TV Source: M3U, pointed at a self-hosted M3U URL Both served by a self-hosted playlist/EPG manager (Stationarr) that merges multiple upstream XMLTV sources with one custom enrichment source layered on top What's confirmed working correctly To rule out the source data as the problem, the following were independently verified before filing this report: The XML is well-formed and successfully parses in Python's xml.etree.ElementTree (a strict parser) with no errors. Emby is downloading and parsing the file successfully — confirmed via Emby's own server log during a manual "Refresh Guide Data" run: the file downloads (200 OK), and programme counts are correctly saved per channel, with no errors or warnings logged. Channel-level <icon> works perfectly — channel logos display correctly throughout the Guide, Channels, and On Now views, confirming Emby's XMLTV parser does read <icon> in at least one context. The <category> value exactly matches Emby's own configuration — copied verbatim from the "Movie categories" field on the XmlTV source's settings page (see screenshot reference in "Additional context" below). The programme-level <icon> URL is independently reachable — confirmed via curl -I directly from the Emby server's host machine, returning HTTP/1.1 200 OK with a valid image/jpeg content type. Confirmed via direct API inspection (browser DevTools → Network → the Items?... request backing the Live TV "Shows" row) that the returned JSON shows "ImageTags":{} (empty) for programme items that have a valid, correctly-formatted <icon> in the source XML — ruling out a UI-only rendering bug and confirming the image reference is not being stored server-side at all. Steps to reproduce Configure a TV Source of type M3U pointed at any valid M3U playlist. Configure a Guide Data Source of type XmlTV pointed at a URL serving XMLTV where at least one <programme> element includes: <programme start="20260701210000 +0000" stop="20260702000000 +0000" channel="EXAMPLE.us"> <title>Example Movie Title</title> <desc>A description of the movie.</desc> <new></new> <icon src="https://image.tmdb.org/t/p/w500/examplePosterPath.jpg"></icon> <category>movie</category></programme> On the XmlTV source's settings page, set Movie categories to movie (or confirm the <category> value above matches whatever is already configured there). Run Refresh Guide Data (Dashboard → Live TV → Setup, or via Scheduled Tasks). Navigate to Live TV → Programs → Shows, and locate the item corresponding to the programme above. Expected: Poster artwork appears for the item, matching the <icon> URL provided. Actual: The item displays the default blank clapperboard placeholder icon. Inspect the underlying API response (DevTools → Network → the Items?... request that returns this item's JSON) and check the ImageTags field for this item. Expected: "ImageTags":{"Primary":"<some hash>"} Actual: "ImageTags":{} Create a DVR recording rule for the series/movie above with "Record new episodes only" (or equivalent) enabled, across a guide window containing both the <new/>-tagged airing and a later <previously-shown start="...">-tagged rerun of the same content. Expected: Only the <new/>-tagged airing is scheduled to record. Actual: Both the new airing and the <previously-shown> rerun are scheduled to record. Sample real-world data The following is representative real output from the pipeline used to test this (channel names/IDs anonymized where not relevant), showing a movie with three airings — the first correctly tagged <new>, and the two reruns correctly tagged <previously-shown> referencing the original air date: <programme start="20260701083500 +0000" stop="20260701120000 +0000" channel="ExampleChannel.us"> <title>Example Movie</title> <desc>Example description.</desc> <new></new><icon src="https://image.tmdb.org/t/p/w500/exampleHash.jpg"></icon><category>movie</category> </programme> <programme start="20260703170000 +0000" stop="20260703202500 +0000" channel="ExampleChannel2.us"> <title>Example Movie</title> <desc>Example description.</desc> <previously-shown start="20260701083500 +0000"></previously-shown><icon src="https://image.tmdb.org/t/p/w500/exampleHash.jpg"></icon><category>movie</category> </programme> Additional context This was tested extensively across multiple variations before concluding it's not a data-quality issue: plain <icon> alone, <icon> + correctly-cased <category>, self-closing vs. explicit open/close tag syntax, and stable vs. unstable programme-identity tracking for the new/rerun logic. None of these variations changed the observed behavior. If this is intentional/by-design (e.g., programme artwork and new/rerun detection are only supported when using Emby's own "Emby Guide Data" service, not third-party XMLTV), it would be very helpful to have this documented explicitly on the XmlTV setup page or in the XmlTV documentation, since the "Movie categories" field in particular strongly implies category-based classification has some functional effect for XmlTV sources specifically. Happy to provide a full sample XMLTV file, HAR export of the relevant API calls, or server logs on request.

I can't disable the subtitles because the option isn't available. When I go to the TV series library, select the series, and then choose the episode, it gives me an error. But if I remove the subtitle file directly on the PC, it works. That's why I think the problem is with the .ass files. I've also tried other series with episodes that have .ass subtitles, and the same thing happens. My server is a PC with a wired internet connection for both the TV and the PC. My internet provider is DIGI, which uses CGNAT. But I've been using Emby for several years with the same provider and haven't had any problems until version 2.3.8.

Try removing the dashes from the names of the image files. Emby uses the dash in defining file names. I am guessing this could be upseting the ID of the images.

Of interest: https://play.google.com/store/search?q=auto off timer&c=apps&hl=en

Fur Web, ist es mogliche mit custom.css. Ich habe eine theme wo der 'Play' knopf ist kleiner, grun und unten links.

Oh okay my bad.... I will stick with the emby expiry plugin then... I thought it is okay to integrate emby with qbittorrent client since there are some legal apps like arr's ( radarr, sonarr ) use emby and integrate it with their apps.

Hi all, I've built a plugin called TV Show Status that adds a status badge to TV series pages, showing whether a show is: Airing (with the next air date, if known) or Returning Series if no date is confirmed yet Last Aired (with the date, for ongoing shows without a confirmed next episode) Ended (with the last aired date) Cancelled (with the last aired date) In Production This data comes from TMDB and updates automatically once a day, so a show that gets renewed after being cancelled will flip back to the correct status without any manual action. How it works: A background task fetches the status for every series in your library from the TMDB API and caches it locally. On the web client, a small badge appears next to the rating/year/network row on each series' detail page (matching the native look of that row). Optionally, the status can also be prepended to the show's real Overview/description. This genuinely updates the library metadata on the server, but it doesn't currently display in the app versions I've tested — I'm hoping this could be picked up by the native apps in the future. Setup: Just enter a free TMDB API key in the plugin's settings page (Settings → Plugins → TV Show Status) and it does the rest.

I guess you need to raise your concerns with the plugin dev.

Can you please play that item until it exhibits the issue and then follow the instructions to send a log from the app?

Hallo, in der Cover Übersicht kommt der Play-button, wenn man mit der Maus rüber scrollt. Mich stört das, weil ich meist nur in die Infos zum Film möchte. Leider klickt man immer wieder auf den Play Button und der Film startet. Gibt es eine Möglichkeit, dass man zumindest in der Übersicht die Option, den Play-Button entfernen kann? Gruß derLurch

except that the issue with Spider-Noir is the versions are more equivalent to cuts, not quality, thus require seperate play state tracking. checked out that thread, but appears this issue has fallen to the bottom of the development pipeline. I'll keep an eye on it. thanks.

Sorry, but we cannot allow this one even outside of the catalog. Thanks

In my previous install, collections was working fine. I look through the forums but was there a reason for a new collection plugin that at least for me now does not work?

this is desperately needed. as I've raised linked, the current mitigation of removing all identifying external id's from the duplicate items is far from an ideal solution and results in even more issues for library management. we're pretty much in a dammed if we do dammed if we don't state atm. and this isn't an uncommon issue. separate editions are becoming more and more come (i.e. Spider-Noir I mentioned in the other thread), not to mention the current escalation in component pricing, we're all having to become very inventive with our library management to offset increasing costs (for example, I've had to duplicate my entire movie library between 4K and 720p versions as I simply can't afford the GPU hardware to transcode 4K anymore). I see too simple fixes here that shouldn't require large scale db changes: support `{edition-}` tags same as Plex. this would be a small change to the existing code that pulls from the filename after the last dash (-), to look for an additional pattern in the filename, and treat it same as currently displayed in the UI. this solves the presentation issue in the UI. track Continue Watching based on the Emby database id, not the external tvdb_id. this solves the duplication issue in the UI. make this a toggleble feature in the server settings, so that those that want to opt in for this wholesale change can if they wish.

No. There are some apps that do not show item backgrounds. Because they have been there since inception and a lot of users use them. The defaults were switched a long time ago to be more compatible with the apps that show item backgrounds.

I can't see any request for the video file in the log, so it's failing before even getting to the subtitle request. If you turn off subtitles before you start playback, does it play? Can you please send me a server log with that test? I'm also seeing some of these errors in your logs. Does the server have a working internet connection? Source: Emby.Server.Implementations TargetSite: Void MoveNext() InnerException: System.Net.Http.HttpRequestException: Resource temporarily unavailable (www.mb3admin.com:443) Source: System.Net.Http

I think the free aspect definitely reinforces a network effect on social media etc. A serious comparison review of Jellyfin / Plex / Emby would require a lot of work which no reviewer has the time for. I do have Jellyfin (and Plex) running and browse Jellyfin from time to time on Github though not in detail and they got a couple of decent developers pretty active on the project in the last year or two. For a long time it was just floating along but I think it got a bit of momentum going recently. PS IF Emby disappeared tomorrow, I could use Plex but JF is nowhere near usable for me. Emby is still the best of the 3, in my case.

You can't. The grid filling all the space in a dialog view needs to be seen as a different mode where it can behave in ways which aren't possible when it's part of the flow layout as certain interactions would conflict with normal page navigation. In a dialog, it is isolated from the regular interactions because you need to close the dialog first to return to the normal page context. When the grid is on a page view (or any other view where it's not maximized), it is just an element like all the others and bound to the same margins like all other elements.

Emby Expiry Manager Emby Expiry Manager is an in-development plugin that tracks items (movie, shows or episodes) in your library and automatically removes them once their time is up (set by user) — handy for content management if you have limited storage or things you want to host temporarily. "Leaving" badges — items show a countdown badge on posters and thumb image ("Leaving tomorrow," "Leaving in 6d," etc.), so viewers know at a glance how much longer something will be available.* Automatic removal — once an item's time is up, it's pulled from the library on schedule, no manual cleanup needed * requires emby new overlay version 1.3.1.0.

You were specifically talking about TV show - and for that, episode naming is irrelevant. Multi-versioning was never intended to be used for multiple cuts, just different versions/resolutions of the same item, but over time userbase took on using it for cuts as well (with all the caveats - like the ones you're facing - it brings). Anyway, you can join and lend your support and/or comment in the already existing FR and related discussion:

Small update: Removed the Music Library ignore from the plugin. Posters for music libraries use a different scale, not really an issue but will require the 200x300 feature to ignore music libraries. Need to add bitrate and sample rate icon support. Update the cache to work with new icons. The troubleshooter needs to be updated with said icons. <-- No way to scan music at all right now. Update profile system. <-- All music settings are global without this. Update UI. <-- Only way to change settings for music right now is by manually editing the settings file. Update help page. Get new icons made (please help!). Update filename-based and tag system. Add scaling option for music libraries to normalize icon position a bit better. And some things I most likely have forgotten. Still a lot to do.

Here is a sneak peak of the upcoming new plugin projects QbitStrm. QbitStrm is an in-development plugin that bridges qBittorrent and Emby It watches your downloads and automatically turns unfinished torrents into .strm files so Emby can display them as upcoming titles. Completed downloaded movies and shows show up in your library without manual copying or waiting on a full file transfer, also you can set premiere date to make them available to watch. Features Premiere countdown badges — see at a glance when a scheduled title will unlock * "Upcoming" badge with progress — incomplete torrents show live download progress right on the poster * Graceful placeholder playback — custom, user-set videos play for upcoming/incomplete titles YouTube-style premiere notification — premiering items play their backdrop with the premiere date burned in, until the real content is ready. * requires emby new overlay version 1.3.1.0.