Bugs item #1906375, was opened at 2008-03-03 08:32 Message generated for change (Comment added) made by zelgadis_ksee You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=757416&aid=1906375&group_id=144022
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Usability Group: Latest release Status: Open Resolution: None Priority: 5 Private: No Submitted By: Konstantin Dmitriev (zelgadis_ksee) Assigned to: Nobody/Anonymous (nobody) Summary: Lock keyframes not preserves all keyframes Initial Comment: == A little summary of wiki and IRC discussion: == I think http://synfig.org/Keyframe#Duplicate_a_keyframe_with_no_waypoint_on_it can be considered not only as example, but as bug report. :) As I understand the main purpose of keyframes is to fixate canvas state at some time (i.e. prevent from changes when neighbor waypoints are created/manipulated/edited). But in this example when we duplicating keyframe we could see what the value of duplicated frame is changed, although we not directly edited him. For me as user keyframes loosing their meaning if they could loose their original values because of some manipulations some simple manipulations. It's possible, what duplicating of just one keyframe can ruin whole animation. --Zelgadis 04:59, 29 February 2008 (EST) You can consider it a bug, yes. But remember that lock keyframes is designed to stop effects on the neighbor keyframes of the place where the new waypoints are inserted. In the example you mentioned there is a keyframe at frame 4s and it keeps the current value. To solve that bug, Synfigstudio would lock all the keyframes past and/or future (depending on the keyframe lock status) and not only the neigbour ones were the new waypoint was created. I don't know if that is better or worse than the current behavior. --Genete 08:28, 29 February 2008 (EST) Notice how "Lock Keyframes" states called: All Keyframes Locked/Past Keyframes Locked/Future Keyframes Locked/No Keyframes Locked. Nothing said about "neighbors". :) Now synfig considering only neighbors. But I think that it's breaks all keyframes concept. I consider keyframes as waypoints for canvases. Waypoint is a fixation for something. Currently keyframes is "not always working fixation". This is irritating, don't you think? Maybe synfig must make more deeper analysis while duplicating keyframes to prevent changes in other keyframes. --Zelgadis 10:43, 29 February 2008 (EST) 16:46 < genete> Zelgadis: absolutely right. But the problem is not with duplicate keyframe. The problem is at lock keyframes status behavoir. You can obtain same result just inserting a waypoint at that position, so that's not related to duplicate 16:46 < Zelgadis> genete: oh, you right 16:47 < Zelgadis> genete: Duplicate keyframes - just example of this behavoir 12:25 < Zelgadis> when we setting _new_ waypoint, we need to check if values preserved in 2 next keyframe and 2 previous (if they haven't waypoints) 12:25 < dooglus> and setting those 2 waypoints could affect the rest of the curve, recursively. 12:25 < dooglus> I get it 11:47 < dooglus> I found that if you set waypoints at 0,1,4,5 with values 0,1,4,5 then you don't get a straight line curve 12:17 < Zelgadis> dooglus: preserving curve is not our goal (it's very-very hard). Our goal is to preserve keyframe values 12:21 < Zelgadis> it's too hard to reproduce curve if we have "bizarre manual interpolation in one of the waypoints". And I think we don't need to. 12:27 < dooglus> and what interpolation should be used for the new, automatically-created waypoints? 12:38 < dooglus> I think using the default interp. method is OK for now 12:38 < dooglus> if you don't want lots of constant waypoints placed along your curve, don't use the constant default interp. type? 12:39 < Zelgadis> that's true 12:39 < Zelgadis> but why while duplicating keyframe we set it's waypoint int. type to TCB? 12:40 < dooglus> we do? 12:40 < Zelgadis> yes 23:33 < dooglus> genete: I was looking at the stuff you wrote about 'duplicating a keyframe' 23:33 < dooglus> http://synfig.org/Keyframe#Duplicate_a_keyframe 23:33 < genete> hi dooglus, nice to see you again :) 23:33 < dooglus> genete: it doesn't seem right that duplicating a keyframe makes TCB waypoints if the default interpolation type is something else - what do you think? 23:38 < dooglus> I wonder whether duplicating a keyframe should use the default interpolation method for new waypoints it needs to create 23:39 < dooglus> rather than using the interpolation method of the waypoints on the old keyframe if they exist and TCB if they don't 23:40 < genete> use the interpolation method of the waypoints of the old keyframe must be mandatory 23:40 < genete> if they exists 23:40 < dooglus> really? 23:41 < genete> when I duplicate a keyframe I want also the intepolation method if I stablished it. 23:47 < dooglus> if the value already happens to be the same, maybe it shouldn't be done, I don't know ---------------------------------------------------------------------- Comment By: Konstantin Dmitriev (zelgadis_ksee) Date: 2012-12-26 04:16 Message: This bugtracker is no longer active. The issue is moved to the new bugtracker - http://synfig.org/issues/thebuggenie/synfig ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=757416&aid=1906375&group_id=144022 ------------------------------------------------------------------------------ LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d _______________________________________________ Synfig-devl mailing list Synfig-devl@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synfig-devl
