Match content causing video to skip first couple seconds of video

I’ve noticed the same issue and I think it’s in built / depends on the app. I notice this issue also when I have match content (fr/dr) on only. It tends to only happen with 3rd party apps and I’ve had all appple tv models since the last hd (1080p). This problem happens with all the 4ks I’ve seen I’d advise switching if off and setting your box to the best setting as the picture quality does not have any noticeable difference.

im pretty certain it’s not the individual box’s issue as I have had 4+ Apple TV 4Ks and ALL of them had this issue.

my internet speed never drops below 200 mb…. With a low ping so definitely not my internet

personally best settings is match content off and depending on your tv 4k Dolby vision 60hz (not 59.9)

You may actually be seeing a TV issue or TV setting that's making the judder... TVs usually have their own video enhancement functions, like noise reduction, motion compensation features, etc that are on by default. Trick is, your ATV4K has all the same stuff and a (probably) better chip. The TV's video enhancement algorithms may choke on the ATV4K's output that's already been enhanced.

My suggestion is that you try turning OFF all such video enhancement features on the TV, then reset your ATV4K's video settings. The ATV4K will attempt to sniff the TV's capabilities and choose a default video mode of the highest res and frequency that your TV can support. From there, you can enable HDR on the ATV4K, try for a superior gamma setting, etc. If the 'judder' continues, you might try a different default setting like 4K HDR (30fps).

On my setup, my ATV4K usually looks great on my lower-end LG 4K HDR TV with Match Content turned off. The only gripe I've noticed is that HDR mode occassionally looks too dark on night scenes in 4K content encoded with DolbyVision; (my TV doesn't support DolbyVision). In these cases, if I switch the ATV4K to send 4K SDR to the TV, I can comfortably see more detail in the darker scenes. I suspect my TV just doesn't have the brightness expected from an HDR10-capable TV (but perhaps I'm nit picking :-).

Here are a few things you can try to fix the problem:

1. Disable Match Content: Go to Settings > Video and Audio > Match Content and turn off both Match Frame Rate and Match Dynamic Range.

2. Adjust the HDMI cable: Try unplugging the HDMI cable from both the Apple TV and your TV, then plug it back in securely. You can also try using a different HDMI cable or port.

3. Reset Apple TV: Go to Settings > System > Reset and select "Reset All Settings". This will erase your preferences but not your content.

4. Check your network connection: Slow or unstable internet speeds can cause buffering and delays. Check your network settings and try resetting your modem or router.

If none of these solutions work, you may need to contact Apple support for further assistance.

This is your TV going blank as it transitions between frame rates and maybe dynamic range also. Nature of the beast and probably why Apple's default approach is to configure the video output to the 'best' mode your TV can handle, then transcode everything to that. I hear newer sets that support Quick Media Switching (QMS) using HDMI VRR can/will eliminate this blank/lag/skip when switching frame rates.

In what way do you find that your new Match Content settings "makes it run better."? How does your issue with 'frame rate drops' show itself?

First try unplugging the Apple TV from power by unplugging it for 2-3 minutes. Then plug in and retest. If this does not help then you likely have a poor Internet signal where the ATV is located.

You can also try resetting both your modem and router, yes even if everything else is fine.

You are not imagining it. The struggle is real. I couldn’t avoid it with frame match but could for a while with HDR match. They had a couple updates that would fix it with HDR match but now it’s back to skipping again. Seems like like they can’t get it right and yea hopefully the newer models have addresses this bs.

I have this exact issue. But it only popped up when I updated to 17.3; and it has persisted with 17.4. No problem at all before the update.