Fix: Incorrect calculation of meta strip range #114644

Merged
Richard Antalik merged 2 commits from ok_what/blender:vse-meta-effect-bug into main 2023-11-20 04:18:27 +01:00
Contributor

The meta strip range was calculated before the effect strip range was updated. To the user this appeared as the meta strip erratically jumping to another location in the timeline when transforming it, under specific conditions.

Ways to reproduce

These are some examples of the bugs this PR fixes. There are other possible ways to trigger this bug, similar to the ones listed below, which involve changing the length or start frame of a strip, which has an effect strip applied to it, which is also inside a meta strip.

  1. Add a color strip at frame 50
  2. Add a glow effect on the color strip
  3. Group them inside a meta strip
  4. Quickly move the color strip to the right
  5. Exit the meta strip and move the meta strip.
  6. The strip "jumps" backward.

  1. Add a movie strip at frame 50
  2. Add a glow effect on the movie strip
  3. Group them inside a meta strip
  4. Entire retiming mode on the movie strip and quickly move the left retiming key to the right
  5. Exit the meta strip and move the meta strip.
  6. The strip "jumps" backward.

This calculation order is also in the code for adding an effect strip. If the effect strip is added on the color strip before grouping, the bug doesn't appear:

  1. Add a color strip on frame 50
  2. Group it inside a meta strip
  3. Go inside the meta strip and add a glow effect on the color strip
  4. Exit the meta strip and move the meta strip.
  5. The strip "jumps" to frame 0.

Review notes

SEQ_time_update_meta_strip_range(...) function:

  • Effect strips which depend on other strips are included in the calculation for the meta strip range. The code could be changed to exclude them. Doing that might obscure other bugs though.
  • I'm not sure if the calculation order of SEQ_time_update_meta_strip_range and seq_time_update_effects_strip_range has any impact in this function, but it could be changed along with the other ones in this PR for consistency.
The meta strip range was calculated before the effect strip range was updated. To the user this appeared as the meta strip erratically jumping to another location in the timeline when transforming it, under specific conditions. ### Ways to reproduce These are some examples of the bugs this PR fixes. There are other possible ways to trigger this bug, similar to the ones listed below, which involve changing the length or start frame of a strip, which has an effect strip applied to it, which is also inside a meta strip. 1. Add a color strip at frame 50 2. Add a glow effect on the color strip 3. Group them inside a meta strip 4. Quickly move the color strip to the right 5. Exit the meta strip and move the meta strip. 6. **The strip "jumps" backward.** ` ` 1. Add a movie strip at frame 50 2. Add a glow effect on the movie strip 3. Group them inside a meta strip 4. Entire retiming mode on the movie strip and quickly move the left retiming key to the right 5. Exit the meta strip and move the meta strip. 6. **The strip "jumps" backward.** This calculation order is also in the code for adding an effect strip. If the effect strip is added on the color strip before grouping, the bug doesn't appear: 1. Add a color strip on frame 50 2. Group it inside a meta strip 3. Go inside the meta strip and add a glow effect on the color strip 4. Exit the meta strip and move the meta strip. 5. **The strip "jumps" to frame 0.** ### Review notes `SEQ_time_update_meta_strip_range(...)` function: - Effect strips which depend on other strips are included in the calculation for the meta strip range. The code could be changed to exclude them. Doing that might obscure other bugs though. - I'm not sure if the calculation order of `SEQ_time_update_meta_strip_range` and `seq_time_update_effects_strip_range` has any impact in this function, but it could be changed along with the other ones in this PR for consistency.
ok what added 1 commit 2023-11-08 21:36:29 +01:00
c86eb8d889 Fix: Incorrect calculation of meta strip range
The meta strip range was calculated before the effect strip
range was updated. To the user this appeared as the meta strip
erratically jumping to another location in the timeline when
transforming it, under specific conditions.
Iliya Katushenock added the
Interest
VFX & Video
label 2023-11-09 06:31:30 +01:00
ok what added 1 commit 2023-11-09 18:15:12 +01:00
758647ce44 Change strip range calculation order in
SEQ_time_update_meta_strip_range as well for consistency.
ok what changed title from WIP: Fix: Incorrect calculation of meta strip range to Fix: Incorrect calculation of meta strip range 2023-11-09 18:22:23 +01:00
ok what requested review from Richard Antalik 2023-11-09 18:22:47 +01:00

Sorry, I was bit busy and just now got to review. I can not reproduce the issue when strip is retimed, but can reproduce 2 other issues.

Looking at the code, I see the issue right away. I was thinking, that this could be recursive issue - if you add effect to meta strip itself, but since metas should not move when being edited, this shouldn't be a problem.

Sorry, I was bit busy and just now got to review. I can not reproduce the issue when strip is retimed, but can reproduce 2 other issues. Looking at the code, I see the issue right away. I was thinking, that this could be recursive issue - if you add effect to meta strip itself, but since metas should not move when being edited, this shouldn't be a problem.
Richard Antalik merged commit c433f6666a into main 2023-11-20 04:18:27 +01:00
ok what deleted branch vse-meta-effect-bug 2023-11-22 12:39:56 +01:00
Sign in to join this conversation.
No reviewers
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
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
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
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
EEVEE & Viewport
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
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
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
2 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#114644
No description provided.