All Activity

I got so tired of waiting for 2fa and a few other features that I have made my own media server.

Same with Apple store version although interface less sluggish but crash the same way as soon as you start playing a media ! ------------------------------------- Translated Report (Full Report Below) ------------------------------------- Process: Emby [3609] Path: /Applications/Emby.app/Contents/MacOS/Emby Identifier: com.emby.mobile Version: 2.2.53 (44) Code Type: ARM-64 (Native) Role: Foreground Parent Process: launchd [1] Coalition: com.emby.mobile [1951] User ID: 501 Date/Time: 2026-06-24 20:19:41.4891 +0200 Launch Time: 2026-06-24 20:19:22.8672 +0200 Hardware Model: MacBookPro18,2 OS Version: macOS 26.4 (25E246) Release Type: User Crash Reporter Key: BE2186AF-84DA-208C-1510-C73C01210373 Incident Identifier: BCC230D3-3707-4AC6-817A-EDEB856BFEA6 Time Awake Since Boot: 2900 seconds System Integrity Protection: enabled Triggered by Thread: 30 com.apple.audio.IOThread.client Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Subtype: KERN_INVALID_ADDRESS at 0x0000000000000000 Exception Codes: 0x0000000000000001, 0x0000000000000000 Termination Reason: Namespace SIGNAL, Code 11, Segmentation fault: 11 Terminating Process: exc handler [3609] VM Region Info: 0 is not in any region. Bytes before following region: 4342546432 REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL UNUSED SPACE AT START ---> __TEXT 102d60000-104f10000 [ 33.7M] r-x/r-x SM=COW /Applications/Emby.app/Contents/MacOS/Emby

That's true. Emby only has LDAP. I am using emby behind reverse proxy with traefik and authentik 2fa. It works great with emby LDAP. Works great with the app emby as the website.

This means that Emby doesn't work properly with Authelia. If I used Authelia, it would just be a gate behind the reverse proxy--meaning I would have to log in twice--and wouldn't work properly with client apps.

@EriksUsername Looked bit deeper. Turns out, not all harddrives are supported. You can try hdparm: https://www.thelinuxvault.net/blog/linux-hdd-sleep-how-to-enable-and-disable-with-hdparm/

Oh, I almost forgot to mention that I've been a Lifetime Emby Premiere user for a long time.

HI, we'll take a look at this. Thanks for reporting.

OK we haven't tested this with strm. But it should work with regular music files.

Okay, wait... Jellyfin has an OIDC plugin, but Emby does not? It's also amazing to find out that Audiobookshelf---which went gold as recent as March 2022, and still doesn't have an official iOS app release outside of TestFlight---has OIDC support. And Emby does not.

Asi los tengo tambien probe con la extension txt y nada y en mi pc donde hago pruebas tengo los archivos originales .mp3 y al adjuntar el lrc tampoco hace nada

I have a high-performance server with 64 cores and 64GB of memory, which is only running Debian and Docker. I use Emby to manage my media files. There are many music files and some movies. I'm having trouble playing audio. In version 4.8.11.0, although there were some minor bugs, playback and display functions worked perfectly. There was no noticeable lag, waiting, or display issues.These problems occurred when I upgraded to version 4.9.X. Specifically, when I quickly skip tracks, there's a long wait. During this wait, there's a chance the music will play normally, but there's also a high probability the program will freeze and I can't stop playing. I've tried many solutions to this problem, even suspecting a reverse proxy (Nginx). Therefore, I specifically created a fresh install of Emby for testing; without a reverse proxy, with SSL disabled, and playing directly from the webpage. I found that when the version is 4.9 or higher, during the buffering phase, it always waits to send a JSON file to http://host:8096/emby/Sessions/Playing, which contains information such as the current playback status. Once the server successfully responds to this file, everything runs smoothly again. During this file transfer anomaly, even the album art wouldn't display. Video transmission doesn't have this problem, which is interesting. The attached file is a screen recording of the issue I encountered while testing Emby. I hope it can help you locate the problem. The log file contains screen recording test content. Please feel free to leave a message if you need anything else, and I will do my best to help you. My time zone is UTC+8. 2026-06-25 00-00-45.mp4 embyserver.txt

Hi there, how are your lrc files named and organized?

Just bumping this with some concern. Cheers team Emby!

No luck, same result.

That should not cause them to get removed from collections unless the item was removed from your Emby library altogether. We’d have to look at a specific example.

Looks like it.

Hi, to accomplish what?

I would say it would look better if it was similar to the Spotify logo in your screenshot but with the Emby logo instead of course. i think the current logo was based on the old movies and tv shows apps but that design now looks old school that’s why Apple removed them

The difference is that iOS buttons are square, so just the logo makes sense, but on Apple TV the are rectangular. It's not inconsistent with other tvOS apps, but probably more a matter of style. @Lukedo you prefer to change it to just the logo like iOS, or keep it like it is now below?

From time to time I get video corruption in the Windows client. This has persisted through many betas and the current stable. It appears as a regular grid of lines, whose spacing varies, and which may be horizontal, vertical, or both. The pattern varies or comes and goes if I change the size of the window. I've not reported it before, because it is hard to capture - it may be a week or two between occurrences, and when I start a screen capture it may disappear when I try to show the effect. The attached video shows it, with changes when I adjust the window size near the end. I suppose it's most likely to be hardware (Intel A380) or the driver (it's persisted through many driver updates). I have two A380s, and I'm pretty sure it's shown on them both. The source video is AV1. I cannot get the problem to appear using the web client on the same machine. Has anyone else had this happen? Paul Video 2026-06-24 142625-001.mkv

@Luke WMA lossless can't DirectPlay, but standard WMA can. Do we need to get more granular with the asf container and only allow 'wma' codec (instead of all) for DirectPlay? What other codecs besides 'wma' are supported, or is this the only one we need to add?

Great, thanks. Will report when it's available.

Client. Actually, it might only be in the beta version at the moment. Keep an eye out for the next client release, it should be resolved

here's the apple tv app design and the ios design