I have the following situation, which I've tested only on OS X and I assume is platform-specific:
QmlVlc is overlayed by a QtWebEngine (a-la-webchimera-desktop)
when animations are triggered in the webengine, I get tearing (few times) on the frames. The more lengthy the animation, the more tearing there is.
What I assume is happening: animations trigger a redraw on the background element, which in turn catches the QmlVlc out-of-sync on a texture/buffer that is part one frame, part another.
RSATom
commented
7 years ago
I have the following situation, which I've tested only on OS X and I assume is platform-specific:
QmlVlc is overlayed by a QtWebEngine (a-la-webchimera-desktop) when animations are triggered in the webengine, I get tearing (few times) on the frames. The more lengthy the animation, the more tearing there is.
What I assume is happening: animations trigger a redraw on the background element, which in turn catches the QmlVlc out-of-sync on a texture/buffer that is part one frame, part another.
I also assume this can be worked around by using a double (triple?) buffer. Maybe something is not right here: https://github.com/RSATom/QmlVlc/commit/8c8832d599b283f2d1d4ed7706661847f935cc5e ?
Maybe on a forced redraw, you need to always pick the last frame which is not currently modified from the pool?