Page MenuHome

VSE: Preview in Video Sequencer window sometimes displays wrong frame
Closed, ResolvedPublic

Description

System Information
Operating system: Windows 10 x64 Pro (1809, ver 10.0.17763.720)
Graphics card: Nvidia GTX 1060

Blender Version
Broken: Tested with 2.80 Release and 2.81 (f3a4f12ac090)

Short description of error
In the VSE, the preview in the Video Sequencer window does not always show the correct video frame when navigating forth and back.

Exact steps for others to reproduce the error

  1. Open this blend file:
  2. Drag the video mentioned below into the VSE
  3. Navigate to frame 551
  4. Navigate to frame 552. You see the image is different to frame 551.
  5. Navigate back to frame 551

Problem: After step 5, the preview still shows frame 552. You can step forth and back between 551 and 552 but the preview does not change even though it should.

I've uploaded the sample video. As I cannot publish it, I'd provide the link in a private message only.

Please note that the problem disappers if I shorten the video (by remuxing it in copy mode with ffmpeg and just changing the length).
I've narowed it down: If the video is longer than 5:51.60, the problem appears, otherwise it does not.

Event Timeline

Hi Please email me link to video file at richardantalik at gogle mail
(I guess AI would get this trick anyway...)

Richard Antalik (ISS) lowered the priority of this task from 90 to 30.Sep 16 2019, 3:52 AM

Hi Please email me link to video file at richardantalik at gogle mail

Sent. Did you receive it?

@Willi (willi) I did receive it, but I am unable to download the file, it seems to let me watch it only.

Can you upload it to google docs or zip it?

Just press the Download button below the video.

Richard Antalik (ISS) changed the task status from Unknown Status to Resolved.Sep 22 2019, 5:19 AM
Richard Antalik (ISS) claimed this task.

Just press the Download button below the video.

Thanks, my browser just bugged a bit so it didn't let me get the file.

I could reproduce this in earlier version, but not with latest one.
I guess that somebody fixed something somewhere.

Thanks. You are right. I've tested with the latest build when opening this ticket, but now with the latest build again, the problem is solved with that example. However, with another example, it still exists. I can't provide it as it's much too long, and I can't repro it with the shortened version. So I'll open another ticket as soon as I'll have a reproducable case again.