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
You really need to chill out. As a software developer myself I will say that there are clearly a lot of moving parts to this problem and various people in this thread appear to be experiencing a varying level of success with the current builds over the last few weeks.
The situation is hardly as dire as you are painting it to be:
- There is a workaround available (disable hardware deinterlacing)
- There are beta builds available which seem to resolve the issue for some or most of us?
On top of which it appears to be an issue introduced by changes Apple made, not Channels themselves. There is no open record of what Apple is changing and there is no commit history to spelunk through that might offer some insight into what happened on their end like you would have with FOSS software.
So give it a rest and let the developers do their work. We are on the path to a resolution and we'll get there.
2 Likes