All Activity

I switched over.. wholpin.. subtitles are a total dealbreaker for me. shame because I like emby a lot.

No offense but "upcoming 4.10 server release" could mean anytime between now and a year from now based on other past 'coming soon' releases.

Has the ability to fine-tune the timing of subtitles forward or back been removed?

Which browser are you using and what language is it set to? When I set mine to English (United States), the date is displayed the same way as in your pictures. It doesn't matter what's set in Emby. My plugin currently uses the date format of the language you have in your browser. I need to test whether it can adopt the date/time format from Emby.

Purpose and Function Clean Person TMDB|TVDB IDs (maximise agreement, remove disagreement). Split and Merge Persons, change media attribution between persons. Identify corrections for TMDB|TVDB providers. Clean Person Metadata Folder (all folders which dont belong to a person are removed) Caches TVDB|TMDB responses. Small sandbox segregation of library for faster initial testing over limited scope. Acknowledgement Uses TVDB and TMDB APIs/Data.. Notes This one was tough and i think ive ended up with at best a white elephant. I went down the route of seeing peple through the lense of their media attributions. There is no point of truth to hang your hat on and there are alot of errors on the providers, the plugin attempts to find clusters of consistent signals and stitch TMDB|TVDB info together with a score/confidence, and overlay that back over the current emby configuration to look for agreement and disagreement. Once the media and then IDs are associated robustly to persons (persons are 'clean'), it should be trivial to clean the metadata folder to match the persons. If there is an appetite and testing proves some value, i will improve but its broken me for now. Getting Started Test on backup server, at a minimum backup library.db and \metadata\people folder before testing. You need to assign a TVDB and TMDB api key in the config (I just asked for them and was sent) Run evidence gathering task. (will take hours) Manually curate "Problem Cases", cases without automated solutions. Run En Masse Correction task for automated repair of simple cases (after a lot of testing of a smal sandbox). Run Folder cleaner task. (does not respect sandbox, covers entire library) 2026-08-28 23-36-22.mp4 Disclaimers Vibe coded with Claude, backup database and people metadata folder before 1st use, until tested. folders in \metadata\people are targetted for deletion and persons are edited and removed. The SQLite database will get large ~ 50 times size of Emby database Download https://github.com/ginjaninja1/PersonCleaner 0.1.16.0PersonCleaner.dll Changes Known issues Suggestions and Issues welcome. GenericEdit UI rendering failures for dxgrid, tab/shift tab will restore ui elements if lost. Probably should have built own ui in html/js. Not tested with \people\letter\person folder layout. Very early days for metadata folder cleaner. Very early with limited testing. No library filter Roadmap See if this has legs Other Info Plugin stores data in \programdata\data\personcleaner-v2 (good to know if you want to reset/uninstall)

nah, it forces my direct played content do get transcoded (hable). DTS/TrueHD, so it is working, like before. If i remove the permission to transcode from the LG client/user, its still stops after like 5 secs in. Can we get LG client release notes, pls? ffmpeg-transcode-12230807-4d28-4b07-b72e-e3c0928ed11c_1.txt ffmpeg-transcode-fe4bf8cf-ae42-46ad-94d3-cefcfdfeace1_1.txt ffmpeg-remux-21e497f6-4b64-4e5a-b4aa-f9531a65fac0_1.txt embyserver.txt

Subs look great there actually but it doesn't pass-thru my Atmos to my receiver. There's always something missing.

Your two pictures are using different CA treatment styles so they aren't very comparable. Still, simply refreshing the metadata should update the treatment style. I think the actual issue here is this: Each item only has one primary image so, if the HD-only user is the first one to request the primary image even after you've added another resolution, they won't see it (and neither will CA) so the treatment stays at just HD. If you did a metadata refresh from a user that can see the 4K versions, then it will get the 4K treatment. CA looks for the highest resolution version and chooses the treatment based on that. Different users aren't going to see different treatments or images.

try Yamby

Ah, I see. To me, that sounds like a bug because it shouldn't be any version in the playlist but, rather, the item.

Can we get this feature added? it's been a few years since requested.. subs over the video when there's space in the black bar area is really not great.

Hello, I am having an issue with hardware HDR-to-SDR tone mapping in Emby Server on Linux. Hardware: GPU: Intel Arc A310 (DG2) Host platform: Intel Z170 BAR2 size: 1 GB maximum on this platform Resizable BAR cannot be increased to 4 GB on this system GPU device: /dev/dri/renderD129 Software: Ubuntu Kernel: 7.0.0-30-generic Emby Server: 4.9.5.0 Official Docker image: emby/embyserver:latest Firefox client on Windows Input: HEVC Main 10 1920x800 Dolby Vision Profile 8.1 / HDR10-compatible EAC3 5.1 audio The source plays correctly when hardware tone mapping is disabled. QSV decoding and encoding also work correctly. However, when Emby selects QuickSync ExtraT/OpenCL tone mapping, FFmpeg fails during QSV-to-OpenCL mapping: WARNING: Small BAR detected for device 0000:03:00.0 Failed to get number of OpenCL platforms: -1001 Failed to create derived device context Error while processing the decoded data Conversion failed The selected processing pipeline is: HEVC_QSV hwmap -> OpenCL tonemap_opencl hwmap -> QSV HEVC_QSV After this failure, Emby falls back to software decoding and x265 encoding. Performance drops to approximately 0.4x realtime, even though the Arc A310 handles QSV transcoding easily. When tone mapping is disabled, the same GPU performs the transcode at several times realtime. I also tested a newer Intel OpenCL runtime (NEO 26.31) in a separate container. OpenCL platform detection works there despite the 1 GB BAR, but the QSV/OpenCL media-sharing path still fails. Could the official Emby Docker image be updated to include a newer Intel Graphics Compute Runtime and a compatible FFmpeg/ QSV OpenCL media-sharing configuration? Important clarification: Increasing the BAR to 4 GB is not possible on this motherboard. The 1 GB BAR is therefore expected and must be supported. QSV decode/encode itself works; only the OpenCL tone-mapping path fails. As a workaround I currently have hardware tone mapping disabled, which makes playback work but removes HDR-to-SDR conversion. I can provide the complete Emby and FFmpeg logs if needed.

Sorry, I am trying to login from my android phone, I have a ds218 +, which is hard wired with a satic ip, if I am on my network it's find I can't login if I'm not on my network. Router settings is attached in picture thanks

Zoo, That's not enough info. What hardware, app or web browser are you using? Are you trying to connect with a direct Ethernet cable to the server, via Wifi? What are you router settings and firewall permissions? Local IP 192... works if you are on the same router / network, otherwise access remotely needs to use the other real IP address. Which are you trying to use when you say remotely. You cannot access remotely from another Internet access point using 192... address.

Moved to t-Mobile fiber which used CGNat, Have got access to Emby server from outside using DDns and tunnel. But the app will not connect using the same FQDN and port it says unable to reach server.

I have been trying for weeks to get access remotely. I have the port forward, my nas has a static ip. I have triple check the settings. What am I missing? Thanks for any help

This is correct. LG don't allow apps to pass uncompressed audio such as TrueHD out via eARC. It needs to be transcoded (so best to avoid TrueHD altogether)

But that's exactly how I am using it here:

Not all my remotes have a play button and that's a bit cumbersome to use. I really wish there was a way to play directly. There could be a setting. I recall Kodi having this option.

OK we are looking into it. Thanks.

What about the 220 segment? Not the last one.

I will look into it about the server Date/Time Locale. Because on my side it shows the european time. I have a few of those with created 1.1.1 too... these dates come directly from Emby and are not a plugin error.

Nice topic, I had already seen this topic on the internet. But some questions - How can I make the movie tabs wider, they seem narrow and elongated to me. - Also how to change the color of the seen and unseen icon Thank you

Following up on my own post, because I went back for the ffmpeg logs afterwards and they contain the mechanism. I attached them (ffmpeg-segment-211.txt — two runs from the same session, sanitised as described in its header). Short version: ffmpeg announces a segment when it opens the NEXT one, so the last segment of any run is never announced — and from the outside it looks like that announcement is what releases a segment to the client. The announcement lines look like this: SegmentComplete=video:0 Index=211 ... Duration=6.027000 filename=C7DAFF_210.mp4 Index=N+1 announcing filename=_N.mp4. Here are three requests from one session, on the 21-minute file from my last post, whose playlist has 212 entries (0..211): segment 106 -> full remux, no seek 212 SegmentComplete lines 200 segment 210 -> full remux, no seek 211 lines, last announces _210.mp4 200 segment 211 -> restart with -ss 00:21:06.000 -start_number 211 ZERO SegmentComplete lines never answered Across every ffmpeg log this server wrote, filename=C7DAFF_211.mp4 appears in zero SegmentComplete lines. C7DAFF_210.mp4 appears in one. Even the full remux that did write 211 ends like this: 21:04:59.046 SegmentComplete=... filename=C7DAFF_210.mp4 [hls] Opening '.../C7DAFF_211.mp4.tmp' for writing [hls] Opening '.../C7DAFF.m3u8.tmp' for writing EXIT It opens 211 and the run ends without announcing it. And the restart for 211 did its job: it wrote C7DAFF_211.mp4 — 1,657,212 bytes, 134 frames, 5.494 s — in about 10 ms at 361x, rewrote the session playlist with that one entry AND an #EXT-X-ENDLIST, and exited with code 0, 96 ms after the request arrived. ffmpeg declared the work finished in its own playlist. The server then held the request for 90 seconds and sent nothing. Two corrections I owe you on my own post from yesterday. First, I said the wait was for a completion signal "from a process that is already gone". The process being gone is not the cause: the signal is never emitted for the last segment of a run, whether the process is alive or dead. Second, I implied the restarts themselves were the problem. They aren't — segments 106 and 210 went through exactly the same restart path minutes earlier and both returned 200. What saves them is that the run continued past them, so they got announced. Which also ties this to the arithmetic at the top of the thread, and I think it's the whole bug in one sentence: because the segment list is computed from the declared duration, the last entry always sits at or past the end of the media, so it is always the final segment of whatever run produces it — and the final segment of a run is never announced. The same shape explains the 500s on short files: when the whole remux takes milliseconds, every segment requested is the last one of its run. If the wait treated EOF — or an exit code of 0, or ffmpeg's own ENDLIST, all three of which are present here — as completing the final segment, I believe every case in this thread would serve. The file is already on disk when the wait begins. Happy to run this against the next build, or to pull any other log from the same session. ffmpeg-segment-211.txt

Looking good, like the "Series finale" and: