u/nonzerogroud

Would very much appreciate an invite to Ninja to boost my indexer quality. Thanks in advance!

These 2 are basically the same price where I live.

House: 130m sq for the floor I’m gonna put it in, 240m total. mostly Porcelain floors, 3 low rugs, sometimes we have shoes on the floor.

Vacuuming is more important to me than moping but wife does seem intrigued by a mopping robovacuum. We’re coming from the Roomba i7.

So this is a first for me. I've a 2160p 4k file that when played, immediately crashes Plex on Apple TV. I enabled verbose logging, pressed play, the app crashed, then I downloaded the logs using the endpoint Plex for ATV exposes.

I then give Claude the logs to analyze, and this is what it found about the file:

HEVC, 3840×2160, 23.976fps, Main 10 @ Level 5.1 @ HIGH tier
  10-bit, BT.2020, PQ, MaxCLL 1000nits, HDR10+ Profile B
  Avg 76.9 Mbps / Peak 85.8 Mbps
  Audio: TrueHD 8ch (transcoded server-side → FLAC 8ch)

Are there known issues with this kind of files? any formats that should be avoided?

I don't want to waste anyone's time with AI generated content, but if it's of any value, this is what Claude thought the failure reasons likely are:

Why this specific file:

1. HDR10+ Profile B dynamic metadata. The video is being direct-streamed (videoDecision: copy in the transcode session events) — the HEVC bitstream including the HDR10+ SEI metadata is passed straight to VideoToolbox. tvOS's HDR10+ support is known to be fragile, especially with Profile B single-layer metadata at the SEI level.
2. HEVC at HIGH tier with 85 Mbps peaks. L5.1 High tier is in spec, but it pushes VideoToolbox harder than typical "Main tier" UHD content. The client URL also requests videoResolution=4096x2160 — wider than 3840.
3. TrueHD source forces audio transcoding. The server emits transcodeHwRequested:true, transcodeHwFullPipeline:false, throttled:true, speed:0.0, progress:2.3% — i.e. the audio pipeline is on CPU and stalled, while the client buffers ahead and eventually crashes during render setup. The audio path itself isn't crashing the client, but it adds latency/jitter on top of an already-strained video path.