VSE: frozen frames after simple edit/cut in final render #103818

New Issue

Michael · 2023-01-12T00:43:38+01:00

Michael commented

2023-01-12 00:43:38 +01:00

System Information
Operating system: Ubuntu 22.04 and Windows 11
Graphics card: Ubuntu: nvidia RTX3070, Windows: Intel UHD Graphics 620

Blender Version
Broken: 3.4.1, Current Alpha dd9e1eded0
Worked: not sure, maybe 2.93

Short description of error
After a simple edit/cut I often see freeze frames at the beginning of the next clip. When using 100% proxies, the frames are not frozen but they are frozen in final render! I waited for #95683 to arrive in stable but I still experience glitches. As mentioned, using proxies does not help since freeze frames are in the final render.

Exact steps for others to reproduce the error
open .blend and examine the cut. There are 3 frozen frames. They are also in my final render (attached). Compare the cut with proxies activated to see what the cut would look like without freeze frames.

MushroomTutorial_Schnitt04_FreezeFrames.blend
MVI_7752.MP4
MushroomTutorial_Schnitt04_FreezeFrames.mp4
BL_proxy.zip

**System Information** Operating system: Ubuntu 22.04 and Windows 11 Graphics card: Ubuntu: nvidia RTX3070, Windows: Intel UHD Graphics 620 **Blender Version** Broken: 3.4.1, Current Alpha dd9e1eded0d4 Worked: not sure, maybe 2.93 **Short description of error** After a simple edit/cut I often see freeze frames at the beginning of the next clip. When using 100% proxies, the frames are not frozen but they are frozen in final render! I waited for #95683 to arrive in stable but I still experience glitches. As mentioned, using proxies does not help since freeze frames are in the final render. **Exact steps for others to reproduce the error** open .blend and examine the cut. There are 3 frozen frames. They are also in my final render (attached). Compare the cut with proxies activated to see what the cut would look like without freeze frames. [MushroomTutorial_Schnitt04_FreezeFrames.blend](https://archive.blender.org/developer/F14143243/MushroomTutorial_Schnitt04_FreezeFrames.blend) [MVI_7752.MP4](https://archive.blender.org/developer/F14143241/MVI_7752.MP4) [MushroomTutorial_Schnitt04_FreezeFrames.mp4](https://archive.blender.org/developer/F14143240/MushroomTutorial_Schnitt04_FreezeFrames.mp4) [BL_proxy.zip](https://archive.blender.org/developer/F14143247/BL_proxy.zip)

Michael commented

2023-01-12 00:43:38 +01:00

Added subscriber: @Michael-47

Michael commented

2023-01-12 12:34:02 +01:00

Added subscriber: @iss

Pratik Borhade commented

2023-01-13 11:46:09 +01:00

Added subscriber: @PratikPB2123

Pratik Borhade commented

2023-01-13 11:46:09 +01:00

Changed status from 'Needs Triage' to: 'Confirmed'

Pratik Borhade commented

2023-01-13 11:46:09 +01:00

Hi, thanks for the report. Can confirm this behavior in preview window but unable to confirm it in final render

Michael commented

2023-01-13 13:47:07 +01:00

Hi! I tried it (again) on my two machines (win and ubuntu) and also using another output format. the freeze frames are always in it.

Michael commented

2023-01-13 19:24:15 +01:00

I was able to fix the broken file by putting the source video into a subfolder and relinking it in the vse by pointing to the new location in the source property or by using find missing files (both work). weird but maybe it helps...

Richard Antalik commented

2023-01-13 19:54:16 +01:00

I am not able to reproduce at all. At what timeline frame this issue can be found?

In #103818#1473904, @Michael-47 wrote:
I was able to fix the broken file by putting the source video into a subfolder and relinking it in the vse by pointing to the new location in the source property or by using find missing files (both work). weird but maybe it helps...

Since I am on Windows, I relinked videos in beginning, but I think C:\mnt\... will work there so will re-check.

I am not able to reproduce at all. At what timeline frame this issue can be found? > In #103818#1473904, @Michael-47 wrote: > I was able to fix the broken file by putting the source video into a subfolder and relinking it in the vse by pointing to the new location in the source property or by using find missing files (both work). weird but maybe it helps... Since I am on Windows, I relinked videos in beginning, but I think `C:\mnt\...` will work there so will re-check.

Richard Antalik commented

2023-01-13 20:03:35 +01:00

I saw sample render, also checked with exact path, but I did not download proxies yet. With proxies I can reproduce. The issue seems to be within timecode index. I will check this more in detail, as it is related to cut position which should not happen.

Ultimately I wanted to remove timecodes completely, because they are causing more issues than they are solving now, so fix may be removal of this system. For now you can disable them by using "None" option in proxy panel.

I saw sample render, also checked with exact path, but I did not download proxies yet. With proxies I can reproduce. The issue seems to be within timecode index. I will check this more in detail, as it is related to cut position which should not happen. Ultimately I wanted to remove timecodes completely, because they are causing more issues than they are solving now, so fix may be removal of this system. For now you can disable them by using "None" option in proxy panel.

Michael commented

2023-01-13 20:42:20 +01:00

ok, by selecting none for timecodes or disabling the proxies the issue was fixed as well. that's way better than moving the files around. thanks! i do not need proxies, it was just to improve performance a little.

blender-admin commented

2023-01-13 21:25:41 +01:00

This issue was referenced by a5c3f5b0bc

This issue was referenced by a5c3f5b0bc3339d94b53ed216f6e915b3968658a

Richard Antalik commented

2023-01-13 21:33:02 +01:00

Changed status from 'Confirmed' to: 'Resolved'

Richard Antalik closed this issue

2023-01-13 21:33:02 +01:00

Richard Antalik self-assigned this 2023-01-13 21:33:02 +01:00

Richard Antalik commented

2023-01-13 21:35:57 +01:00

I have looked into index file building and process is as follows:

Read packet
If packet is keyframe, store previous and current seek positions

Technically in parallel to that runs building process with varying delay:

decode frame
write last seek positions to indexer file

If this delay is greater than GOP size, which in this case is, this process will fail. Fortunately frames carry over data from packets, so this can be fixed.
Please check this with alpha build from https://builder.blender.org/download/daily/, existing proxies have to be rebuilt though, since they are already "corrupted".

I have looked into index file building and process is as follows: - Read packet - If packet is keyframe, store previous and current seek positions Technically in parallel to that runs building process with varying delay: - decode frame - write last seek positions to indexer file If this delay is greater than GOP size, which in this case is, this process will fail. Fortunately frames carry over data from packets, so this can be fixed. Please check this with alpha build from https://builder.blender.org/download/daily/, existing proxies have to be rebuilt though, since they are already "corrupted".

Michael commented

2023-01-22 17:17:17 +01:00

I opened my broken edit with blender-3.5.0-alpha+master.cc332264ae07-linux.x86_64-release from 15th january. After recalculating the proxies the freeze frames where gone. For preview and also for final render. It was just a quick test but it seems to be fixed.

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

VSE: frozen frames after simple edit/cut in final render #103818