All Activity

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.

Good morning, Here is a URL that works for me (not tested with Emby but on another IPTV application): [redacted] It takes a little while to understand, but all the channels are there (you may need to replace TF1 and M6 with TF1 Swiss and M6 Swiss, which are a little further down in the list).

Hi there, I was having an issue where a windows client was sending multiple play/stop events to the server per second. I sent the user a message to try and fix this, but no response. So, first I tried to block his ip in the Remote IP address field, the logs were now filled with I then tried to remove the block and completely delete the user from the server, the spam changed to I'm getting about 50 of these message per second... I'm currently rotating the log every 15 minutes, they are about 25MB in size each, which is not ideal I will block his ip upstream when I'm able to (waiting for some hardware), but will it then spam the firewall forever? Is there a way to stop the server from logging this ? It's been doing this for a bit more than one day now nonstop. Thanks,

added the Stats for Nerds info noticed that happens when the app is windowed at first, then hitting the full screen button at the bottom right

Hello great people! Recently I facing a black screens and no sound (only subs) on my iPhone and Mac with the last apps version while playing some content like movies / tv shows that require or forced to transcode. After a lot of digging i found that enabling the "Disable HLS Subtitles" option in the "Diagnostic Options" Manu is the resoen of the black screen. If I leave the settings "Disable HLS Subtitles" untouched there is image but any subtitle is becoming gibberish and it choose the first subtitle in the list. I'm using the "Disable HLS Subtitles" because it fixed the out of sync when you fast forwards see the post here: https://emby.media/community/topic/147466-subtitles-going-out-of-sync-when-transcoding-sound/ I tied rebooting the Emby, the server physically, changing transcoding settings back and forward and reboot after each time, uninstall the Diagnostic Options addon, several devices but I was not manage to fix it. till 5 days ago it was good from the last app version for IOS 2.2.54. The test I made: - Direct play - no Issue at all (Picture, Sound, Subs) - Transcoding and "Disable HLS Subtitles" enable - issue with (Picture, Sound) - Transcoding and "Disable HLS Subtitles" disable - issue with (Subs) - Transcoding + "Disable HLS Subtitles" enable with no subs at all - no issue (Picture, Sound) *On Emby for Android app and Chrome browser all tests was playing without any issues. logs with 01 = Transcoding and "Disable HLS Subtitles" enable - issue with (Picture, Sound) logs with 02 = Transcoding and "Disable HLS Subtitles" disable - issue with (Subs) ffmpeg-transcode-e6ae01bc-3760-43d3-9520-e8ab799756e3_1-01.txt embyserver-01.txt ffmpeg-transcode-4762c6f7-e05b-432e-988b-b6518253b129_1-02.txt embyserver-02.txt

Hi Look is the same with the last version of the server. Right now i'm on 4.9.5.0

Same to me. On iphone and Mac with the last version.

Unknown. The user limit was set to 1, network to unlimited and LiveTV simultaneous to 0. So it’s a mystery to me how a single user, watching a single TV can run into this.

We've been over this for 8 months, and it's clear you're just dismissing the problem since security apparently isn't a priority for Emby. That is absolutely not how the app behaves and the issue is trivial to reproduce. Why are you so adamantly against fixing a basic security flaw that leaves restricted profiles completely exposed? It is extremely odd that you would rather shove your head in the sand and pretend a reproducible PIN bypass doesn't exist than take a few minutes to actually fix it. The worst part is this isn't even the first time you guys have completely ignored account security and PIN issues like this. This lackadaisical attitude toward fundamental and basic account security is absolutely insane.

Hi @kaj Controller Windows 11 RTX 4090, 9800x3d, Pcie 5 x 4 NVME (2GB+ sustained read/write), 1Gbit nic, 64Gbit Ram Emby server / music storage (mp3/flac various bit depths), SMB File shares, 5920K (6core, 12 thread) 1Gbit Nic, 16 GB Ram, PCIE 4x4 SSD (1GB+ sustained read). Nvidia-smi baseline (1st time ever used tool dont know wether it reliable) 800MB, Worker_Batch 2= 2GB, Worker_batch_8= 2GB, 0% Utilisation, 30W) Im pasting these errors at the plugin end just i so dont loose sight of them, dont know if they are 'interesting'. I can retest the fresh installation method, but at the moment the controller and worker and plugin seem to be Online/talking to each other (and i dont think the controller/worker/plugin have received updates beyond installation improvement), so im assuming i dont need to reinstall to keep testing? I am 50,000 tracks in according the andoid app config page, so i dont want to loose that if avoidable (with cost of electricity im £15 under :-)). Looking for advice on whether i should pause for investigation of the errors? problem with my content? problem with the chosen cuda wheel for my gpu? a 'you' problem in need of log capture my end? There was the plugin connectivity issue but does that account for all errors, i seem to be stably connected now (didnt change anything/reinstall anything, just came back to it over night). Should i do a full library scan or will that loose my analysis progress. Where is the scan data held, can i back it up as an optional part of testing? Not sure where to go. Full disclosure the Emby server was ingesting the music library during the analysis over a 1GB connection so that cant of 'helped'. the Emby ingestion has now finished. these errors look understandable/contained perhaps to inter component comms, maybe restarting a component during testing, nothing to see here? [WinError 10061] No connection could be made because the target machine actively refused it Server error '503 Service Unavailable' for url 'http://localhost:8096/Items/1300213/Download' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/503 this error looks interesting..is it just a warning. Given input size: (256x1x16). Calculated output size: (256x0x8). Output size is too small Not sure what this one is about from the worker, or what to do with it. every now and then the worker runs throughs 100s of these. is my gpu broken...ive never done any cuda workload before..(to my knowledge). Bitrot perhaps? [C:\vcpkg\buildtrees\mpg123\src\-66150af195.clean\src\libmpg123\parse.c:wetwork():1389] error: Giving up resync after 1024 bytes - your stream is not nice... (maybe increasing resync limit could help). Note: Illegal Audio-MPEG-Header 0x00000000 at offset 3937028. 2026-07-03 10:02:41 [worker] results POST failed: Out of range float values are not JSON compliant; tracks will be re-leased. Seems to continue ok after Lower batch number anecdotally produce less errors but even batch 1 produces errors see below. The Cpu, network and GPU seem underutilised (only cursory glance), could a 10GB? Cache on the worker help with audio files at the other end of an SMB\Network? the program is moderately loading the network 20%-50% according to windows perfmon so thats perhaps as good as real world gets. Doh! Emby is being used to get the files. I have restarted Emby LOL, apologies that may account for flurry of 100s of errors (edit no still happening).. all the other errors are with emby consistently up. I wonder what this resync limit is "(maybe increasing resync limit could help)" what a emby sever service restart looks like

Forgot to say, That's the plan anyway. Music album posters at first glance looks to be reused across whole albums and songs so it might be impossible to make aggregation work as it's supposed to do. I don't know if Emby uses the same tag system for music so i will have to research that, can't see why it wouldn't though. While it's mostly copy and paste work with some modifying it will take some time to do all this. So don't expect this to be ready first thing tomorrow.

1) Making it text would be ugly, the ratings only did it out of necessity. 2) The plan is to copy the TV series aggregation system, so that music will have it's own and then modify it to work with only music related properties. It will be like the TV series, all or nothing. So if not all have for example 44.1k then the icon won't be shown. 3) Plan is music will just be, format (e.g. MP3), bitrate, samplerate, bit depth with support for the tag and filename-based system. 4) That's simple.. That won't be implemented because i don't think that will ever be needed for movies and TV shows! It would though be rather simple to implement, problem is the plugin is already doing a lot and i want to try and limit CPU usage where ever possible.

Thanks for sending the logs. Yet it seems you have sent the log from the session which you started to get the log rather than from the session which exited before. (the logs from from earlier sessions have a timestamp in the name) Can you see anything in the Windows event log about app crash or something?

@LidFYI channel 323 Great Romance+1 has now been fixed

This works perfect for quicksync on my intel 265k. thank you! It would be great if emby could integrate this fix directly without this patch, but for now, I don't mind running this. Thank you