Currently, each frame of an animation in a slide show is loaded individually before it is printed to the screen. Multiple test machines snuggle to maintain a consistently high frame rate (like 60 fps).
To resolve this problem, a buffer should hold the frames for the next animation. For example, if the current slide is at frame 31 in the video file and the subsequent animation is 61 frames, those 61 frames should be loaded into memory before the right arrow is pressed. Thus, I presume, would the animation run more smoothly, consistently achieving the target frame rate.
Currently, each frame of an animation in a slide show is loaded individually before it is printed to the screen. Multiple test machines snuggle to maintain a consistently high frame rate (like 60 fps).
To resolve this problem, a buffer should hold the frames for the next animation. For example, if the current slide is at frame 31 in the video file and the subsequent animation is 61 frames, those 61 frames should be loaded into memory before the right arrow is pressed. Thus, I presume, would the animation run more smoothly, consistently achieving the target frame rate.