All Activity

Hi everyone! I recently moved my Emby server to a new computer. The old server was running a really old version, so I preferred to start from scratch. I plugged in my USB drives and created the libraries again. After a loooooong scan, most of my TV shows showed up correctly, but I noticed that some didn’t. Those were locked because, when I originally added them, I edited the metadata for custom reasons and didn’t want it to be modified by a general library scan or refresh. For some of them, I was able to unlock the show, press “Refresh Metadata”, and select to look only for missing metadata, and it worked. “The Bullwinkle...” show is one of those cases. But with others, like the next two on the right (“Los Caballeros...” and Candy Candy), I try the same and nothing happens. No images, nothing. Both of them have their IMDb and TVDB IDs correct. This happens with several shows. One thing the old server had correct is what was already in the .nfo files for those shows in terms of seasons and episodes. I curated a bunch carefully to match what I have. Sometimes TMDB and TVDB do not match regarding the number of seasons and which episodes are in which season, especially for older shows. So I’m looking for a strategy that will preserve and respect the current .nfo files for the show, not recreate them, and just download the missing images. Even the episode descriptions and summaries are already in the episode .nfo files. Please suggest the best strategy for that. I don’t want to make a mess. It was really hard to curate the correct order of many old shows back when I had the old server. Thanks! Sorry if it is the wrong forum to ask..I wasn't sure in wich one this topic will be more appropiate...

Hi, has this helped?

Hi, did you figure anything out?

Hi, you'll have to disable cinema intros in the Emby Samsung app for now, but this should be resolved once you have the 2.2.8 update. Thanks.

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

to get all the none movies or shows you can do it like this: so you will find them as NR when filtering and you can edit them.

Hi, not yet but it’s possible for future updates. Thanks.

Different problem. A router issue would not cause only videos of certain types to freeze, and not after exactly the same amount of time every time.

I'm not entirely sure if this is the right sub-forum to post this so feel free to relocate it to the proper form, as necessary. I have the latest binhex-Emby docker installed on an unRAID server. The Emby app is installed on multiple nVidia Shields. I have four HDHomerun tuners - two HDHR Prime with cablecards on Verizon FIOS, one HDHR Connect Quatro, and one HDHR Connect 4K for OTA TV. I recently replaced my aging Linksys EA8500 wireless router with a TP-Link AXE5400 wireless router. All devices use hardwired connections via CAT6 ethernet on a home network. In addition to Emby, I also have the Channels app installed on the Shields with the Channels DVR recording engine on a separate Windows 10 HTPC. I also have two Windows 7 HTPCs with Windows Media Center installed using EPG123 and guide data from Schedules Direct.. Both of the Windows 7 HTPCs with WMC as well as the Channels apps on the Shields have no problems tuning to live TV. When I try tuning to a TV channel in the Emby guide on any of the Shields I get a message indicating that it is unable to tune to the channel at this time. I have reset each of the tuners as well as the Shields but still cannot access live TV via Emby. The HDHR tuners show up when I access the Emby server via the Web UI so I'm stumped as to why I can no longer tune to live TV. It worked perfectly fine before I replaced the router and I tried to maintain the same settings as the old router for a smooth transition. I have the router configured for DHCP to automatically assign an IP address to each device on the network with the exception of the unRAID server which has a static IP address. I set the range of DHCP address to range from 10 to 189 with the unRAID server static address set above that range.

If you take away transcoding permissions for the user that is using the Apple TV it will allow the Apple TV to convert the TrueHD stream to LCPM. Keep in mind this can cause issues if you use this user on other devices that are not capable of converting audio. For a more information on this check out this thread:

Seems it was just a network issue for me, I just restarted my router and the issue stopped.

Restarting the router fixed the issue it seems. Thanks for the help

I am new to Emby and have lots to learn. I have purchased the appropriate Emby Premier license. Emby says recordings are in \config\emby-server. I can't find that path anywhere on my Mac. I have searched, using Finder, the Users folders, my folder under Users, the Macintosh HD folder, and ever a couple of the attached hd. Nothing. So just where is that folder supposed to be? And how can I make sure the DVR recordings go to the folder I want them to go to, the ones I listed in the DVR Settings part of my dashboard? Thank you for the help. Oh, and if it matters, I am using a Mac Mini M4 running MacOS 26.3.

Just pinging this thread to check back on any progress for a native AAOS client. FYI: I have sideloaded the Emby Android client onto my Chevrolet and it works quite well, a few screen navigation issues but I am able to connect to my home Emby Server and watch videos while parked. Currently my vehicle is on AAOS v12, but AAOS v14 just came out for it and I have heard that they may have closed the path that allowed sideloading so may loose Emby once I upgrade.

Here it is and it looks like it sees only the GPU in the Intel processor: 2026-02-21 20:37:14.108 Info Application: App details Name: Emby Client Beta Version: 2.295.0 Nom de l’appareil:debian Debian GNU/Linux 13 (trixie) ID de l’appareil:4f541598deb3410aaa798514bfeec5ce Colis: Emby Client, X64, Debian GNU/Linux 13 (trixie) Chemin d’accès aux données:/home/vincen/.config/Emby Client Beta/data Chemin d’accès au journal:/home/vincen/.config/Emby Client Beta/cache/logs Racine de toile:/opt/Emby-Beta/resources/bin/web OS Info:: Unix .NET 8.0.22 OS/App:: x64/x64 DesktopEnvironment::KDE - Version 6.3.6 Sesstion:: KDE - Version wayland IsWSL:: False 2026-02-21 20:37:14.125 Info MainViewLinux: MainViewLinux - Run 2026-02-21 20:37:14.125 Info MainViewLinux: MainViewLinux - CommandLine: /opt/Emby-Beta/resources/bin/Emby.Client.Electron.dll --no-sandbox 2026-02-21 20:37:14.444 Info PlatformCodeService: System Spec: OS: Linux Distro: Debian (raw: debian) DE: KDE (raw: KDE) DisplayServer: Wayland CPU: Intel (raw: 11th Gen Intel(R) Core(TM) i7-11800H @ 2.30GHz) IntelGen: TigerLake GPU: Intel (raw: 00:02.0 VGA compatible controller [0300]: Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:9a60] (rev 01)) IntelGpuGen: TigerLake RAM: Gb32 (bytes: 33429803008) Display1: FHD (raw: 1920x1080) [Primary] (eDP-1) Display2: NoDisplay (raw: ) Display3: NoDisplay (raw: ) Display4: NoDisplay (raw: ) Notes: - os-release VERSION_ID=13 - de version=6.3.6 2026-02-21 20:37:14.445 Info PlatformCodeService: System ^Code: 1DTG56ATZ9OC81SH81Z1 2026-02-21 20:37:14.706 Warn ApplicationStateMonitor: App_BrowserWindowFocus 2026-02-21 20:37:15.788 Debug Application: ConnectWebView 1 2026-02-21 20:37:15.989 Debug InhibitionHost: Try PortalInhibitProvider 2026-02-21 20:37:16.002 Debug InhibitionHost: Adding candidate 'PortalInhibitProvider' 2026-02-21 20:37:16.002 Debug InhibitionHost: Try GnomeSessionManager 2026-02-21 20:37:16.003 Debug InhibitionHost: Dropping candidate 'GnomeSessionManager' 2026-02-21 20:37:16.003 Debug InhibitionHost: Try ScreenSaverProvider 2026-02-21 20:37:16.006 Debug InhibitionHost: Adding candidate 'ScreenSaverProvider' 2026-02-21 20:37:16.006 Debug InhibitionHost: Try FreedesktopPowerManagementProvider 2026-02-21 20:37:16.008 Debug InhibitionHost: Adding candidate 'FreedesktopPowerManagementProvider' 2026-02-21 20:37:16.020 Debug CoreMpvPlayer: .ctor [1 - 0 16]: ctor2 2026-02-21 20:37:16.028 Debug CoreMpvPlayer: .ctor [1 - 7F5B680197A0 16]: ctor2-exit 2026-02-21 20:37:16.029 Debug CoreMpvPlayer: CommandNoThrow [1 - 7F5B680197A0 16]: CommandNoThrow: set d3d11-adapter help 2026-02-21 20:37:16.040 Debug CoreMpvPlayer: CommandNoThrow [1 - 7F5B680197A0 16]: CommandNoThrow: set gpu-context help 2026-02-21 20:37:16.070 Debug CoreMpvPlayer: DisposeAsync [1 - 7F5B680197A0 16]: DisposeAsync 2026-02-21 20:37:16.071 Debug CoreMpvPlayer: EventLoop [1 - 7F5B680197A0 20]: EventLoop: isDisposing detected, exiting loop 2026-02-21 20:37:16.071 Debug CoreMpvPlayer: Command [1 - 7F5B680197A0 11]: Command: quit 2026-02-21 20:37:16.071 Debug CoreMpvPlayer: OnShutdown [1 - 7F5B680197A0 20]: OnShutdown 2026-02-21 20:37:16.080 Debug Application: ConnectWebView 2 2026-02-21 20:37:16.081 Debug JsInteropProvider: AddJsHostObjectCore: AddJsHostObjectCore 1 2026-02-21 20:37:16.081 Debug JsInteropProvider: AddJsHostObjectCore: AddJsHostObjectCore 2 2026-02-21 20:37:16.081 Debug JsHostObjectProxy: Init: JsHostObjectProxy.Init 1 2026-02-21 20:37:16.083 Debug JsHostObjectProxy: RegisterInteropEvent: Registered event handler for JsAppHost.Resume 2026-02-21 20:37:16.083 Debug JsHostObjectProxy: Init: JsHostObjectProxy.Init 2 2026-02-21 20:37:16.086 Debug JsHostObjectProxy: Init: JsHostObjectProxy.Init 3 2026-02-21 20:37:16.086 Debug JsInteropProvider: AddJsHostObjectCore: AddJsHostObjectCore 3 2026-02-21 20:37:16.086 Debug JsInteropProvider: AddJsHostObjectCore: AddJsHostObjectCore 1 2026-02-21 20:37:16.086 Debug JsInteropProvider: AddJsHostObjectCore: AddJsHostObjectCore 2

Saw this while I was trying to figure the same thing out. Save this as like Seer.js and add this to the bottom of your index.html, above </body> <script src="Seer.js" defer></script> Seer.js (edit the placeholder link at the bottom) const AddRequestMedia = () => { const targetClass = '.headerSelectedPlayer.headerSectionItem'; const headerRightClass = '.headerTop-withSectionTabs .headerRight'; const osdClass = '.view-videoosd-videoosd'; const breakpoint = 1080; // 1. Inject Styles const styleId = 'injected-button-styles'; if (!document.getElementById(styleId)) { const styleSheet = document.createElement("style"); styleSheet.id = styleId; styleSheet.textContent = ` .request-button { background-color: #21A9E1 !important; color: white !important; border: none !important; margin: 0 15px 0 0 !important; padding: 5px 10px !important; font-family: sans-serif !important; font-size: 14px !important; font-weight: 600 !important; border-radius: 3px !important; cursor: pointer !important; transition: background-color 0.3s ease; display: inline-block !important; text-decoration: none !important; text-align: center !important; white-space: nowrap !important; } .request-button:hover { background-color: #1B8CBA !important; } `; document.head.appendChild(styleSheet); } // 2. Advanced Check: Is the OSD actually visible? const isElementVisible = (selector) => { const el = document.querySelector(selector); if (!el) return false; // Checks if element is hidden via CSS or has no size const style = window.getComputedStyle(el); return (style.display !== 'none' && style.visibility !== 'hidden' && el.offsetParent !== null); }; // 3. Logic for Visibility and Layout const updateLayout = () => { const btn = document.querySelector('.request-button'); const headerRight = document.querySelector(headerRightClass); // Hide if screen is small OR OSD is actually visible const isVideoOSDActive = isElementVisible(osdClass); const isSmallScreen = window.innerWidth <= breakpoint; const shouldHide = isSmallScreen || isVideoOSDActive; if (btn) { btn.style.setProperty('display', shouldHide ? 'none' : 'inline-block', 'important'); } if (headerRight) { if (!shouldHide) { headerRight.style.setProperty('width', '30%', 'important'); } else { headerRight.style.removeProperty('width'); } } }; // 4. Observe and Inject const observer = new MutationObserver(() => { const targetDiv = document.querySelector(targetClass); if (targetDiv && !document.querySelector('.request-button')) { const link = document.createElement('a'); link.href = 'https://your-request-url.com'; link.target = '_blank'; link.rel = 'noopener noreferrer'; link.className = 'request-button'; link.textContent = 'Request Media'; targetDiv.prepend(link); } updateLayout(); }); observer.observe(document.body, { childList: true, subtree: true, attributes: true, // Crucial: detects style changes like display: none attributeFilter: ['style', 'class'] }); window.addEventListener('resize', updateLayout); }; AddRequestMedia();

Yes, that's what I meant: with a single command, you can get it back after a FW update. And your settings and caches won't even get lost, because tthey are stored under /home. An essential element of application security is that it gets installed to a place where the account of the user doesn't have permission to write to, otherwise you are opening an attack surface that one might call "a hacker's dream"

Yup, that's very close - just one paragraph above is exactly what needs to be done... (the packages are built with electron-builder - with some customizations).

Yeah its a LOT different, this one WORKS like a charm lol Saw this a few weeks ago for appimage https://docs.appimage.org/packaging-guide/optional/updates.html#making-appimages-self-updateable

Almost all issues will come back to embedded metadata and/or multiple versions of embedded tags. As it is really impossible to troubleshoot music content without actually having the content as no ones music is tagged the same. In the end since Emby relies on what ffprobe returns from the tracks you would have the compare the ffprobe results per track per album.

This is neat, but unfortunatelly with SteamOS it work untill next OS update. root fylesystem gets overwritten except of /home. so anything installed with pacman will be removed. If you could detect steamos and install the package (maybe even the AppImage) to /home/deck/Applications/Emby instead of /opt/Emby. I can help with testing or even adjust the installer if needed With Steam Machine release around the corner it would be good to have Emby working on it too.

Unless the Universal Installer has changed since I last used it you still need to disable read only mode in steamos before running the installer: steamos-readonly disable After installing you can turn back on read only mode.

Devs will need server and ffmpeg logs for the specific example to possibly provide an answer. Just like no client has been mentioned either. But my guess would be the encoding level.

The new app is very different from the old one: The legacy app always loads and executes its UI code (htmljs) from an online source, so it's more like when using a browser to app.emby.media - so it was always up-to-date in this regard, but also insecure and subject to a lot of caveats and issues. The new app is fully self-contained, all code is included and it doesn't depend on any online connectivity. The consequence though, is that it needs to be continuously updateable in an easy way for users - that's the point which our AppImage package doesn't fulfil at the moment. It can be done - but it needs to be done first and it may take a while until we get to it. Let me think about what we could do meanwhile....