All Activity

@yockerThanks, but disabling UPNP makes it worse. After a restart emby can not be accessed anymore, no matter on which port or address. I enabled it via ssh. Emby is installed on synology via package manager. @LukeThank you, now it is loading instantly. I saw that the plugin wasn't configured (no username saved), maybe this was the problem?

Im not experiencing that in TV mode across 3 different PC's on 2 different servers.

Hi, I would like to report an issue with Bulky Editor when editing tags in bulk. I am using a mixed Emby library that contains both movies and TV series. My goal is simple: add a tag such as movies to all movies and another tag such as series to all TV shows, so I can later filter the library by tag. The problem is that Bulky Editor appears to add the tag in its own interface, but the tag is not actually applied to the selected items in Emby. What happens: I select several movies in Bulky Editor. I use the bulk edit option to add a tag, for example movies. Bulky Editor shows the tag as if it was added. In Emby, the tag appears in the filter list. But when I filter by that tag, no movies appear. If I open/check the movies in Emby, the tag does not seem to be really assigned to them. I also thought it could be related to locked metadata, so I removed/unlocked the metadata protection from those movies and tried again, but the result was exactly the same. Interestingly, removing tags seems to work, but adding tags in bulk does not appear to persist correctly in Emby. I am currently using the latest Emby beta, so I do not know if this issue already existed before or if something changed recently in Emby. However, it looks like Bulky Editor has not been updated for a long time, possibly since 2023, while Emby has continued to receive many updates. Maybe some API or metadata handling changed, especially with mixed libraries, folders, or item tagging. Could you please check if Bulky Editor is still maintained and whether it can be updated for the latest Emby versions? This plugin is very useful for bulk metadata editing, but if it is not updated, more compatibility issues may continue to appear as Emby keeps changing. Thanks.

I have a holiday to look forward to at the weekend, but will have another go when I get back.

Yes I'm certain. If I disable TV mode, there are many more there. And as mentioned, prior to the most recent update the section was larger. Also if I add a new episode to a series we're watching and its ahead in the "queue" it makes the options update as expected, and we see shows drop off the "back" of the displayed queue, only to re-appear if a show is ticked off/watched, so I'm certain there is more here than is being displayed. Screenshot attached for reference.

There is no limit of 9 anywhere. Are you sure you have more than that to display?

As mentioned above, in either application (web or 'for windows') in TV mode the continue watching section is hard limited to 9 rows, a change from a few weeks ago where it held 18.

Hi, you may want to try removing the tunein plugin, and then restarting the server and seeing how things compare.

Reading here it doesn't sound like Emby got a heads up, and it doesn't sound like a remote code execution can happen on Emby either, like it could on Jellyfin, but an Emby server could be crashed. Less than ideal, but far less worrying than a RCE. They also tested v4.8.11 rather than the current release.

I disagree, I would prefer to use my configured hostname that I entered when I manually set up the connection to the server. The resolution of that address differs depending on if I'm inside or outside my network, but it should be user choice what is advertised or utilized. I never want devices to try to connect directly to the server, and I've put policies in place to prevent that from happening.

Hi! Yes you have to set them up for each user individually. Maybe I can look into the option for a "bulk add". Unfortunately (depends how you look at it) this plugin gets very low attention from me. I just had another kid, starting a new job soon and I just bought a house... So I have my hands full On the bright side this will be a good time to test the plugin without any changes/updates before going to the plugin catalog. If an Emby updates breaks the plugin I will prioritize to get it working again, but I'm not gonna do a lot of "nice to have features" right now. There is about 100+ downloads of the plugin, with very limited bug reports, so I would consider this stable enough for the catalog. My ambition is to put it out there when Emby 4.10 goes stable.

Yes instead of having to do folder by folder. Maybe even have it have a hook to scan for new items added to those folders and autoadd them to playlist / collection they are in.

HI, what does your custom profile look like?

OK we'll take a look at it. Thanks for reporting.

i’m using docker. tried both the linuxserver and emby official images — same behaviour either way, which is partly why I moved to the official one, to rule out linuxserver-specific variables. I did try the suggested options; that’s where I started, and the device/permission side is all correct: /dev/dri/renderD128 is mounted, GIDLIST includes the render group, and the container reports libva 1.22.0 + iHD 25.2.4. The proof it isn’t a setup/permissions problem is that running the bundled ffdetect by hand inside the exact same container and image returns the full codec list (vaencdec/qsvencdec both fine). So everything on the suggested-options page is already satisfied — manual detection succeeds, only Emby-spawned detection fails. the difference between the two is a leaked file descriptor. when EmbyServer spawns ffdetect/ffmpeg/ffprobe, the child inherits an unrelated high-numbered fd from the parent — in my repro fd 117, pointing at an EmbyServer socket. a manual docker exec launch doesn’t carry that fd, which is why the same binary detects hardware fine by hand but reports zero codecs when Emby launches it. closing all fds ≥3 before exec is the only thing that fixes it: detection went straight from 0 → 17 hardware codecs (QSV H.264/H.265 decode+encode + VAAPI), and a real 4K HEVC playback then used hevc_qsv/vpp_qsv/h264_qsv with intel_gpu_top showing video-engine activity. so the question is really about the launcher, not the docker options: is EmbyServer expected to spawn the ffmpeg-family tools with arbitrary non-stdio fds inherited? if not, the fix would be setting CLOEXEC on EmbyServer’s own sockets (or only passing stdin/stdout/stderr when forking the detector), which would let me ditch the wrapper. or, perhaps even better, for someone to tell me why i chased these geese so far when the answer was right in front of me.

Also the automatic recovery is not yet supported during playback. Only when browsing the user interface.

@Grimx00perhaps you're just not waiting long enough? When requests start timing out and failing, that's when the automatic recovery happens. It may take time for that to happen.

@eliduvidhas this helped?

The horizontal home screen has never used these options.

I doubt it will help but i see some errors that has to do with UPnP. I suggest try and disable automatic port mapping if possible.

Here is the log file. The problem occurs across all clients (Windows, Browser, Android, …). embyserver.txt

Hi, they are already there, right above the guide, when you have them.

HI, to answer your question, giving us as much detail as possible is most ideal for us. In other words just letting us know what you did at what times. Thanks.

I'm old school and like to scroll through a guide, not look at thumbnails. Maybe you could add the tags to the guide somehow?

Can you please post a screenshot that shows that? Thanks.