All Activity

@SamES

Hi, there’s no evidence it switched, in fact, we don’t even have a switching mechanism for audio like we do for video. However with this update I think we did stop direct playing opus due to all the problems reported with it. @SamES can confirm.

Just an update - backup emby server re-installed as new, reset all settings the same, no plugins, libraries being read now - likely tomorrow I can get the restore from prod happening for the users/watch states, I need to verify that process before I kill the prod system.

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

After updating to Emby for LG 1.0.51, I started noticing that Opus audio files are always transcoded, even on a local connection, but the transcoding starts the stream offset about ~30s into each track. So far I have only observed this issue on Emby for LG 1.0.51, all other local clients are able to Direct Play. I'm aware that LG and Opus have inconsistent support across models. I cannot confirm if Emby for LG was able to Direct Play these Opus files prior to the app upgrade, but hopefully if it were I would have noticed issues with playback sooner. The LG TV is an OLED C4 on webOS24 (9.2.2-1806) I did not immediately see anything in the embyserver.txt log that might indicate an issue, but one of the tracks that had issue started at 2026-09-25 19:03:12.978 and I have attached that track's ffmpeg-transcode log as well. On the server side, I have observed this behavior first on 4.9.5.0, and it has continued after upgrade to 4.10.0.40 embyserver.txt ffmpeg-transcode-69497d66-a0cd-4731-9262-96366405f79b_1.txt

Hi Luke, Following up on theme song support for the Apple TV / tvOS app. On 6 Feb 2024 you said this was planned for an upcoming update. That was over two and a half years ago. In that time the App Store build has shipped 26 versions: 1major (2.0.0), 1 minor (1.9.0), and 24 patches. If “upcoming” meant anything under normal ALM practice, the next minor (1.9) or the next major (2.0) would have been the obvious slots. Both shipped. Theme songs did not. The rest of the ecosystem already has this. Theater, the web app, and Roku have had theme songs since around 2014(about twelve years). iOS and Android mobile have had them since at least 2017 (about nine years). Android TV and Fire TV got them in 1.6.00 in June 2018 (about eight years; the release notes literally say “Support theme songs while browsing”). Apple TV is still the odd one out: roughly eight years behind the other living-room apps, and about twelve behind everyone else, even though theme media is a documented server feature and there are paid Premiere plugins (TV / Movie Theme Songs) that exist specifically to fill those files. In fact, I just personally paid for that plugin today. Apple TV is the only Emby client I use, so I have no way to use what I just bought, and no idea when that changes. I’m seriously looking at asking for a refund, because I don’t feel the need to keep a plugin for a feature I have no idea when I’ll be able to use. That puts the plugin author in a bad spot for something that isn’t their fault. The failing here is Emby. What is actually happening with this feature on Apple TV, and when do you expect users to be able to turn it on? Thanks

ScreenRecording_09-25-2026 21-21-32_1.mov

That makes sense. It's just the individual library view that I would like to have the ability to either display the entire file system, or just the items in the folder that is used to build the library.

Hi, I’ll be more helpful When I go to download something by just pressing “Download”, a blank screen pops up and nothing happens when I press the download button when I try to use “Download to” my iPhone, it says it’s downloading but nothing happens iOS 27.0 latest Emby app ScreenRecording_09-25-2026 21-21-32_1.mp4

@rob51I also run on windows server with a dedicated user for emby as a service and never had any major issues or security concerns. If you're that concerned with that user being part of the Authenticated Users group then I would just explicitly define read only or deny permissions for that user. It might get a bit tedious, but it's doable to lock down any unnecessary permissions for that user account (even on root drives). This should help you better understand how permissions are handled. Permission Precedence - NTFS.com

How's the best way to handle movies with multiple names? A lot of the Godzilla movies have the Original name and another name for the US release. Godzilla vs Monster Zero (1965) is also known as Invasion Of Astro-Monster. I've been using the Original Title field to add AKA and the extra title. It does show up in searches that way but you have to edit the Metadata to verify. The Primary view doesn't have the option to display the Original Name.

Tags must never go away. Really. I have 107,000 Tags and would have to go into therapy if they disappeared. Bulky Editor could stand some updates to be more user friendly. Would be really great is Tags could be used in some kind of structure. Like Comedy, with sub-Tags of Standup Comedy, Satire/Parody, Rom-Com........ The Inability to rename a tag is a hardship. I have a Clip App that I use to hold Tags so I don't have to worry about typing mistakes. @user24You can Bulk edit tags with Bulky Editor in the Dashboard. It's not the most user friendly but I've edited 4-5000 tags at a time with it.

That is correct. But any, remote access comes with a bit of risk; and anyone who thinks allowing others to use a VPN/tunnel to your server is safer is sadly mistaken. Whatever way you go, you should definitely have it use TLS 1.2 or greater (ssl died over a decade ago)

Can Emby add a red "LIVE" badge for live TV channels consistent with other platforms (IOS, web, etc)? This would be a nice UX enhancement in the interim until dynamic media home section has a filter for "LIVE"

Ive run it in a docker, a dedicated VM and simply on the host computer. Now, I have stand alone "mini" computer that ONLY runs emby, the data is stored on a NAS the box has access too. I have it running as a service, but I control it via scripts on my primary laptop. From a security POV, the docker or dedicated VM are ideal, the dedicated VM was easy to setup, the docker took a bunch of tweaking to get working correctly. However its been over a year or so, and I didnt stick with it. My VM was set to auto start when the system booted, in the VM I had it auto login to the the emby user, which kicked off the starting of the emby server which was installed (not as a service). Now I just have it running as a service as I mentioned above

Hi. You can see how that is contradictory. You cannot have two tracks that are default. As for selecting a track based on whether or not it can direct play, this would be a bad decision in many cases because a lot of movies will have a true movie audio track in a format like DTS or TrueHD and then a commentary track in something like AAC. If we selected based on playability, the commentary would get selected in many cases.

Can you help me get the programs again

interesting discussion. I also felt having the Versions drop-down was a big plus coming from Plex - I used to have to split into separate entries and, while I found ways to make it work, it was often annoying and artificially increased my library size and views. While I occasionally use Versions to pick different resolutions of movies, I mostly also use it for theatrical/directors editions and also special segments like deleted-scenes files/featurettes. I'm happy with how it is working for me and am not requesting any changes, but I guess I'm also using Versions in ways that were not originally intended.

I have something new to report. I have had two more lockups. With the assistance of AI, I have tracked these down to Out of memory issues in Unraid docker for ember, but these are NOT restarting the container when it happens - they just stop dead. These are the two dates and times (one was last night). /var/log/syslog.1:Sep 25 20:24:23 Tower kernel: .NET TP Worker invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 /var/log/syslog.2:Sep 22 14:28:32 Tower kernel: .NET TP Worker invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 It explains why the logs just stop dead - as emby has stopped dead itself. AI suggests this - but I take it with a grain of salt - 'Because Emby runs inside a .NET environment (.NET TP Worker), a recent update to the production release has caused either an aggressive memory leak or a massive spike in memory consumption during heavy tasks (like library scans or transcoding), triggering the host's OOM killer. When the host kernel steps in to kill a process like this, Docker often doesn't recognise it as a "clean" container exit and fails to automatically restart it. As I said before, I have had very stable system for many years. I am leaning towards a few drastic possible solutions here - I increased the container RAM after the one on 22/9. To 16GB which is very high for a container. I have a GPU doing the transcoding, but I replace any media that seems to be transcoding. I am thinking of going back to shipped - I have been using emby since the early years and I must have installed and removed loads of things in that time and something must be left behind that may be incompatible with this later version ? I am thinking of doing this - Remove emby beta from my backup server, delete the emby system folders, install emby prod. Compare any settings to the prod system, Recreate the libraries, then read media (all info files). Restore the users and watch lists from the prod system - Verify. If all goes well - Emby prod outage, Repeat the exact same process above on the prod system, and restore the users/watch list from he backup server. No plugins will be installed, only notifications from Sonarr/radarr to refresh the library will be installed. Run for a while, if no issues after a while, add the link seerr container to the system via an API.

Hi. What version of the app?

if this is your own server it's not a problem as it's the same account you would use here. If it's someone else's server, you need to contact them. No one here can assist you.

Like if you get to the artist from search then you would see them all.

Sorry, I don't understand your response

Yes. The QuickSync encoder and VAAPI encoder for H.264 crash my system without warning or logs when I use them.

I also experimented with AI. I decompiled the Emby APK and modified the `launchMediaIntent` method. After that, I rebuilt the APK, and now the integration with ViMu works correctly. Perhaps you could add this code to the official Emby app?1.txt