Lip Sync/Audio Off - RTR (specific to 3.1/5.1 in Phoenix)

[RTR]

Channels are still doing this; any progress with Gray Media or are they still denying there's an issue?

[randygeske]

Hi RTR, I’m still seeing the exact same thing on my end with my Flex 4K across multiple devices (Fire TV, Windows, and Pixel).

Since we know Gray Media is currently broadcasting out-of-spec timing data, I'm curious if anyone has tested these channels with a different streaming device? I'm wondering if a client with a stricter hardware decoder (like an Apple TV 4K or an Nvidia Shield) handles this specific broadcast error better, or if they all drift out of sync just like my Firestick?

It seems that the standard TVs in the Phoenix metro area are able to auto-correct or compensate for whatever the station is doing right now without any lip-sync issues. I'd love to know if there is a specific streaming box or app setup that can natively power through these problematic broadcasts and recordings the same way a standard television does.

I really appreciate the developers actively communicating with the station and looking into this. Hoping a software-side workaround can be implemented for the rest of us soon!

[RTR]

sigh This has been going on since July now and I was hoping this would've been fixed by the fall premiere season. Some of us don't have TVs connected to antennas and rely on HDHomeRun to watch TV.

[randygeske]

I have been doing some testing on my own. So far every other app that I use to play one of the problematic recordings plays the audio without the lip-sync problem. I downloaded the file from the hard drive connected to my HDHomerun Flex device to my Windows computer hard drive. Media player, VLC, and Plex play the file fine.

[bgrubb1]

the 5.1 feed on Youtube TV plays fine as well

[RTR]

Furthermore, I don't know whether I should make a new post or not, but this also affects the Phoenix market. Closed captions have disappeared from unencrypted 103 NG, 108 NG, and 128 NG for about a month now.

[bgrubb1]

@nickk
Can you giveus an update on this ??
Its been happening for 2 months across all platforms
...Barry

[bgrubb1]

Issue seems resolved. Was it a broadcast fix ?

[RTR]

Issue seems resolved.

Agreed. And the captions issue seems to have been fixed as well after a month or so without.

[geriakt]

It may have been resolved in your market, but we would like to hear how it got fixed by SiliconDust and how they worked directly with the broadcast engineer? I still have soundtrack sync issues in my market as well as the lighthouse transmitter stating only AC4 2ch (with many apps based on EXOplayer) when I know it has 5.1.
I have tried connecting the tower engineer directly via email multiple times but no reply. They do not care about ATSC 3.0.

[RTR]

It may have been resolved in your market, but we would like to hear how it got fixed by SiliconDust and how they worked directly with the broadcast engineer? I still have soundtrack sync issues in my market...

Oh, I agree and want to hear the reasons too. I was just reaffirming that the 3/5 issue seems to have been fixed but now I'm noticing 12.1 has sync issues now.

[randygeske]

I switched over to using the ChannelsDVR app. It still uses my Silicon Dust Flex device as the tuner, but replaces HDhomerun app for everything else. Below is the log from the ChannelsDVR app after playing a recording of Hot Bench from Channel 5.1 this morning. The timecode error is still being broadcast. I confirmed this with some other shows on channel 5.1.

All of the channels that I'm recording are playing fine in the ChannelsDVR app. It handles these timecode errors fine. It's a great app and has features not found on in HDhomerun.

2026/09/25 14:06:45.533207 [HLS] ffmpeg: file57-ip192.168.1.90: [hls @ 000001f9a7979c40] Invalid DTS: 161910171 PTS: 161907171 in output stream 0:0, replacing by guess
2026/09/25 14:06:45.538841 [HLS] ffmpeg: file57-ip192.168.1.90: [hls @ 000001f9a7979c40] Invalid DTS: 161911673 PTS: 161910174 in output stream 0:0, replacing by guess
2026/09/25 14:06:45.539355 [HLS] ffmpeg: file57-ip192.168.1.90: [hls @ 000001f9a7979c40] Invalid DTS: 161916177 PTS: 161913177 in output stream 0:0, replacing by guess
2026/09/25 14:06:45.542257 [HLS] ffmpeg: file57-ip192.168.1.90: [hls @ 000001f9a7979c40] Invalid DTS: 161917679 PTS: 161916180 in output stream 0:0, replacing by guess
2026/09/25 14:06:45.551361 [HLS] ffmpeg: file57-ip192.168.1.90: [hls @ 000001f9a7979c40] Invalid DTS: 161922183 PTS: 161919183 in output stream 0:0, replacing by guess
2026/09/25 14:06:45.551361 [HLS] ffmpeg: file57-ip192.168.1.90: [hls @ 000001f9a7979c40] Invalid DTS: 161923685 PTS: 161922186 in output stream 0:0, replacing by guess
2026/09/25 14:06:45.556187 [HLS] ffmpeg: file57-ip192.168.1.90: [hls @ 000001f9a7979c40] Invalid DTS: 161926688 PTS: 161925189 in output stream 0:0, replacing by guess
2026/09/25 14:06:45.567083 [HLS] ffmpeg: file57-ip192.168.1.90: [hls @ 000001f9a7979c40] Invalid DTS: 161934195 PTS: 161931195 in output stream 0:0, replacing by guess
2026/09/25 14:06:45.571408 [HLS] ffmpeg: file57-ip192.168.1.90: [hls @ 000001f9a7979c40] Invalid DTS: 161935697 PTS: 161934198 in output stream 0:0, replacing by guess
2026/09/25 14:06:45.581828 [HLS] ffmpeg: file57-ip192.168.1.90: [hls @ 000001f9a7979c40] Invalid DTS: 161940201 PTS: 161937201 in output stream 0:0, replacing by guess
2026/09/25 14:06:45.582453 [HLS] ffmpeg: file57-ip192.168.1.90: [hls @ 000001f9a7979c40] Invalid DTS: 161941703 PTS: 161940204 in output stream 0:0, replacing by guess
2026/09/25 14:06:45.586807 [HLS] ffmpeg: file57-ip192.168.1.90: [hls @ 000001f9a7979c40] Invalid DTS: 161946207 PTS: 161943207 in output stream 0:0, replacing by guess
2026/09/25 14:06:45.597051 [HLS] ffmpeg: file57-ip192.168.1.90: [hls @ 000001f9a7979c40] Invalid DTS: 161947709 PTS: 161946210 in output stream 0:0, replacing by guess
2026/09/25 14:06:45.597051 [HLS] ffmpeg: file57-ip192.168.1.90: [hls @ 000001f9a7979c40] Invalid DTS: 161952213 PTS: 161949213 in output stream 0:0, replacing by guess
2026/09/25 14:06:45.602047 [HLS] ffmpeg: file57-ip192.168.1.90: [hls @ 000001f9a7979c40] Invalid DTS: 161953715 PTS: 161952216 in output stream 0:0, replacing by guess
2026/09/25 14:06:45.612767 [HLS] ffmpeg: file57-ip192.168.1.90: [hls @ 000001f9a7979c40] Invalid DTS: 161958219 PTS: 161955219 in output stream 0:0, replacing by guess