Yes, reverting to 2.15 build 14696 corrects the issue for me as well.
Version 2.16 build 14771 is the first version that shows the issue for me. And it continues through 2.17 15061.
Yes, reverting to 2.15 build 14696 corrects the issue for me as well.
Version 2.16 build 14771 is the first version that shows the issue for me. And it continues through 2.17 15061.
@tv_fan thanks for the info! I installed TestFlight however I believe I need an invitation code to be invited by a developer. If anyone can send me an invitation that would be much appreciated.
TestFlight requests are handled directly by Plex; you’ll get one when you get one. I believe the number of testers is also limited so you may not get one as soon as you like.
Also, I’m not 100% sure if a new TestFlight install will include builds previous to the current beta released through TestFlight – someone else might know for sure one way or the other…
Thanks everyone for your feedback! If 2.16 is definitely the first version causing the issue, I think the reason for this bug is the improved post-play experience, where you can now “minimize” playback to a small window when playback is about to finish.
I’m gonna check if my theory is correct and try to prepare a fix ASAP. Thanks again for your help!! I’ll keep you posted
If any of you would like to test a build with the potential fix, please send me an email address via DM and I’ll share the build with you using Testflight.
Thanks!
@sergiou87 is that in addition to the normal Testflight process? (already using Testflight here and want to save you unnecessary email)
Yeah since I would be sharing a specific build with specific people, I need to identify those people So I’m afraid I need an email address.
For those who (eventually) get the invite, you have to test version 2.18, build number 15088.
Beware that it’s a WIP build so even if it fixes this problem it could cause others, so for now just focus on the issue at hand
Sorry, that was taking too long (needs Apple’s approval to distribute) so I put the fix on top of the current 2.17 beta.
I just shared the version 2.17, build 15095 with those who sent me an email address. Please take a look and test. Looking forward to your feedback!
Spot checking in version 2.17, build 15095 looks to have corrected the issue. In previous builds the issue was noticable within a few moments and I’m not seeing it on hevc or h264 content any more.
Thanks for the quick turnaround!
Also can confirm I’m about 20 minutes into an episode and haven’t noticed any issues. Quick question – how do you bring up chapters during a playing video? It use to just be swipe down but it isn’t there anymore? Is it a different action?
It should still be there I just tested it and still see the chapters there
So super weird, I just put on an episode and noticed it wasn’t there (since it’s convenient to skip the opening credits). So after it I went back to the settings to see if I was missing an option and then started the same episode again and chapters were there. Super odd.
when will this new build be out on test flight?
From another thread / employee but know that there can be delays:
I just wanted to throw my two cents that the beta fixed my issues, too. I’ll hit it hard tonight and let you know if I see anything different but it looks great so far.
Also some really cool visual changes to the Ui in the new beta too!
The only thing I’ve noticed that I had an issue with is it seems I can’t playback an MKV that’s a “2in1” file. It will play the video fine but no audio. I can confirm this works via Plex on Tizen on another tv in the house but not on this current beta. There’s no audio. But that’s the only bump I’ve run into – The app itself has crashed once and completely frozen another time today.
Im also having this issue. AppleTV non-4K with the enhanced player on. I will turn off the enhanced player and see if that helps.
It will be fixed in the next release; the fix is in the current beta.
Just installed version 2.17 with TestFlight on AppleTV 4K and it still shuttering when using the enhanced video player… still have to fallback to old player to fix the issue. So no the problem still exist on the 2.17 latest build!