All Activity

Update: I updated the server to 4.10.1.0, as the patch logs stated that this version would fix HW Tonemapping for HDR. I can report that in my case, it did not. Hardware tonemapping failed again. Problem was once again fixed/solved by reverting back to 4.9.1.90

I tested and see the same. Good thinking to try this. Shuffle on Folders also shows the error.

It's not the emby guide data source, that is for sure. if the xmltv is the only one you setup, then yes.

Ah I see this in the logs: 2026-10-02 06:42:46.761 Info HttpClient: Http response 404 from https://www.fetchtv.com.au/v2/epg/program/141113/image after 76ms 2026-10-02 06:42:46.767 Info HttpClient: Http response 404 from https://www.fetchtv.com.au/v2/epg/program/246745/image after 82ms 2026-10-02 06:42:46.767 Info HttpClient: Http response 404 from https://www.fetchtv.com.au/v2/epg/program/126253/image after 82ms 2026-10-02 06:42:46.767 Info HttpClient: Http response 404 from https://www.fetchtv.com.au/v2/epg/program/1241715/image after 82ms 2026-10-02 06:42:46.767 Info HttpClient: Http response 404 from https://www.fetchtv.com.au/v2/epg/program/132592/image after 82ms 2026-10-02 06:42:46.767 Info HttpClient: Http response 404 from https://www.fetchtv.com.au/v2/epg/program/403471/image after 82ms 2026-10-02 06:42:46.806 Error ImageService-0HNOVVI34HFKN:00000005: Error processing request Are you sure these URL's are being fed from the XML TV net EPG guide? dont want to point fingers at wrong people.

I see the same when trying to shuffle albums on web app (4.10.1.0 also hosted web app 26.0.30) and Android app (3.5.63), working fine on Linux Beta (2.322.0) and Emby for Windows (2.317.2.0). Shuffle on songs is fine. Nothing is reported in the server log at all.

If this is not your server, no one here can help you. The fact you state "membership" means you are more than likely using Emby on a server that violates the terms of use.

That's what it looks like, yes. It is not a domain that we use directly.

Love these, any possibility you could generate a Music Videos Image? Would be immensely grateful. Thanks in advance

Did you mean fetchtv.com.au not .com? as fetchtv.com is just a parked domain, but fetchtv.com.au is an Australiain digital TV set top box and streaming service popular here. Although im not a customer of theres, maybe XML TV net is pointing to them for some images?

This is most strange, because I do this 4 days a week and never had an issue.

Is this the web app in the browser? can you get the contents of the browser debug console?

Hi there, let's look at an example. Please attach the information requested in how to report a media playback issue. Thanks!

Where and how exactly are you starting play from?

didn't help

You may still want to check your directories. Many people actually have these files created by other software and aren't aware of it.

Please open a topic with log file examples and we can look at that in detail and get to the bottom of it. Thanks.

Your guide data source - fetchtv.com - (never heard of them)...it is sending back 404 not found responses. So I would ask them about it. If you've never heard of them either, then your xml guide probably has image urls pointing to that domain. Maybe those urls have now gone bad, or maybe they were never working to begin with. Whichever it is, it's an issue with your guide data source.

Theres absolutely no way thats true. 4.11.0.4 beta searches flawlessly with zero issues. Downgrade back to stable 4.10.1, no go. This is on 2 completely separate servers this was tested on.

4.10.1 has everything related to search that 4.11.0.4 has.

I didn't recommend it. I just said that it would be a good time if he is looking to switch branches.

Here are 2 more screenshot examples of this issue from my system as well as the server and front end logs. Thanks for trying to fix this. embyserver.txt EmbyClient.txt

I don't use my own custom .nfo files and have TMDB as my primary metadata downloader. So I guess it is down to the metadata editor that has no actor ID fields.

I dont understand how you release the 4.11.0.4 beta, which addresses some of the issues at hand, most notably to me the search issue that is a big problem. Then AFTER you release that beta, you release stable 4.10.1.0 which does not have the fixes? The stable was released after the beta. Shouldnt it follow to include what was in the prior beta?

Well, that was the idea, maybe it still is, but I'm pretty sure ebr said somewhere that the ATV app is going to be kept as long as they can manage it, which is a bit vague, but a lot better then trying to shunt it off into app heaven asap, and as mentioned its got a fair few updates recently.

...then why would you recommend it? It would be a downgrade.