All Activity

Screenshots below - start-halfway-finish. Dry-run "on" or "off" seems to give exactly the same logging progress results. The green progress bar moves step-by-step and a new line appears in the live log as each album is completed. Halfway length along the bar also aligns well in real time (e.g.) halfway takes 1:14 and completion takes 2:28. A comparable "scan" takes roughly about 30-40% of the time of Mp3tag. Let me know if you need more on this?

Not seeing an issue here connecting to 4.9.3.0 or 4.10.0.8. Edition Windows 11 Pro Insider Preview Version 25H2 Installed on ‎1/‎31/‎2026 Evaluation expires on ‎8/‎11/‎2026 11:09 AM OS build 26300.8142 Experience Windows Feature Experience Pack 1000.26100.345.0

That's the: Have fun!

Any update on this? As I still only see the same trailers as above.

Any news on the Trakt integration?

FYI, Tunarr will happily max out open files/handles on a server. It caused havoc on my end, causing other containers to crash due to resource starvation. I had to restore my Emby databases from backup because they got corrupted. After restoring Tunarr from a backup (it too decided to off itself), I set "--ulimit nofile=4096:4096" (I initially set it to 1024:1024 after restoring), but it's maxing that out, and it just silently fails once it exceeds the limit. I'm done with that vibe-coded monstrosity.

The biggest deterrent to plugin devs on Emby has always been around the stable release schedule and the instability of beta builds. Infrequent stable releases push regular users to run beta builds and the beta builds are pushed out with no internal testing and often break things. Expect to be doing regular maintenance releases to keep up with the beta or have people questioning why you only support stable server releases. We've been asking for quarterly stable server releases for years but we are stuck waiting 1-2 years between stable releases. IMO it doesn't make sense to add this to the catalog until the Home Screen Selection make it to a stable server releases.

High quality uses software decoding energy efficient all hardware, balanced piggy in the middle. There is a ffmpeg bug with Truehd and atmos that has been fixed with custom mpv builds and will also be incorporated into the next beta with a bit of luck.

Edition Windows 11 Pro Version 25H2 Installed on ‎2025-‎02-‎26 OS build 26200.8037 Experience Windows Feature Experience Pack 1000.26100.300.0 Same problem here. Emby Theatre just loads to a black screen and hangs.

Thank you soo much I tried it and it is amazing

Hola, tengo un plan mensual Emby Premiere de 80 días. Mi servidor tuvo problemas recientemente (disco lleno/base de datos reiniciada) y ahora me aparece un error de "límite de dispositivos excedido" aunque en realidad no tengo tantos dispositivos activos.Parece que hay dispositivos fantasma registrados en mi cuenta. ¿Podrían restablecer el contador de dispositivos o eliminar los dispositivos registrados? Gracias.

Hello i run with last beta (v4.10.0.8) When i start a play, it plays well for some seconds and then a loop (still image)! Only occur on LG, on others clients it works (Windows/Chrome). What's wrong? Thanks Here some traces in logs: 2026-04-02 21:27:41.032 Info MediaInfoService-0HNKGT4245IHO:0000002A: User policy for admin. EnablePlaybackRemuxing: True EnableVideoPlaybackTranscoding: True EnableAudioPlaybackTranscoding: True EnableTranscodingQuality: True 2026-04-02 21:27:41.032 Info SessionManager: Setting _lastPlaySessionId for session 27cf6c95e31db59854fbef1fa9ede1ac to 4d943bbed9c14a489556b0bd3188d413 2026-04-02 21:27:41.032 Info MediaInfoService-0HNKGT4245IHO:0000002A: http/1.1 Response 200 to host4. Time: 2824ms. POST http://192.168.1.44:8096/emby/Items/682491/PlaybackInfo?UserId=x_secret5_x&StartTimeTicks=0&IsPlayback=true&AutoOpenLiveStream=true&MediaSourceId=mediasource_682491&MaxStreamingBitrate=200000000&X-Emby-Client=Emby for LG&X-Emby-Device-Name=LG Smart TV (OLED65G26LA)&X-Emby-Device-Id=daf44956-3950-4daa-8b23-997437ff4e32&X-Emby-Client-Version=1.0.50&X-Emby-Token=x_secret6_x&X-Emby-Language=fr&reqformat=json. 2026-04-02 21:27:41.210 Info VideoService-0HNKGT4245LBT:00000001: http/1.1 GET http://192.168.1.44:8096/emby/videos/682491/original.mkv?DeviceId=daf44956-3950-4daa-8b23-997437ff4e32&MediaSourceId=mediasource_682491&PlaySessionId=4d943bbed9c14a489556b0bd3188d413&api_key=x_secret6_x. Source Ip: host4, Connection=close, Host=192.168.1.44:8096, User-Agent=Mozilla/5.0 (Web0S; Linux/SmartTV) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.6099.270 Safari/537.36 WebAppManager, Accept-Encoding=identity, icy-metadata=1 2026-04-02 21:27:41.218 Info HttpClient: GET http://xxx.xxx.xxx/series/rsjT6CNvovgQZ4/aFWUeNgdyuajgZ/686758.mkv 2026-04-02 21:27:41.447 Info HttpClient: Http response 401 from http://xxx.xxx.xxx/series/rsjT6CNvovgQZ4/aFWUeNgdyuajgZ/686758.mkv after 229ms 2026-04-02 21:27:41.448 Error VideoService-0HNKGT4245LBT:00000001: Error processing request *** Error Report *** Version: 4.10.0.8 Command line: /system/EmbyServer.dll -programdata /config -ffdetect /bin/ffdetect -ffmpeg /bin/ffmpeg -ffprobe /bin/ffprobe -restartexitcode 3 Operating system: Linux version 6.17.2-1-pve (build@proxmox) (gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44) #1 SMP PREEMPT_DYNAMIC PMX 6.17.2-1 OS/Process: x64/x64 Framework: .NET 8.0.22 Runtime: system/System.Private.CoreLib.dll Processor count: 6 Data path: /config Application path: /system MediaBrowser.Model.Net.HttpException: MediaBrowser.Model.Net.HttpException: Unauthorized at Emby.Server.Implementations.HttpClientManager.CoreHttpClientManager.SendAsyncInternal(HttpRequestOptions options, String httpMethod) at Emby.Server.Implementations.HttpClientManager.CoreHttpClientManager.SendAsync(HttpRequestOptions options, String httpMethod) at Emby.Server.Implementations.HttpServer.HttpResultFactory.GetContent(StaticFileResultOptions options, Int64 offset, Int64 length, CancellationToken cancellationToken) at Emby.Server.Implementations.HttpServer.FileWriter.SetContentResponseHeaders(Nullable`1 reportedTotalContentLength, CancellationToken cancellationToken) at Emby.Server.Implementations.HttpServer.HttpResultFactory.GetStaticResult(IRequest requestContext, StaticResultOptions options) at Emby.Server.MediaEncoding.Api.Progressive.BaseProgressiveStreamingService.ProcessRequest(StreamRequest request, Boolean isHeadRequest) at Emby.Server.Implementations.Services.ServiceController.GetTaskResult(Task task) at Emby.Server.Implementations.Services.ServiceHandler.ProcessRequestAsync(HttpListenerHost httpHost, IServerApplicationHost appHost, IRequest httpReq, IResponse httpRes, IStreamHelper streamHelper, RestPath restPath, String responseContentType, CancellationToken cancellationToken) at Emby.Server.Implementations.HttpServer.HttpListenerHost.RequestHandler(IRequest httpReq, RestPath restPath, String urlString, String localPath, String contentTypeInPath, CancellationToken cancellationToken) Source: Emby.Server.Implementations TargetSite: Void MoveNext()

I'm posting this if anyone needs a work-around. I've been having an issue with bitstreaming Dolby Atmos to my Yamaha RX-A8A AVR. If an AC3 or EAC3 stream is encoded with Atmos, the audio cuts out, sometimes often, sometimes periodically (the frequency of cut outs changes with each movie). I didn't notice any issues with Atmos encoded streams in any of the higher bitrate streams (e.g. Dolby True HD 7.1 seems fine). Also, it doesn't seem to matter if I have bitstreaming enabled or not, the audio was cutting out with it off, but without the Atmos decoder on my AVR flipping out, it was just little blips of audio cutting out). This cropped up after a hardware change (at least I think thats what it is, becuase I don't recall having an issue until I changed out the GPU). Current hardware: AMD Ryzen 5 5700G, 32GB ram, Radeon 9060XT 16GB (previous graphics card was a GeForce 4060Ti 8GB). I also never had an issue with my main PC hooked up (AMD Ryzen 9 9950X3D, GeForce 4090). AFAIK the default behaviour for the Windows app is Balanced video decoding. If you change to High Quality, the problem gets significantly worse, changing to Energy Efficient appears to fix the issue.

Hi everyone, I'm trying to understand what the actual limitations are when using the free Emby Android app (downloaded directly from the Play Store) connecting to a free Emby server (no Premiere license). My setup: - 3 Android smartphones, all with the official Emby app from the Play Store - None of them have any in-app purchase or Premiere subscription - I connect to a server that also has no Premiere license - I'm always on a different network than the server (remote streaming) The surprising part: on all three devices I can browse the library and stream movies without any paywall, warning, or limitation appearing whatsoever. The server admin was actually surprised by this — he had always told users to install a modified APK because he assumed the official Play Store app wouldn't work without Premiere. Yet here I am, three devices, fully functional, no purchase made. Downloading content offline is disabled by the admin on the server side, so I can't test that specific feature. My question is: what exactly are the limitations when using a free Android app + free server in a remote streaming scenario in 2025/2026? Has the playback paywall been silently removed for Android mobile, similar to what was announced for Android TV (free playback up to 5 devices per server)? Thanks in advance for any clarification!

Super, wusste ich nicht, wird sofort abgespeichert, danke

Du findest die aktuellste Beta Version immer auf Git Hub. https://github.com/MediaBrowser/Emby.Releases/releases Dort einfach die richtige Version runterladen, Emby runterfahren und dann drüber installieren.

I made an ios in-app purchase to unlock playback in 2025 and now it doesn't work on any of my devices, I only use the apple ID that made the purchase to download the emby app but it doesn't work at all. The restore button doesn't work also, I click the "Restore purchase" button but its only for the Premier subscription.

Getting your Plugin in the catalog

Not scientific but I’ve sometimes seen issues with just the sheer number of files in a single large volume. Yet a larger share with larger file sizes but less files is relatively quicker. There’s also the potential for the metadata providers rate limiting you, or something else being rate limited (I never investigated it enough). My volumes are no where as large as yours but single libraries would sometimes take over 12 hours to scan back in.

You can do it with tags with EmbyIcons. It's a manual process though so will be fiddly.

Because I don't want any of them to play automatically and if I put everything in the season 0 folder, all specials will be mixed up in a Specials season view in the Emby app. If you have tens of specials for a show, it becomes cumbersome to scroll through the whole list of specials to find the specials related to the season you just watched. It's much more intuitive to have them in the season itself (for example, Deleted Scenes of S01E01 in S01 view after all normal episodes of season 1.

I agree, i was about to make a post about this but i kept scrolling to see what other said, then i found this post, i would also want to add to be able to change the color, and support Arabic text also.

Hi, Could you make gracenote aware of some changes to the Movie Channels for Sky UK (Satellite and Glass) - these changes happened on 17th March Movies 24+ moved from 315 to 329 on satellite only Movies 24 moved from 312 to 315 on satellite only Sky Cinema Animation moved from 305 to 312 on satellite and 315 on Sky Glass & Stream Sky Cinema Action moved from 307 to 306 on satellite, Glass & Stream Sky Cinema Family moved from 306 to 304 on satellite, Glass & Stream Sky Cinema Greats moved from 304 to 307 on satellite, Glass & Stream Disney+ Cinema HD launched at 305 on satellite, Glass & Stream Source: Changes to the TV Guide - March 2026 | Sky Community

I sent the logs again now after doing as you suggested. Let me know the update.

This is a Windows Insider Preview version. When you are running these, errors like the one you are seeing must be expected. It's not an Emby issue.