Video Sequencer glitch #101541

New Issue

Ondřej Vachek · 2022-10-02T01:00:39+02:00

Ondřej Vachek commented

2022-10-02 01:00:39 +02:00

System Information
Operating system: Windows-10-10.0.19044-SP0 64 Bits
Graphics card: Radeon RX 570 Series ATI Technologies Inc. 4.5.0 Core Profile Context 22.8.2.220819

Blender Version
Broken: version: 3.3.0, branch: master, commit date: 2022-09-06 15:39, hash: 0759f671ce
Worked: 2.79

Short description of error
I probably found a little glitch in the video sequencer, when the window is too small this appears https://imgur.com/a/G4BAgv5
Glitch.mp4

Exact steps for others to reproduce the error

Resize the sequences area of the Video Sequence editor

**System Information** Operating system: Windows-10-10.0.19044-SP0 64 Bits Graphics card: Radeon RX 570 Series ATI Technologies Inc. 4.5.0 Core Profile Context 22.8.2.220819 **Blender Version** Broken: version: 3.3.0, branch: master, commit date: 2022-09-06 15:39, hash: `0759f671ce` Worked: 2.79 **Short description of error** I probably found a little glitch in the video sequencer, when the window is too small this appears https://imgur.com/a/G4BAgv5 [Glitch.mp4](https://archive.blender.org/developer/F13608321/Glitch.mp4) **Exact steps for others to reproduce the error** - Resize the sequences area of the Video Sequence editor

Ondřej Vachek commented

2022-10-02 01:00:39 +02:00

Added subscriber: @Vachyas

blender-admin commented

2022-10-02 01:00:39 +02:00

#103829 was marked as duplicate of this issue

Iliya Katushenock commented

2022-10-02 01:35:43 +02:00

Added subscriber: @mod_moder

Iliya Katushenock commented

2022-10-02 01:35:43 +02:00

Can you reproduce this for some time?
If possible, could you provide the parameters of your system?
Also, chances are it's a hardware problem. But this is not yet how not to check.

Can you reproduce this for some time? If possible, could you provide the parameters of your system? Also, chances are it's a hardware problem. But this is not yet how not to check.

Pratik Borhade commented

2022-10-02 06:33:55 +02:00

Added subscriber: @PratikPB2123

Pratik Borhade commented

2022-10-02 06:33:55 +02:00

Changed status from 'Needs Triage' to: 'Needs User Info'

Pratik Borhade commented

2022-10-02 06:33:55 +02:00

Thanks for the report. We need reliable way to reproduce the issue.
As @mod_moder said , it could be a hardware specific problem. We already have received a few bugs on newer AMD driver. This could be another one

#100530 (Regression: EEVEE: AMD driver 22.7.1 - 22.8.2: Volumes created from VDB and Geometry Nodes show artifacts)
#100096 (New AMD Drivers (Adrenalin 22.7.1 or 22.8.2) for Windows 10 cause toolbars to be completely black)
#100034 (Glitches with new AMD drivers (Adrenalin 22.7.1 or 22.8.2) when overlay has transparent images)

Thanks for the report. We need reliable way to reproduce the issue. As @mod_moder said , it could be a hardware specific problem. We already have received a few bugs on newer AMD driver. This could be another one - #100530 (Regression: EEVEE: AMD driver 22.7.1 - 22.8.2: Volumes created from VDB and Geometry Nodes show artifacts) - #100096 (New AMD Drivers (Adrenalin 22.7.1 or 22.8.2) for Windows 10 cause toolbars to be completely black) - #100034 (Glitches with new AMD drivers (Adrenalin 22.7.1 or 22.8.2) when overlay has transparent images)

Ondřej Vachek commented

2022-10-02 14:46:16 +02:00

My spec:

CPU: AMD Ryzen 5 2600
GPU: Sapphire RX 570 Pulse ITX Mini (driver 22.8.2)
RAM: 4x4GB DDR4 Patriot Viper 2666
MB: MSI B450M MORTAR

This is the way how to reproduce that glitch (for me):
https://streamable.com/8gjy0m

My spec: - CPU: AMD Ryzen 5 2600 - GPU: Sapphire RX 570 Pulse ITX Mini (driver 22.8.2) - RAM: 4x4GB DDR4 Patriot Viper 2666 - MB: MSI B450M MORTAR This is the way how to reproduce that glitch (for me): https://streamable.com/8gjy0m

Pratik Borhade commented

2022-10-03 03:12:20 +02:00

Hi, video link is not reachable. Could you upload the video file directly in here?

Hi, video link is not reachable. Could you upload the video file directly in here? ![2019_12_04_upload_icon_developer_blender_org.png](https://archive.blender.org/developer/F8190038/2019_12_04_upload_icon_developer_blender_org.png)

Ondřej Vachek commented

2022-10-03 03:56:07 +02:00

Glitch.mp4

[Glitch.mp4](https://archive.blender.org/developer/F13608321/Glitch.mp4)

Pratik Borhade commented

2022-10-03 04:07:34 +02:00

Added subscriber: @mano-wii

Pratik Borhade commented

2022-10-03 04:07:34 +02:00

Thanks. Does this happen with factory settings: {nav File > Defaults > Load Factory Settings}
@mano-wii , can you replicate in your AMD GPU machine?

Thanks. Does this happen with factory settings: {nav File > Defaults > Load Factory Settings} @mano-wii , can you replicate in your AMD GPU machine?

Ondřej Vachek commented

2022-10-03 14:16:52 +02:00

Yes, it's there even with factory settings.

Pratik Borhade commented

2022-10-03 14:42:19 +02:00

Changed status from 'Needs User Info' to: 'Needs Triage'

Pratik Borhade commented

2022-10-03 14:42:19 +02:00

ok, thanks for the information. I suspect newer drivers are causing the issue. Will wait for Germano's reply.

Germano Cavalcante commented

2022-10-03 15:36:09 +02:00

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

Germano Cavalcante commented

2022-10-03 15:36:09 +02:00

It seems related to the same issue described in #83318 and #99066 (although it varies a bit depending on the GPU).
Since the steps and the result here are different, I'm keeping the report separate.

It seems related to the same issue described in #83318 and #99066 (although it varies a bit depending on the GPU). Since the steps and the result here are different, I'm keeping the report separate.

Sergey Sharybin commented

2022-11-11 12:46:07 +01:00

Added subscriber: @Sergey

Sergey Sharybin commented

2022-11-11 12:46:07 +01:00

This is something related to the GPU, and not something we can help from the VFX module perspective.

Germano Cavalcante commented

2022-11-11 13:40:49 +01:00

In #101541#1444393, @Sergey wrote:
This is something related to the GPU, and not something we can help from the VFX module perspective.

I think it's debatable.
It would be interesting to have a little more context for this conclusion.
If it's a misuse of the drawing API in the editor; the GPU module should only create features that prevent this misuse. But if the error is really within the GPU code, then it really has nothing to do with the VFX module.

> In #101541#1444393, @Sergey wrote: > This is something related to the GPU, and not something we can help from the VFX module perspective. I think it's debatable. It would be interesting to have a little more context for this conclusion. If it's a misuse of the drawing API in the editor; the GPU module should only create features that prevent this misuse. But if the error is really within the GPU code, then it really has nothing to do with the VFX module.

Sergey Sharybin commented

2022-11-11 14:36:03 +01:00

This is something we agree with Jeroen.

I can see the point about possible GPU API misuse, but this is something that can not be done efficiently from the module side and input from the GPU module is needed.

From the work planning perspective having the task in the VFX module is tricky because it is not possible to plan any work about it. From a user perspective the bug is to be investigated and fixed regarless of the assigned modules.

This is something we agree with Jeroen. I can see the point about possible GPU API misuse, but this is something that can not be done efficiently from the module side and input from the GPU module is needed. From the work planning perspective having the task in the VFX module is tricky because it is not possible to plan any work about it. From a user perspective the bug is to be investigated and fixed regarless of the assigned modules.

Germano Cavalcante commented

2023-01-13 19:12:35 +01:00

Added subscriber: @StaLeningrad

Kit Helmer commented

2023-01-25 10:42:16 +01:00

Added subscriber: @helkit

Kit Helmer commented

2023-01-25 10:42:16 +01:00

Enabling GCaps.clear_viewport_workaround in sources helps.

A suggestion to add a command line option to enable the clear viewport workaround. Or otherwise include GCaps.clear_viewport_workaround = true; line to the existing --debug-gpu-force-workarounds set.

Currently the workaround is only enabled for MacOS or Intel GPUs but other platforms or GPUs may also be affected by the issue and need the workaround to be enabled.

I wrote a script for Linux to patch the Blender binary, it changes default value of the GCaps.clear_viewport_workaround to true. The script only works for build 55485cb379f7 (official 3.4.1 from 2022-12-20) but can be extended for newer versions if you know how. blender_dirty_hack.sh

To run it, type these commands in a console:

chmod +x blender_dirty_hack.sh
./blender_dirty_hack.sh blender

where the last blender argument must be a path to the Blender executable. Running the script second time removes the patch.

Enabling `GCaps.clear_viewport_workaround` in sources helps. A suggestion to add a command line option to enable the clear viewport [workaround](https:*developer.blender.org/diffusion/B/browse/master/source/blender/gpu/intern/gpu_capabilities_private.hh$57). Or otherwise include `GCaps.clear_viewport_workaround = true;` line to the existing `--debug-gpu-force-workarounds` [set](https:*developer.blender.org/diffusion/B/browse/master/source/blender/gpu/opengl/gl_backend.cc$217). Currently the workaround is only enabled for [MacOS or Intel GPUs](https://developer.blender.org/diffusion/B/browse/master/source/blender/gpu/opengl/gl_backend.cc$424) but other platforms or GPUs may also be affected by the issue and need the workaround to be enabled. --- I wrote a script for Linux to patch the Blender **binary**, it changes default value of the `GCaps.clear_viewport_workaround` to true. The script only works for build `55485cb379f7` (official 3.4.1 from 2022-12-20) but can be extended for newer versions if you know how. [blender_dirty_hack.sh](https://archive.blender.org/developer/F14196322/blender_dirty_hack.sh) To run it, type these commands in a console: ``` chmod +x blender_dirty_hack.sh ./blender_dirty_hack.sh blender ``` where the last `blender` argument must be a path to the Blender executable. Running the script second time removes the patch.

Sun Kim commented

2023-02-06 08:11:01 +01:00

Added subscriber: @persun

Philipp Oeser removed the

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Video Sequencer glitch #101541