Blender VSE suddenly laggy. Lag persists after deleting all strips. #128464

Open
opened 2024-10-02 02:21:37 +02:00 by Alessandro-Terlizzi · 6 comments

System Information
Operating system: Windows-10-10.0.19045-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.23

Blender Version
Broken: version: 4.2.2 LTS, branch: blender-v4.2-release, commit date: 2024-09-23 12:18, hash: c03d7d98a413
Worked: (All versions I tested have the same issue)

Short description of error
The Blender video sequencer stutters when some metastrips are pasted in the project. The stutter is very particular because metastrips of similar complexity are handled very well by my system. Additionally, the stutter doesn't occur when playing the sequence, only when navigating the timeline.
The biggest issue, though, is that the stuttering persists in the project after deleting the "corrupted" strips and there is nothing I can do that gets rid of this odd interaction. Not even duplicating the file fixes it. I have also tested this on multiple computers.

Below, I have attached a video that demonstrates the issue. The sequence is very simple and worked fine before introducing the problematic strip. I have also attached an empty .blend file where I have replicated the problem

Exact steps for others to reproduce the error
-Open Blender VSE
-Paste the problematic strip

  • Delete the problematic strip
**System Information** Operating system: Windows-10-10.0.19045-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.23 **Blender Version** Broken: version: 4.2.2 LTS, branch: blender-v4.2-release, commit date: 2024-09-23 12:18, hash: `c03d7d98a413` Worked: (All versions I tested have the same issue) **Short description of error** The Blender video sequencer stutters when some metastrips are pasted in the project. The stutter is very particular because metastrips of similar complexity are handled very well by my system. Additionally, the stutter doesn't occur when playing the sequence, only when navigating the timeline. The biggest issue, though, is that the stuttering persists in the project after deleting the "corrupted" strips and there is nothing I can do that gets rid of this odd interaction. Not even duplicating the file fixes it. I have also tested this on multiple computers. Below, I have attached a video that demonstrates the issue. The sequence is very simple and worked fine before introducing the problematic strip. I have also attached an empty .blend file where I have replicated the problem **Exact steps for others to reproduce the error** -Open Blender VSE -Paste the problematic strip - Delete the problematic strip
Alessandro-Terlizzi added the
Severity
Normal
Type
Bug
Status
Needs Triage
labels 2024-10-02 02:21:38 +02:00
Member

Hi, thanks for the report. Deleting those drivers resolve the issue. Can you check?

Hi, thanks for the report. Deleting those drivers resolve the issue. Can you check?
Pratik Borhade added
Status
Needs Information from User
and removed
Status
Needs Triage
labels 2024-10-02 05:57:28 +02:00

I apologize for not understanding well. In the empty .blend file (LagTest.blend) where can I find the drivers?

I apologize for not understanding well. In the empty .blend file (LagTest.blend) where can I find the drivers?
Member

Open driver editor 😅

Open driver editor 😅

@PratikPB2123 it is a good question however, how that many "broken" animation drivers ended up there. Maybe some operations within Blender itself create/leak drivers? In the LagTest.blend there are a ton with the same name (sequence_editor.sequences_all["Empty.047"].transform.offset_y[0]). Maybe whichever code/system has created them, should not? There's half a million drivers in that file.

@Alessandro-Terlizzi do you recall how did you create this problematic scenario? You say "metastrips are pasted in the project" -- you mean they are pasted from another file? Or another scene? or...?

@PratikPB2123 it is a good question however, *how* that many "broken" animation drivers ended up there. Maybe some operations within Blender itself create/leak drivers? In the `LagTest.blend` there are a ton with the same name (`sequence_editor.sequences_all["Empty.047"].transform.offset_y[0]`). Maybe whichever code/system has created them, should not? There's half a million drivers in that file. @Alessandro-Terlizzi do you recall *how* did you create this problematic scenario? You say "metastrips are pasted in the project" -- you mean they are pasted from another file? Or another scene? or...?

@PratikPB2123 I apologize again for my misunderstanding. I just started using drivers so I wasn't familiar with how to find them. Deleting the corrupt drivers from the projects seems to solve the issue. Thank you so much for the support.

@aras_p I do recall using a simple driver set-up where I was moving an image based on the position of a color strip. I never made use of this but I didn't delete the drivers. This was all inside of a metastrip. The issue might be that I duplicated and modified this metastrip, breaking the relationship set by the driver while doing so.

I broke the .blend file I sent you guys by copying and pasting the strips from the original corrupt project and deleting them. I duplicated a bunch of them so that's how that many broken drivers ended up there.

I'm not sure if this can be considered a but or not because it might be due to me using drivers incorrectly. If it helps, I can do further testing and try to replicate the situation.

@PratikPB2123 I apologize again for my misunderstanding. I just started using drivers so I wasn't familiar with how to find them. Deleting the corrupt drivers from the projects seems to solve the issue. Thank you so much for the support. @aras_p I do recall using a simple driver set-up where I was moving an image based on the position of a color strip. I never made use of this but I didn't delete the drivers. This was all inside of a metastrip. The issue might be that I duplicated and modified this metastrip, breaking the relationship set by the driver while doing so. I broke the .blend file I sent you guys by copying and pasting the strips from the original corrupt project and deleting them. I duplicated a bunch of them so that's how that many broken drivers ended up there. I'm not sure if this can be considered a but or not because it might be due to me using drivers incorrectly. If it helps, I can do further testing and try to replicate the situation.
Member

Thanks @aras_p . I should have investigated further 😅

Thanks @aras_p . I should have investigated further 😅
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset System
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Code Documentation
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Viewport & EEVEE
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Asset Browser Project
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Module
Viewport & EEVEE
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Severity
High
Severity
Low
Severity
Normal
Severity
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#128464
No description provided.