--- Operating System, Graphics card ---
MacOS X 7
--- Blender version with error, and version that worked ---
--- Short description of error ---
A pasted strip doesnt contains the original F-Curve keyframes.
--- Steps for others to reproduce the error (preferably based on attached .blend file) ---
Create/import some strip. Configure some animation in one or more of its properties (put some keyframes in F-Curve editor). Copy this strip. Paste the strip.
--- Operating System, Graphics card ---
Revisions and Commits
- Mentioned In
- D7264: Fix T74897: VSE animation doesn't work
T64682: Video Sequence Editor (Sequencer) Module
T73891: Pasted video sequencer strip doesn't have animation curves
T68160: Keyframes lost when copy-pasting strips
- Mentioned Here
- T71723: VSE (2.81): Copy-pasted meta strips lose all key frames
P1166 T71723 minimal
D6120: Separate operators (mesh/curve/armature/gpencil): take user preferences into account for duplicating actions
Ok, I've taken a look into this.
From the user-side
- Shift-D duplication seems to work well. <--- For now, this is the workaround to this bug
- Copy/Paste however doesn't
The cause of this bug is that when strips are copied into the copy buffer, they are assigned unique names. A consequence of this however is that these strips get pasted, it is impossible to figure out what the original curve names should have been. Thus, there are no curves copied over.
- We cannot disable the "SEQ_DUPE_UNIQUE_NAME" flag in sequencer_copy_exec() -> BKE_sequence_base_dupli_recursive(), as it seems that this is necessary to avoid some other bug T25932. Even if we did disable this, there are several other things that work against us there
- An alternative may be to make the copy operation make copies of the F-Curves used by copied strips as well. The problem here though is that keeping copies of this info around is a bit messier. Besides, no other area of Blender does this sort of partial copying of F-Curves for their clipboards.
So, for now, more investigations on how to resolve this problem are needed.
Thanks for the detailed explanation algorith!
I already make monthly donations to blender, but how much would I have to donate to get this problem fixed? :P It's killing my workflow, as I do occasional video editing for a local community TV station and I like to work with multiple scenes for separate but related segments, so duplicate isn't an option unfortunately :( Unless you know of another trick I could use...? I really enjoy editing in blender, but I don't get much time to do it, so when I do I hate dealing with technical issues and duplicated effort :(
Anyway, will wait patiently either way, cheers!
I am in the same situation than you. I too have donated to the project some time ago. I make videos for an internal channel and most of this (if not all) are done in blender vse. This feature would make our work easier and faster.
Blender is an extremelly interesting software for video editing, but it seems that, unfortunatelly, the developers don't want to give much attention to this specific part. By the way, where could I, as a user, not a developer, give some suggestions for the project?
While Duplicating a strip works in a scene, it doesn't work between scenes.
Once a VSE strip is copied and pasted, you can also 'copy paste the f-curve' as a second step. However the newly copied strip needs to have a target keyframe created before pasting can occur. Also the pasted f-curve doesn't respect strip first frame or timeline offset value.
I have no experience with this specific issue, but I just submitted another problem about the video sequencer. I'm adding my voice to the one of slinkeepie and jonata that Blender is a really cool piece of video editing software, but unfortunately, I haven't been able to get any one publishable piece out of it because of odd technical issues. But I'd like to be able to use it for an internal channel...
Could it be fixed rewriting the copy/past operation to:
- store references to the selected strip(s)
- to paste, use the duplicate operator on copied trips and modify their start frame, channel and scene owner when it's needed.
Just ran into this bug when trying to write an addon that copies a strip to another scene... not possible to use duplicate for such a task, and there seems to be no way of linking the strips, so it seems I might be stuck until this is fixed...
Would it be possible to give bpy.ops.sequencer.duplicate() the ability to duplicate into another scene maybe?
Here's an idea for using bits of sequence repeatedly: Found out recently that scene input for the sequencer can use either the camera or the inputted scene's sequencer as what is displayed, audio included.
Also, one can make linked copies of a scene and put them in the sequencer to work around the 2.80 disabling of self-scene input disabling (which was probably created to allow the above to work without recursion problems I guess).
@Clint Hobson (Domarius) Even if this is classified as a known issue, we will look into this and do what we can to resolve them.
Current meaning of known issue is:
Known Issues: Documented short-come of existing features.
When I first looked at this code, it looked hard to maintain(not quite readable), proved by prolonged efforts to fix this. To me this means that there is need to review and possibly rewrite that section completely.
So I agree with Known issue classification.