Image crop keyframes/fcurves do not 'stick' to strip *NEED BLEND FILE* #28158

New Issue

bassam kurdali · 2011-08-05T00:18:12+02:00

bassam kurdali commented

2011-08-05 00:18:12 +02:00

%%%In the sequence editor, fcurves for sequence strips are supposed to 'stick' to their strips, such that translating a strip left or right (forward or back) in time results in the same transformation to the fcurves for that strip.

For the image Crop properties (max_x,max_y,min_x,min_y) this is not the case, and the fcurves have to be moved manually.

Note: this in itself is a regression from 2.4 where you could have IPOs in 'scene time' or 'strip time' This is no longer possible in 2.4, and we have 'strip time' via mirrored translations- in theory we should be able to have a strip property flag (use_animation_lock) or similar, that allows fcurves associated with that strip to move with it or not. But this is a feature request, the original bug report still stands.

OS ubuntu 10.10, intel cpu, nvidia gfx, 64 bit.
%%%

%%%In the sequence editor, fcurves for sequence strips are supposed to 'stick' to their strips, such that translating a strip left or right (forward or back) in time results in the same transformation to the fcurves for that strip. For the image Crop properties (max_x,max_y,min_x,min_y) this is not the case, and the fcurves have to be moved manually. Note: this in itself is a regression from 2.4 where you could have IPOs in 'scene time' or 'strip time' This is no longer possible in 2.4, and we have 'strip time' via mirrored translations- in theory we should be able to have a strip property flag (use_animation_lock) or similar, that allows fcurves associated with that strip to move with it or not. But this is a feature request, the original bug report still stands. OS ubuntu 10.10, intel cpu, nvidia gfx, 64 bit. %%%

bassam kurdali commented

2011-08-05 00:18:12 +02:00

Changed status to: 'Open'

Campbell Barton commented

2011-08-05 08:33:18 +02:00

%%%Works for me - note that this code didnt change recently, attached example blend file.

Could you please attach an example which fails?%%%

%%%Works for me - note that this code didnt change recently, attached example blend file. Could you please attach an example which fails?%%%

bassam kurdali commented

2011-08-05 09:21:04 +02:00

%%%Interesting, it's happening only on a (unfortunately huge) edit... will try to make it happen on a smaller file
%%%

%%%Interesting, it's happening only on a (unfortunately huge) edit... will try to make it happen on a smaller file %%%

Campbell Barton commented

2011-08-05 11:10:07 +02:00

%%%Suspect this is caused by a duplicate named sequence strip - which should never happen :S

Try rename the sequence strip to something you know is unique, then add fcurves and move.%%%

%%%Suspect this is caused by a duplicate named sequence strip - which should never happen :S Try rename the sequence strip to something you know is unique, then add fcurves and move.%%%

bassam kurdali commented

2011-08-17 01:48:48 +02:00

%%%Hi Campbell,
further testing on the file reveals it's something else
I think this happens because the strip in question is inside a metastrip - there are no duplicate names in the files (checked by looping over sequences_all in the console)
will see if the mere existance of a metastrip causes it in a new file, then report.
cheers
Bassam%%%

%%%Hi Campbell, further testing on the file reveals it's something else I think this happens because the strip in question is inside a metastrip - there are no duplicate names in the files (checked by looping over sequences_all in the console) will see if the mere existance of a metastrip causes it in a new file, then report. cheers Bassam%%%

bassam kurdali commented

2011-08-17 01:54:17 +02:00

%%%Hi Campbell, further testing:
If you have a metastrip within a metastrip, and it has crop fcurves they do not move with the strip if you move the top level metastrip:
this doesn't happen to the top level metastrip
this doesn't happen to another type of strip (color) within the metastrip
%%%

%%%Hi Campbell, further testing: If you have a metastrip within a metastrip, and it has crop fcurves they do not move with the strip if you move the top level metastrip: this doesn't happen to the top level metastrip this doesn't happen to another type of strip (color) within the metastrip %%%

Campbell Barton commented

2011-09-28 12:07:42 +02:00

%%%fixed r40652.%%%

Campbell Barton commented

2011-09-28 12:07:42 +02:00

Changed status from 'Open' to: 'Resolved'

Campbell Barton closed this issue

2011-09-28 12:07:42 +02:00

bassam kurdali commented

2011-09-28 22:46:33 +02:00

%%%Thanks Campbell!%%%

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Image crop keyframes/fcurves do not 'stick' to strip *NEED BLEND FILE* #28158

Image crop keyframes/fcurves do not 'stick' to strip NEED BLEND FILE #28158