Keyframes on Cut-ted strips #60370

Closed
opened 2019-01-10 00:00:35 +01:00 by Guillaume M · 8 comments

System Information
Operating system: Ubuntu 18.04.1 LTS

Blender Version
Broken: 95736683a9

Short description of error
When cutting a meta strip, the F-curves linked to the strips inside the meta are copied, but the property indicators for the right meta-strip do not update until a keyframe is added/changed

Exact steps for others to reproduce the error

  • Open a new "Video Editing" file

  • Add a "color" strip

  • Set two keyframes to the "opacity" property of this strip (example : at frame 1, opacity=1, at frame 25 opacity=0)

  • Soft-cut this strip at frame 15 (K)

  • Open a graph editor, and see that the F-curve has correctly been duplicated by selecting the two halves one after the other

  • Select the first half, in the properties panel, watch the "Opacity" value as you scrub over the first half. The opacity changes as expected

  • Select the second half, in the properties pane, watch the "Opacity" value as you scrub over the second half. The opacity does not change

  • With the second strip selected, in the graph editor, select and move a keyframe, but cancel the move by hitting ESC or right-mouse. Now the opacity changes as expected when scrubbing

**System Information** Operating system: Ubuntu 18.04.1 LTS **Blender Version** Broken: 95736683a96d33a8a7220788502250fa9e109132 **Short description of error** When cutting a meta strip, the F-curves linked to the strips inside the meta are copied, but the property indicators for the right meta-strip do not update until a keyframe is added/changed **Exact steps for others to reproduce the error** - Open a new "Video Editing" file - Add a "color" strip - Set two keyframes to the "opacity" property of this strip (example : at frame 1, opacity=1, at frame 25 opacity=0) - Soft-cut this strip at frame 15 (K) - Open a graph editor, and see that the F-curve has correctly been duplicated by selecting the two halves one after the other - Select the first half, in the properties panel, watch the "Opacity" value as you scrub over the first half. The opacity changes as expected - Select the second half, in the properties pane, watch the "Opacity" value as you scrub over the second half. **The opacity does not change** - With the second strip selected, in the graph editor, select and move a keyframe, but cancel the move by hitting ESC or right-mouse. Now the opacity changes as expected when scrubbing
Author

Added subscriber: @mathers

Added subscriber: @mathers
Member

Added subscriber: @JacquesLucke

Added subscriber: @JacquesLucke
Member

I can somewhat reproduce something that feels wrong, but not exactly what you describe..

Can you prepare a .blend file that makes it easier for us to reproduce the issue you are experiencing?

I can somewhat reproduce something that feels wrong, but not exactly what you describe.. Can you prepare a .blend file that makes it easier for us to reproduce the issue you are experiencing?
Author

Sorry about that, it looks like I introduced this bug in my local build by applying a patch I made to solve this bug : #60194

I believe the weirdness you are seeing is the bug above ?

Should I close this task, or move it as a sub-task of #60194 ?

Sorry about that, it looks like I introduced this bug in my local build by applying a patch I made to solve this bug : [#60194 ](https://developer.blender.org/T60194) I believe the weirdness you are seeing is the bug above ? Should I close this task, or move it as a sub-task of [#60194 ](https://developer.blender.org/T60194) ?
Member

Actually it looked like in my case the problematic sequence was the left one. However maybe I just don't know what I'm doing when using the VSE :D
If you think it is the same, then close this task.

Actually it looked like in my case the problematic sequence was the left one. However maybe I just don't know what I'm doing when using the VSE :D If you think it is the same, then close this task.

Added subscriber: @mont29

Added subscriber: @mont29

This is actually caused by the exact same issue as #60194. Fix incoming.

This is actually caused by the exact same issue as #60194. Fix incoming.

Closed as duplicate of #60194

Closed as duplicate of #60194
Sign in to join this conversation.
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
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#60370
No description provided.