Talk:Keyframe - Revision history

D.j.a.y: Information about "menu /../ keyframe" are missing

2013-05-19T13:30:56Z

Information about "menu /../ keyframe" are missing

Zelgadis: answer

2008-02-29T15:43:26Z

answer

Genete: Reply to Zelgadis

2008-02-29T13:28:57Z

Reply to Zelgadis

Zelgadis: "Duplicate_a_keyframe_with_no_waypoint_on_it" is a bug?

2008-02-29T09:59:43Z

"Duplicate_a_keyframe_with_no_waypoint_on_it" is a bug?

Genete: Reply to dooglus

2007-10-11T08:32:08Z

Reply to dooglus

Dooglus at 00:21, 11 October 2007

2007-10-11T00:21:19Z

Dooglus at 00:18, 11 October 2007

2007-10-11T00:18:38Z

Dooglus at 00:15, 11 October 2007

2007-10-11T00:15:42Z

Dooglus: New page: "Also it is a mark to a special frame where the information of every parameter in the animation is stored there in order to be reused later." : No information is stored at all if you don'...

2007-10-11T00:11:12Z

New page: "Also it is a mark to a special frame where the information of every parameter in the animation is stored there in order to be reused later." : No information is stored at all if you don'...

New page

"Also it is a mark to a special frame where the information of every parameter in the animation is stored there in order to be reused later."

: No information is stored at all if you don't edit any parameter values. For example, make a scene, set the slider to 0s, arrange things, change the slider to 10s, arrange things again. You'll have a bunch of waypoints at 0s and 10s.

: Then add keyframes at 2, 4, 6, and 8s, save the file and look at the saved .sif. You'll not see any information at all about the values of the parameters at 2, 4, 6, or 8s; you'll only see information about the value at 0s and 10s. The values at 2, 4, 6, and 8s are calculated using interpolation, just like all other points in time between 0s and 10s.

: It's only when you edit parameters _after_ making a keyframe that information is stored about the value of the parameter at the keyframe(s). -- [[User:Dooglus|dooglus]] 20:11, 10 October 2007 (EDT)

← Older revision		Revision as of 13:30, 19 May 2013
Line 1:		Line 1:
		+	--[[User:D.j.a.y\|D.j.a.y]] ([[User talk:D.j.a.y\|talk]]) 13:30, 19 May 2013 (UTC) Information about "menu /../ keyframe" are missing
		+
		+	----
		+
	I think [[Keyframe#Duplicate_a_keyframe_with_no_waypoint_on_it]] can be considered not only as example, but as bug report. :)		I think [[Keyframe#Duplicate_a_keyframe_with_no_waypoint_on_it]] can be considered not only as example, but as bug report. :)

@@ Line 2: / Line 2: @@
 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. --[[User:Zelgadis|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 neigbour 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. --[[User:Genete|Genete]] 08:28, 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. --[[User:Genete|Genete]] 08:28, 29 February 2008 (EST)
 ----

@@ Line 1: / Line 1: @@
 I think [[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. --[[User:Zelgadis|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 neigbour 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. --[[User:Genete|Genete]] 08:28, 29 February 2008 (EST)
 ----

← Older revision		Revision as of 09:59, 29 February 2008
Line 1:		Line 1:
		+
		+	I think [[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. --[[User:Zelgadis\|Zelgadis]] 04:59, 29 February 2008 (EST)
		+
		+	----
		+
	"Also it is a mark to a special frame where the information of every parameter in the animation is stored there in order to be reused later."		"Also it is a mark to a special frame where the information of every parameter in the animation is stored there in order to be reused later."

@@ Line 6: / Line 6: @@
 : It's only when you edit parameters _after_ making a keyframe that information is stored about the value of the parameter at the keyframe(s). -- [[User:Dooglus|dooglus]] 20:11, 10 October 2007 (EDT)
 "A keyframe could live all the time without any waypoint but it stores the information of the values of the parameters on that specific frame"
@@ Line 14: / Line 16: @@
 : Waypoints are all that is stored to record animation information.  The only thing stored about keyframes are their positions in time (2,4,6,8s) and their names. -- [[User:Dooglus|dooglus]] 20:18, 10 October 2007 (EDT)
 "Anyway the creation of a waypoint implies possible creation of keyframes"
 : I think that's probably just a typo, rather than a misunderstanding.  The creation of waypoints can cause the creation of other waypoints at keyframes.  It doesn't cause the creation of keyframes themselves - they are only made directly by the user. -- [[User:Dooglus|dooglus]] 20:21, 10 October 2007 (EDT)
 I'm going to have to stop reading this for now, I'm too tired.  It looks like a very good basis for the page on keyframes, and it well overdue.  Well done! [[User:Dooglus|dooglus]] 20:21, 10 October 2007 (EDT)

← Older revision		Revision as of 00:21, 11 October 2007
Line 14:		Line 14:

	: Waypoints are all that is stored to record animation information. The only thing stored about keyframes are their positions in time (2,4,6,8s) and their names. -- [[User:Dooglus\|dooglus]] 20:18, 10 October 2007 (EDT)		: Waypoints are all that is stored to record animation information. The only thing stored about keyframes are their positions in time (2,4,6,8s) and their names. -- [[User:Dooglus\|dooglus]] 20:18, 10 October 2007 (EDT)
		+
		+	"Anyway the creation of a waypoint implies possible creation of keyframes"
		+
		+	: I think that's probably just a typo, rather than a misunderstanding. The creation of waypoints can cause the creation of other waypoints at keyframes. It doesn't cause the creation of keyframes themselves - they are only made directly by the user. -- [[User:Dooglus\|dooglus]] 20:21, 10 October 2007 (EDT)
		+
		+	I'm going to have to stop reading this for now, I'm too tired. It looks like a very good basis for the page on keyframes, and it well overdue. Well done! [[User:Dooglus\|dooglus]] 20:21, 10 October 2007 (EDT)

← Older revision		Revision as of 00:18, 11 October 2007
Line 10:		Line 10:

	: There, you said it again. I suppose you can think of it as storing the information if you like. It doesn't really though. It's just a note that the information must be stored if anyone ever tries to change it by editing in 'neighboring' frames. -- [[User:Dooglus\|dooglus]] 20:15, 10 October 2007 (EDT)		: There, you said it again. I suppose you can think of it as storing the information if you like. It doesn't really though. It's just a note that the information must be stored if anyone ever tries to change it by editing in 'neighboring' frames. -- [[User:Dooglus\|dooglus]] 20:15, 10 October 2007 (EDT)
		+
		+	"If there is a waypoint there then the waypoint information is stored also (I have to verify this)"
		+
		+	: Waypoints are all that is stored to record animation information. The only thing stored about keyframes are their positions in time (2,4,6,8s) and their names. -- [[User:Dooglus\|dooglus]] 20:18, 10 October 2007 (EDT)

← Older revision		Revision as of 00:15, 11 October 2007
Line 6:		Line 6:

	: It's only when you edit parameters _after_ making a keyframe that information is stored about the value of the parameter at the keyframe(s). -- [[User:Dooglus\|dooglus]] 20:11, 10 October 2007 (EDT)		: It's only when you edit parameters _after_ making a keyframe that information is stored about the value of the parameter at the keyframe(s). -- [[User:Dooglus\|dooglus]] 20:11, 10 October 2007 (EDT)
		+
		+	"A keyframe could live all the time without any waypoint but it stores the information of the values of the parameters on that specific frame"
		+
		+	: There, you said it again. I suppose you can think of it as storing the information if you like. It doesn't really though. It's just a note that the information must be stored if anyone ever tries to change it by editing in 'neighboring' frames. -- [[User:Dooglus\|dooglus]] 20:15, 10 October 2007 (EDT)