All Activity

@Luke, if you need someone to test something for you, let me know.

Yes，have .nfo

@adnaan77has this helped?

Hi, we are getting closer to having a new ffmpeg build on the server beta channel. Thanks.

And is the metadata locked for the item?

what image types are enabled for download in fetcher settings?

There won't be any exposure of actual data because that is blocked at the api level. This is just the web app allowing that html screen to be viewed when it should be bouncing back to the login screen. You can pick any server screen you want and they'll all be throwing errors and displaying black and putting up error messages if you pressed anything.

Well that's good to know! I made this because I know I was interested in it at the very least. As a MVP it's has a surprising amount of features. If anyone would like screenshots of other features I'd be happy to post them.

Hi, this thread is not dead. Your screenshot looks nice.

will never see it probably

Attached. Thanks! embyserver-63911807999.txt

This is my Server logs https://pastebin.com/GPDk2pWb

I know this thread is kind of dead but I do wonder if there is still an interest in this feature via a plug-in. Because I've been working pretty hard on something but don't want to put the work into trying to get it out unless there is actual interest in it. Let me know any thoughts.

@Hoochee?

Hi, not currently, but this question has come up before and options are possible for future updates. Thanks.

If it helps I've rotated the log file, still with debugging enabled, and ran the "inotifywait" watchers again, and saved the output, to align the two logs and be able to compare timestamps, and perhaps narrow down what is triggering it embyserver_inotifywait.txt inotifywait_log.txt

Is there a way to turn off the splash screen?

HI, the horizontal home screen doesn't show information under the poster, but rather shows info about whatever you have highlighted. In general it also just doesn't have the full feature set of the vertical home screen. It really is a special sauce screen taken from an old design of ours and it's specifically for the users who still want it. It sounds to me like you want to use the vertical home screen.

Apologies for the late reply, as I haven't had access to the server for a couple of weeks. After some more testing I'm back with some more information, and I can now say that disabling the saving to NFO files doesn't fix this. As you correctly suggested. I've attached another server log, with debugging enabled of course, but not really that much new in it, unfortunately. However, I noticed that the spin up seems to happen right around when chapter images are queried. Not that they necessarily are related, just that I noticed this is where it hangs while waiting for the disk to spin up, as you can tell by the time. And for context, the movie that triggered the drive spin up in this log, is "Ice Age - Continental Drift (2012)" around 18:17:28, and it also only has the two files, the .mkv and the .nfo. 2026-04-15 18:17:37.755 Debug ImageService-0HNKNOMEABN1D:00000024: http/1.1 Response 200 to host2. Time: 9479ms. GET http://192.168.0.245:8096/emby/Items/12317/Images/Chapter/0?maxWidth=972&tag=cf47c124579c3b18e6bd388dbc9880b1&mediaSourceId=mediasource_12317&quality=90. 2026-04-15 18:17:37.755 Debug ImageService-0HNKNOMEABN1G:00000023: http/1.1 Response 200 to host2. Time: 9479ms. GET http://192.168.0.245:8096/emby/Items/12317/Images/Chapter/1?maxWidth=972&tag=cf47c124579c3b18e6bd388dbc9880b1&mediaSourceId=mediasource_12317&quality=90. This however led me to try and monitor disks for access to get a better understanding of what is happening. So I setup "inotifywait" with watchers for all the disks in the array, and more specifically the "movie" share. And surprisingly it actually seems to always access the folder containing the movie whenever the details page is accessed. Whether that is due to trying to query the chapter images, just verifying that the files still exists, or something else, I'm not sure. Here's an example of the output from the "inotifywait" watchers when accessing a random movie: 18:59:41 /mnt/disk1/movies/The Green Mile (1999) OPEN,ISDIR 18:59:41 /mnt/disk1/movies/The Green Mile (1999)/ OPEN,ISDIR 18:59:41 /mnt/disk1/movies/The Green Mile (1999) ACCESS,ISDIR 18:59:41 /mnt/disk1/movies/The Green Mile (1999)/ ACCESS,ISDIR 18:59:41 /mnt/disk1/movies/The Green Mile (1999) ACCESS,ISDIR 18:59:41 /mnt/disk1/movies/The Green Mile (1999)/ ACCESS,ISDIR 18:59:41 /mnt/disk1/movies/The Green Mile (1999) CLOSE_NOWRITE,CLOSE,ISDIR 18:59:41 /mnt/disk1/movies/The Green Mile (1999)/ CLOSE_NOWRITE,CLOSE,ISDIR 18:59:41 /mnt/disk1/movies/The Green Mile (1999) OPEN,ISDIR 18:59:41 /mnt/disk1/movies/The Green Mile (1999)/ OPEN,ISDIR 18:59:41 /mnt/disk1/movies/The Green Mile (1999) ACCESS,ISDIR 18:59:41 /mnt/disk1/movies/The Green Mile (1999)/ ACCESS,ISDIR 18:59:41 /mnt/disk1/movies/The Green Mile (1999) ACCESS,ISDIR 18:59:41 /mnt/disk1/movies/The Green Mile (1999)/ ACCESS,ISDIR 18:59:41 /mnt/disk1/movies/The Green Mile (1999) CLOSE_NOWRITE,CLOSE,ISDIR 18:59:41 /mnt/disk1/movies/The Green Mile (1999)/ CLOSE_NOWRITE,CLOSE,ISDIR Any idea as to what might be causing it to access the folder containing the media whenever you view the details page? The surprising bit here, is that after I had setup the watchers I could no longer reproduce the issue for the movie library. And the answer to why that is, is that "inotifywait" of course needs to traverse all the directories to setup the watchers, and in doing so the directories are added to the RAM cache (VFS). So, it appears that the reason for the spin up is that the directory of the movie, which details page I was accessing, wasn't cached to the RAM. At least that is my theory, since I haven't been able to reproduce it since. I've now manually "forced" the directory structure to be cached by the RAM by simply running a find command, and thereby touching all the directories. find /mnt/disk*/concerts/ /mnt/disk*/documentaries/ /mnt/disk*/movies/ /mnt/disk*/series/ /mnt/disk*/standup/ /mnt/user/concerts/ /mnt/user/documentaries/ /mnt/user/movies/ /mnt/user/series/ /mnt/user/standup/ -type d But I'm still wondering why Emby needs to access the directory when all the metadata is supposed to be in the server folder, which is currently on a separate SSD? Any ideas? embyserver.txt

Could be, Luke once wrote rhat PIL Skia is only one possibility for the overlays and it‘s not available on all platforms, will investigate. Can you take a look in your server log and see if you some errors in your server log after the reboot?

I've been doing a lot more digging in to this as I thought I had things working, but I do not. Only decoding, no encoding with the A380. @kikinjoWould you mind confirming that both encoding and decoding are working for you and not falling back to CPU and if you would not mind sharing the following as the only next step that I can see is for Emby to rebuild ffmpeg. I'm running 4.10.0.10. Kernel version (I assume still 6.17, did things work before 6.17? Is that the only thing you needed to do to get QSV working)? Intel media driver version (vainfo driver string and package version), libvpl / oneVPL versions, ffmpeg version and whether it’s built with --enable-libvpl, does your direct ffmpeg -hwaccel qsv -c:v h264_qsv ... command work without device creation errors. QSV fails even though I have options of QSV in both encoding and decoding. QSV needs to be disabled for me for my system to work. I only have VAAPI options in decoding (they work). I do not have VAAPI options in decoding. Thank you.

@Error3972Are you running the beta server? Luke, I can reproduce with the latest beta server. It looks like the new image validation is failing but the image tags are being provided and this was not a problem until the most recent server beta release. 2026-04-15 14:23:25.011 Debug ImageService-0HNKQVE5EALOI:0000009F: http/1.1 GET http://‌192.168.4.46‌:8096/emby/Items/5175575/Images/Primary/0?EnableImageEnhancers=true&tag=dc8b048b0e1469b45d6c4642651dca3c&maxwidth=244&maxHeight=1080&quality=90. Source Ip: ‌192.168.4.65‌, UserAgent: Roku/DVP-15.2 (15.2.4.03416-46) 2026-04-15 14:23:25.012 Error ImageService-0HNKQVE5EALOI:0000009F: Image access denied

I'm able to reproduce this. While no server details are shown it is problematic that someone could get past the login page without having authenticated. The potential is there for a secondary vulnerability to allow even deeper navigation or exposure of actual data.

Before make changes to "about:config" After make change

Thank you for making one so fast, I have tried to load this plugin but its not working could it be because I am using Arm64 as well?.