Dev:Bline Speed - Revision history

Zelgadis: moved Bline Speed to Dev:Bline Speed

2010-02-19T06:53:57Z

moved Bline Speed to Dev:Bline Speed

Zelgadis: Text replace - ']]' to '}}'

2009-09-08T06:30:48Z

Text replace - ']]' to '}}'

Zelgadis: Text replace - '[[' to '{{l|'

2009-09-07T15:19:55Z

Text replace - '[[' to '{{l|'

Dooglus: /* Solving the equation */

2008-02-15T20:49:28Z

‎Solving the equation

Dooglus: /* Adjusting a Bline's "speed" */

2008-02-15T20:47:37Z

‎Adjusting a Bline's "speed"

Dooglus: /* Why does "speed" changes? */

2008-02-15T20:44:16Z

‎Why does "speed" changes?

Dooglus: /* Bline's parameter's "speed" */

2008-02-15T20:42:18Z

‎Bline's parameter's "speed"

Yoyobuae at 20:29, 15 February 2008

2008-02-15T20:29:15Z

Yoyobuae: Adding an explanation page to a method to ensure things move at certain speed when following a Bline

2008-02-15T20:20:58Z

Adding an explanation page to a method to ensure things move at certain speed when following a Bline

New page

== Bline's parameter's "speed" ==

If you have played enough with Blines, "Bline Vertex" and "Bline Tangent" converts you perhaps have noticed that a change in the "Amount" parameter doesn't always step forward/backwards the same amount. For example, adding 0.1 to "Amount" doesn't move a "Bline Vertex" by the same distance all the time.

Near the bline's vertexes (or near the curved parts) you'll notice that evenly spaced "Amount" values are either compressed together or expanded away from each other. Trying to make an object follow a bline will lead to the object changing speeds as it goes along it.

The problem lies in how Blines are defined and how a position in the Bline changes as "Amount" parameter changes. I'll refer to the rate of change as the Bline's "speed".

== Why does "speed" changes? ==

Firstly, a Synfig Bline is composed of several bezier sections. Each segment is a cubic bezier line. This sections are joined back to back, allowing for arbitrarily complex shapes. All the properties that for a single section, also hold true for any number of sections. So I'm gonna focus on Blines with a single section, in other words, Blines with only two vertexes.

A Bline with a single section reduces to a [http://en.wikipedia.org/wiki/B%C3%A9zier_curve#Cubic_B.C3.A9zier_curves Cubic Bezier] defined like this:

<math>\mathbf{B}(t)=(1-t)^3\mathbf{P}_0+3t(1-t)^2\mathbf{P}_1+3t^2(1-t)\mathbf{P}_2+t^3\mathbf{P}_3 \mbox{ , } t \in [0,1].</math>

This equation describes the shape of the curve. As the <math>t\,\!</math> parameter increases from zero up to one, the point defined by the equation moves from the Bezier's start towards it's end. The rate of the motion to as <math>t\,\!</math> increases describes the curve's "speed". Taking the [http://en.wikipedia.org/wiki/Derivative derivative] of this equation yields the "speed":

<math>
\frac{d\mathbf{B}(t)}{dt}=
(1-t)^2
[
3
(
\mathbf{P}_1
-
\mathbf{P}_0
)
]
+
2t(1-t)
[
3
(
\mathbf{P}_2
-
\mathbf{P}_1
)
]
+
t^2
[
3
(
\mathbf{P}_3
-
\mathbf{P}_2
)
]
\mbox{ , }t \in [0,1].
</math>

You may have noticed that this equation is equivalent to a [http://en.wikipedia.org/wiki/B%C3%A9zier_curve#Quadratic_B.C3.A9zier_curves Quadratic Bezier]. This tells us that the "speed" can and does change as the <math>t\,\!</math> parameter changes.

== Adjusting a Bline's "speed" ==

Our objective is now to compensate the derivative to achieve a desired "speed". We cannot change the control points to the curve without changing it's shape. The only other thing we can change is the parameter <math>t\,\!</math>. Therefore, we define a function <math>g(t)\,\!</math> so that:

<math>\frac{d\mathbf{B}(g(t))}{dt}=\boldsymbol{s}(t)\,\,</math>

Where <math>\boldsymbol{s}(t)</math> is a vector <math>(s_x(t),s_y(t))\,\!</math> that defines the desired speed as a function of <math>t\,\!</math>. The curve needs to move in a whole range of directions as the curve describes its shape. Our objective is only to control its magnitude. This magnitude condition can be expressed as:

<math>s_x^2(t)+s_y^2(t)=s_{mag}^2(t)</math>

Where <math>s_{mag}(t)\,\!</math> is a function defining the desired "speed" magnitude.

We can expand our first equation a bit:

<math>\frac{d\mathbf{B}(g(t))}{dt}=\frac{d\mathbf{B}(g(t))}{d(g(t))}\,\frac{dg(t)}{dt}=\boldsymbol{s}(t)\,\,</math>

Expanding the equation like this lets us use the Bline's derivative, by replacing <math>t\,\!</math> with <math>g(t)\,\!</math>. Next we replace the x and y components into the magnitude condition equation:

<math>\Bigg[\frac{dB_x(g(t))}{d(g(t))}\,\frac{dg(t)}{dt}\Bigg]^2+\Bigg[\frac{dB_y(g(t))}{d(g(t))}\,\frac{dg(t)}{dt}\Bigg]^2=s_{mag}^2(t)</math>

Rearranging we obtain an [http://en.wikipedia.org/wiki/Differential_equation#Types_of_differential_equations ordinary non-linear differential equation]:

<math>\frac{dg(t)}{dt}=\frac{s_{mag}(t)}{\sqrt{\Big[\frac{dB_x(g(t))}{d(g(t))}\Big]^2+\Big[\frac{dB_y(g(t))}{d(g(t))}\Big]^2}}</math>

Solving this equation yields a function <math>g(t)\,\!</math> such that the curve's "speed" is dictated by the function <math>s_{mag}(t)\,\!</math>.

== Solving the equation ==

All that is left is to solve the equation. It is quite complex and as I said before, the differential equation that we got is non-linear. This makes it hard to find <math>g(t)\,\!</math> in a clear formula.

But even such a complex equation is easy to solve numerically. Keeping in mind that what we want is simply the value of <math>g(t)\,\!</math> so we can plug into "Amount". A numerical solution of the equation gives us just that, the value of <math>g(t)\,\!</math> at certain intervals.

The [http://en.wikipedia.org/wiki/Runge-kutta Runge-Kutta] method serves this purpose quite well, and it's quite simple also. All we need is to evaluate the derivative of the function that we need to find, and feed the values into the Runge-Kutta method.

Let's try a simple case, constant speed. If <math>s_{mag}(t)\,\!</math> is a constant value, then it would need to be equal to the Bline's length, so that as the <math>t\,\!</math> goes from 0.0 up to 1.0, the curve moves from the start to the end. Too little speed and the curve won't reach the end when <math>t\,\!</math> reaches 1.0. Too much and the curve will go past the end when <math>t\,\!</math> reaches 1.0.

Conveniently, this method also allows to find a Bline's length. If we assume <math>s_{mag}(t)=1\,\!</math> then the curve will reach it's end when <math>t=LENGTH\,\!</math>, where LENGTH is the Bline's length.

@@ Line 1: / Line 1: @@
 == Bline's parameter's "speed" ==
-If you have played enough with Blines, "{{l|Convert#BLine_Vertex|BLine Vertex]]" and "{{l|Convert#BLine_Tangent|BLine Tangent]]" converts you perhaps have noticed that a change in the "Amount" parameter doesn't always step forward/backwards the same amount.  For example, adding 0.1 to "Amount" doesn't move a "Bline Vertex" by the same distance all the time.
+If you have played enough with Blines, "{{l|Convert#BLine_Vertex|BLine Vertex}}" and "{{l|Convert#BLine_Tangent|BLine Tangent}}" converts you perhaps have noticed that a change in the "Amount" parameter doesn't always step forward/backwards the same amount.  For example, adding 0.1 to "Amount" doesn't move a "Bline Vertex" by the same distance all the time.
 Near the bline's vertices (or near the curved parts) you'll notice that evenly spaced "Amount" values are either compressed together or expanded away from each other.  Trying to make an object follow a bline will lead to the object changing speeds as it goes along it.

@@ Line 1: / Line 1: @@
 == Bline's parameter's "speed" ==
-If you have played enough with Blines, "[[Convert#BLine_Vertex|BLine Vertex]]" and "[[Convert#BLine_Tangent|BLine Tangent]]" converts you perhaps have noticed that a change in the "Amount" parameter doesn't always step forward/backwards the same amount.  For example, adding 0.1 to "Amount" doesn't move a "Bline Vertex" by the same distance all the time.
+If you have played enough with Blines, "{{l|Convert#BLine_Vertex|BLine Vertex]]" and "{{l|Convert#BLine_Tangent|BLine Tangent]]" converts you perhaps have noticed that a change in the "Amount" parameter doesn't always step forward/backwards the same amount.  For example, adding 0.1 to "Amount" doesn't move a "Bline Vertex" by the same distance all the time.
 Near the bline's vertices (or near the curved parts) you'll notice that evenly spaced "Amount" values are either compressed together or expanded away from each other.  Trying to make an object follow a bline will lead to the object changing speeds as it goes along it.

← Older revision		Revision as of 20:49, 15 February 2008
Line 89:		Line 89:
	Let's try a simple case, constant speed. If <math>s_{mag}(t)\,\!</math> is a constant value, then it would need to be equal to the Bline's length, so that as the <math>t\,\!</math> goes from 0.0 up to 1.0, the curve moves from the start to the end. Too little speed and the curve won't reach the end when <math>t\,\!</math> reaches 1.0. Too much and the curve will go past the end when <math>t\,\!</math> reaches 1.0.		Let's try a simple case, constant speed. If <math>s_{mag}(t)\,\!</math> is a constant value, then it would need to be equal to the Bline's length, so that as the <math>t\,\!</math> goes from 0.0 up to 1.0, the curve moves from the start to the end. Too little speed and the curve won't reach the end when <math>t\,\!</math> reaches 1.0. Too much and the curve will go past the end when <math>t\,\!</math> reaches 1.0.

−	Conveniently, this method also allows to find a Bline's length. If we assume <math>s_{mag}(t)=1\,\!</math> then the curve will reach ~~it's~~ end when <math>t=LENGTH\,\!</math>, where LENGTH is the Bline's length.	+	Conveniently, this method also allows to find a Bline's length. If we assume <math>s_{mag}(t)=1\,\!</math> then the curve will reach its end when <math>t=LENGTH\,\!</math>, where LENGTH is the Bline's length.

← Older revision	Revision as of 06:53, 19 February 2010
(No difference)

@@ Line 55: / Line 55: @@
 == Adjusting a Bline's "speed" ==
-Our objective is now to compensate the derivative to achieve a desired "speed". We cannot change the control points to the curve without changing it's shape. The only other thing we can change is the parameter <math>t\,\!</math>. Therefore, we define a function <math>g(t)\,\!</math> so that:
+Our objective is now to compensate the derivative to achieve a desired "speed". We cannot change the control points to the curve without changing its shape. The only other thing we can change is the parameter <math>t\,\!</math>. Therefore, we define a function <math>g(t)\,\!</math> so that:
 <math>\frac{d\mathbf{B}(g(t))}{dt}=\boldsymbol{s}(t)\,\,</math>

@@ Line 15: / Line 15: @@
 <math>\mathbf{B}(t)=(1-t)^3\mathbf{P}_0+3t(1-t)^2\mathbf{P}_1+3t^2(1-t)\mathbf{P}_2+t^3\mathbf{P}_3 \mbox{ , } t \in [0,1].</math>
-This equation describes the shape of the curve.  As the <math>t\,\!</math> parameter increases from zero up to one, the point defined by the equation moves from the Bezier's start towards it's end. The rate of the motion to as <math>t\,\!</math> increases describes the curve's "speed". Taking the [http://en.wikipedia.org/wiki/Derivative derivative] of this equation yields the "speed":
+This equation describes the shape of the curve.  As the <math>t\,\!</math> parameter increases from zero up to one, the point defined by the equation moves from the Bezier's start (<math>\mathbf{P}_0</math>) towards its end (<math>\mathbf{P}_3</math>). The rate of the motion as <math>t\,\!</math> increases describes the curve's "speed". Taking the [http://en.wikipedia.org/wiki/Derivative derivative] of this equation yields the "speed":
 <math>

@@ Line 1: / Line 1: @@
 == Bline's parameter's "speed" ==
-If you have played enough with Blines, "Bline Vertex" and "Bline Tangent" converts you perhaps have noticed that a change in the "Amount" parameter doesn't always step forward/backwards the same amount.  For example, adding 0.1 to "Amount" doesn't move a "Bline Vertex" by the same distance all the time.
+If you have played enough with Blines, "[[Convert#BLine_Vertex|BLine Vertex]]" and "[[Convert#BLine_Tangent|BLine Tangent]]" converts you perhaps have noticed that a change in the "Amount" parameter doesn't always step forward/backwards the same amount.  For example, adding 0.1 to "Amount" doesn't move a "Bline Vertex" by the same distance all the time.
-Near the bline's vertexes (or near the curved parts) you'll notice that evenly spaced "Amount" values are either compressed together or expanded away from each other.  Trying to make an object follow a bline will lead to the object changing speeds as it goes along it.
+Near the bline's vertices (or near the curved parts) you'll notice that evenly spaced "Amount" values are either compressed together or expanded away from each other.  Trying to make an object follow a bline will lead to the object changing speeds as it goes along it.
-The problem lies in how Blines are defined and how a position in the Bline changes as "Amount" parameter changes.  I'll refer to the rate of change as the Bline's "speed".
+The problem lies in how Blines are defined and how a position in the Bline changes as the "Amount" parameter changes.  I'll refer to the rate of change as the Bline's "speed".
 == Why does "speed" changes? ==

@@ Line 69: / Line 69: @@
 <math>\frac{d\mathbf{B}(g(t))}{dt}=\frac{d\mathbf{B}(g(t))}{d(g(t))}\,\frac{dg(t)}{dt}=\boldsymbol{s}(t)\,\,</math>
-Expanding the equation like this lets us use the Bline's derivative, by replacing <math>t\,\!</math> with <math>g(t)\,\!</math>.  Next we replace the x and y components into the magnitude condition equation:
+Expanding the equation like this lets us use the original Bline's derivative definition, by replacing <math>t\,\!</math> with <math>g(t)\,\!</math>.  Next we replace the x and y components into the magnitude condition equation:
 <math>\Bigg[\frac{dB_x(g(t))}{d(g(t))}\,\frac{dg(t)}{dt}\Bigg]^2+\Bigg[\frac{dB_y(g(t))}{d(g(t))}\,\frac{dg(t)}{dt}\Bigg]^2=s_{mag}^2(t)</math>
@@ Line 83: / Line 83: @@
 All that is left is to solve the equation. It is quite complex and as I said before, the differential equation that we got is non-linear. This makes it hard to find <math>g(t)\,\!</math> in a clear formula.
-But even such a complex equation is easy to solve numerically. Keeping in mind that what we want is simply the value of <math>g(t)\,\!</math> so we can plug into "Amount".  A numerical solution of the equation gives us just that, the value of <math>g(t)\,\!</math> at certain intervals.
+But even such a complex equation is easy to solve numerically. Keeping in mind that what we want is simply the value of <math>g(t)\,\!</math> so we can plug it into "Amount".  A numerical solution of the equation gives us just that, the value of <math>g(t)\,\!</math> at certain intervals.
 The [http://en.wikipedia.org/wiki/Runge-kutta Runge-Kutta] method serves this purpose quite well, and it's quite simple also.  All we need is to evaluate the derivative of the function that we need to find, and feed the values into the Runge-Kutta method.