I know what a "normal" process would be in any software development organization I have been involved with. This should have been considered a high priority fix though that would have been equal to a hot patch. Hot patches don't take 6 weeks to get out, they take a matter of days. Unless it was that big of a problem that there are other fundamental problems, in which a role back would have been in order.
1 Like
Ok, mister developer. Thank you for your feedback.
1 Like
For me, the only frustration stems from the fact that for a while there was active participation and communication in this thread from at least one of the developers. That person has since gone silent.
Someone has to raise the bar of expectations given that the current developers do not appear to be recognizing the level of frustration. If this was an open source development I might understand it, but then it would have been fixed by now.
@hal9000, your comment feels like it is supposed be a jab, but I will take it as recognition that I actually have more experience than you do.
2 Likes
I believe they are compensating for an issue that was introduced in tvOS 26.4. tvOS 26.5 could solve whatever issue Apple introduced with deinterlacing.
1 Like
There is no identified fix yet. There is no fix on the beta version. There is no fix to deploy as a wide release.
We're still gathering information.
What we know, is what we've posted to this thread. When we have more information, we'll post again.
To repeat: It's an issue with interlaced content from HDHomeRun devices. When utilizing the Hardware deinterlacer, this issue pops up. When switching away from that, the issue does not show up.
This issue was introduced with tvOS 26.4. What changed with that is anyone's guess. Apple's systems are black boxes.
Will it get fixed with 26.5 because Apple fixed a bug they introduced in 26.4? Maybe. But we're still trying to track down the exact reason this is happening to see if we can resolve it ourselves. So far, we have not been able to.
1 Like
The problem does not exist with the TestFlight beta Channels app, you can run it all day with Hardware Deinterlacer and it works fine, it only happens in the public version of the app.
1 Like
Thank you, Jon!
In my case it is much improved, but a slight audio/video sync issue still exists with interlaced content via OTA/HDHomeRun.
Except that your Testflight betas seem to have resolved the issue for many of us..... So, something you guys changed in the beta resolved the issue, or am I missing something?
Exactly Ivan!
We have not made any changes to Hardware Deinterlacing in any of the TestFlight betas, only added additional diagnostic logging to try to isolate if it really is the Hardware Deinterlacer.
If it is fixed in the TestFlight betas, that would point to the issue actually not being in the Hardware Deinterlacer but in something else, which is even more confounding.
Still happening on Test Flight for me.
Did you submit diagnostics
It’s possible that building with the 26 SDK resolved it.
But I very specifically tested this after we first got on the 26 SDK to see if it fixed it, and saw the same issue.
So, very peculiar indeed.
Not sure what to tell you because I am not an engineer but with the public Channels app it happens everyday, all day, with the TestFlight Beta Channels app it never happens on the same Apple TV4K and the same HDHomerun Quatro so something in my non technical mind says it has to be different.
This is happening to me too. I've submitted diagnostics from my ATV a couple of times and just sent a follow up email.
Same for me. The Testflight Beta works great (other than an occasional glitch with scrolling the guide), the public release, not so much.
I’m going to repeat myself here:
- Submitting diagnostics from the App Store build (7.0.2) is not going to help us on this issue — it doesn’t have the info we need
- Saying it’s still happening on the latest TestFlight without submitting diagnostics is not going to help us figure out this issue — we can’t see what’s going on without the diagnostics
1 Like
multiple times
Let me reiterate Ivan's post and also say: Since one of the Testflight updates a few weeks back, I stopped having the issue with hardware deinterlacing as well. You can scroll up to see my post on it from 4/21.
Looking in testflight I can see that the 4.15.250 build has "First build with iOS/tvOS 26 SDK" in it's release notes. 4.21.522 has "Match Context and Frame Rate was not being kicked off when starting playback"
Maybe one of those fixed it?
1 Like