All Activity

Update after downgrade, qts is not a problem, i don't have a problem with emby 4.9.3

Intro/Credits Backup & Restore - open-source replacement for the intro/credits backup plugin Hi all, The "Intros Backup/Restore" plugin that many of us have relied on to back up and restore intro/credits chapter markers hasn't seen an update in a while, and I know several people here have been running into issues or just waiting on fixes that haven't come. I ended up writing an independent, open-source replacement from scratch, built purely against Emby's public plugin SDK - no code from the original plugin, just the same general idea (export markers to JSON per episode, restore them back later). What it does: Backs up every TV episode's intro/credits chapter markers to one JSON file per episode Restores markers from those JSON backups, matching episodes by TVDB ID + season + episode number Before each backup run, zips up whatever was already in the backup folder into a timestamped archive first, so nothing gets silently overwritten Optional companion .nfo output alongside the JSON Both backup and restore run as normal Emby scheduled tasks - no custom in-app dialogs, just Dashboard > Scheduled Tasks like anything else Scope: TV episodes only for now - movie intro/credits markers aren't handled. Settings: Scheduled Task: Requirements: Built and tested against Emby Server 4.10.0.18. You'll need the .NET 8 SDK (or Docker) to build it, and you'll need to copy three DLLs from your own Emby install to build against (not redistributed in the repo for licensing reasons - the README walks through exactly where to find them on Synology/Docker/Windows/Linux installs). It's MIT licensed, so do whatever you want with it. Source, build instructions, and a v1.0.0 release are all here: https://github.com/guilty57/credits-intros-backup-restore Happy to hear feedback, and PRs are welcome if anyone wants to extend it (movie support would be the obvious next step).

Hi all, I'm running Emby Server 4.9.3.0 on Linux. I share my library with several users and I have Max simultaneous streams set to 1 per user. One user keeps getting "Your account exceeded the maximum streaming limit set by your Emby Server Administrator", but he only ever uses a single Apple TV (Emby for Apple TV 2.0.6). I checked and his device ID only ever connects from one single IP — he is definitely not streaming anywhere else at the same time. Looking at the server log, I think the app is tripping its own limit. During a single movie, the Apple TV app repeatedly reports "Playback stopped" and then keeps sending progress events and re-adds the same play session to the same session container, and eventually starts a new PlaySessionId for the same title. The content is being transcoded (ContainerNotSupported / ContainerBitrateExceedsLimit), so a server-side transcode is still finishing when the next session registers. Server-wide I also see more play sessions added than removed (53 vs 49), so some sessions aren't being released cleanly. My guess is that with the limit at 1 there's zero headroom, so the brief overlap between the not-yet-released old stream and the new one is counted as 2 and rejected. My questions: Is this the expected cause of a false "limit exceeded" for a user on a single device? Is there any server-side setting to add a small tolerance/grace to the simultaneous-stream check, or to make a stopped session/transcode release immediately, so I can keep the limit at 1 without these false positives? Relevant log excerpt (session IDs shortened, server IP removed) below. Full log attached.Thanks! 2026-07-13 15:45:18.467 SessionManager: Adding playSession 86430611... to session 337b0590... 2026-07-13 15:45:18.929 SessionManager: Playback start reported by app Emby for Apple TV 2.0.6 (3) on Apple TV playing <title>. PlaySessionId: 86430611... IsPaused: False ... normal playback for ~25 min ... 2026-07-13 16:10:39.973 SessionManager: Playback stopped reported by app Emby for Apple TV 2.0.6 (3) ... PlaySessionId: 86430611... 2026-07-13 16:10:39.974 SessionManager: Removed playSession 86430611... from session 337b0590... 2026-07-13 16:12:17.094 SessionManager: Adding playSession 86430611... to session 337b0590... <-- same play session re-added 2026-07-13 16:13:36.796 SessionManager: Playback stopped reported by app Emby for Apple TV 2.0.6 (3) ... PlaySessionId: 86430611... 2026-07-13 16:13:36.797 SessionManager: Removed playSession 86430611... from session 337b0590... 2026-07-13 16:13:38.484 SessionManager: Adding playSession 86430611... to session 337b0590... <-- re-added again 2026-07-13 16:14:00.465 SessionManager: Playback stopped reported by app Emby for Apple TV 2.0.6 (3) ... PlaySessionId: 86430611... 2026-07-13 16:14:00.850 SessionManager: Removed playSession 86430611... from session 337b0590... 2026-07-13 16:14:03.005 SessionManager: Playback start reported by app Emby for Apple TV 2.0.6 (3) ... PlaySessionId: 0e78ef8c... <-- NEW PlaySessionId, same title/position 2026-07-13 16:39:53.203 SessionManager: Playback stopped reported by app Emby for Apple TV 2.0.6 (3) ... PlaySessionId: 0e78ef8c... Same device across the whole log: 977 requests, all from ONE source IP. Transcode reasons for this device: ContainerBitrateExceedsLimit, ContainerNotSupported, DirectPlayError. Server-wide: playSession "Adding" = 53 vs "Removed" = 49.

Of course no one responded.

Hallo ihr Alle, ich bin seit dieser Woche neu bei Emmy und wurschtle mich grad noch so ein... Meine Mediatheken (Filme, Serien) wurden erkannt und auch die Cover, Beschreibungen werden dank IMDB/ TVDB/ OMDB gefunden. Einige Cover bzw. Filme musste ich händisch korrigieren - hatte ich erwartet. Nun zu meinem Problem... - bei Serien wird vom Hauptcover, über Staffeln, bis zur einzelnen Episode immer nur das Cover der Serie eingeblendet. Bei Plex hatte ich zu jeder einzelnen Folge auch ein eigenes Folgencover. Habe ich was nicht aktiviert? Wo muss ich denn klicken um das noch zu bewerkstelligen? Mein bisheriges Setup: Serie (Coverbild) Staffel (Coverbild) Episoden (jeweils eigene Bildchen) Z.b. die Reihe "Es war einmal... das Leben" hat ein Coverbild. Dieses nutze ich auf für die einzelnen Staffeln/ DVDs, für jede einzelne Folge gibts Bildchen inkl. Beschriftung mit Folgentitel. Funzt bei mir derzeit alles nicht... Grüße Jan

Just thought I would give this a little bump and see if anyone has any ideas. I have CachyOS exclusively on my NVME drive. I have an SSD with Win 11. The dual boot works fine as is. Now I am trying to install Debian to a partition on the SSD as a L1 hypervisor (based on what I understand), and then Debian should be able to run from CachyOs or Windows and stay synced. I am a bit concerned about how many resources it would need to reliably stream 1080p @ 10 Mb/s using x265, although most videos would be x264/265 @ around 2-3 Mb/s while trying to game. If I want to watch something with a higher bitrate and HDR I can always offload the video to a flash drive and watch it directly from the TV. I am wondering if, in the end, a NAS might be my best option since Emby can run directly from most NAS. It's just I wouldn't have the funds until closer to September or generally the end of the year.

Always remember to provide the important detail as requested in that link:

Hello, I need your help, i have a same problem with emby and hardware transcoding. HW is down after the last update of QTS 5.2.9. before the update it's run successfully I try your docker compose with jellyfin and it's OK i try with emby and it's down (i have a premium key) Emby Server 4.9.5.0 Command line: /app/emby/system/EmbyServer.dll -programdata /config -ffdetect /app/emby/bin/ffdetect -ffmpeg /app/emby/bin/ffmpeg -ffprobe /app/emby/bin/ffprobe -restartexitcode 3 Operating system: Linux version 5.10.60-qnap (root@mini-builder-01) (x86_64-QNAP-linux-gnu-gcc (toolchain config: [gcc-4.9.2 binutils-2.25 glibc-2.21]) 4.9.2, GNU ld (G OS/Process: x64/x64 Framework: .NET 8.0.25 Runtime: app/emby/system/System.Private.CoreLib.dll Processor count: 8 Data path: /config Application path: /app/emby/system Docker compose file : services: emby-qnap: build: dockerfile: /share/Container/repository/emby-qnap/Dockerfile context: /share/CACHEDEV1_DATA/.qpkg/NVIDIA_GPU_DRV/usr container_name: emby-built environment: PUID: 1000 PGID: 100 GIDLIST: 0 TZ: Europe/Paris volumes: - /share/Container/repository/emby-qnap/config:/config - /share/mediatheque:/mediatheque - /share/Container/repository/emby-qnap/scratch:/scratch ports: - 8096:8096 # HTTP port - 8920:8920 # HTTPS port - 7359:7359 - 1900:1900 devices: - /dev/nvidia0 - /dev/nvidiactl - /dev/nvidia-uvm restart: unless-stopped image: embyhwtrc2 network_mode: bridge embyserver.txt hardware_detection-63919621670.txt

Incidentally, the old Windows Theater app worked fine. I've just pulled that from Github to test and it works. I guess if nothing else works I can still use the old version.

No, that folder doesn't exist. Everything up to /LocalCache is there, but there is no log dir. It's not a cloud VM but it is a VM. My other apps, including those from the Windows Store, all work fine. It's only Emby that doesn't launch. I also tried launching the app as an admin but that didn't make a difference other than to give me the elevation prompt by Windows. It's not part of a domain and there shouldn't be any group policies as it's a pretty standard Parallels VM that runs a handful of apps. I'm guessing the nature of it being a VM is part of the issue but it seems strange my other apps work fine. I wonder if there's anything I can try?

Maybe in 10 more years

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

I may have found the problem in my setup. Not sure yet but will observe it. I am using the projectivity launcher and hitting the home button just brings me to the custom launcher. I now closed the launcher and used stock Android. And it seems to update the continue watching section when I reopen emby from the stock launcher. I am not deep enough into Android to know if this makes a difference.

I installed the app from the google playstore. Should be the latest stable version. yes I do close the app with the home button. If I use the exit command and open the app it refreshes the progress.

+1 by country

No problem, there was a log attached to my original post on this thread that I'll reattach here, as well as a new one for today. embyserver.txt embyserver.txt

G'day. I tried this again on an Android 14 tablet after following this thread on and off over the years. I downloaded the apk from the Emby site, Version 4.10.0.19. It did not want initially to install, Android quoting that it was for an older version of Android and was missing therefore several security features. I overrode that. It then asked (from Emby Server) to allow All files access. I selected that. Small print in that dialog box said Allow this app to read, modify and delete all files......including connected storage volumes. In the USB C port I had placed a Samsung T7 4TB solid state drive and checked that Xplore could see it and its directories. Emby Server could not in the initial dialog show the external drive as far as I could tell, so I went to Xplore and it showed me it was at /storage/5AEE-B089, which I then added manually - and now Emby Server found my directories and was able to scan them. Hooray.

Well, I never got around to hitting that API endpoint, I think I just abandoned the idea at the time because I didn't want to try to ping 100s of thousands of URLs to get their information. I was just searching for how to do this exact probe and found this thread, so @TeamBthanks again! I did figure out how to get jellyseerr (now seerr) to recognize media in the library. I ended up re-having this issue recently and ended up using mitmproxy to sit in front of emby and modify the data in the API responses that emby sends to seerr so it will mark the content as available. https://github.com/bruor/EmbySeerrSTRMproxy

Thanks! Quick question: In which Emby Server version (4.9.5, 4.10, beta?) is this live? I want to test it on my setup.

File played and correction ritual performed then logs sent.

Thank you for the reply. It's not showing up in my library, I'll have to check the mount is set up correctly and the permissions on the files are right. HS

Another observation: One task that causes a jump in memory usage is backup. Emby Memory usage jumps by 200MB or more every time it runs. Having said that, it does appear the memory was quickly released after the backup.

@Cat091Hi, what version number of the app do you have installed?

The server has native support for youtube now where emby apps will use the youtube sdk on the client device and play the YT video in a google-approved way. You may want to consider updating your plugin to do that instead.

After making the setting changes, nothing seems to have changed with respect to memory usage by Emby on the Synology platform. Within 6hours of restarting the server with cache reduced to 128MB, library scan changed to 12hours (instead of 8 hours as recommended), and doing only individual library scans when new media is added, memory usage is sitting at 1.2GB as per the norm. No sudden spikes in memory usage. So that is good so far. And here is I went off script. I reinstalled several of the plugins that Luke asked to be uninstalled. Yesterday, I reinstalled TimelordTV, TimeLord Movies, and Statistics. I had library updates I was doing that required them. After doing so, the memory utilization did not change. Within 24hours, Emby was utilizing around 900MB to 1GB of memory as per the norm. This morning, I accidentally manually ran the scheduled library scan task after I added new media to my library instead of scanning the individual library. Whoops! Old habits die hard. Emby's memory utilization almost doubled immediately. This time Emby did release the memory without shutting down. I captured the memory jump with the script running. Unfortunately, I don't have the full history from server restart to the memory jump as my PC went to sleep at some point last night and shutdown the puTTy connection. I restarted the script when I woke up this morning about 20minutes before the memory utilization jumped. Whether or not it is of use? I have no idea. But I'm providing it anyway. Library scan started at around 8:54am. I'll shutdown the potentially "problematic" plugins again later tonight and continue monitoring with the script enabled. MediaStorage_emby_memory_log_2026-07-13.csv embyserver-63919547583.txt