Maniphest T60370

Keyframes on Cut-ted strips
Closed, Duplicate
Actions

Assigned To
None
Authored By
Guillaume M (mathers)
Jan 10 2019, 12:00 AM
Tags
  • BF Blender
Subscribers
Bastien Montagne (mont29)
Guillaume M (mathers)
Jacques Lucke (JacquesLucke)

Description

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

Revisions and Commits

rB Blender
AbandonedD4186 Set names of cut sequences properly, so that the duplicated animation data is attached to the right sequence

Related Objects

Event Timeline

Guillaume M (mathers) created this task.Jan 10 2019, 12:00 AM
Jacques Lucke (JacquesLucke) added a subscriber: Jacques Lucke (JacquesLucke).Jan 10 2019, 11:05 AM

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?

Guillaume M (mathers) added a comment.Jan 10 2019, 11:19 AM

Sorry about that, it looks like I introduced this bug in my local build by applying a patch I made to solve this bug : 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 T60194 ?

Guillaume M (mathers) mentioned this in D4186: Set names of cut sequences properly, so that the duplicated animation data is attached to the right sequence.Jan 10 2019, 11:21 AM
Jacques Lucke (JacquesLucke) added a comment.Jan 10 2019, 11:22 AM

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.

Guillaume M (mathers) mentioned this in T60194: Sequencer cut loses animation data for the right strip.Jan 10 2019, 11:24 AM
Guillaume M (mathers) added a revision: D4186: Set names of cut sequences properly, so that the duplicated animation data is attached to the right sequence.
Bastien Montagne (mont29) added a subscriber: Bastien Montagne (mont29).Jan 11 2019, 7:52 PM

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

Bastien Montagne (mont29) closed this task as a duplicate of T60194: Sequencer cut loses animation data for the right strip.Jan 11 2019, 7:53 PM