Leaderboard

Is there plans on the roadmap for OpenID. I have searched but not found any indication this is in development. With many admins taking up SSO through Authelia or Authentik to enhance security it would be great for Emby to support it. One of the easier open standards is OpenID which the aforementioned support. Users could continue to use LDAP if they wish while others can use the arguably better SSO experience.

I haven’t received this yet but I’m watching for it….

Thanks for the workaround Ra'Jiska, but i think it's a bad idea to label this as solution. It's a workaround, a solution would be an updated beta that works, as this is a half year old issue with people asking for something reasonable like support for "current" CPUs. Besides that, nice work, love the Repo with the workflow!

I'm a plex life time member, but I have been using Emby for over six years continuously, but there is a feature which I have always thought is missing in Emby which I would like and encourage the developer to consider including especially in this dispensation where families can social or commingle due to COVID 19. Today, I received a notification from Plex about it new feature titled Watch together you can read about it here https://support.plex.tv/articles/watch-together/ The feature allows friends and families at distance to watch same movies together instantly, you simply invite all your buddy, once they signed to the system which can be seeing in the server then play and pause as needed, this I think is cool feature should be added to emby. Let's here your though if Emby developer should consider adding this feature to our beloved Emby Media https://www.bing.com/news/search?q=Plex+Watch+Together&qpvt=plex+watch+together&FORM=EWRE

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

As I'm transitioning from Volumio and Plex to Emby to centralize my usage to one app, the one thing I'm missing the most is gapless playback. This is particulary annoying when listening to albums like "Dark Side of the Moon" by Pink Floyd. I'm experiencing a buffer of about 1 second in between songs, which really ruins the immersion. Would be awesome if this would be implemented in both the Chromecast, and web player.

I am looking to see if a SAML2/OAuth plugin is something others would use. I myself would love this feature to share Emby publicly with family members and friend and worry a little less about insecure passwords that some may use. I personally am a big advocate for security as I work in IT and see how a lack of good security can cause havoc. I love Okta and what it offers. Anyone can sign up and use it for free under 1000 users if you sign up as a Developer. That is just plain awesome. Let's see who else is interested. I am excited to find out! Thanks

Hi, yes this will be coming. Thanks.

You could isolate just the useragent also in Identification/HeaderHttpHeaders also. Mediabolic-IMHTTP/1.8.225

Yeah, this is pretty much the QA engineer in me, wanting to know how things work...

My app was initially designed to stream M3U8 content on PC and Xbox. Recently, I started exploring Emby on my NAS and found that integrating it wasn’t too difficult. So I implemented a set of minimum viable features - including directory browsing, media pages, and playback. I'd love for you to give it a try. Most features are available for free. Download Link -> Microsoft Store What's working: - Directory navigation and search - Media info including genres, release year, ratings, overview, casts, video and audio metadata etc - Native playback for Windows 10/11 and Xbox Series S|X. The full feature-set of Playback including audio, subtitle, video ratio, playback speed adjustment. Change audio output device. PIP mode on PC. - Subtitles (built-in and the first external subtitle provided by Emby) Screenshots: How to access the Media Hub: Known issues: - 4K HEVC playback on Xbox is not hardware decoded. It's using local server transcoding(Native HEVC decode for XSS|X is possible but I don't want to give up the background play feature, PC is using native decoder) - Only one external subtitle will be carried over to the video. Internal subtitles are fine - Xbox version won't resume play after leaving the playback page

Don't just play a song. I don't think that will create the log entry you need. Turn the receiver off, then on, and let it establish connection with the Emby server. Grab the log file after that.

Awesome thanks!!! Have a great weekend!

Right in front of me. My brain is fried from Docker troubleshooting. Thank you.

network_mode: host

Brilliant this works a treat ! Thank you

This might be something useful in that chain. https://github.com/bluenviron/mediamtx

for everyone commenting +1, please do not forget to like the first post so it is visible

This has been referred to Gracenote

Happy to know this could help you guys and that it works on other CPUs (I only have N150 to test on). Since I am not sure how long it will take Emby's team to update libraries, I made a Github repo with actions that automatically build an image with the updated libraries when a new Emby release is published.

If the device cannot natively play the video, please still add a "Direct" option (grayed out to indicate it's not selectable).

For anyone that may be struggling with HTTP/2 support from clients to the IIS reverse proxy, you may be missing registry keys to properly enable support. I recently discovered this on my own server which started off as Server 2016 Essentials and was later upgraded to Server 2022 with the essentials roles added back in via installer. This may also be the case if you have an old install of windows 10 or upgraded from 10 to 11, as well as any kind of in-place upgrade of server os versions. I'm not sure whether these keys are present on a fresh install of IIS on more recent builds of both server and client windows versions. Check the following location in your registry: Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HTTP\Parameters You'll want to make sure that you have a DWORD key named "EnableHttp2Tls" and it is set to a hex value of 1. If this key doesn't exist you'll need to add it. You may also need to check for the "EnableHttp2Cleartext" DWORD key as well and make sure it is set to 1. After adding both of these keys and rebooting my server, logs started showing clients negotiating http/2 connections to IIS instead of http/1.1. Something else worth noting, from my testing it doesn't seem possible to establish an HTTP/2 connection from ARR to emby's webserver (or any other service for that matter) to get full HTTP/2 support from the Client to IIS & from IIS to Emby. This obviously requires making an https connection to emby, and having a trusted certificateconfigured in emby (self signed is fine as long as the host trusts it), and a host/domain name that matches the cert. From what I can tell it seems that ARR 3.0 is limited to http/1.1 at best when making outbound connections. Of course I would love if someone could prove me wrong on this last point Otherwise, IIS is fully capable of acting as an http/2 gateway for emby and other apps (assuming you don't need the connection to be http/2 on the backend)

Logs attached. anyway I solved my issue by proxifing traffic to themoviedb.org and tmdb.org via my external proxy in the EU country. embyserver-63885888000.zip

I can answer that, at least from my point of view: The Emby "standard" app is less pleasant to use. There are a number of, from my point of view, really horrendous choices that make it less pleasant to use like dropping labels underneath the images on the Next up row. It has the advantage of using a somewhat better player but the does not make up for the inadequacies of the "regular" app. I know I will eventually be forced, kicking and screaming, to use the "standard" app and it does work but it is just unpleasant to use. I guess I should be glad that I have apps to use but I believe that usability makes a huge difference between the apps.

For me, the most frustrating part is the lack of acknowledgment from anyone on the team (aside from softworkz) that this has taken significantly longer than what was initially suggested. As paying customers, don't we at least deserve some transparency or recognition of that fact? At this point, it honestly feels like there's a lack of appreciation for the people who have supported the project financially and stuck around through all the delays.

I see the same thing on Beta 4.9.1.1 On Release 4.8.11.0 it is shown here

AND if you move files your watched status will not change. One thing I do if moving files is, -create the new directory where I plan to move the files. -add the new location to the appropriate library. -shut down Emby Server and move the files. -restart Emby and confirm everything is OK. -remove the old directory from the Emby library. DO NOT put the same files in two locations that are location for the same library. Bad things happen when you do. You CAN put them in a new library with a different name, remove the original files in the old location and after a restart of Emby rename the library. If you do that emby will rescan the library though. I have found if you do it as described above - Emby doesn't rescan or anything, it just carries on as if nothing changed.

My very first computer was a TRS-80 model 1 it had "storage" that was a cassette player. I upgraded it to a single sided floppy disk drive (128 k) and there I thought was all the storage i will ever need. I then a bit later upgraded to 2 double sided double density floppy drives (512 K each) and again that was all the storage i will ever need. I then upgraded to an IBM PC with a 100 mb hard drive and, again, that was all the storage I would ever need. I then went through about 5 different computers each one with more storage than the one before until I had about 4 tb total storage. I then discovered Plex and started adding storage and started to see the warts that Plex has in its Eco structure and looked for different/better media manager and found Emby. From there I had added drives but quickly discovered that management of a number of different drives was complex at best and i discovered Drivepool and pooled my existing media storage and had about 20 tb total storage, and that was all i would ever need. I am now up to 86 tb and I may have to, pretty soon, add another 10 tb. as my 86 tb was not all I would need. I think my next upgrade will finally really be all I need as I am getting quite old and my warranty is running out so my body will have to be retired as the "Steve Austin" upgrades are not materializing and I do not have $6,000,000.00 anyway. There is an axiom in computer systems that says: "Data grows to fill available space" and I think I have proved that, at least to my satisfaction. Fortunately/unfortunately the next growth event for my data will probably be its last as my body is nearing its "EOL" and I think EOL trumps data growth. ( obtuse pun intended ) Have fun with your additional storage.

After many trial-and-error I've finally been able to get it working by rebuilding the `intel-media-driver` library with the latest version, the hard part was compiling this with dependencies having compatible ABI as the ones running on the Emby image (thanks closed source), which I found with image `ubuntu:18.04`. Sharing here to everyone who was stuck like me. To get this working you need to make your custom image of the emby image with the updated dependencies. The following steps took me 15 minutes to build on a 20 cores CPU, the build process will take longer with less cores (therefore, much longer on a N150 if you're compiling directly there). 1) Create an empty folder with a file `Dockerfile` file with the following content FROM ubuntu:18.04 AS builder WORKDIR /workspace RUN apt-get update && \ apt-get install -y \ build-essential \ git \ cmake \ automake \ autoconf \ libtool \ m4 \ pkg-config \ libdrm-dev RUN mkdir build build/usr build/lib # Libva RUN \ git clone https://github.com/intel/libva.git && \ cd libva && \ git checkout 2.22.0 && \ ./autogen.sh --prefix=/workspace/build/usr --libdir=/workspace/build/lib && \ make -j$(nproc) && \ make install && \ cd - # Gmmlib RUN \ git clone https://github.com/intel/gmmlib.git && \ cd gmmlib && \ git checkout intel-gmmlib-22.7.2 && \ mkdir build && \ cd build && \ cmake -DCMAKE_INSTALL_PREFIX=/workspace/build/usr -DCMAKE_POLICY_VERSION_MINIMUM=3.5 -DCMAKE_INSTALL_LIBDIR=/workspace/build/lib -DCMAKE_BUILD_TYPE=ReleaseInternal .. && \ make -j$(nproc) && \ make install && \ cd ../../ # Media Driver RUN \ git clone https://github.com/intel/media-driver.git && \ cd media-driver && \ mkdir build && \ cd build && \ export PKG_CONFIG_PATH=/workspace/build/lib/pkgconfig && \ cmake -DCMAKE_LIBRARY_PATH=/workspace/build/lib -DCMAKE_INSTALL_PREFIX=/workspace/build/usr -DCMAKE_INSTALL_LIBDIR=/workspace/build/lib .. && \ make -j$(nproc) && \ make install RUN find /workspace/build -name "*.so" -exec strip --strip-unneeded {} \; FROM emby/embyserver:4.9.1.0 AS emby COPY --from=builder /workspace/build/lib /lib 2) Build the image using `docker build -t emby-n150-fixed .` This will take a while, the more CPU cores you have the shorter (took me about 30 minutes with 20 cores) 3) Check that this is working by running `docker run --rm -it --device /dev/dri:/dev/dri --entrypoint vainfo emby-n150-fixed`, if this returns something as follows, then it worked: Trying display: drm libva info: VA-API version 1.22.0 libva info: Trying to open /lib/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_22 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.22 (libva 2.22.0) vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 25.2.5 (4b3a078bd) vainfo: Supported profile and entrypoints VAProfileNone : VAEntrypointVideoProc VAProfileNone : VAEntrypointStats VAProfileMPEG2Simple : VAEntrypointVLD VAProfileMPEG2Simple : VAEntrypointEncSlice VAProfileMPEG2Main : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264Main : VAEntrypointFEI VAProfileH264Main : VAEntrypointEncSliceLP VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileH264High : VAEntrypointFEI VAProfileH264High : VAEntrypointEncSliceLP VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main : VAEntrypointVLD VAProfileVC1Advanced : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointEncPicture VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointFEI VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP VAProfileVP8Version0_3 : VAEntrypointVLD VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain : VAEntrypointEncSlice VAProfileHEVCMain : VAEntrypointFEI VAProfileHEVCMain : VAEntrypointEncSliceLP VAProfileHEVCMain10 : VAEntrypointVLD VAProfileHEVCMain10 : VAEntrypointEncSlice VAProfileHEVCMain10 : VAEntrypointEncSliceLP VAProfileVP9Profile0 : VAEntrypointVLD VAProfileVP9Profile0 : VAEntrypointEncSliceLP VAProfileVP9Profile1 : VAEntrypointVLD VAProfileVP9Profile1 : VAEntrypointEncSliceLP VAProfileVP9Profile2 : VAEntrypointVLD VAProfileVP9Profile2 : VAEntrypointEncSliceLP VAProfileVP9Profile3 : VAEntrypointVLD VAProfileVP9Profile3 : VAEntrypointEncSliceLP VAProfileHEVCMain12 : VAEntrypointVLD VAProfileHEVCMain12 : VAEntrypointEncSlice VAProfileHEVCMain422_10 : VAEntrypointVLD VAProfileHEVCMain422_10 : VAEntrypointEncSlice VAProfileHEVCMain422_12 : VAEntrypointVLD VAProfileHEVCMain422_12 : VAEntrypointEncSlice VAProfileHEVCMain444 : VAEntrypointVLD VAProfileHEVCMain444 : VAEntrypointEncSliceLP VAProfileHEVCMain444_10 : VAEntrypointVLD VAProfileHEVCMain444_10 : VAEntrypointEncSliceLP VAProfileHEVCMain444_12 : VAEntrypointVLD VAProfileHEVCSccMain : VAEntrypointVLD VAProfileHEVCSccMain : VAEntrypointEncSliceLP VAProfileHEVCSccMain10 : VAEntrypointVLD VAProfileHEVCSccMain10 : VAEntrypointEncSliceLP VAProfileHEVCSccMain444 : VAEntrypointVLD VAProfileHEVCSccMain444 : VAEntrypointEncSliceLP VAProfileAV1Profile0 : VAEntrypointVLD VAProfileHEVCSccMain444_10 : VAEntrypointVLD VAProfileHEVCSccMain444_10 : VAEntrypointEncSliceLP You can compare and run the same command on the emby image, you should have a bunch of errors instead. 4) (OPTIONAL) For your convenience, I uploaded the image on DockerHub if you want an easy way to see if it works, use the image rajiska/emby-n150-fixed:4.9.1.0, though I'd recommend to build the image yourself

After nearly 9 years, emby still does not support databases such as MySQL

Semantics? Softworkz has been using the completed TVNext for at least a year according to him and I have no reason to doubt what he says. He even told me that the reason not to include it in emby was not on him and also made no sense to him. Whether true or not I think I remember something about the core of emby being rewritten and thus the completed module TVNext no longer worked correctly so then it has to be updated and that is the hold up. If that is correct then what I said is true, TVNext was completed and compatible but not included. If this is correct you are technically true here to but functionally you are gaslighting. This is the problem for the emby team...no one believes what you say anymore. You are like the Democrat Party, our eyes see something different from what you say. Emby has been broken in the web app for me since last Feb and it is not getting corrected because I have to wait for the new beta, but 16 months? Really? I apologize for busting your chops. I have nothing against any of you, I am just frustrated from having smoke blown in my face for 5 years on this issue. The reason I came to emby and the reason I bought Premiere was for the promise of LiveTV actually functioning properly right around the corner back in the fall of 2020. I have concluded there is a "Decider", as in KING here and all of you have to haul the water and suffer the consequences for him but whoever he is he has absolutely no clue how to run a business. Once again, I will reiterate. I love emby and I use it every day in some capacity but my frustration is in not being able to use it the way I want, they way that I was told it would be soon all those years ago. I just don't post much here anymore because the only thing I really care about is TVNext and I am worn out on purposely vague promises. Being vague is a form of lying people whether you admit it to yourselves or not.

@chef @Cheesegeezer Another amazing production is about to be brought to you from devs - Cheesegeezer - I have started a new theme to bring to the masses. I am a long way off completion however we can continue to update you on the progress. The layouts are about 80% complete and once completed we can start to work on the code behind. We are interested in a closed group of testers when the time comes. I would just like to say that this was originally designed for Emby WMC back in 2014 and was just release there when M$ ditched support for WMC and the project died. @shaefurr did an amazing job with the concept artwork for me to work with back then, and this theme pays homage to him. So with out further ado... here's some of the layouts that are now coded. IRIDIUM - One theme to conquer all LOGON SCREEN HOME PAGE FIRST VIEW TYPE - COVERFLOW COVERFLOW 2 BANNER VIEW FINAL DETAILS PAGE LIST VIEW THUMB VIEW