All Activity

Summary Roku Live TV playback failures on Apple Silicon Docker (linuxserver/emby ARM64) are caused by two issues. Fixed with lightweight wrapper scripts. No image changes. No native install required. Problem Some Live TV channels buffer or show black screen on Roku No consistent pattern Other clients work fine (browser, Fire TV, Apple TV) Root Cause Two failures stack: Broken runtime linking LD_LIBRARY_PATH from base image contaminates Emby’s bundled ffmpeg On ARM64 this causes incorrect library resolution at runtime Bad codec selection for Roku HLS Emby often selects -c:v copy -c:a copy Roku cannot reliably handle these segments for certain streams Results: buffering, stalls, black screen Key detail: ffdetect (capability detection) and actual transcode execution are separate. Only runtime execution needs fixing. Fix Wrapper scripts injected via custom-cont-init.d: Copy bundled ffmpeg/ffprobe to clean paths Replace originals with wrapper scripts Wrappers: Strip LD_LIBRARY_PATH Launch via correct ARM64 loader Rewrite problematic copy codec calls → libx264 + aac superfast preset zerolatency short GOP no B-frames No impact to ffdetect. Capabilities remain intact. Results Stable HLS playback on Roku No buffering or black screens Valid .ts segment output Encoder detection unchanged Tested Setup Mac mini M4 (ARM64) macOS 26.3.1 Docker Desktop 29.2.1 linuxserver/emby (ARM64) Emby Server 4.9.3.0 Roku Streambar SE IPTV via M3U + XMLTV Install Clone repo Copy custom-cont-init.d Add mount to docker-compose.yml Restart container Repo: https://github.com/shiz504/emby-roku-as-fix Notes ARM64 Apple Silicon only Uses CPU transcoding (no GPU in Docker macOS) Minimal overhead on Apple Silicon Only rewrites problematic live transcode paths All other ffmpeg calls untouched Shawn McCalla @shawnmccallax

I have the x3600h. So far so good with this one but I'm less critical now about these kinds of things than I used to be. I use it probably every day

我看你没有回复我 其实就是danmaku功能 应该挺多用户需要的 我看你没回复我了 不知道你知不知道我说的danmaku

"Good" to know this is a Firefox bug, not a bug in Emby's browser app! Found this thread when I saw Emby (Firefox actually, apparently), trying to pre-fetch a whole ~16GiB movie ... cancelled it / gave up after ~6GiB (going by server logs) ... haproxy[185627]: [206] 192.168.1.10:48730 [31/Mar/2026:15:33:27.753]... 0/0/0/4/63732 6556730260 - - CD-- 19/19/1/1/0 0/0 {emby.example.org} "GET /emby/videos/185771/original.mkv?DeviceId=... HTTP/1.1" That's 6,556,730,260 bytes. Here's the related Firefox bug report, for those curious: https://bugzilla.mozilla.org/show_bug.cgi?id=2000420 Sucks that most non-tech-savvy users might end up thinking it's Emby at fault!

While we are in there ... clicking this button doesn't do anything:

thanks

the metadata editor would be the best way.

And how do I know if something has an external ID or !external ID?

If it has an external ID - you can't. Emby willl always remember it for userdata/tracking purposes (watchstates/playstates).

Are you saying this is not possible? : How do I delete everything about a title so that if I add it again later it is as if Emby never knew it existed before?

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.