All Activity

Fixed for the next version. Thanks

Je ne crois pas que le problème vienne de la : Futurama\Saison 11\Futurama - S11Exxx Je pense que ça vient de l'écart entre Aired Order et Streaming Order

thanks great catch basically PremiereDate is nullable, and my fallback (`?? DateTime.MinValue`) was quietly getting converted using the server's local timezone offset. If that offset is positive it pushes the date past year 1 and blows up. Since it happens inside the cache key function, Emby just keeps calling it over and over trying to recover, which is why your CPU was getting cooked. i'm going to fix it on the next release. Saved me a lot of digging. Glad the plugin's otherwise been working out for you.

So wouldn’t it make sense creating a separate area for Vega OS, because as the moment FireOS and VegaOS are not separated?

Hi, First of all, thank you for this excellent plugin. I've been using it extensively and really appreciate the work you've put into it. Unfortunately, I found what appears to be a bug with the latest Emby server. Environment Emby Server: 4.9.5.0 Windows 11 24H2 .NET Runtime: 8.0.27 EmbyNewOverlay: 1.3.4 Problem When the plugin is enabled, EmbyServer.exe eventually reaches 90–100% CPU usage even though there are: no active scans, no library tasks, no playback, no background jobs. Disabling or removing the plugin immediately drops CPU usage back to around 5%. The server log is continuously flooded with the following exception: Error ImageProcessor: Error in GetConfigurationCacheKey System.ArgumentOutOfRangeException: The UTC time represented when the offset is applied must be between year 0 and 10,000. (Parameter 'offset') at System.DateTimeOffset.ValidateDate(DateTime dateTime, TimeSpan offset) at System.DateTimeOffset.op_Implicit(DateTime dateTime) at EmbyNewOverlay.Enhancer.NewBadgeEnhancer.GetConfigurationCacheKey(BaseItem item, ImageType imageType) at Emby.Drawing.ImageProcessor.GetImageCacheTag(...) I decompiled the plugin and traced the exception to NewBadgeEnhancer.GetConfigurationCacheKey(). The problematic code appears to be: (item.PremiereDate ?? ((DateTimeOffset)DateTime.MinValue)).Date.ToString("yyyyMMdd") The generated IL is: callvirt BaseItem::get_PremiereDate() ... ldsfld DateTime::MinValue call DateTimeOffset::op_Implicit(DateTime) The exception is thrown during the implicit conversion from DateTime.MinValue to DateTimeOffset. This seems to happen when an item has no valid PremiereDate, and because the exception occurs inside GetConfigurationCacheKey(), Emby keeps retrying image generation, causing a continuous loop and very high CPU usage. I also verified several items from my library database and their PremiereDate values were valid, so it may only occur with specific item types or metadata. Would it be possible to replace this fallback with something safer (for example DateTimeOffset.MinValue or another guarded approach) to avoid the exception? Thanks again for your work! I hope this helps identify the problem.

Salut Alors déja comment sont nommés tes médias ? et ensuite comment est configuré ta bibliothèque Séries dans Emby ?

Hello, Je suis un peu perdu avec les métadonnées de futurama. * Je pensais mettre la saison 11 dans EMBY mais cela ne fonctionne pas. J'ai ça : Depuis quand ce serait la numérotation de Streaming qu'il faudrait utiliser ?

I have been experimenting with getting Emby to run directly on a VIZIO SmartCast/VIZIO OS television, and I have it working surprisingly well. This is not Chromecast, screen mirroring, or an external streaming device. Emby is actually running in the web application environment built into the VIZIO TV. The first important discovery was that VIZIO's old SmartCast Conjure/App Launcher still works with my television. I connected to the TV's SmartCast interface on port 7345 from my PC, paired with the PIN displayed on the TV, and was able to launch a URL directly on the television. I initially launched: http://tv.emby.media and Emby Theater came up directly on the VIZIO. I was able to log in, browse my server, and play media. I then changed this to use the web client served directly by my own Emby server: http://<EMBY-SERVER-IP>:8096/web/index.html?vizio=1 Video playback works, navigation with the VIZIO remote works, and the interface is quite usable. There was one significant remote-control problem: the VIZIO Back button did nothing in Emby. I made a small JavaScript key-test application and launched that through the same VIZIO App Launcher. That showed exactly what the VIZIO remote sends: Up = ArrowUp / 38 Down = ArrowDown / 40 Left = ArrowLeft / 37 Right = ArrowRight / 39 OK = Enter / 13 Back = Backspace / 8 The important part was: Back = Backspace keyCode = 8 Emby's web client wasn't treating that as its Back command. I added a very small JavaScript compatibility shim to the locally served Emby web client. On a VIZIO/SmartCast user agent only, it translates: Backspace / keyCode 8 -> Escape / keyCode 27 It deliberately leaves Backspace alone when the cursor is in a text-entry field. After doing that, the physical VIZIO Back button works normally in Emby, including getting back out of Settings and navigating through the UI. I then worked on eliminating the need to use a computer or phone to launch Emby. My VIZIO remote has an old dedicated Redbox button. VIZIO has since reassigned that button to launch WatchFree+ On Demand. Using the local SmartCast API, I captured what the TV reports when that button is pressed. On my TV it is: APP_ID: 145 NAME_SPACE: 4 MESSAGE: https://ui.sctv.prod.smartcasttv.com/watchfreeplus/avod/entry/entrypoint.html When my locally hosted Emby application is running, the TV reports: APP_ID: 17 NAME_SPACE: 4 MESSAGE: http://<EMBY-SERVER-IP>:8096/web/index.html?vizio=1 I paired my Emby Linux server directly with the VIZIO and wrote a small systemd service using the Python vizaio library. The service watches the TV's current application through the local SmartCast API. When it sees the exact WatchFree+ entry point generated by pressing the physical Redbox button, it immediately launches my local Emby URL instead. So I now have: Press REDBOX on VIZIO remote ↓ TV starts WatchFree+ On Demand ↓ Linux service detects that application ↓ SmartCast /app/launch ↓ Local Emby web client launches ↓ Physical VIZIO remote controls Emby The switch happens very quickly. So in practice, the old Redbox button is now my dedicated Emby button. No Chromecast. No Roku/Fire TV/Apple TV. No phone. No PC needed to launch it. The only always-on component is my Emby server itself, which is already running anyway. There are two modifications involved: A small VIZIO-specific JavaScript shim in Emby's locally served web client to translate the VIZIO Back button. A small Linux/systemd service that watches the VIZIO local API and redirects the obsolete Redbox button to Emby. Obviously this isn't equivalent to having an officially published Emby tile in the VIZIO app catalog, but functionally I now have a native-feeling Emby client running directly on the television. If anyone is interested, I can clean up and post the JavaScript Back-button shim, the VIZIO pairing procedure, and the Python/systemd launcher service. I'm especially interested in whether the Emby developers still have the VIZIO-specific client/build that was mentioned in the past. Given that the underlying SmartCast web application environment is still perfectly capable of running Emby, it seems like there may still be a useful path here even without VIZIO catalog approval.

Same places shown in the pictures were it’s horizontal not vertical, and still other few places .

Hi @Luke Im writing a "reccomend me" user plugin (users can reccomend media items to other family members). The feedback i got from the family on my "manage coming soon" plugin (submit media requests) was its all well and good but "we dont use computers [to access emby] we use tablets and tvs". So the pick up has been lower. Do you think there could be some sort of conformance policy, that plugin writers could adhere to and submit their plugin for approval?

Just an update to let you know that Gracenote are discussing with the KOXI-CD broadcaster the additional channels. It appears that charges are involved and that would need to be agreed between KOXI-CD and Gracenote.

Thank you @Dickydodah!, I though I tried to get it there 1st time I saw this post but was unable to download it. Got it and love it!

Where can I find release notes for beta stuff, is there a location? TY I have the latest AndroidTV beta and will test tomorrow to check the new search function Thank you

Na dann! Ich bin gespannt und freue mich schon. Danke

Hi there, let's look at an example. Please attach the information requested in how to report a media playback issue. Thanks!

HI, not yet, but stay tuned for the upcoming smart views/playlists feature. Also the upcoming 4.10 release will allow you to design your own home screen sections, so I think that will help you with this.

Hallo an alle, Besteht irgendwie die Möglichkeit zum anlegen einer Bibliothek die Täglich Vorschläge zu ungesehenen Filmen generiert? Ich stell mir das ganze in etwa so vor: mit Leiste der Zufälligen Filme In dieser Bibliothek sollen nur Ungesehene Filme ... Zufällig ausgewählt ... aus den von mir hinterlegten Ordnern (Filme-1, Filme-2, Filme-3, etc.) erscheinen. Am liebsten zeitlich einstellbarer Intervall, etwa alle 6 / 12 / 24 / 48 / 60 Stunden. Die Anzahl der Gezeigten Objekte kann auch ruhig auf 30 Stk. beschränkt sein, oder gar selbst definierbar nach Unterordner. z.B. Filme-1: 5 Objekte, Filme-2: 10 Objekte ... Auch wäre es schön auf der Startseite im allgemeinen die "Bewertungen (IMDb)" unter den Filmen und Serien anzuzeigen, in einem anderen Beitrag wurde schon vor Jahren dieses feature als Update versprochen, wurde aber bis heute nicht umgesetzt ... oder ich habe den Schalter dafür noch nicht gefunden Viele liebe Grüße H

I encountered the same problem. I am a docker emby deployed under wsl2 of windows server 2025. Version 1.0.5.0 of the Bluray Folder Support plug-in in Emby Server 4.9.5.0 does not play the BDMV folder normally. Returning Emby4.8.10.0 with Bluray Folder Support1.0.2.0 version can achieve normal playback of the original Blu-ray folder. Looking forward to the official repair.

After testing, this scheme is a thing of the past and is completely unsuitable for the plug-in Bluray Folder Support 1.0.5.0 of the new version of 4.9.5.0. Emby4.8.10.0 with Bluray Folder Support1.0.2.0 version can achieve normal playback of the original Blu-ray folder.

That does, of course, depend on the screen size and resolution of the poster artwork used. In any event, this may be why the BBFC has an alternative set of certificate icons that use colour and shape to differentiate. The "classic" set was already pretty good in this respect, with only the 12 and 15 ratings being differentiated solely by text. It should be noted that this set is missing "12A", which is the same colour as "12". However, being 50% MORE text (as opposed to just different text), it remains easily differentiated even at small sizes. Ultimately, if this was an OPTION, then users could decide.

What example are we focusing on in these log files?

What do you mean by same old locations?

Ok yes now I found it, it’s available only when I use “TV mode”, but still the horizontal problem persists, it’s not in everything but mainly still the same old locations .

I apologize for the delay. The emby server is up2date and I was having no issue with the truehd7.1 until I updated the shield emby app. Issue remains with only truehd7.1 audio codec. When I change to another codec, no problem. Emby is still awesome. Thank you. NOTE: when I updated the app it gave the option to try another emby app android interface. I did not wish to push my luck like if I did not like it could I go back, but now I wonder. I will also endeavor to return to the previous app on the shield. I appreciate your effort. Thank you. To tidy things up a bit, please close the thread.

i added log in first post but here are some others not sure what one it would be in now. these are from the 5/6th embyserver-63921571200.txt embyserver-63921657600.txt embyserver-63921589611.txt