All Activity

The Plugin stopped working suddenly. I was considering to pay. It says trial ended. Glad, checked this thread and saw that it won't work even after payment. A frustrating situation. People are seeking for a native credits detector. Unfortunately there isn't for years. So they seek plugins like Credits Detector. It unfortunately deletes all the markers after any library scan. Its a bug. Not just credits also intro markers, then this is the plugin that we found to backup a huge library markers. Let’s go back to the begining, The problem comes from the lack of a native credits detector. Its been years since the first request. How hard can it be to be implement? Its disappointing for us not to use a fully functional streamer app even if paid.

@Javier008 hi, please check out our quick start guide: Quick Start

Thanks for the feedback.

The filter and display text are not unified so they can produce different results occasionally. It’s something that needs to be improved. Thanks.

The Emby server log was erased when I uninstalled and reinstalled the server... I know exactly what I did.. On the posted picture(I found this picture on google, its not from my Emby, just posting pic to show what I did) I put a ip address in the first row that says Lan networks.(where it should have been kept empty) What I was trying to do was use my dedicated Ip address that I have from a VPN, to try to access Emby outside of my home address..

Hi, yes my WAN access shows my Dynu domain and my Home access matches my router DHCPS-Fixed IP.

HI there, can you please provide a specific example? How to Report a Problem Thanks !

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

Hi, you can already setup a webhook when something is played using the notifications feature.

Hi, does your Emby server dashboard display the correct addresses that you want Emby apps to connect with?

Hi, please run a library scan and then attach the Emby server log: How to Report a Problem Thanks.

As a matter of interest, in my opinion 42 of the movies I have listed under SD, out of 156, should be under 720p.

Runs nice . Few suggestions: - On my 1080p Screen, the badges are barely redable, could you make them a little bit larger like in the Docker version? - Can the forecast be extended to more than 120 days?

Not yet, I think this is one Gemini mentioned amongst other things I've tried, I was hoping someone would have an example of a real life fix, but thanks

Has this got anything to do with why when filtering by resolution it seems get quite a few wrong ? eg filter for SD I get movies that on their detail page says they are 720p, filtering for 720 movies I get ones that say they are 1080p.

Yes, once its been out on Google for a bit.

The app is not going to be able to determine what is supported in that case. Have you tried enabling/disabling the pass thru options in the settings? Or, alternatively, you can just use the standard app if that is working for you.

How do you downgrade Emby for Android TV? I can't find a way to do it.

No items found, appears within emby client via http access for the tv's. I have rescanned the libraries many times and refreshed the meta data many times I guess deleting the db files might fix it

First off, the number of +1s on this thread proves that Live TV/m3u resilience is a massive pain point. Dropped streams, buffering, and failed reconnects completely ruin the "couch experience." However, I want to chime in with some perspective from the backend infrastructure side—and share a glimpse of how this is ultimately solved. I have massive respect for @Lukeand the Emby team. They are building a phenomenal, all-encompassing media server for a huge user base across countless devices. The reality is that building native, bulletproof IPTV stream orchestration (handling token expirations, 401 errors, rogue ffmpeg crashes, and upstream provider glitches) is incredibly complex. It honestly falls more into the realm of "Headend Appliance Infrastructure" than standard media server duties. I actually responded to this thread back in March offering the architecture for a dedicated streaming engine to handle this, but I completely understand and respect that adopting a third-party engine didn't fit their roadmap. They have a massive ecosystem to maintain, and keeping the core stable has to be their priority. Because the problem still needed solving, I have been quietly building the solution at the infrastructure level. To @jonzey231and everyone else in this thread: asking for a configurable timeout or an auto-reconnect loop in the Emby UI is ultimately just a band-aid. If your provider's stream drops or changes tokens, looping a reconnect on a dead URL from the client side is still going to fail or cause massive lag. I am currently engineering a dedicated, standalone backend appliance that does exactly what this thread is asking for, and a whole lot more, by fixing the problem before it ever reaches Emby: Infrastructure-Level Orchestration: This engine sits between your provider and Emby, running a custom process monitor. If a stream jitters, drops, or errors out, the backend intercepts the failure, renegotiates with the provider, and recovers the feed seamlessly in the background. Zero Client Timeouts: Because the backend handles the connection resilience, Emby is fed a continuous, perfectly stable local stream. As far as Emby is concerned, the stream never went down. Emby doesn't need a timeout setting because it never loses the connection. True Headend Features: It handles localized circular buffering, instant JIT (Just-In-Time) catch-up of guide data, and active Tuner/Stream pooling. Emby is an absolutely stellar front-end and library manager. But if you want enterprise-grade Live TV reliability, you shouldn't be relying on a media server to manage raw stream health. You handle stream orchestration at the backend. I am keeping the project under wraps for now, but I am looking forward to sharing this solution with the community when the time is right.

Purpose: I was finding it longwinded creating a new plugin shell at the beginning of a project. I created this repository with an automated workflow to quickly instantiate a working plugin inside a git repository framework. https://github.com/ginjaninja1/EmbyTemplatev2 Hopefully others might find a use, I'm hoping its going to make it massively easier to create new plugins. Zero-Configuration Scaffolding: Uses automated GitHub Actions to rename namespaces, solution files, and projects instantly upon repository creation. setup.bat: instantiates a pre-commit in `.git/hooks/` so any commit with "[bump]" at the END of description increases the the version number in .csproj. Working Plugin with thumbnail: Ready to compile plugin with thumbnail, pluginui configuration page with autopostback (autosave) and task. Further instruction/guidance in readme.md in repository. Issues and suggestions welcome. Disclaimer: Vibecoded with Claude. The sample code will 'do work' if you schedule / run the task so avoid doing that 'blind'.

Pour compléter, il y a des épisodes aussi qui me met en double sur le même jour à quelques minutes d'intervalle ou quelques heures

Hello smity3, ** 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

Server version: 4.10.0.18 (started on 4.10.0.17 but auto-updated overnight) OS: Windows 11 Server Setup: Reverse proxy (Caddy) in front of Emby, HTTPS via Let's Encrypt (handled by Caddy), External domain set from Dynu, "Handled by reverse proxy" mode. Internet Setup: ATT Fiber using IP Passthrough with DHCPS-Fixed IP allocated, open ports configured on router. Usually have Mullvad VPN on with relevant programs split-tunneled, but for all these tests Mullvad was disconnected to rule out any VPN shenanigans. Hello, I recently set up a reverse proxy to handle SSL for my server. Got it working fine and tested internal and external connections which all worked using the Emby App, Emby Connect, and direct from the new domain I set up. However, I was doing some cleaning and deleting some old users successfully when suddenly on the next one I got an error: mediabrowser.common.extensions.remoteserviceunavailableexception. From then on I have been unable to connect to the server at all via Emby Connect or through any app. When trying to do so I can log in but then I just see the option of my server name, and when I click it it says: "Unable to reach server name. We're unable to connect to the selected server right now." I get the same result on app.emby.media connecting from a separate device not on my home network. No settings were changed between when I set up reverse proxy and when the error started. I can still connect directly through my new domain from an outside network and get through to the server and playback works fine. I've double-checked the reverse proxy, DNS, and certificates and all are in order. I tried going through the Connecting From Client Apps page, and added some firewall ports that weren't in there before (even though I could still connect from anywhere before those were added up until now), and did all the other steps but still am having no luck. I tried unlinking and relinking Emby Connect emails from the users too. Any thoughts on what I may have missed or why Emby Connect suddenly doesn't want to reach my server? Log file attached. Thanks! embyserver.txt

With that many SATA drives in that many enclosures using that many USB ports the interfaces are going to be your bottlenecks. Both USB and PCIe would be overcommitted. This is assuming Windows can handle the number of drives. It shouldn't be a noticeable problem for a media server, it being a low I/O throughput application. If you go through with this then building out, transferring files and general maintenance if you try to reorg and rebalance storage periodically are when you're likely to notice things being slower than expected. But these wouldn't be day-to-day events.