After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 793323 - iOS 11.2 vtdec ! glimagesink decoding broken on iphone 6
iOS 11.2 vtdec ! glimagesink decoding broken on iphone 6
Status: RESOLVED OBSOLETE
Product: GStreamer
Classification: Platform
Component: gst-plugins-bad
1.12.4
Other Linux
: Normal critical
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2018-02-09 07:22 UTC by Jan Schmidt
Modified: 2018-11-03 14:17 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Jan Schmidt 2018-02-09 07:22:21 UTC
In iOS 11.2.5 testing with GStreamer 1.12.4 on an iPhone 6, I'm currently seeing that vtdec ! glimagesink output plays incorrectly, with frames showing out of order.

It only happens with GL output from vtdec, and I suspect is related to the GL textures being invalidated too early, or otherwise not having the content we think they do.

The same build works fine on an older ipad3 with iOS 9.2, and since the latest work on vtdec references iOS 11.1, I suspect it worked there and is therefore possibly an iOS change we need to find a solution for.

Has anyone else been testing on iOS 11.2 recently?
Comment 1 Jan Schmidt 2018-02-17 14:31:45 UTC
I had a chance to test decoding on an iPhone 7, and it *does not* show the same behaviour - video decoding seems to work fine there with iOS 11.2.5.
Comment 2 Jan Schmidt 2018-02-23 08:54:59 UTC
I think the problem is specific to iphone 6 (or lower?), and seems to be about how long textures are valid for. Simply doing vtdec ! videorate ! glimagesink makes things work - and I suspect it's because videorate holds a reference to the video buffer until the next one arrives.
Comment 3 Sebastian Dröge (slomo) 2018-02-26 11:21:41 UTC
Is this a regression on our side also, or only on Apple's side?
Comment 4 Jan Schmidt 2018-02-26 11:33:55 UTC
I have no way to tell.
Comment 5 Tim-Philipp Müller 2018-03-09 10:10:54 UTC
Do you have any ideas where to look / things left to try?

Not sure I want to block the release on this, esp. if it only happens with some/older devices.
Comment 6 Tim-Philipp Müller 2018-03-09 10:26:13 UTC
Oh, but it happens with 1.12 as well, so not really a blocker anyway I guess, other than in the sense that it would be nice to fix.
Comment 7 Jan Schmidt 2018-03-09 11:38:34 UTC
Yes, not a blocker. If it's a regression, it's not a very recent one, and afaict I'm the first to notice it.
Comment 8 Matthew Waters (ystreet00) 2018-03-16 00:56:53 UTC
I have some (third party) results that indicate that the problem starts to occur on the iPhone 6/6S/6+ between iOS 10.3.1 and iOS 11.2.5 which would indicate a regression in the underlying OS/frameworks.
Comment 9 GStreamer system administrator 2018-11-03 14:17:48 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/gstreamer/gst-plugins-bad/issues/653.