All Activity

I've struggled with finding good plugins for adult film metadata, but I came across swapsmut.com recently. It features a solid collection of amateur videos in diverse categories and could be a fun alternative while plugin issues are sorted out. Plus, the community aspect there is pretty engaging with comment and upload features. Might be worth checking out while waiting for an Emby solution.

Several weeks ago I installed a new version of Emby. Ever since then I've had an issue /w collections. 1) The collections manager runs 1/day and it fails every time. I specifically ran it again today at 2026-07-03 10:19:59.756 ET. Fails. 2) A large % of the collections built do not have a collection image applied. If I add the poster manually or I refresh the metadata and include images, that works. But it should work for all without me having to do this 1 by 1. embyserver (2).txt

Thank you!

OK we’ll take a look at it. Thanks.

How have you configured the startup option in the app?

Hi, we’ll take a look at it. Thanks.

OK we’ll take a look at it. Thanks.

Thx is there a easy way to find the plugins folder. my server runs on a Nas server

For now I logrotate every 15 minutes and remove old logs via a cronjob so it's under control and I'll block on the firewall when able to do so. I'll probably hear from him sometime in the near future, I'll then try to get a better idea on how he managed to do this. Knowing him, he opened 20 clients at the same time when it didn't start playing immediately and then clicked everywhere as fast as possible, he's very good at creating/finding bugs Fingers crossed that a reboot will fix this. Thanks,

@jellis413 Thanks a lot for the details. That exact error has been fixed just two days ago. A new stable release will be out by the end of the weekend. Thanks again for reporting!

Hi, I had this same issue after upgrade to TOS7. Some media files was played ok, and same not. I try also beta versions, but no change. Then I noticed that same media file was failed using my browser and same time it was ok when there was a android client. Server logs show transcoding errors like this 2026-06-30 06:22:20.192 Info MediaInfoService-XXXXXXXX: User policy for emby. EnablePlaybackRemuxing: True EnableVideoPlaybackTranscoding: True EnableAudioPlaybackTranscoding: True EnableTranscodingQuality: True 2026-06-30 06:22:20.192 Info MediaInfoService-XXXXXXXX: Bitrate exceeds DirectPlay limit: media bitrate: 4763567, max bitrate: 4000002 2026-06-30 06:22:20.192 Info MediaInfoService-XXXXXXXX: Bitrate exceeds DirectStream limit: media bitrate: 4763567, max bitrate: 4000002 Transcode settings was "no limit" After change that to example 4K everything works fine. My Terra-Master NAS is F4-425 Plus with latest TOS7 updates

It sounds to me like a bug under some very specific and rare conditions. If the user with the client cannot be contacted, then I think that blocking it at the firewall level is the best option for the moment.

"home screen companion" by @soderlund can do this https://emby.media/community/topic/146080-plugin-home-screen-companion/

Maybe you can help me with my other problem too. I once downloaded the plugin 'Collections' and later deleted it, and now I can't delete the Collection Library anymore.

Too bad something like that doesn't exist, I guess

Hi. No, the developer had to step away and was not able to maintain it.

Not sure what process it could be in that would cause that. @softworkz

Hello everyone. I know there used to be the Top Picks plugin, does anyone know if it still exists? I can't find it in the plugin catalog anymore. Thanks for your help

Overnight, I did quite a bit more research, and indeed I found that my paid XMLTV did NOT contain any icon images. I am trying to write a script that will populate these, but it tough going for a newbie! Sorry, I should have done more research before asking.

Yeah, spam is not the correct word, I see your point, "flood" is more appropriate. Still, it would be preferable to have something like "last message repeated x times" like syslog if they always are the exact same event for the same client. I guess, then, the issue is "Why does the client, when receiving a 401 or 403, retries as fast as possible forever?"

Hi. I'm afraid that link is most likely not legal to access in many parts of the world so we cannot have it here. Thanks.

It was that one. The issue could have been temporary where they were switching quickly and a stream had not quite been cleaned up yet.

Hi. I would not call this "spam". You have an actual event occurring and the server is reporting it. What if it were someone you didn't know and the server just stopped reporting it after a while? You might never see what was happening.

Yes, I see a .NET error and then immediately (every time there is a .NET/app crash) a coreclr.dll error. Maybe re-install .NET is my solution? Anyway, here is one of the Event Viewer for both: the errors from one of the events for both .NET and CORECLR.DLL are attached. Thank you for your assistance. Net.txt coreclr.txt

Thanks @ginjaninja— really useful report, and that's a proper stress test (50k tracks while Emby's still ingesting, on a beast of a box ). Quick answers so you're not left hanging tonight: Safe to leave it running — these are all per-track errors, not a whole-scan failure. It'll keep chewing through the library. You won't lose progress. Analysis state lives in data/sonic.db (+ the FAISS index in data/), so stopping/retrying just picks up where it left off — and data/ is the folder to back up. Not your hardware — nothing here points at the 4090/9800X3D. It's a few software-handling gaps on our end. I've already pinned down what's going on: a handful of tracks with short/corrupt audio are tripping the analyser (the "output size too small" + mpg123 resync messages), and when that produces bad numbers we're re-queuing them instead of cleanly skipping — which is the noise you're seeing. The 10061/503s are mostly Emby being hammered while it ingests + streams at the same time. I'll fix the track-level handling (skip + mark bad tracks instead of retrying them forever) tomorrow and let you know when it's in a build. Keep it running in the meantime — the good tracks are all landing fine.