What's a good efficient way to reverse a QMovie to play it backwards?

[GrecKo]

The way it is done is to start the QTimer after each frame, with the timeout being the frame minus the time it took to process the current frame.

[jsulm]

@JonB said in What's a good efficient way to reverse a QMovie to play it backwards?:

human to see at least 50 frames per second

Smartass mode: 24 actually :-)

[JonB]

OK, so does a default precision QTimer tick accurately at at least 24 per second? Not to mention that presumably if the OS is off doing something it won't, but perhaps all movie players would suffer from that issue?

[jsulm]

@JonB Such low frequencies should be fine for QTimer I would say.
https://doc.qt.io/qt-6/qt.html#TimerType-enum
"On UNIX (including Linux, macOS, and iOS), Qt will keep millisecond accuracy for Qt::PreciseTimer.
...
On Windows, Qt will use Windows's Multimedia timer facility (if available) for Qt::PreciseTimer"

[JonB]

@jsulm Indeed, that is for Qt::PreciseTimer option, which is why I was asking about the "default" mode, which is something like "coarse".

[GrecKo]

QMovie uses a default QTimer.

[jeremy_k]

@Mizmas said in What's a good efficient way to reverse a QMovie to play it backwards?:

@jeremy_k Do you mean for the laggy animation? I've tried it, but I didn't get a noticeable performance improvement.

Yes, to decrease the time required to access each frame when playing in reverse. Have you profiled the code to verify that the animation is a hotspot?

I'm using a .webp animation file though to have a full transparency channel, if I use .gif the lag is minimal, but it doesn't have full transparency, only 0 or 1

Webp uses VP8, which stores key frames and intermediate frames that modify earlier frames. Jumping to a frame may require reconstructing prior frames first.

[Mizmas]

@jeremy_k Thanks for the help. What I did was create a minimal new .py file with only a QLabel and a QMovie to only test the animation, and the performance is exactly the same as in the video I shared before, so it seems that there was nothing bottlenecking the animation in my main app code. I'm on PyQt6 6.7.1 if that helps.
On the left it's opened on Chrome, and on the right PyQt6 window:

from PyQt6.QtWidgets import QApplication, QLabel
from PyQt6.QtGui import QMovie
import sys
import resources

app = QApplication(sys.argv)
label = QLabel()
label.setStyleSheet("background: black;")
movie = QMovie(':/Animations/b_mode.webp')
movie.setCacheMode(QMovie.CacheMode.CacheAll)
print(movie.cacheMode())
print(movie.format())
label.setMovie(movie)
label.setFixedSize(50, 50)
label.show()
movie.start()
sys.exit(app.exec())

[jeremy_k]

@Mizmas Thanks for providing the POC. I gave it a quick try with a test image, but apparently my Qt installation lacks webp movie support.

The image on the right appears to be less smooth than the one on the left. Does it look any better if the label is allowed to assume its implicit size from the QMovie rather than being set to 50x50?

[Mizmas]

@jeremy_k Here's an answer I got on stackoverflow: https://stackoverflow.com/questions/79672044/qmovie-is-stuttering-lagging-when-using-an-animated-webp-file-on-both-pyqt6-a/79672867#79672867

[SGaist]

From the looks of it, it seems like having the animation available for both direction is the easy path.