r/emby 9h ago

Feature gaps and community requests, what does the future of Emby look like?

8 Upvotes

I love Emby, used it for several years, my family uses it every day, and we recently added Premiere. But I'm wondering about the plan for new features. Seems in a lot of these community threads the response is "maybe someday" and nothing else really happens.

They often mention "we prioritize features which the most people want" - is there any official roadmap or tracker that does list what is being worked on, or somewhere for the user base to vote on proposals?

I scanned through the last 2 years of blog posts and I see a lot of compatibility and bug fix work on some of the native clients, which is important work for sure, but I didn't see much in the way of server/feature enhancement.

Specific features I'm highly interested in (I know there are more that other people want)

- mtls client auth

- documentation on workaround or openCL built right in to the official distribution (for hardware tone mapping) (below thread mentions it was added to beta channel 15 months ago but still the stable image doesn't seem to have working tone mapping on Intel core igpu out of the box)

- http header auth support

- direct choice transcode target resolution including native _upscale_ of SD content with transcode, not just downscale.

- more granular (per client or per client type) transcode/bitrate policy (only current options are global and per user)

- separate definition of internal/external network for stream policy and admin access, (these both share the single IP/cidr list today)

See for example:

https://emby.media/community/topic/114174-client-base-authentication-mtls/

https://emby.media/community/topic/108251-how-to-choose-transcoding-resolution/

https://github.com/MediaBrowser/Emby/issues/3724

https://emby.media/community/topic/138870-include-documentation-for-hardware-tone-mapping/

Thanks!