All Activity

OK. user data, which is not metadata, does not get purged from the database unless the user is deleted. this is also what makes it possible to move a movie file from one place to another and have it retain watch data.

What exactly happens?

The latest beta server build has a hidden config switch. so if you open up the /config/system.xml file, set ValidateImageTags to true and then start the server. this will make the image tag value required, which will be unique per image and therefore you won't be able to guess a url anymore. It's an opt-in config switch for now to allow for time to identify cases where that param may not be supplied.

Record a program, watch the program, delete the program, record the same program again and Emby thinks it has already been watched.

I think if you can produce another couple examples then it might be easier to identify the common thread. Thanks.

@Brusniss?

HI there, can you please provide a specific example? How to Report a Problem Thanks !

You can also try that IPTV app on an Android emulator, and then intercept those requests using a tool like Fiddler, so you'll know what kind of request headers your IPTV streams accept. Once you do that, you can tweak the streams you added through Dispatcharr accordingly. Good luck!

Examples above, but I have only local IPs in my log. Still inconsistent behavior.

They actually should be, as long as those are remote IPs - but by no means it means it works 100%, you might've just found a bug - but you need to provide specific example.

Indeed I see the difference now, if a device/endpoint has a host name, it is obfuscated (e.g., "host2") but if the device/endpoint has an IP address then it is ignored and not obfuscated. (at least in most cases) What's the point of that?

Have you tried messing around with the Stream profiles when adding a new stream?

hosts are generally masked remote addresses - you can also see them unmasked if you look at the log directly in the Web UI or toggle-off log anonymization before downloading it so you can easily compare raw vs. sanitized log and find out all the addresses.

@ebr?

What is "host1"? (my HDHR does not respond to that URL) Shouldn't the HDHR device IP address be obfuscated? 2026-03-31 00:00:03.011 Info LiveTV: Discovered tuner device HD Homerun at http://192.168.50.163 2026-03-31 00:00:03.012 Info HttpClient: GET http://192.168.50.163/discover.json 2026-03-31 00:00:03.016 Info HttpClient: Http response 200 from http://192.168.50.163/discover.json after 4ms 2026-03-31 00:00:03.068 Info HttpClient: GET https://api.hdhomerun.com/api/lineup?DeviceAuth=ioMZ5KSi95xUFM-lc72nGfYM 2026-03-31 00:00:03.241 Info HttpClient: Http response 200 from https://api.hdhomerun.com/api/lineup?DeviceAuth=ioMZ5KSi95xUFM-lc72nGfYM after 173ms 2026-03-31 00:00:03.250 Info HttpClient: GET https://host1/v1.1/lineups/USA-OTA35810/channels?enhancedCallSign=true 2026-03-31 00:00:03.250 Info HttpClient: Http response served from cache from https://host1/v1.1/lineups/USA-OTA35810/channels?enhancedCallSign=true Why is the server IP address obfuscated on one line but not the vast majority of places? 2026-03-31 10:02:35.836 Info SessionsService-0HNKCUOBGN6D7:00000004: http/1.1 POST http://192.168.50.162:8096/emby/Sessions/Capabilities/Full. Source Ip: host2, UserAgent: Dalvik/2.1.0 (Linux; U; Android 11; SHIELD Android TV Build/RQ1A.210105.003) 2026-03-31 10:34:47.962 Info SessionsService-0HNKCUOBGN6E3:00000001: http/1.1 POST http://host3:8096/emby/Sessions/Capabilities/Full?X-Emby-Client=Emby Web&X-Emby-Device-Name=Firefox Windows&X-Emby-Device-Id=6bf416da-37cb-41fe-94e7-04c1bc472974&X-Emby-Client-Version=4.9.3.0&X-Emby-Token=x_secret4_x&X-Emby-Language=en-us&reqformat=json. Source Ip: host4, UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:149.0) Gecko/20100101 Firefox/149.0 Seems very inconsistent.

Playing around i found some bugs regarding multi line values (former comma-separation), specifically regarding actors, writers and persons as a whole. If using these filters with multi values, don't upgrade yet! Will get a fix for this tomorrow.

Hi, can you use the web app directly on the nas?

Hi, we'll do some testing on this. Thanks.

But why do you think it's waking up your drives? It would wake up your drive even if it succeeded, right?

Hi, we are currently working on the ffmpeg update, so stay tuned for that. Thanks.

Hello all, I have been waiting for ffmpeg support since last year. It seems things are moving quite slow at Emby. I also bought the lifetime subscription with Emby and love it so far. Considering current RAM shortages and rising prices, putting a bit of more effort on implementing this fast would be nice. I own an Orange Pi5 Plus with rockwell chip as well, and would love to have HW transcoding available. I would install the beta for testing as well. @Lukeit is very nice that you are active and answer quite fast, but please stop saying the ffmep will be implemented in the "near future". It has been more than 1 year now and near future is just confusing everyone.

Hi there, how exactly are the files named and organized? Can you please show us an example? Thanks.

Unfortunately not, in Chrome on macOS it always happens no matter what the primary tab is unless it also captures these inputs.

ffmpeg-remux-8f1517b3-e1a0-47ac-924a-905b617d7eec_1.txt

HI, please attach the main emby server log as well. thanks.