All Activity

Why? The issue with this is someone has to put the infected file onto your server, and then has to wait for ffmpeg to do it's thing, and even then, Emby is apparently not RCE capable. If you're not getting your files from questionable sources, and doing it all yourself, you really have nothing to worry about. I remember when everyone was freaking out back when there was the subtitle exploit, and people blew it out of proportion. You could fully RCE a system with en embedded subtitle, but again, if you weren't getting your files from sketchy sources, you had nothing to worry about.

Pixel, size, sorry. if you zoom in my picture you see that the covers are to small. that's just ugly... and is probably an easy fix?

Hi, what do you mean by adding some px?

Sounds like something a tool could be developed for but not really broadly applicable such that it should be a part of the main interface.

For those that do not want to wait - You can possibly just replace the ffmpeg from the beta. I would suggest keeping a copy of the stable ffmpeg to rollback if this does not work, but it would seem unlikely that a newer ffmpeg would fail to work with the stable codebase imo. Beta source here - just extract the ffmpeg from the zip's etc - do not replace ALL the files ! https://github.com/MediaBrowser/Emby.Releases/releases/tag/4.10.0.16 Try at your own risk - I have not tested this.

Hello everyone, As we move closer to the end of the Ear Wax beta program, I wanted to take a moment to share the Ear Wax development roadmap with you. Ear Wax has come a long way since the beginning of the project, and development will continue after the public release. The goal of Ear Wax—and the lane it will stay in—is simple: to let you listen to your personal music library on your Alexa-enabled speakers using consistent voice commands, regardless of which supported media server you use. Ear Wax is designed to complement Plex and Emby—not replace them. Its purpose is to enhance voice control of your personal music library while allowing Plex and Emby to continue doing what they already do well. Going forward, there will be two editions: Ear Wax – Free Ear Wax Select – Available through a small monthly subscription. Rather than describe every feature in detail, I’ve attached a feature comparison spreadsheet that shows what’s included in each edition. Thank you all for your assistance during the beta. Your feedback has helped shape Ear Wax into what it is today, and I look forward to hearing your thoughts on where it goes next https://global.discourse-cdn.com/plex/optimized/4X/c/8/a/c8aaa96888fd20fe623b9c178a167d01a61d595c_2_690x446.jpeg

Pushed into the latest beta and not as a hotfix is really disappointing. Regardless, thank you for the fix.

Is there a plan to add back the previous functionality to limiting refreshing internet channels to only new/added links? Each refresh takes 10hrs to reprocess 500k+ links when only a handful are new. I feel a little guilty of all the carbon emissions that are created with each refresh.

How's the stable fix coming along, team Emby?

Yes - I can confirm the magicyuv decoder is now disabled in ffmpeg. Tks Emby. 4.10.0.15 C:\Emby-Server>system.old\ffmpeg -decoders | find "magicyuv" ffmpeg version 5.1-emby_2023_06_25_p4 Copyright (c) 2000-2022 the FFmpeg developers and softworkz for Emby LLC built with gcc 12.2.0 (Rev10, Built by MSYS2 project) Execution Date: 2026-06-26 14:24:48 VFS..D magicyuv MagicYUV video EXIT 4.10.0.16 C:\Emby-Server>system\ffmpeg -decoders | find "magicyuv" ffmpeg version 5.1-emby_2023_06_25_p5 Copyright (c) 2000-2022 the FFmpeg developers and softworkz for Emby LLC built with gcc 12.2.0 (Rev10, Built by MSYS2 project) Execution Date: 2026-06-26 14:24:39 EXIT

The thing is, there are 3 major software vendors and all 3 of them fall short in one way or another. But there are indeed several features that I have been requesting for several years that either have been completely overlooked or else only given a barebones implementation. I wouldn't say it's dead, but I haven't been expecting major feature updates for a while now. They can't even get audiobook implementation right, and I feel like I'm the only voice still bothering to ask for it.

Hi! No sir. N/

Do you have Cover Art plugin installed by any chance?

hi is there a possibility to slightly change the size of the covers? for my skin arctic zephire reloaded this standard is not as beautiful as it could be...I saw that with other skins as well. maybe just adding some px would solve that? thanks

Hi! I have custom library images made for the "front wiev" in regards to the librarys and also one of the librarys wich is my collection folder. I change them on my win 11 server manually, and those are then visual on all my apps (Android Universal) on my phone and Nvidia Shield aswell as Android TV app on the same shield like so: But it changes back to: I have disabled all fetching of metadata in the library settings on my server but this still happens. I seem to recall that there was a setting to "show library folders as a picture" but i cant seem to find it and disable it if that was the solution. This is also applied to my collections from my collection folder (Filmsamlingar in front-wiev librarys) from: to: I havent been able to figure out why this occurs and when, i have tried to pinpoint when it happens by running manual metadata scans and library updates and that doesnt break it so im all out of clues, any help would be appreciated. This reproduces itself to all connected apps. N/

Added a new beta to the catalog (v2.6.6.0) Changed a few FFMpeg arguments plus added "-hwaccel qsv" as fallback. This *SHOULD* work and the fallback makes ffmpeg automatically try it self if everything else fails. Just so people don't think it's a major problem (should ofc. be fixed anyway!!) Vaapi in this instance will work and is just as fast as the hardware acceleration is only for extracting images and nothing else.

Hi, The playback device is ugoos am9 pro. Client is latest emby for android and emby for android tv. Both of them has following issues: 1. Purple color when playing DV Profile 5 content, even the box do support it. 2. Hi-end audio codecs are down mixed to AC3 but not passthrough, even all my devices support that. Tried with some third party client app like Moonfin, Yamby, all of them work fine without above two issues. Please, think about to upgrade the playback engine of emby client! Looking to other popular playback apps in the market, they are widely include at least two playback engine into the app - the native media3 core, and the mpv core.

I missed that. Thanks much!

@dcatiany plans to make this open source?

@LukeAny closer to finding a permanent fix to this 2-year bug Thanks

It works for me with linuxserver. There was an ffmpeg update in the new beta.

This works but not with nvidia gpu and dont show in here.

Hi team I've hit a wall trying to get my docker install of emby working with gpu transcoding. I;ve got all the package working and both cli on server and in container cli all see the card. nvidia-container-runtime or the legacy nvidia-docker2 are all installed as well. Connecting to emby... Shell: /bin/sh, User: root / # / # ls /dev/nvidia* /dev/nvidia-modeset /dev/nvidia-uvm /dev/nvidia-uvm-tools /dev/nvidia0 /dev/nvidiactl nvidia-smi +-----------------------------------------------------------------------------------------+ | NVIDIA-SMI 580.126.20 Driver Version: 580.126.20 CUDA Version: 13.0 | +-----------------------------------------+------------------------+----------------------+ | GPU Name Persistence-M | Bus-Id Disp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap | Memory-Usage | GPU-Util Compute M. | | | | MIG M. | |=========================================+========================+======================| | 0 NVIDIA RTX A2000 Off | 00000000:01:00.0 Off | Off | | 30% 28C P8 6W / 70W | 0MiB / 6138MiB | 0% Default | | | | N/A | +-----------------------------------------+------------------------+----------------------+ +-----------------------------------------------------------------------------------------+ | Processes: | | GPU GI CI PID Type Process name GPU Memory | | ID ID Usage | |=========================================================================================| | No running processes found | +-----------------------------------------------------------------------------------------+ nvidia-container-cli info NVRM version: 580.126.20 CUDA version: 13.0 Device Index: 0 Device Minor: 0 Model: NVIDIA RTX A2000 Brand: NvidiaRTX GPU UUID: GPU-6ba078af-51d7-13c5-a9c3-4070981db16a Bus Location: 00000000:01:00.0 Architecture: 8.6 I think it has something to do with the docker compose. services: emby: image: emby/embyserver:latest container_name: emby runtime: nvidia # Expose NVIDIA GPUs hostname: emby environment: PUID: "1000" PGID: "1000" GIDLIST: "993" TZ: "xxxx" NVIDIA_VISIBLE_DEVICES: "all" NVIDIA_DRIVER_CAPABILITIES: "compute,video,utility" labels: - "traefik.enable=true" - "traefik.http.routers.village-https.entrypoints=websecure" - "traefik.http.routers.village-https.rule=Host(`xxxx`)" - "traefik.http.routers.village-https.tls=true" - "traefik.http.routers.village-https.tls.certresolver=cloudflare" - "traefik.http.services.village.loadbalancer.server.port=8096" - "traefik.http.services.village.loadbalancer.passhostheader=true" volumes: - ./config:/config - /mnt/synology:/san-backups - /mnt/VillageFS:/VillageFS - /mnt/VillageFS2:/VillageFS2 ports: - "8096:8096" - "8920:8920" - "1900:1900/tcp" - "1900:1900/udp" - "7359:7359" # devices: # - /dev/dri:/dev/dri # VAAPI/NVDEC/NVENC render nodes restart: unless-stopped networks: - ggNet networks: ggNet: external: true Any help would be amazing thanks as its doing my head in... i know it will be something to do with the GID

@a11an I have looked into having preset collections custom images and whilst we do not have functionality to pick images for collections automatically from a folder structure as you gave But I managed to get it to work and pick my custom images for the collections So for each movie, the nfo would have the collection name defined with different variations possible - either with a tmdbid for the collection or without I am going to use examples I had from other users This one with a tmdbid of 661028 for the collection <set tmdbcolid="661028"> <name>Pokémon Best Wishes! Collection</name> </set> and this one is an example where there is not a tmdbid <set> <name>Blaxploitation Classics Vol. 1</name> </set> Then you would create a folder for each collection named either with a tmdbid or without, depending how the set was defined So for these 2 examples, I would have folders for the collection images and collection.nfo named like this Blaxploitation Classics Vol. 1 and Pokémon Best Wishes! Collection-tmdb-661028 In these folders i have files like: poster.jpg, collection.nfo These collection named folders need to be copied into the metadata\collections folder under the Emby Server Data Folder Having a pre-existing collection folder there may change the timing when adding media / scanning / refreshing - so there may be some odd issues that crop up as this is not the normal way for collections to be created Update: Adding more info This is the structure under metadata\collections for my tests C:\USERS\EMBYTEST1\APPDATA\ROAMING\EMBY-SERVER\PROGRAMDATA\METADATA\COLLECTIONS ├───Blaxploitation Classics Vol. 1 │ collection.nfo │ poster.jpg │ ├───Pokémon Best Wishes! Collection-tmdb-661028 │ collection.nfo │ fanart.jpg │ poster.jpg │ └───Tommy Gibbs Collection-tmdb-534652 collection.nfo poster.jpg And this shows my custom images for the collections

BTW Bulky is Version 1.0.20.0 and my Emby Server is 4.9.1.90 for QNAP. Bulky was installed from the Plugins library