Leaderboard

Your wish has come true. Ebr was so nice as to give me an ID so i could put this and EmbyIcons in the catalog. EmbyCredits is now in the catalog under metadata.

Emby should be available for this device as of this morning.

Hello Emby Team and Community, I am writing this post out of sheer frustration and disappointment. I was originally a Jellyfin user who decided to give Emby a try, hoping that a paid, commercial product would offer better performance and a more polished experience. However, after detailed testing and comparison over the last few weeks, my conclusion is shocking: Jellyfin completely outperforms Emby in almost every technical aspect. Here is a breakdown of why I find the current state of Emby incomprehensible: 1. Ancient FFmpeg Version It is 2026. Why is Emby still clinging to ffmpeg version 5.1-emby_2023_06_25_p4? I understand the argument for "stability" and "compatibility," but this doesn't feel like compatibility anymore—it feels like stagnation. You are sacrificing performance for the sake of legacy support that holds back modern hardware. Jellyfin is already on FFmpeg 7.x, leveraging the latest driver optimizations and AV1 support, while Emby is stuck in the past. 2. Abysmal Transcoding Performance & Hardware Utilization I tested the exact same video file on the exact same hardware (Docker container). The difference is night and day: Jellyfin: consistently hits ~80 fps. Emby: struggles to reach ~30 fps. What’s worse is the resource management. Emby fails to utilize the GPU effectively. My GPU sits idle while Emby hammers the CPU. Jellyfin, on the other hand, fully utilizes the GPU for a smooth experience. Why is a free, open-source project optimizing hardware usage better than paid software? 3. The Subtitle Burning Nightmare This is the deal-breaker. Emby seems to force software (CPU) tone-mapping and subtitle burning for almost all graphical subtitles (PGS/image-based). The result? Massive CPU spikes and playback stuttering. Other players handle this by extracting subtitles or handling them on the client side much better. In Emby, it seems to be "burn-in or nothing," and the burn-in process is inefficient and single-threaded. It makes watching foreign content with subtitles a painful experience. 4. The "Brain-Dead" Audio Transcoding Logic This is just as bad as the video issues. Emby seems obsessed with converting almost all audio tracks into mediocre AAC. I tested this on the Web client with both servers set to "Auto" quality: Jellyfin: Smartly detects my browser's capabilities. If the browser supports the format (e.g., Opus, FLAC, or high-bitrate codecs), it Direct Streams the audio. No quality loss, no CPU usage. Emby: Blindly transcodes everything to AAC. Why? The source audio is pristine, my browser can play it, yet Emby insists on degrading the audio quality and wasting CPU cycles to convert it. It feels like the client detection logic hasn't been updated in years. 5. Lack of Control & Slow Library Scans Why is the library scan logic so slow? Why can't we set the concurrency for scanning tasks? Jellyfin feels snappy; Emby feels heavy and sluggish. It seems you are hiding advanced parameters from users, ostensibly to "simplify" things, but for power users, it’s just restricting. We have powerful servers; let us decide how many threads to use! Conclusion I really wanted to love Emby. I like the UI and the metadata scraping. But the core function of a media server—playing media—is inferior to the free alternative. Please stop using "compatibility" as an excuse for an outdated backend. It’s not a feature; it’s a bug. If Emby continues down this path of slow updates and inefficient resource usage, I fear the software is slowly losing its relevance. For now, I have no choice but to migrate back to Jellyfin. I sincerely hope this feedback serves as a wake-up call.

I'd really like to have 2 Factor Authentication added to the login screen. It's just this (optional) extra layer of security to help secure the server (which, especially if people use camera uploads) contains pretty private data. There are for every type of programming language quite a few libraries available, so implementation on a server shouldn't be too hard to realise

Hi, I'm a big fan of Emby, but (unless I've missed something) there seems to be very limited support for listing musicians appearing on an album (or even track). I happen to listen to a lot of jazz - where the set of musicians appearing on albums published by a particular artist / band is very 'fluid', which makes it a prticular area of interest of who is playing what on a track / album. I think it would be great if there was an option to list band members during playback. I realise the info has to come from somewhere, so I took a random album as example and quickly found a page on Musikbrainz that supplied the info: https://musicbrainz.org/release/7dca5d94-ae00-48fe-ae27-2c8dd86bf614 I've not explored if their API readily supports retrieval of this info - but it looks a promising approach. So to my qu: Is there parhaps already some support for this (plugin perhaps?), if not, could this be a future feature enhancement? Looking forward to any responses, cheers, FF

Congrats @yockerJust got the auto-update and was slightly irritated.

There are also emby client app logs that may help as well as event log fir bits-client. But as there have been fixes in the forthcoming version for downloads, it may be best for you to join the beta group we are putting together for the Emby Web app. If you like to try the next beta, let me know and i will add you to the PM thread and you can provide the requested info and get added to the beta group

Yes, it will update just like other plugins in the catalog. Will still require a reboot of the server ofc. Edit: You will need to install it from the catalog before it will automatically update. Having the dll manually installed is not enough.

WOOOOOWWW nice! thx a lot to you and @ebr! So when an update drops is the plugin updated automatically? P.S.: using EmbyServer on Linux in an Unraid docker.

Ich schätze, dass Ryo Saeba genau die richtige Frage gestellt hat. Durch deine Ordnerstruktur in Kombinationen mit den gemischten Inhalten werden manche Filme wohl als Serien oder Episoden von Serien gematcht. Verwende am besten nfo Dateien zum Speichern der Metadaten, so dass korrekte Matches erhalten bleiben. Eventuell hilft es, eine neue Filme Library zu erstellen, und diese die Metadaten korrekt für deinen Filmeteil matchen zu lassen. Initial könntest du auch mit z.b. mit Tiny Media Manager die Ordner+Filme korrekt mit nfos für Emby versehen lassen. Deine Extras kannst du in entsprechende Unterordner wie trailers verschieben, siehe Emby Doku, so dass sie ignoriert werden, TMM bietet auch eine Option, Ordner beim Scan auszuschließen.

Hi, yes this is the most common reason for conversions taking up a lot of disk space.

Conversions should not fill up the space unless there's a problem with the job or a bug. Each file that's converted is copied back into the library based on the settings (replace or new version) and the temporary work file should be deleted. If there's a problem copying the file back then work files could be left behind. Usually because the library folder (directory) or the source media file itself have the wrong ownership and/or permissions that keep Emby from creating or overwriting. Other problems or failures during conversion could also leave files behind. The activity should be logged along with possible errors. Enable debugging to get more detail in the logs.

2.5.0 configuration pages seem to be working with reverse proxy. I have yet to see Tracer do anything, but I have other priorities now. Thank you

Downloaded and testing. If there are any issues, I'll let you know.

It works absolutely flawlessly, I tested it on my kometa , many thanks for this. Really really appreciate it.

I will consider it, just not sure i would like the responsibility. Also requires that it gets accepted.

It is too much, some changes was made in the DB and if you don’t have enough RAM this will be consumed with a couple of user’s when the app start

Try to set 64MB instead of 128mb on the DB settings and do a server reboot, let me know if this helped you

Thank you so much for this plugin version, you are a true legend , I loaded this and it picked up in my plugins folder on my Emby. I am running Kometa now to see if it will apply the overlays. I must say a massive thanks for this.

@yocker Any plans to release this plugin in the emby plugin store? This way we dont have to care about manual updates.

@hatharry YES... F'ING YES.. it works!! happy happy joy joy Thank you Merci Beaucoup

Try this one, i changed the pathing slightly. EmbyCredits.dll

I know this is an old post, it's the web browser. In Chrome go to the 3 dots at the top right, then settings, click Reset Settings. This seemed to fix the issue for me.

@mainsupport Thank you. I also needed to dowgrade from .Net8.0 to 6.0. I've also added a thumb, working on my 4.8.3.0 installation Please beware: either I mixed up my 4.8.3.0 test install with my production server and deleted my database myself by accident (as Emby was constantly auto updating the fresh 4.8 install to 4.9.3), or the plugin might have deleted my 4.10 database while testing the downgraded version. Either way, using this version is currently only reconmended for 4.8 server versions. Please make sure to have a working backup, just restoring my libraries... /EDIT: After restoring the backup and multiple restarts I come to the conclusion that I've deleted the db myself. Plugin working fine with Emby server 4.8.3 & current beta. Btw. new image, new name. EmbyKometaOverlays.dll

@Luke I think it should be an option but with a disclaimer that it is an experimental feature and may not be consistent across all devices. Maybe only allow it to trigger when transcoding is not occurring.

Hi, @Lukethis is the whole capture. I will try to do the same capture between Kef device and minidlna server. test_dlna.pcap

I've been following for years hoping to see this implemented. Even though it doesn't seem like anyone cares, I'll throw in my +1 for this to be implemented please...

Emby is not a piracy service.

That may be the case and only you guys would know how different the reported ffmpeg 5.1 is from newer 5.1.x or the current 7.1 release. But to me it brings up another thing. That Emby transcoding and ffmpeg IS softworkz. And as good as he is it seems that putting all of your eggs in one basket is risky. Between the long release cycles, his availability and the locked-in nature of a forked ffmpeg there's exposure you might not have if you were using the mainline. I get that you have your reasons for this approach. In my opinion the OP is wrong on most counts though there have been more than a few cases of side-by-side examples where some aspect of HW accel doesn't work in Emby while it does with Jellyfin and standalone ffmpeg.

It is per .db file and each .db file can have multiple connections up to a set maximum We have these databases: authentication.db, activitylog.db, users.db and library.db. The cache is defaulted as 128Mb per connection for the library.db and hard wired at 64Mb for each of the connections to the other db's We can have up to 5 connections for each of the library.db and authnetication.db and up to 3 connections for each of the remaining 2 databases. So with the defaults, the max cache Mb usage could be 640Mb for the library.db and 704Mb for the other 3 db files. So maximum

Is your /tmp file system RAM backed or disk backed? This is where the temporary files will go when remuxing or transcoding. Do you monitor the space used for this path?

Comments are going to slow down the user interface unless these are on a separate screen you click the link or button to get to. Again its not a computer app like iTunes for feedback. Most people just have a remote for Tv use and who is going to type comments on onscreen keyboard. I also wouldn't want Emby tied in to referring to any web sites. I have all my meta data on the server already and wouldn't want slow web sites or timeouts cause of web site down etc. Luke, if this is enabled, can an option be to disable comments completely please?

Hello! I love Emby, but the limitation of SQLite makes it impossible to scale this across multiple nodes. I think it would be better for anyone if there were an option to use Postgres (or MySQL or Mongo or whatever) so that we could scale it to multiple nodes, as I think this would put less strain the devices when multiple users are streaming and transcoding. I thought about adding this myself (I'm a software engineer), and I think I could, but from what I'm seeing it looks like it would be a relatively big ripping of the `ManagedConnection` by making it use some kind of `IDatabase` or something. I'm not opposed to doing it, but currently the only language I use for work is F#, and while I would be happy to write a Postgres driver in a super-duper-functional style, I don't know that that would be approved upstream, and my OOP experience is a bit out of date. -Thomas Gebert.

Hi, we’ll take another look at it. Thanks.

HI, we are working on chasing this down. Thanks.