Synfig Studio :: Documentation - User contributions [en]

Canvas Properties Dialog

2014-02-08T19:19:14Z

Yoyobuae: Add description section heading so that TOC appears at top

{{Title|Canvas Properties Dialog}}
{{Category|Dialogs}}
{{NewTerminology}}

== Description ==
[[Image:Canvas properties 0.63.06.png|frame|none]]

This Canvas Properties dialog is used to establish the properties of the current main canvas. If you have defined the SYNFIG_ENABLE_NEW_CANVAS_EDIT_PROPERTIES {{l|Environment Variables|environment variable}}, then this will automatically be displayed when you start a new project. To change these parameters while working on a project, go to the {{l|Canvas_Menu_Caret|caret menu}}, select '{{l|Edit Menu|edit}}' and then 'properties'. Or you can alternatively use the {{l|Keyboard Shortcuts|keyboard shortcut}} F8.

In the main dialog you can set:

#Canvas Info:
#* Name
#* Description

== Image tab ==
In the '''Image''' tab you can set:

#Image Size:
#* Width
#* Height
#* X Resolution
#* Y Resolution
#* Physical Width
#* Physical Height
#Image Area:
#* Top Left (x,y)
#* Bottom right (x,y) - Those parameters defining the Top Left and Bottom Right canvas corners relatively to the center of the coordinates.

== Time tab ==
In the '''Time''' tab you can set:

[[File:Canvas properties time 0.63.06.png|frame|none]]

#Time Info:
#* Frames per second
#* Start Time (seconds)
#* End Time (seconds)
#* Duration (seconds)

== Other tab ==
In the '''Other''' tab you can set:

[[File:Canvas properties other 0.63.06.png|frame|none]]

#Locks and Links:
#* Image Width
#* Image Height
#* Image Aspect
#* Image Span
#* Pixel Width
#* Pixel Height
#* Pixel Aspect
#Other:
#*Focus Point

== Resizing the Canvas ==
In the '''Other''' tab, uncheck all of the Locks and Links:

[[File:Canvas_Prop_for_resize.png|frame|none]]

Then edit Image Width and Height. This will resize the canvas, stretching it's contents in the process.

== Expanding the Canvas ==
In the '''Other''' tab, check only Pixel Aspect in Locks and Links:

[[File:Canvas Prop for expand.png|frame|none]]

Then edit Image Width and Height. This will expand the canvas, keeping it's contents at the same size but adding extra space at the top/bottom and left/right.

Please note that since this dialog caused confusion, even among some very experienced people, here are some unofficial {{l|Image_Dimensions|thoughts}} about image dimensions.

Canvas Properties Dialog

2014-02-08T19:18:10Z

Yoyobuae: Add instructions to resize and to expand canvas

{{Title|Canvas Properties Dialog}}
{{Category|Dialogs}}
{{NewTerminology}}

[[Image:Canvas properties 0.63.06.png|frame|none]]

This Canvas Properties dialog is used to establish the properties of the current main canvas. If you have defined the SYNFIG_ENABLE_NEW_CANVAS_EDIT_PROPERTIES {{l|Environment Variables|environment variable}}, then this will automatically be displayed when you start a new project. To change these parameters while working on a project, go to the {{l|Canvas_Menu_Caret|caret menu}}, select '{{l|Edit Menu|edit}}' and then 'properties'. Or you can alternatively use the {{l|Keyboard Shortcuts|keyboard shortcut}} F8.

In the main dialog you can set:

#Canvas Info:
#* Name
#* Description

== Image tab ==
In the '''Image''' tab you can set:

#Image Size:
#* Width
#* Height
#* X Resolution
#* Y Resolution
#* Physical Width
#* Physical Height
#Image Area:
#* Top Left (x,y)
#* Bottom right (x,y) - Those parameters defining the Top Left and Bottom Right canvas corners relatively to the center of the coordinates.

== Time tab ==
In the '''Time''' tab you can set:

[[File:Canvas properties time 0.63.06.png|frame|none]]

#Time Info:
#* Frames per second
#* Start Time (seconds)
#* End Time (seconds)
#* Duration (seconds)

== Other tab ==
In the '''Other''' tab you can set:

[[File:Canvas properties other 0.63.06.png|frame|none]]

#Locks and Links:
#* Image Width
#* Image Height
#* Image Aspect
#* Image Span
#* Pixel Width
#* Pixel Height
#* Pixel Aspect
#Other:
#*Focus Point

== Resizing the Canvas ==
In the '''Other''' tab, uncheck all of the Locks and Links:

[[File:Canvas_Prop_for_resize.png|frame|none]]

Then edit Image Width and Height. This will resize the canvas, stretching it's contents in the process.

== Expanding the Canvas ==
In the '''Other''' tab, check only Pixel Aspect in Locks and Links:

[[File:Canvas Prop for expand.png|frame|none]]

Then edit Image Width and Height. This will expand the canvas, keeping it's contents at the same size but adding extra space at the top/bottom and left/right.

Please note that since this dialog caused confusion, even among some very experienced people, here are some unofficial {{l|Image_Dimensions|thoughts}} about image dimensions.

File:Canvas Prop for expand.png

2014-02-08T19:11:20Z

Yoyobuae: Locks and Links settings required in Canvas Properties to expand the canvas.

Locks and Links settings required in Canvas Properties to expand the canvas.

File:Canvas Prop for resize.png

2014-02-08T19:04:42Z

Yoyobuae: Locks and Links settings required in Canvas Properties to performa a canvas resize.

Locks and Links settings required in Canvas Properties to performa a canvas resize.

Dev:How Synfig Works

2009-02-13T14:56:03Z

Yoyobuae: typo

[[Image:Synfig-engine.png]]

The diagram shows more or less how Synfig is currently organized. "V" stands for valuenodes, "L" for layers, "BL" for blank layer (completely transparent layer default background), "BM" for blend method.

When Synfig needs to render a frame it starts by evaluating the valuenodes parameters of layers. If a valuenode is a Convert type then it evaluates its parameters. This process works recursively, going all the way down to the leaf nodes, calculating their value, then calculating the value of their parent, and so on until reaching the root of the node tree.

Note that valuenodes can be animated, meaning that they change value as animation time progresses. Since any leaf valuenode may have changed, the entire tree needs to be evaluated on each frame.

Once a layer has the values for it's parameters, it renders the intended shape or effect onto a raster. A raster is an array of pixels, each pixel with its color/opacity. It doesn't carry any information about the vector shapes that it's representing, only their pixel data.

Then comes blending. The raster result of the previous layers is combined with the current one according to the set blending method. Some layers (transforms, distortions, etc) just modify the raster result of the previous layers and pass that on to the next layer, instead of blending.

Note that a layer sees all the layers underneath as a single combined raster. That layer cannot distinguish the pixel data that comes from the next layer that's underneath, from pixel data from any other layer that's underneath.

The distinction between vector and raster "worlds" is important (green background for vector, red for raster in the diagram). In vector world the objects are represented symbolically, with numbers and equations that describe their caracteristics. In raster world everything is represented in a concrete way, as pixel data.

There needs to be a way to go from vector to raster world. This is called rasterization or rendering. The layers (some of them that is) sit in between the two worlds, providing the rendering.

Dev:How Synfig Works

2009-02-13T14:55:24Z

Yoyobuae: Added vector/raster world explanation

[[Image:Synfig-engine.png]]

The diagram shows more or less how Synfig is currently organized. "V" stands for valuenodes, "L" for layers, "BL" for blank layer (completely transparent layer default background), "BM" for blend method.

When Synfig needs to render a frame it starts by evaluating the valuenodes parameters of layers. If a valuenode is a Convert type then it evaluates its parameters. This process works recursively, going all the way down to the leaf nodes, calculating their value, then calculating the value of their parent, and so on until reaching the root of the node tree.

Note that valuenodes can be animated, meaning that they change value as animation time progresses. Since any leaf valuenode may have changed, the entire tree needs to be evaluated on each frame.

Once a layer has the values for it's parameters, it renders the intended shape or effect onto a raster. A raster is an array of pixels, each pixel with its color/opacity. It doesn't carry any information about the vector shapes that it's representing, only their pixel data.

Then comes blending. The raster result of the previous layers is combined with the current one according to the set blending method. Some layers (transforms, distortions, etc) just modify the raster result of the previous layers and pass that on to the next layer, instead of blending.

Note that a layer see all the layers underneath as a single combined raster. That layer cannot distinguish the pixel data that comes from the next layer that's underneath, from pixel data from any other layer that's underneath.

The distinction between vector and raster "worlds" is important (green background for vector, red for raster in the diagram). In vector world the objects are represented symbolically, with numbers and equations that describe their caracteristics. In raster world everything is represented in a concrete way, as pixel data.

There needs to be a way to go from vector to raster world. This is called rasterization or rendering. The layers (some of them that is) sit in between the two worlds, providing the rendering.

Dev:How Synfig Works

2009-02-13T14:36:19Z

Yoyobuae: Small explanation of the internals of Synfig

[[Image:Synfig-engine.png]]

The diagram shows more or less how Synfig is currently organized. "V" stands for valuenodes, "L" for layers, "BL" for blank layer (completely transparent layer default background), "BM" for blend method.

When Synfig needs to render a frame it starts by evaluating the valuenodes parameters of layers. If a valuenode is a Convert type then it evaluates its parameters. This process works recursively, going all the way down to the leaf nodes, calculating their value, then calculating the value of their parent, and so on until reaching the root of the node tree.

Note that valuenodes can be animated, meaning that they change value as animation time progresses. Since any leaf valuenode may have changed, the entire tree needs to be evaluated on each frame.

Once a layer has the values for it's parameters, it renders the intended shape or effect onto a raster. A raster is an array of pixels, each pixel with its color/opacity. It doesn't carry any information about the vector shapes that it's representing, only their pixel data.

Then comes blending. The raster result of the previous layers is combined with the current one according to the set blending method. Some layers (transforms, distortions, etc) just modify the raster result of the previous layers and pass that on to the next layer, instead of blending.

Note that a layer see all the layers underneath as a single combined raster. That layer cannot distinguish the pixel data that comes from the next layer that's underneath, from pixel data from any other layer that's underneath.

File:Synfig-engine.png

2009-02-13T13:58:45Z

Yoyobuae: Diagram of the internal organization of Synfig's valuenodes, layers, etc.

Diagram of the internal organization of Synfig's valuenodes, layers, etc.

Dev:Wish list

2009-02-13T05:59:57Z

Yoyobuae: Adding vector object concept.

'''''Warning''''': We need more people working on the code if we are going to be able to achieve all the feature requests.

Got a great idea for a new feature? Just add it here, or on the [http://sourceforge.net/tracker/?group_id=144022&atid=757419 feature requests tracker]. Before you do, please check the [https://synfig.svn.sourceforge.net/svnroot/synfig/ETL/trunk/TODO etl], [https://synfig.svn.sourceforge.net/svnroot/synfig/synfig-core/trunk/TODO synfig] and [https://synfig.svn.sourceforge.net/svnroot/synfig/synfig-studio/trunk/TODO synfigstudio] TODO files for similar ideas. Please add a rating of how essential this feature is to your workflow according to the following scale:

#"Well, it might be nifty. To someone."
#"I probably would make use this"
#"It's not essential, but I'd really like to have this at my disposal."
#"Synfig would be soooo much better with this change"
#"I can't/won't use Synfig without it!"

== Misc ==

Please clean this section up as desired.

* A different color dialog for picking/changing colors easier.
** A color wheel like inkscape has (or the same) [done]
** Swatch menu from gimp with .gpl files.
* Workflow improvements, like content help and ui-refinement.
** set the fine line between design and animation work.
** Greet the user at startup, give hints and help in the ui to better the usability and user-experience.
* test synfig cross-platform (Linux, Windows, Mac)
* Installer for windows [done]
* Pluggable App (run from memory stick)
* make a short film about synfigs capabilitys in a starwars kind of spaceship setting as promo video about 3 minutes long.
* Sound layer
* full tablet support
* small set of vector contend for fast animation results
* Help is available as pdf-file and distributed with the program

'''Input:'''
* Import rastergraphics png, jpg, tif [done]
* Import vectorgraphics (svg,fig)

'''Output:'''
* Render output to animated gif [done]
* Render output to png, bmp, OpenEXR [done]
* Export vectorgraphics (svg,fig)

== Interchangeable/customizing Splash screen ==
[3] GIMP has this feature of letting users [http://docs.gimp.org/2.2/en/using-customize-splashscreen.html|customize GIMP's splash screen]. GIMP looks for <code>'''samples'''</code> directory under <code>'''.gimp-2.x'''</code> then randomly picks a picture from it to become the spash image.

This will also help GNU/Linux distro, like Ubuntu, to adopt Synfig and put their logo on the splash screen.

Also, official Synfig distribution can pack sample arts created by other artists to be randomly displayed -- like the synfig.org's title's background image.

== Verbosity levels for error output ==

Synfigstudio needs verbosity levels for the error output. Levels are info, warning and error. Make sure, to spew out only errors when something nasty happens. If someone wants to know all what happens in synfigstudio, the user should activate a higher level of verbosity with the command line switch --verbose=all,info,warning

== Usage screen for new users ==

Synfig and Synfigstudio need a usage screen, which helps a new user to type in the right syntax on the command line. Any switch not known to the program should point to the usage screen. On the bottom of the usage screen could be a hint: " For more help use synfig --help"

== Keyboard shortcuts for panning ==

The navigation and canvas windows need shortcut keys that pan the canvas view horizontally and vertically. Probably just the arrow keys would work for this, as well as the home/end/pageup/pagedown keys. Ctrl and shift variants could make the panning more or less.
: You can pan with a middle mouse button. --[[User:Zelgadis|Zelgadis]] 00:59, 24 October 2008 (EDT)

== Linking Zoom layer to Paste Canvas ==

[3] It is impossible to link Center of Zoom layer to Origin of Paste Canvas without exporting a value. It often needed for pans & zooms. Suggestion: rename "Center" parameter of Zoom Layer to the "Origin". Will improve the workflow. --[[User:Zelgadis|Zelgadis]]

== Convert Strings ==
[4] It could be very good to have feature to represent Convert sequences as strings and vice versa - make convert sequences from strings. Example: To produce this convert sequence:

[[Image:WishList-ConvertStrings.png]]

I just right-click on "Origin" parameter and choosing "String Convert" menu item. In the appeared dialog I just entering: "=Composite(Scale(x, Switch(scalar, 1.0, 0)), y)".

Also if I clicking on the parameter already containing convert sequence and choosing "String Convert", it shows string representation of current convert sequence with an ability to edit.

This feature will make possible to easy copy convert sequences from one parameter to another. --[[User:Zelgadis|Zelgadis]] 03:46, 2 November 2008 (EST)

== Non scalable timeline ==
[3] It should be useful for me to have non scalable timeline. It's hard to set timing when the distance between frames is always different in different documents and in different situations. Suggestion: make a non-scalable mode for timeline, where 1 second interval is always the same. Will improve the workflow. --[[User:Zelgadis|Zelgadis]]

==Smart linking of tangents==
[4] As described in [[Sewing BLines]], when linking red tangent to yellow they are placed opposite against each other. This is normal from the program's point of view, but not normal for new users. Even more, to avoid this effect user needs to made some complex steps (see [[Sewing BLines#Solution]]). It takes a lot of time if we vahe lot of verticles to sew their tangents.

Suggestion:
* When linking tangents with the same color, program should act as usual.
* When linking tangents with different color program should automaticaly add Convert->Scale (-1) to avoid their opposite placement.
To allow linking two tangents in opposite position, I suggest to add a new menu option for tangents "Link Opposite". When linking two tangents with this option:
* When linking tangents with the different color, program should act as it acts now - no additional converts added.
* When linking tangents with the same color program should automaticaly add Convert->Scale (-1) to plcae them opposite against each other.

--[[User:Zelgadis|Zelgadis]]

==Movement blur effect==
To make the motion most realistic for movies, it should be possible to activate in the render dialog the option to smear the border of all objects, which move faster than a given value. For example, if a ball gets shot over the canvas/rendering-screen with speed over 50 px/frame it should have a blurry streak attached. This effect could be applied only at rendering time as an after-effect. --[[User:SvH|SvH]] 09:50, 28 May 2008 (EDT)

:There is a [[Motion Blur Layer]] that you can apply to the entire document or to the layers you want. It allows to turn the blur effect on and off during animation. I think it is more flexible that your proposal. [[User:Genete|Genete]] 10:13, 28 May 2008 (EDT)

==Morph sets==
This feature is similar to some other suggestions below, just with another way to approach. In animations are many movements, which can be put in some kind of library, to make use of at a later time. For example, movements to animate the key moments of a mouth, sampling syllables. For vector graphics, it should be possible to define some key points, which move just a small amount of space, to form another syllable. These syllables in this example, should be stored in a drop down list, to be able to select them for the key time on the timeline.
A morph-set for walking-left-to-right is different from a morph-set for a mounth, which has as options a,e,i,o,u,bah-disgust,happy-smile. The morph-set has to be stored as vector coordinates in a relative way(offset), e.g. X1=+212,+34;X2=-56,-23;X3=+3,-88;

To make use of the morph-set for the mouth, you have to define first, which vector points in your drawn mouth, correspond to the key-points of your morph-set. X1, X2, X3, Xn

--[[User:SvH|SvH]] 06:53, 27 May 2008 (EDT)

==Render time approximation==
Synfigstudio should get a button in the render dialog, which calculates the total render time for the actual settings (frames per second, length of the film, resolution, output format) It should testrender 1 picture, when the amount of total frames is below 1000. Over 1000 frames, it should testrender 10 pictures for more precise calculation.

--[[User:SvH|SvH]] 12:49, 22 May 2008 (EDT)

==Smartrendering==
I have made 25,000 small png-pictures with my 800Mhz computer in about 45 minutes. Synfigstudio did calculate each single frame of it. Nothing changed in this picture, so it does only need to get written to disk for the amount of pictures, until the next change (animation) has an effect on the output picture. This should save time for bigger projects with thousands of pictures. With smartrendering it is also possible to predict the total amound of space in Megabytes (Mibibytes) of the final render of the movie. It should calculate how much it needs and see, if enough space is free on the harddisk before the rendering get started.

--[[User:SvH|SvH]] 12:49, 22 May 2008 (EDT)

== get_color method in text and radial blur ==

[5] Without get_color method distorion produces artifacts
[http://sourceforge.net/tracker/index.php?func=detail&aid=1831355&group_id=144022&atid=757416 bug 1831355]. So I would like to get this problem fixed before doing something else. --[[User:AkhIL|AkhIL]] 22:41, 1 May 2008 (EDT)

== Full functional of group dialog ==

[5] Group dialog is broken now [http://sourceforge.net/tracker/index.php?func=detail&aid=1796833&group_id=144022&atid=757416 bug 1796833]. So we should get old features work right before making new one. --[[User:AkhIL|AkhIL]] 22:41, 1 May 2008 (EDT)

== import/export .swf files ==

very important productivity feature

== import/export .svg frames sequence, and/or .svg animations ==

very important productivity feature

== a realtime .sif synchronized text window ==

just like the xml editor of Inkscape, or the html editor in Dreamweaver (this is hugelly useful for productivity)

I thinks scripting API can be implement in this way. For example you make XML DOM like implementation for python which alows to change DOM tree from python code and see chenges in canvas. By this way you can implement import/export scripts. Automation scripts. And a lot of different things. Even synchronization of animation between blender and synfig. --[[User:AkhIL|AkhIL]] 23:10, 26 April 2008 (EDT)

== choosing colour from gimp/inkscape palettes ==

very useful when you need some colour comformity of what you're doing

== Good high-level documentation of the source code ==

(2) It'd be nice if a newbie could quickly navigate around the source code. The best thing to do would be to add top-level comments in each file, explaining what that file does, a README.TXT in each directory, explaining what's in that directory. This would be pretty fast and easy to do, and make it much easier for new programmers to join.

Time permitting, it would also be good to document on a high level what the data structures are, but that's harder, since those tend to evolve, and it is often difficult to keep in sync. It would also be useful to document what individual functions do (just a one-liner high-level description), but that also takes more time.
: There is a page link in the wiki that connect to the [http://www.synfig.com/doc Synfig API Documentation]. I think this link should be highlighted to be more accessible for newbies contributors and mature developers (the link was found [[Releases/DeveloperPreview#Support | here]]). --[[User:Genete|Genete]] 10:02, 11 December 2007 (EST)

== Mathematical functions to animate ==
(2/4) If you want to make a waving flag, it would be handful a sine function, tuned with random correctors, for example.
: -This should generate waypoints each 1, 2, 4 frames or any other step at artist's wish.
: -When applying a function you can add it to current values, add it to 1st frame values or simply override old values. Perhaps other options (such multiplication) would be fine, too. Something like texture editor in [http://www.artofillusion.org Art of Illusion], perhaps.
Perhaps it would be useful reusing the [http://www.gnu.org/software/octave/ Octave] source code to parse mathematical expressions.
I have rated this wish with a '2' because undoubtly many users will not be familiar to mathematical concepts, but for those who will be, I'd rate it with a 4. It would be possible to make a ball describing a parabolic moving in no time.
[[User:ajotatxe|ajotatxe]] 20 November 2007
: dooglus can probably chime in better than I here (see his example of balls on mathematical paths at http://uk.youtube.com/watch?v=YTpSfUthuVE ), but I believe that this is already possible. Synfig does support a variety of mathematical transforms for parameters, although the way you do this is by no means intuitive. (You might also want to check out the preambletaffy.sifz example for an easier approach to a waving flag. I know you were just using that as an example, but for the record...) [[User:Pxegeek|Pxegeek]] 00:58, 21 November 2007 (EST)

: I'd also rate it with a (4) (and updated the rating accordingly), not for this special case, but to make many workarounds much easier. Simulating [Parabolic Shot|free fall], for example, would be a lot easier with real formulas. I don't know, though how easy it will be to implement, maybe waiting for a scripting interface to be implemented is better than hacking this feature in an ad-hoc manner. --[[User:Rubikcube|Rubikcube]] 16:38, 29 February 2008 (EST)

== Warning about editing bizarre things in animate editing mode ==
(3.5) It seems to have little sense animate certain things like Blend Method or Type of Feather. It would be very nice that the program asked comfirmation if you change these attributes in animate editing mode. If you do want to, you would have three options: "Yes, never ask", "Yes, never ask for this attribute", "No". I guess that internally, this attributes has integer type (or something like that) and the attributes that you normally want to animate, float type, so I think that this feature is relatively easy to implement. My English is not very good, so please feel free to fix this post.
[[User:ajotatxe|ajotatxe]] 20 November 2007

== Bones with FK & IK + grouping of objects into folders ==

(5) Bones cane move specific vector assigned to them or the bones can have envelopes that move the vectors within their field of influence, much Like Anime Studio/Moho does. It's quite a time saving process of animating. Objects created can be saved into separate groups or folders using the same system as Anime Studio/Moho -Shadowphoenix 27/8/2007

== Animated sketch ==

(5) it would be great, if the tool Sketch was animatable (for example, in a form of a special sketch-layer). --Zelgadis 2007-06-14

: For now as a workaround we could use animation program called Pencil. See [[Related Projects]] page. --[[User:Zelgadis|Zelgadis]]

: So, currently it could be achieved by using other software, but integration with synfig is poor, cause it requires importing a movie through a sequence of images. This is not intuitive and not obvious for new users. It will be good if synfig will have it implemented like [url=http://www.blender.org/development/release-logs/blender-248/grease-pencil/]blender's Grease Pencil[/url]. This feature will improve workflow, make synfig usable for frame-by frame animation (it is intuitive way of learning animation and powerful tool for producing preproduction work like animatic). --[[User:Zelgadis|Zelgadis]]

: It would be nice to also implement the onion peel feature, where you can see the frame before or after, and/or selectable keyframes if this is included. An example can be seen in the program Pencil--[[User:richardwad1|richardwad1]]

== Duck for Amount value in Zoom layer ==

(2) It would be nice if Amount value in Zoom layer was controlled by additional duck. --[[User:Zelgadis|Zelgadis]] 02:49, 29 December 2007 (EST)
: I found that I can better use Warp layer instead of Zoom to change size. But it'd be nice to have Amount duck for Zoom layer anyway...
:: The Amount parameter works exponentially; each time you add 1 to the Amount, the image is zoomed by a further factor of e (= 2.71828 or so). Would a duck be any use if it just controlled the value of Amount in a linear way?
:: Workarounds include: export Amount, select it in the children dialog. Whatever's selected in the children dialog shows a duck. You can adjust it using that duck.
:: Also, if you use a Stretch layer, convert the Amount to Composite, export the X-Axis and connect it to the Y-Axis, then you have a duck-controllable fixed-aspect zoom. -- [[User:Dooglus|dooglus]] 15:32, 15 January 2008 (EST)
::: Yeah I found this workaround, but it's to much actions - i prefer better use Warp or Stretch layers. Why not the link Amount duck and Amount value with logarithmic function? ;) --[[User:Zelgadis|Zelgadis]] 10:33, 17 January 2008 (EST)
::::[[Convert#Logarithm|Logarithm]] convert type for real parameters exists since svn 2034. [[User:Genete|Genete]] 10:17, 30 August 2008 (EDT)

== Automatic colour palette optimisation ==

(0) it would be nice to use libcontrast [http://david.navi.cx/blog/?p=132] [http://david.navi.cx/blog/?p=94] [http://david.navi.cx/blog/?p=99] [http://svn.gnome.org/svn/xchat-gnome/trunk/src/libcontrast/] to automatically adjust selected or all the palette items for best visual contrast. It would also be interesting to have a layer that uses this code to filter the image.

== Arbitrary Color Channels ==

— The ability for the user to create any number of custom channels for various purposes.

== Autorecover History ==

— It would be great if autorecover could also recover the associated history of a file in the event of a crash.

== Layer Convert ==

<strike>(4)</strike> (2) — The original intent of this feature request has been solved and documented - [[How_do_I#Fill_an_outline.3F|How do I....Fill an Outline?]] - but it would still be nice to have a way to convert one sort of path layer to another. ''(Downgraded to level 2) [[User:SnapSilverlight|Snap]] 12:32, 17 Jan 2006 (PST)''

== Vector fill bucket ==

(3) — Like the traditional bitmap fill, but this fills the area clicked out to the nearest boundary paths with a region of that area, set to the foreground color (it actually would create a new [[Region Layer|region layer]]). <p>Alternatively, a single-duck layer object, that performs a simple bitmap fill from its (animatable) location, with its stored color value. (This second approach is similar to the behavior of one of Softimage's TOONZ[http://www.google.com/search?q=softimage+TOONZ]'s tools)</p><p>If this is implemented, it will probably be necessary to change the existing "fill" tool's name and icon to a "color injector" (hypodermic needle / turkey injector icon) tool, as that's closer to describing what it does.

*Inkscape has a very innvative version of this tool. Maybe you can just grab the code from there and integrate it in synfig? --[[User:SvH|SvH]] 01:37, 14 May 2008 (EDT)

== [[redraw tool]] ==

(4-5) — Intutive reshaping of path-based layers. See link.

== [http://developer.gnome.org/projects/gup/hig/ Gnome HIG Compliance] ==

— This should solve all complaints about the layout, without requiring Synfig to be "just like program (x)". See [[UI Reloaded]] for progress on this.

== Feedback for [[Smooth Move Tool]] ==

(3) — This tool does what a lot of folks are looking for, warping selected ducks in a "soft" fashion. But it's not very obvious what sort of effect it will have, from the tool's interface. It needs some sort of momentary center-of-action and radius indicator at the very least. Perhaps an "influence gradient" overlaid on the canvas once Synfig's core is sped up?

== Networkability ==

(2) — Like Inkscape's "inkboard" feature (using Jabber), or Blender's Verse server [http://www.blender.org/modules/verse/index.php], or OpenCanvas's Networking option. This should probably farm off all the networking stuff to the telepathy framework so that synfig doesn't have to deal with all the account/etc issues.

== Intuitive tangent modification ==

(3) — (BBQ Pulled Duck) Inkscape has this for still handles - basically, grab a section of the spline between handles, and pull it around, the program automatically alters the tangent handles to match. What would be really neat is if you could do the same for temporal handles - be able to grab the spline between keyframes, and yank it around, and have Synfig automatically adjust the key interpolation to match. Not sure exactly what the workflow in the UI would be for this, however.

-Agreed; blender does this with its IPO curves, and it's a really efficient way to work.

== Plugin API ==

(1) — Would be nice to enable additional functionality to be added to the program without it necessarily needing to be in the Synfig source tree. ''According to the Synfig 0.61.01 roadmap on [http://deepdarc.com/ deepdarc.com], there is a plugin API already implemented. So instead, this may be a [[Wiki Wish List|Wiki Wish]] for documentation, depending on how much has already been completed. [[User:SnapSilverlight|Snap]] 19:57, 13 Jan 2006 (PST)

== Python support ==

(1) of some sort will no doubt be demanded by the userbase eventually, for studio-specific automation of tasks, noncompiled plugins, etc. I ([[User:Snap|SnapSilverlight]]) don't have any particular use for it at the moment, tho'.

I suppose to join this request with [[Wish_list#a_realtime_.sif_synchronized_text_window]]. We can implement python access to XML DOM and write XML Editor in python. --[[User:AkhIL|AkhIL]] 06:54, 30 April 2008 (EDT)

== mod_synfig ==

(1) — For Apache. Render .sif to some format like png/mng on access.

== synfig nsplugin ==

(1) — Let Mozilla and Mozilla-based view synfig files in-browser.

== Align function ==

(3) — Align objects at a common border (as in Inkscape)

== Improved SVG import ==

(4) — Currently, all importing an SVG does is render it in ImageMagick. What I want is the ability to import the SVG document so that all the shapes, etc. of the SVG document show up as their equivilant synfig layers - i.e. if I had put them there myself. I'm trying to write a patch for this but the codebase is mostly undocumented. [[User:KMeist|KMeist]] 16:38, 25 Feb 2006 (PST)

[[svg2synfig]] could be incorporated using an open source XSLT processor. --[[User:Dmd|Dmd]] 13:34, 26 January 2008 (EST)

== Gradient Paint Tool ==

How about a tool that can 'paint' a gradient object. For example the options would be width and gradient type, one would make a stroke with the tool and the gradient would be automatically applied inside of the outline (set by width). This would save the trouble of having to the all the encapsulation stuff. (Actually any tool that makes creating gradient one step would be good).--[[User:Triclops|Triclops]] 09:52, 9 Aug 2006 (PDT)

== Bone Animation Tools ==

Bone system with inverse kinematics, very important for quick animation. You put bones on a drawed man and you can animate him like a puppet. I'm using that in Moho (lost marble product).--[[User:Ziolive|ziolive]] 23 Aug 2006
*I would find this very useful too. I think it is called '''rigging'''(4/5) --[[User:SvH|SvH]] 01:33, 14 May 2008 (EDT)

== AVI Backgrounds ==
Is there any way I can add an avi as a background so I could add facial expressions to a stop-motion animated figure. [zotz here, I was thinking DV background or extra timeline. I would like to mix animations with live footage. rating (3/4)]
: Already implemented for ffmpeg pipeline of ppm in svn r2161 [[User:Genete|Genete]] 05:36, 9 November 2008 (EST)

== Character tool on Tool Options Dialog ==

I want to use the as a character generator for a TV show. By using chroma key hide the background. Even better interface to a video overlay card with Alpha blending.

== Collect for Publication ==

(3/4) - (zotz) Menu item, functionality that would collect alll files referenced in a sif and place them all in a tgz for sending elsewhere or publishing animations in source form.

== Object Library ==

(3/4) - (zotz) Haven't thought this all through yet, but synfig could come with a library of categotrised "objects" with a copyleft license (GPL? CC BY-SA?) An animation clip art type deal.
:I'd suggest this should be public domain and distributed by openclipart.org -- --[[User:PaulWise|pabs]]

== Flash Export ==

(3/4) Well, might just be me but if there was a posiblity to export in .swf or .fla, I think the project might become a lot more popular.[[User:Conceit|Conceit]]

(4/5) I wholeheartedly agree. I would definitely use synfig more if this feature were added and it would most definitely increase popularity. [[User:cdj05a|cdj05a]]

(4[me]/5[others]) Definitely would love flash export. There is no well maintained Flash animation studio that is Open Source. To have Synfig become that along with all that it already is would be absolutely wonderful. You'd also possibly add to your user base all the flash animators out there that don't want to pay Adobe. Some people would only want it for the flash animation hence the 5 for others. [[User:jblandrum|jblandrum]]

== Single window ==

Depending on individual desktop setups, single window is sometimes preferable to many windows. Can we have a single-window option?

Also, even with many windows, Windows-users especially might find it better if all the windows only appeared as a single one on the taskbar.

== Export Wizard ==

(2/4) Conversion and export to other file formats (mpg, avi, flash formats, others, and the synfig format) with a step by step wizard for choosing format and place of saving. Similar to Gimp's saving of .png files but for movie/video type files. --
[[User:Hiddenghost|hiddenghost]]

== Using Synfig as a portable app ==

(3) This isn't really a feature request (though it could be) but I was wondering if synfig could be used as a portable application (as in www.portableapps.com). Does the windows install require registry access? i really want to use Synfig at work, but I'm reluctant to install it just in case it leave footprints in the regisitry or something, and it would be sweet to use it on my travels as well. Only thing is, I can't test it out at home because I am using Linux.
See also: http://portableapps.com/node/5761
[[User:Zenoscope|zenoscope]]

This isn't currently possible without modifying the source code. That has been on my TODO list for ages [[User:PaulWise|pabs]] 01:17, 26 October 2007 (EDT)

== Allow organize child valuenodes in an hierarchy ==
(3-2) And allow maintain the organization once the file is saved. At the moment they are reordered in alphabetical order which is useless and annoying.

== Triangle sliders to be always visible ==
(3) I would like that the triangle sliders from [[Colors Dialog]] and [[Gradient Editor Dialog]] were visible whatever color or channel you're editing. Some times when the color or channel is to bright or light the slider is difficult to distinguish. --[[User:Genete|Genete]] 14:30, 29 October 2007 (EDT)

== XICC support ==

It would be cool if synfigstudio had support for [http://burtonini.com/blog/computers/xicc XICC].

== Area to Edit ==

An option like blender - select area to update would be nice, so the only part of the image that updates when you add or change something is in the selected area

ie. when working on a complex composition, studio doesn't know, when I tweak a tiny part of the composition, that only that part needs redrawing, so it redraws the whole thing. It would be good if there was some way of telling it which part to focus on. -- [[User:Dooglus|dooglus]] 04:02, 3 February 2008 (EST)

== Histograms ==

01:23 * AkhIL wish to have histograms and luma/color scope like [http://mac.softpedia.com/progScreenshots/Avid-Xpress-DV-Screenshot-14207.html] in synfig

I've looked at those pictures but don't know what they're showing. Can you describe what those scopes are doing, and what the histograms display? ie. what are the X and Y axes of the histograms? -- [[User:Dooglus|dooglus]] 04:07, 3 February 2008 (EST)

First look this description in blender wiki [http://wiki.blender.org/index.php/Manual/VSE_Modes]

Ok There is four things.
* Upper left is Lumascope (Luma Waveform in blender). X-Axis represents image's X-Axys. Y-Axis is average luminescence of column of pixels.
* Upper right is Chromascope (Chroma Vectorscope in blender). Just look description on blender wiki.
* Lower left is like Lumascope but for each channel
* Lower right is histograms. X is luminescence and Y is count of pixels with such luminiscence.

== Sound Layer ==

(4) It would be a very good improvement if the sound system were implemented into synfig in [[Sound Layer | this]] way. --[[User:Genete|Genete]] 07:46, 8 February 2008 (EST)

== Rearrange the view of waypoints for Canvas param ==
As reported in [http://sourceforge.net/tracker/index.php?func=detail&aid=1888858&group_id=144022&atid=757416 Bug #1888858] waypoints are not displayed for canvas switch events.
I suggest to rearrange waypoints display according to [[Media:Canvas_prop.png|this scheme]].

== Width weigths ==
Is it possible to add "weigths" for widths? ^_^ I.e. width changes not all the way along the segment. Maybe something like a duck on bline which indicates the region where the width of current vertex isn't changed.
[[Media:width-proposal.png|Illustration here.]]

More ideas around this concept in [http://dooglus.rincevent.net/synfig/logs/2008/%23synfig-2008-04-16.log this conversation]. Although the log of that day is very interesting the lines related to this idea are from 22:38 to 23:43. [[User:Genete|Genete]] 17:51, 16 April 2008 (EDT)

== Improved Colour Dialog ==
How easy is it to stick in a colour square/wheel? Messing with sliders is somewhat obstructive.

== Insert Waypoints ==
A button to create a waypoint for every selected duck, in its current position. Moving each duck up a bit and down again quickly gets tedious.
:If the duck in question has already a waypoint then you don't need to move it to create a new waypoint. Just select the corresponding parameter in your child list panel and select 'Add Waypoint' from the right click context menu over the parameter. No need to have the duck selected. If you want to freeze the entire bline just do that over the Bline Point List. [[User:Genete|Genete]] 07:48, 29 April 2008 (EDT)
::Yes, but it would be nice to have opportunity to add waypoint to parameer which not have any ducks yet (i.e. non-animated parameter). --[[User:Zelgadis|Zelgadis]] 08:33, 29 April 2008 (EDT)

== Automatically split tangeants ==

Holding shift while moving tangeant ducks should automatically split them. They can be rejoined if necessary through the context menu as they are now.

== A way to link params without exporting ==
I need a way to link params with different names without exporting. It is possible to achive by manualy editing of sif file. But inposible by gui. I will be nice to have linking by drag-n-drop. Or just by selecting reference param, pushing copy button, selecting another param and bushing link button. ---[[User:AkhIL|AkhIL]] 21:47, 30 May 2008 (EDT)

== Allow select the origin of rotation when using the Rotate Tool ==

It can be initially set to the geometrical center of the selected ducks or the gravity center depending of the selected checkboxes in the tool options panel. Later the user could move it before perform the rotation operation. It is a waste of time to rotate and translate the ducks every time a rotation manipulation is done. ---[[User:Genete|Genete]] 12:16, 4 June 2008 (EDT)

:I was adding this request at the same time than you Genete :-). Here is an example of how this issue is solved in Inkscape:

:[[Image:rotate-tool-inkscape.png|center]]

:---[[User:Yaco|Yaco]]

== Labels for rows in the Timetrack window [1]==
The rows in the timetrack palette and the parameters palette are obviously related, doing a scroll in the Timetrack window with the mouse makes the parameters window scroll.

It's be nice to have the rows labeled with the corresponding label from the parameters palette, and to have the "list" parameter at the top of the time track window, with the possibility of dragging them around to move them up or down, personally I would prefer the "list" to be up the top so I can see the keyframes I'm making.

[[Image:Stencil 3.jpg|center]]

:---[[User:zenoscope|zenoscope]]

:Is this what you want? Just arrange the dock able dialogs as you need. [[User:Genete|Genete]] 10:03, 30 July 2008 (EDT)

:[[Image:Params-TimeTrack.png]]

yeah, that works. Cheers :) :---[[User:zenoscope|zenoscope]]

== Non-symetrical but "smooth" tangents on ducks ==
Add another mode for duck tangent, where the tangent can have different radius, but keep the same angle. (a "split tangents (radius only)" mode).

== Dockable windows ==
The current GUI is a pain in the rear by not complete covering the desktop and it's showing 5 tabs instead of usual one tab so it's frustrating to switch windows if you running more than one software. (windows version)

:--[[User:super animator|super animator]]

== Combining the installations files ==
This is the most common problem that the user will face when trying to running program for the first time since the user needs to install 4 files instead of one. This common problem needs to be fixed.

:--[[User:super animator|super animator]]

== A Particle Tool/Particle Object Editor ==
I thought it might be interesting to add a Particle tool that is intuitive. Genete's script is amazing and I am sure I will do a lot of things with it once I have a chance to sit down and figure it out, but if there were a way to make it into tool with all the settings on sliders, it would be much easier. His script adds endless possibilities of nice effects to make animations look better. I personally rate this rather high. 3.5/5

:--[[User:richardwad1|richardwad1]]

== A programation language as code behind like python, ruby or any ==
Code behind should be important to program the animation or events associated, programers and designers could work in a colaborative workspace and make applications with richfull content on desktop applicactions or web applications like expression blend or macromedia flash CS.

:--[[User:nickholai|nickholai]]

== Embedding animation on web applications ==
Like Macromedia Flash, it seems to require a plug in for internet explorer or firefox diferent as silverlight or flash, open source and "software libre" projects are working on animation but using the flash plug in, this wish needs a free plug in.

:--[[User:nickholai|nickholai]]

This seems a bit confusing; why do you want a plug in for synfig? When we add the import and export swf. file feature, it will use the flash plug in. Besides the flash player program is free, so you don't have to pay anything. I find that this feature is useless until you explain to us better why you think this software needs a plug-in.

Create a thread in the synfig forum if you want to continue to talk about this. We're listening.
:--[[User:super animator|super animator]]

== Split Tangent indicator ==

Its hard to tell if a tangent is split or not without clicking on it (either to use the context menu, or move a duck). All of the ducks should change to another shape (eg a square) for a quick visual indication of a ducks state.

:---[[User:zenoscope|zenoscope]]

== Guide lines ==

Guide lines that can be dragged from the side (like in the Gimp) would be very
useful.
:---[[User:zenoscope|zenoscope]]

== Progress indicators ==

Eg % complete in opening file, pop-up window which indicates how many frames are rendered of a render, eg "rendering 10 of 999" that can be closed/ignored if needed.
:---[[User:zenoscope|zenoscope]]

== Improve the Timeline ==

I know, this is one hell of a wish, but, as in all, i think that is best if you think in the ideals conditions and then you downgrade into what is possible to achieve in a reasonable period of time.

:D greetings!!

[4] Normal mode // [4] Layer mode // [4] Secuence mode

.I think that this modes are three diferent windows layout, therefore the hability to create new and save different windows layout, should be the first to do in order to achieve this three modes.

(click to enlarge)

02/01/2009 [[User:Belifilmaker|Belifilmaker]]
[[Image:Timeline-normal-mode-explained.jpg|left|thumb|800px]]
[[Image:Timeline-layer-mode-explained.jpg|left|thumb|800px]]
[[Image:Timeline-secuence-mode-explained.jpg|left|thumb|800px]]

== Lockable Layers ==
I would use them all of the time.
[[User:Zenoscope|Zenoscope]]

== Vector Objects ==
Represent objects (ie. circles, rectangles, regions, outlines, etc) as a new type of element. These objects exist as childs of some layer. The layer then takes care of rendering these objects to a raster. Currently layers do both things, represent objects and render them.

Having objects as a seperate entity would allow defining operations between them. For example:
* Take two region objects and find the union of their regions. This would produce a vector representation of the resulting region (ie. Bline) which in turn can be used for other operations (ie. link vertex to Bline).
* Apply transformation to a vector object producing a vector object as a result which can be further processed.
* Trace a [[Media:Smooth_silhoutte.png|smooth silhoutte]] around a set of vector objects.
* Slice an animated vector object into pieces and be able to move the pieces around (while preserving the original animation). Would be useful for reflection on a broken glass effect.

:---[[User:Yoyobuae|Yoyobuae]]

File:Smooth silhoutte.png

2009-02-13T05:16:24Z

Yoyobuae: Smooth silhoutte tracing.

Smooth silhoutte tracing.

File:Smooth silhoutte.sifz

2009-02-13T03:10:39Z

Yoyobuae: Tracing with a smooth curve the silhoutte of shapes

Tracing with a smooth curve the silhoutte of shapes

People

2008-04-08T01:53:40Z

Yoyobuae: Adding myself to the People page

<table>


<tr syle="border-bottom: 2px solid #ccc;">
<td style="text-align:center;">
[[Image:Diloxyn.png|72px]]
</td>
<td style="text-align:justify; border-left: 5px solid #eee">
<div style="font-size:120%; padding:4px; margin-bottom:10px; vertical-align:top; border-bottom:1px solid #ccc;"><b>[http://synfig.org/FAQ#Why_doesn.27t_dyloxin_talk_on_the_Synfig_IRC_channel.3F Dyloxin]</b></div>
dyloxin is a bot that sits in the [[Communication|Synfig IRC channel]] and stores the [[Communication|IRC logs]], not a human. It has no commands, so you won't get any response out of it either.
</td>
</tr>

<tr syle="border-bottom: 2px solid #ccc;">
<td style="text-align:center;">
[[Image:Dooglus2.jpg|72px]]
</td>
<td style="text-align:justify; border-left: 5px solid #eee">
<div style="font-size:120%; padding:4px; margin-bottom:10px; vertical-align:top; border-bottom:1px solid #ccc;"><b>[[User: dooglus | dooglus]]</b></div>
He's an alien, a legal alien, he's an Englishman in New York. Or Czechoslovakia. Or some such. Dooglus is the resident chief programmer and greatest contributer to Synfig since it's release to GPL (1500+ commits and going strong). He favours Linux as an OS, but has been known to run Windows on occasion.
</td>
</tr>

<tr syle="border-bottom: 2px solid #ccc;">
<td style="text-align:center;">
[[Image:Genete-2.png|72px]]
</td>
<td style="text-align:justify; border-left: 5px solid #eee">
<div style="font-size:120%; padding:4px; margin-bottom:10px; vertical-align:top; border-bottom:1px solid #ccc;"><b>[[User:Genete|Genete]]</b></div>
'''This is just an example, someone EDIT THIS!!'''. A great person, helps a lot with the project. Love fishing. Use to make sandwiches. Try not to cry.Try not to cry.Try not to cry.Try not to cry.Try not to cry.
</td>
</tr>

<tr syle="border-bottom: 2px solid #ccc;">
<td style="text-align:center;">
[[Image:Factor.gif|72px]]
</td>
<td style="text-align:justify; border-left: 5px solid #eee">
<div style="font-size:120%; padding:4px; margin-bottom:10px; vertical-align:top; border-bottom:1px solid #ccc;"><b>[[User:factor|Icarus Factor]]</b></div>
'''This is just an example, someone EDIT THIS!!'''. A great person, helps a lot with the project. Love fishing. Use to make sandwiches. Try not to cry.Try not to cry.Try not to cry.Try not to cry.Try not to cry.
</td>
</tr>

<tr syle="border-bottom: 2px solid #ccc;">
<td style="text-align:center;">
[[Image:KiBi.png|72px]]
</td>
<td style="text-align:justify; border-left: 5px solid #eee">
<div style="font-size:120%; padding:4px; margin-bottom:10px; vertical-align:top; border-bottom:1px solid #ccc;"><b>KiBi</b></div>
'''This is just an example, someone EDIT THIS!!'''. A great person, helps a lot with the project. Love fishing. Use to make sandwiches. Try not to cry.Try not to cry.Try not to cry.Try not to cry.Try not to cry.
</td>
</tr>

<tr syle="border-bottom: 2px solid #ccc;">
<td style="text-align:center;">
[[Image:Pabs3.png|72px]]
</td>
<td style="text-align:justify; border-left: 5px solid #eee">
<div style="font-size:120%; padding:4px; margin-bottom:10px; vertical-align:top; border-bottom:1px solid #ccc;"><b>[[User:PaulWise|pabs]]</b></div>
Helping out with synfig since it was GPLed. Sysadmin, occasional coder, wiki editor, not much of an artist.
</td>
</tr>

<tr syle="border-bottom: 2px solid #ccc;">
<td style="text-align:center;">
[[Image:Pixelgeek-2.png|72px]]
</td>
<td style="text-align:justify; border-left: 5px solid #eee">
<div style="font-size:120%; padding:4px; margin-bottom:10px; vertical-align:top; border-bottom:1px solid #ccc;"><b>[[User:pxegeek|Pixelgeek]]</b></div>
He's an alien, a legal alien, he's an Englishman in New York. Or Oregon. Or some such. Ask him questions about how Synfig works under Windows.
</td>
</tr>

<tr syle="border-bottom: 2px solid #ccc;">
<td style="text-align:center;">
[[Image:Avatar_rore.png|72px]]
</td>
<td style="text-align:justify; border-left: 5px solid #eee">
<div style="font-size:120%; padding:4px; margin-bottom:10px; vertical-align:top; border-bottom:1px solid #ccc;"><b>[[User:rore|Rore]]</b></div>
'''This is just an example, someone EDIT THIS!!'''. A great person, helps a lot with the project. Love fishing. Use to make sandwiches. Try not to cry.Try not to cry.Try not to cry.Try not to cry.Try not to cry.
</td>
</tr>

<tr syle="border-bottom: 2px solid #ccc;">
<td style="text-align:center;">
[[Image:Magnifiedulrik.png|72px]]
</td>
<td style="text-align:justify; border-left: 5px solid #eee">
<div style="font-size:120%; padding:4px; margin-bottom:10px; vertical-align:top; border-bottom:1px solid #ccc;"><b>[[User:Ulrik|Ulrikboden]]</b></div>
'''This is just an example, someone EDIT THIS!!'''. A great person, helps a lot with the project. Love fishing. Use to make sandwiches. Try not to cry.Try not to cry.Try not to cry.Try not to cry.Try not to cry.
</td>
</tr>

<tr syle="border-bottom: 2px solid #ccc;">
<td style="text-align:center;">
[[Image:Yaco.png|72px]]
</td>
<td style="text-align:justify; border-left: 5px solid #eee">
<div style="font-size:120%; padding:4px; margin-bottom:10px; vertical-align:top; border-bottom:1px solid #ccc;"><b>[[User:Yaco|Yaco]]</b></div>
'''This is just an example, someone EDIT THIS!!'''. A great person, helps a lot with the project. Love fishing. Use to make sandwiches. Try not to cry.Try not to cry.Try not to cry.Try not to cry.Try not to cry.
</td>
</tr>

<tr syle="border-bottom: 2px solid #ccc;">
<td style="text-align:center;">
[[Image:yoyobuae.png|72px]]
</td>
<td style="text-align:justify; border-left: 5px solid #eee">
<div style="font-size:120%; padding:4px; margin-bottom:10px; vertical-align:top; border-bottom:1px solid #ccc;"><b>[[User:Yoyobuae|Yoyobuae]]</b></div>
An occasional contributer with a couple of submitted patches here and there. Still learning to handle himself with the code, but willing to answer any questions to the best of his knowledge. Also a novice artist, mainly interested dragons, birds and furry art in general.
</td>
</tr>

<tr syle="border-bottom: 2px solid #ccc;">
<td style="text-align:center;">
[[Image:none.png|72px]]
</td>
<td style="text-align:justify; border-left: 5px solid #eee">
<div style="font-size:120%; padding:4px; margin-bottom:10px; vertical-align:top; border-bottom:1px solid #ccc;"><b>Your name here!</b></div>
'''You. Yes, you, my dear reader.''' If you contribute to the project, please join with us into making this possible. We do need your help.
</td>
</tr>
</table>

<div class="note">
Also semi-frequent visitors - [[User:Zelig|Zelig]],[[User:Atrus|Atrus]],[[User:Madsen|Madsen]], [[User:Bombe |Bombe]], TMM, Tokyo, Zipola, [[User:zotz|zotz]], [[User:Omry|Omry]], [[User:Riggzy|Riggzy]], Zelgadis, AkHil.
</div>

File:Yoyobuae.png

2008-04-08T01:52:08Z

Yoyobuae: my picture =)

my picture =)

Dev:New Animation Tools

2008-04-05T21:17:14Z

Yoyobuae: A new Wiki page for suggesting a new animation tool ideas

== Animation Tools on Synfig ==
It may sound a bit harsh, but for a "2d vector animation studio" Synfig Studio has far too few and far too simple animation tools. Only the first five (Normal, Smooth move, Scale, Rotate and Mirror) in the tool box can do some sort of animation.

IMHO this needs to change. So I started thinking about what new tools would be useful for animation.

== Motion Tool ==
The name says it all, a tool designed to easily add motion to any of Synfig's objects.

At the moment one of the first five tools is used to move things around in animation mode in order to create waypoints, and therefore defining the animation. While using Synfig I've notice a few things:

* Having to jump all around the timeline
* Guess estimating how fast/slow will the motion be
* Problems trying to simulate motions in specific patterns (ie. Circular)

Taking this into consideration the Motion Tool could work like this:

* Only set the time to the start of the motion, the tool inserts waypoints further down the timeline automatically
* Either type in the speed on the Tool Options panel, or have a graphical representation of it (ducks perhaps)
* Allow the motion to describe an arbitrary path, the tool calculates the right position, time and number of waypoints to insert
* Optionally, specify a certain pattern for the motion to follow (ie. Circular)

== Morph tool ==
A tool that can easily morph between two shapes (Blines).

The description makes it sound simple. But there are a few things to consider first:

* Does the vertexes on each shape correspond with vertexes on another?
* Where does the vertexes, which don't correspond, go to (in the other shape)?
* How do you make everything morph smoothly?

Luckily, the code knows exactly how to do it:

* The vertexes that do correspond in both shapes, are simply interpolated
* The ones that appear in one shape, but not in the other, have their Activepoint set to On in one shape and to Off in the other
* The Origin parameter in the Blinepoints tells which part of the other shape a vertex move towards, when there's no corresponding vertex on that shape
* Interpolation makes everything move smoothly

But the truth is that Activepoints are a rather obscure feature of Synfig. The Morph tool would make them easier to use:

* First set which shape you want to morph
* Select the start shape (from another Bline) and time
* Select the end shape and time
* Drag the points on the morphed shape around, changing which vertex or part they correspond to (in the corresponding shape)
* Vertexes are automatically interpolated or turned on/off accordingly

== Pose tool ==
Also a tool to animate shapes, but its objective is to create and apply poses to shapes.

There is a way to [[Reuse Animations]], but it would be better to have an easy (and faster) to use tool for the job.

This tool would be able to:

* Create poses from ready made shapes
* Apply these poses to other shapes, animating them
* Deal with mismatch of the number/position of vertexes

This tool bears many similarities with the morph tool, perhaps it might be possible to make an unified tool that does both jobs well.

== Math/Physics tool ==
It's entirely possible to create mathematically defined motions in Synfig (thanks to it's convert types). But it is also true that this features would be a bit to hard or time consuming to understand and use.

Perhaps this tool could be subdivided in a set of modes:
* Free falling mode: Objects falling/flying in presence of gravity
* Elastic deforming: Any sort of elastic object that deforms with force
* Hair simulation: 2d hair simulation of some sorts
etc...

Perhaps this tool won't be essential in order to animate, but a few simple but cool effects would certainly add a lot to an animation. Of course math/physics can get very complex rather fast. So perhaps only the simplest cases would be considered, specially if they in return produce a rather stunning effect.

== Animated Character tool ==
A tool that makes easier the animation of characters.

Probably would need to be a conjunction of tools, perhaps with a number of submodes:
* Bones: Used to rig and then to animate a character using bones technique
* Morph/Pose: Use the poses and transitions that other tools generate and combine them in order to form the entire character
* Walk: Make your character walk with his feet firm on the ground
* Talk: Use poses defining phonemes to have the character talk
* Face: Manage facial expressions (defined by poses), control the focus point of eyes, etc

== Make your own Suggestions ==

Feel free to add any other tool idea you have, or make comments on the ones already posted. The best would be to have a lot of tools ideas first, then we can see which tools are similar, and make a single unified tool that does many jobs.

I tried to make my tool suggestions practical, imagining what would a real animator working on a project would like from it. Tools that are easy and fast to use and that accomplish a certain goal. On the other hand, I have zero experience on real world animation work, so I was just making things up as go. Imagination is a powerful thing though =).

Latter on, I will also try to look into the implementation details, and post whatever I find here, or perhaps in a page specific to each tool. Then we can tweak the tool to fit what's possible to implement, or come up an idea on how to implement the tool. Hopefully this method will help to achieve a complete implementation, even if little by little.

The idea is to at least end up with a well defined tool, and a good starting point for a developer to start his work.

Talk:Link to BLine

2008-03-03T17:31:23Z

Yoyobuae: corrected typo

By a [http://dooglus.rincevent.net/synfig/logs/2008/%23synfig-2008-03-03.log discussion] at the IRC channel it has been requested to be possible to:

1) Provide easy way for user to attach a vertex of a bline to another bline but without the need of create a new vertex over that bline. That allow simplify the animation of complex compositions due to it needs less vertices.

See Yoyobuae example:

[[Image:sif_icon.png|16px]][http://members.lycos.co.uk/yoyobuae/bline_attached_2sections.sifz bline attached]

In that example there are some vertices converted to Bline vertex and some tangents converted to Bline tangents. Manipulating the exported parameter that represent the position of the vertex along the curve it is possible to easily modify the shape of the composition allowing a better morphing of the shapes created.

Currently it done through various export/connect manipulations.

'''Suggestion:''' It's desired that this attachment be achieve visually, by using the mouse and context menus. The current method requires the use of exported values and parameter linking, which is less intuitive and also is slower.

'''Possible realization way:'''
# Select the duck you want to link to bline. It could be
## bline vertex duck
## bline tangent duck
## or real duck
# Right click on the bline (not the bline vertex!)
# Link
## Linking creating appropriate convert sequences.
## if selected vertex duck, it placed on bline at position where clicked
## if selected tangent duck, it links with bline tangent at click position
### Which one of two? Maybe both? --[[User:Zelgadis|Zelgadis]] 12:27, 3 March 2008 (EST)
### We need to scale tangents as in example above
## if selected real duck, it links with bline width at click position
### currently width value at specific point of bline couldn't be easily retrieved via export/convert combinations --[[User:Zelgadis|Zelgadis]] 12:27, 3 March 2008 (EST)
# If was more than one duck selected for linking (i.e. bline vertex duck and bline tangent duck) then they Amount values (in "Bline Vertex"/"Bline Tangent" converts) must be linked to ensure that they retrieved from the same position on a bline (if changed).

2) Derived from that request it appears the need to be able to manipulate the ducks that have been converted to a composition. That is: inverse manipulation of valuenodes.
For the moment there are some convert types that allow inverse manipulation and only for certain parameters. For example tangents allow inverse manipulation (you modify the x/y position and it calculates the r,theta values. It is know that inverse manipulation leads on some inconsistencies. If the the function that convert a type into other is not biunivocal then it can produce undesired results form the point of view of the final user. For example, the Scale convert type would not have any inconsistency due to it has a easy computable reverse function (the reciprocal)

Considering that and taking account that inverse calculation of valuenodes based on ducks position could need some extra computation, it would be good if some convert types can have inverse manipulation.

'''The proposal is''' that BLine Vertex converted types allow inverse manipulation. So, manipulating a vertex duck you move the attached vertex along the bline and also match the tangent of the attached vertex to the bline's tangent at that position.

Talk:Link to BLine

2008-03-03T17:05:01Z

Yoyobuae: added some content

By a [http://dooglus.rincevent.net/synfig/logs/2008/%23synfig-2008-03-03.log discussion] at the IRC channel it has been requested to be possible to:

1) Attach a vertex of a bline to another bline but without the need of create a new vertex over that bline. That allow simplify the animation of complex compositions due to it needs less vertices.

See Yoyobuae example:

[[Image:sif_icon.png|16px]][http://members.lycos.co.uk/yoyobuae/bline_attached_2sections.sifz bline attached]

In that example there are some vertices converted to Bline vertex and some tangents converted to Bline tangents. Manipulating the exported parameter that represent the position of the vertex along the curve it is possible to easily modify the shape of the composition allowing a better morphing of the shapes created.

It's desired that this attachment be achieve visually, by using the mouse and context menus. The current method requires the use of exported values and parameter linking, which is less intuitive and also is slower.

2) Derived from that request it appears the need to be able to manipulate the ducks that have been converted to a composition. That is: inverse manipulation of valuenodes.
For the moment there are some convert types that allow inverse manipulation and only for certain parameters. For example tangents allow inverse manipulation (you modify the x/y position and it calculates the r,theta values. It is know that inverse manipulation leads on some inconsistencies. If the the function that convert a type into other is not biunivocal then it can produce undesired results form the point of view of the final user. For example, the Scale convert type would not have any inconsistency due to it has a easy computable reverse function (the reciprocal)

Considering that and taking account that inverse calculation of valuenodes based on ducks position could need some extra computation, it would be good if some convert types can have inverse manipulation.

The proposal is that BLine Vertex converted types allow inverse manipulation. So, manipulating a vertex duck you move the attached vertex along the bline and also match the tangent of the attached vertex to the bline's tangent at that position.

Talk:Link to BLine

2008-03-03T16:51:01Z

Yoyobuae: corrected typo

By a [http://dooglus.rincevent.net/synfig/logs/2008/%23synfig-2008-03-03.log discussion] at the IRC channel it has been requested to be possible to:

1) Attach a vertex of a bline to another bline but without the need of create a new vertex over that bline. That allow simplify the animation of complex compositions due to it needs less vertices.

See Yoyobuae example:

[[Image:sif_icon.png|16px]][http://members.lycos.co.uk/yoyobuae/bline_attached_2sections.sifz bline attached]

In that example there are some vertices converted to Bline vertex and some tangents converted to Bline tangents. Manipulating the exported parameter that represent the position of the vertex along the curve it is possible to easily modify the shape of the composition allowing a better morphing of the shapes created.

2) Derived from that request it appears the need to be able to manipulate the ducks that have been converted to a composition. That is: inverse manipulation of valuenodes.
For the moment there are some convert types that allow inverse manipulation and only for certain parameters. For example tangents allow inverse manipulation (you modify the x/y position and it calculates the r,theta values. It is know that inverse manipulation leads on some inconsistencies. If the the function that convert a type into other is not biunivocal then it can produce undesired results form the point of view of the final user. For example, the Scale convert type would not have any inconsistency due to it has a easy computable reverse function (the reciprocal)

Considering that and taking account that inverse calculation of valuenodes based on ducks position could need some extra computation, it would be good if some convert types can have inverse manipulation.

The proposal is that BLine Vertex converted types allow inverse manipulation. So, manipulating a vertex duck you move the attached vertex along the bline and also match the tangent of the attached vertex to the bline's tangent at that position.

Convert

2008-02-24T23:06:51Z

Yoyobuae: /* Compatibility */ Change to compatibility table format

Right-clicking on a value in the Parameters dialog brings up a context menu which has a sub-menu called "Convert". The "Convert" menu allows you to specify that the parameter should be controlled automatically in various ways. Depending on the type of the parameter the Convert menu will contain different options.

To convert the value back to its original type, select "Disconnect" from its context menu.

== Convert Types ==

=== Add ===

Converting a parameter to "Add" adds three sub-parameters, the first two of which are the same type as the parameter itself:
* <param> "LHS"
* <param> "RHS"
* real "Scalar"

The "Add" conversion can be used with parameters of type [[Convert#Angle|angle]], [[Convert#Color|color]], [[Convert#Gradient|gradient]], [[Convert#Integer|integer]], [[Convert#Real|real]], [[Convert#Time|time]], and [[Convert#Vector|vector]].

The resulting value is:
(LHS + RHS) * Scalar

=== aTan2 ===

Converting an [[Convert#Angle|angle]]-valued parameter to "aTan2" adds two sub-parameters:
* real "X"
* real "Y".

The resulting value is:
atan2(y,x)

ie. atan(y/x) but without an error when x is 0. The value is the angle between the x axis and the vector (x,y).

=== BLine ===

Converting a [[Convert#List|list]] parameter to "BLine" doesn't seem to change anything. Perhaps that's the default type for lists of vertices, such as are found in outlines and regions?

=== BLine Tangent ===

Converting a [[Convert#Angle|angle]] or [[Convert#Vector|vector]] parameter to "BLine Tangent" adds three sub-parameters:
* bline "BLine"
* bool "Loop"
* real "Amount"

Amount is a number between 0 and 1, defining the distance along the given bline. The resulting value for the whole parameter is the tangent to the bline, at the given point along the bline, either as an angle or as a vector, depending which type was converted.

This [[Following a BLine|tutorial]] gives an example of the use of this convert type.

=== BLine Vertex ===

Converting a [[Convert#Vector|vector]] parameter to "BLine Vertex" adds three sub-parameters:
* bline "BLine"
* bool "Loop"
* real "Amount"

Amount is a number between 0 and 1, defining the distance along the given bline. The resulting value for the whole parameter is a vector giving the position of the given point along the bline.

This [[Following a BLine|tutorial]] gives an example of the use of this convert type.

=== BLine Width ===

Converting a [[Convert#Real|real]] parameter to "BLine Width" adds three sub-parameters:
* bline "BLine"
* bool "Loop"
* real "Amount"

Amount is a number between 0 and 1, defining the distance along the given bline. The resulting value for the whole parameter is the width of the bline at the given point along it.

=== Composite ===

Converting a [[Convert#BLinePoint|blinepoint]] parameter to "Composite" adds six sub-parameters:
* vector "Vertex"
* real "Width"
* real "Origin"
* bool "Split Tangents"
* vector "Tangent 1"
* vector "Tangent 2"

Converting a [[Convert#Color|color]] parameter to "Composite" adds four real-valued sub-parameters:
* real "Red"
* real "Green"
* real "Blue"
* real "Alpha"

Converting a [[Convert#Segment|segment]] parameter to "Composite" adds four vertex sub-parameters:
* vertex "Vertex 1"
* vertex "Tangent 1"
* vertex "Vertex 2"
* vertex "Tangent 2"

Converting a [[Convert#Vector|vector]] parameter to "Composite" adds two real-valued sub-parameters:
* real "X-Axis"
* real "Y-Axis"

The resulting value is a blinepoint, color, segment, or vector made by combining the component parts.

=== Cos ===

Converting a [[Convert#Real|real]]-valued parameter to "Cos" adds two sub-parameters:
* angle "Angle"
* real "Amplitude".

The resulting value is:
Amplitude * cos(Angle)

=== Duplicate ===

This ValueNode type is only used by the [[Duplicate Layer]]. It never appears in the Convert menu. It is used to control the range of the Index in the Duplicate Layer (q.v.).

The "Duplicate" ValueNode type has 3 real-valued sub-parameters:

* real "From"
* real "To"
* real "Step"

The value of the ValueNode varies from the value of "From" to the value of "To" in steps of size "Step". The sign of "Step" is ignored. If From<To the steps are positive, else they're negative.

=== Dynamic List ===

Converting a [[Convert#List|list]] parameter to "Dynamic List" seems to replace each of the "Vertex NNN" sub-parameters with "Item NNN" parameters which can't be expanded, but can be exported.

=== Exponential ===

Converting a [[Convert#Real|real]] parameter to "Exponential" adds two sub-parameters:

* real "Exponent"
* real "Scale"

The resulting value is the result raising the [http://en.wikipedia.org/wiki/E_%28mathematical_constant%29 mathematical constant 'e'] to the power of Exponent, and scaling the result by Scale. That is, it returns:
Scale * e^Exponent

This is useful for tracking layers which have been zoomed, since the Zoom layer scales by e^(zoom factor).

See [http://youtube.com/watch?v=GAWtndOHkUw this video] for an example of the use of this convert type.

=== From Integer ===

This is currently disabled. It converts an integer to one of several types.

=== Gradient Rotate ===

Converting a [[Convert#Gradient|gradient]] parameter to "Gradient Rotate" adds two sub-parameters:

* gradient "Gradient"
* real "Offset"

The resulting value is a gradient based on the "Gradient" parameter, but shifted left (for negative values) or right, according to the value of the "Offset" parameter. An offset of 1.0 will shift the gradient by its entire visible width. Values shifted off the left or right edge aren't lost - they aren't visible in the gradient as it's displayed in the parameters dialog, but they will still be used when rendering (depending on parameters such as 'Loop' and 'Zigzag', which can cause gradients to be looped between their their left and right edges, rather than using the non-displayed parts).

=== Linear ===

Converting an [[Convert#Angle|angle]] parameter to be 'Linear' adds two angle sub-parameters:
* angle "Rate"
* angle "Offset"

Converting a [[Convert#Color|color]] parameter to be 'Linear' adds two angle sub-parameters (since svn r617):
* color "Rate"
* color "Offset"

Converting an [[Convert#Integer|integer]] parameter to be 'Linear' adds two angle sub-parameters (since svn r617):
* integer "Rate"
* integer "Offset"

Converting a [[Convert#Real|real]] parameter to be 'Linear' adds two real-valued sub-parameters:
* real "Rate"
* real "Offset"

Converting a [[Convert#Time|time]] parameter to be 'Linear' adds two time sub-parameters:
* time "Rate"
* time "Offset"

Converting a [[Convert#Vector|vector]] parameter to be 'Linear' adds two vector sub-parameters:
* vector "Slope"
* vector "Offset"

The parameter's value will change linearly over time, starting with the value specified by "Offset" at time zero, and increasing by the value specified by "Rate" (or "Slope", in the case of vector parameters) every second.

The resulting value for vector parameters is:
Offset + Slope*time

and for the other 5 types of parameter it is:
Offset + Rate*time

=== Radial Composite ===

Converting a [[Convert#Color|color]] to "Radial Composite" adds four sub-parameters:
* real "Luma"
* real "Saturation"
* angle "Hue"
* real "Alpha"

Converting a [[Convert#Vector|vector]] to "Radial Composite" adds two sub-parameters:
* real "Radius"
* angle "Theta"

For color parameters, the resulting value is the color with the given lima, saturation, hue, and alpha amounts.

For vector parameters, the resulting value is the point reached by traveling a distance "Radius" from the origin, in the distance given by the angle "Theta".

=== Random ===
'''(currently only in [[Source_code|subversion]])'''

Converting a parameter to "Random" adds five sub-parameters, the first of which is the same type as the converted parameter:

* <param> "Link"
* real "Radius"
* integer "Seed"
* real "Animation Speed"
* integer "Interpolation"

"Random" can be used on [[Convert#Angle|angles]], [[Convert#Color|colors]], [[Convert#Integer|integers]], [[Convert#Real|reals]], [[Convert#Time|times]], and [[Convert#Vector|vectors]].

It is used to cause a parameter's value to vary randomly over time, around a central value:

* "Link" provides the central value.
* "Radius" defines the maximum random difference.
* "Seed" seeds the random number generator
* "Animation Speed" defines how often a new random value is chosen (in choices per second)
* "Interpolation" determines how the value is interpolated from one random choice to the next. Possible values are:
** 0 - no interpolation; the value jumps from one value to the next
** 1 - linear interpolation
** 2 - cosine
** 3 - spline
** 4 - cubic (the default); uses [http://www.gamedev.net/reference/articles/article1497.asp Catmull-Rom] spline interpolation

The "Interpolation" sub-parameter should really be a drop-down menu, rather than an integer field, but that isn't yet implemented.

=== Range ===

Converting a parameter to "Range" adds three sub-parameters, all the same type as the parameter itself:
* <param> "Min"
* <param> "Max"
* <param> "Link"

"Range" can be used on [[Convert#Angle|angles]], [[Convert#Integer|integers]], [[Convert#Real|reals]], and [[Convert#Time|times]].

It is used to limit the value of the linked parameter to be between Min and Max.

The resulting value is:
Min (if Link < Min)
Max (if Link > Max)
Link (otherwise)

=== Reciprocal ===

Converting a [[Convert#Real|real]]-valued parameter to "Reciprocal" adds three sub-parameters:
* real "Link"
* real "Epsilon".
* real "Infinite".

The resulting value is:
1/Link (Link <= -epsilon or epsilon <= Link)
Infinite (if 0 <= Link < epsilon)
-Infinite (if -epsilon < Link < 0)

The epsilon and infinite parameters are only needed to prevent division by zero. For regular operation the resulting value is simply the reciprocal of Link.

=== Reference ===

Converting a parameter to "Reference" adds a single sub-parameter called "Link". The "Link" parameter is the same type as the parameter being converted.

It doesn't seem to do anything at all, other than adding an extra parameter. Whatever value is put into "Link" becomes the value of the parameter being converted.

The only use for this conversion type I can think of is the following:

* you know that point A should follow point B, so you export point B and connect point A to it
* you're not yet sure exactly how point B should move, so you experiment with different conversion types for point B
* changing the conversion type for point B breaks the connection you made in the first step
* converting point B to be a reference, and then experimenting with different conversions in its "Link" parameter allows point A to connect to point B and for the connection to remain in place while you experiment in the "Link" parameter

The resulting value is:
Link

=== Repeat Gradient ===

Converting a [[Convert#Gradient|gradient]] parameter to "Repeat Gradient" adds seven sub-parameters:
* gradient "Gradient"
* integer "Count"
* real "Width"
* bool "Specify Start"
* bool "Specify End"
* color "Start Color"
* color "End Color"

The resulting value is a gradient containing "Count" equally spaced, equally wide copies of gradient "Gradient". Each copy has "Gradient" going forwards and then backwards. "Width" specifies relative width of the forward copy, with a width of 0 or less meaning only the backward copy is used, and a width of 1 or more meaning only the forward copy is used. A value of 0.5 will result in the forward and reverse copies of "Gradient" being the same width.

If "Specify Start" is checked then "Start Color" will be inserted at the beginning of the new gradient, otherwise the beginning of "Gradient" will be used as the beginning of the new gradient.

If "Specify End" is checked then "End Color" will be appended to the end of the new gradient, otherwise the end of "Gradient" will be used as the end of the new gradient.

Here's an example of a repeated gradient - the radiating green/yellow lines are a repeated gradient, applied to a perpendicular curve gradient. This gradient was repeated with a width of 0.5, meaning it is used backwards and forwards the same amount:

[[Image:Repeat-gradient-valuenode-gradient.png]]

and here's the resulting image, along with the .sif file:

[[Image:Repeat-gradient-valuenode.png]]
[[Image:Repeat-gradient-valuenode.sif]]

=== Reverse Tangent ===

Converting a blinepoint parameter to "Reverse Tangent" adds two sub-parameters: one called "Reference" of type BLinePoint, and a boolean parameter called "Reverse".
* BLinePoint "Reference"
* bool "Reverse"

"Reverse Tangent" can only be used on [[Convert#BLinePoint|blinepoints]].

The resulting value is the same as the reference BLinePoint, but with its tangents switched over. This is useful when attempting to link the verticies of a region to the vertices of an outline when the region and the outline were drawn in opposite directions, and so tangent1 of an outline vertex needs to be linked to tangent2 of the region vertex, and vice versa.

=== Scale ===

Converting a parameter to "Scale" adds two sub-parameters: one called "Link", of the same type as the parameter itself, and a real-valued parameter called "Scalar".
* <param> "Link"
* real "Scalar"

"Scale" can be used on [[Convert#Angle|angles]], [[Convert#Color|colors]], [[Convert#Integer|integers]], [[Convert#Real|reals]], [[Convert#Time|times]], and [[Convert#Vector|vectors]].

The resulting value is:
Link * Scalar

=== Segment Tangent ===

Converting a [[Convert#Vector|vector]] parameter to "Segment Tangent" adds two sub-parameters:
* segment "Segment"
* real "Amount"

Amount is a number between 0 and 1, defining the distance along the given segment. The resulting value for the whole parameter is the tangent to the segment, at the given point along the segment.

=== Segment Vertex ===

Converting a [[Convert#Vector|vector]] parameter to "Segment Vertex" adds two sub-parameters:
* segment "Segment"
* real "Amount"

Amount is a number between 0 and 1, defining the distance along the given segment. The resulting value is the vertex at the given point along the segment.

=== Sine ===

Converting a [[Convert#Real|real]]-valued parameter to "Sine" adds two sub-parameters:
* angle "Angle"
* real "Amplitude".

The resulting value is:
Amplitude * sin(Angle)

=== Step ===

Converting an [[Convert#Angle|angle]], [[Convert#Color|color]], [[Convert#Integer|integer]], [[Convert#Real|real]], [[Convert#Time|time]], or [[Convert#Vector|vector]] parameter to be 'Step' adds four sub-parameters:
* <param> "Link"
* time "Duration"
* time "Start Time"
* real "Intersection"

The parameter's value will change in steps. Each step is "Duration" seconds long. The steps start at times "Start Time", "Start Time"+"Duration", etc. The value of the valuenode is the value of "Link" at some time. "Intersection" determines which time is used. An "Intersection" of 0.0 means that the value of "Link" at the start of the step should be used. An "Intersection" of 0.5 (the default) means to use the value of "Link" at the middle of the step, etc.

The resulting value at time <math>T</math> is:
<math>Link \Bigg ( \Bigg ( Duration \cdot \left ( \left \lfloor \frac{T - Start\ Time}{Duration} \right \rfloor + Intersection \right ) \Bigg ) + Start \ Time \Bigg )</math>

=== Example ===

"Link" is a sine wave. "Duration" is 10f (the frame rate is 24 fps). "Start Time" is 1s.

So one step starts at 1s, and others start at 0s 14f, 0s 4f, 1s 10f, etc.

This is the sine wave:

[[Image:Smooth-sine.png]]

And this is the effect of the Step valuenode on it, with an "Intersection" of 0.0. Notice that at time 0s, the step has a negative value -- that step runs from -6f to 4f, and so its value is the value of Link at time -6f. ''These images were created in [http://www.gimp.org/ The Gimp] - it's not currently possible to view two curves at the same time in Synfig Studio.''

[[Image:Stepped-sine-0.0.png]]

Here it is with an "Intersection" of 0.5:

[[Image:Stepped-sine-0.5.png]]

and here, with an "Intersection" of 1.0:

[[Image:Stepped-sine-1.0.png]]

=== Stripes ===

Converting a [[Convert#Gradient|gradient]] parameter to "Stripes" adds four sub-parameters:
* color "Color 1"
* color "Color 2"
* integer "Stripe Count"
* real "Width"

The resulting value is a gradient containing "Stripe Count" equally spaced, equally wide stripes of color "Color 2" with a background of "Color 1". "Width" specifies the width of the stripes, with a width of 0 or less meaning they are invisible, and a width of 1 or more meaning the whole gradient is of "Color 2".

=== Subtract ===

Converting a parameter to "Subtract" adds three sub-parameters, the first two of which are the same type as the parameter itself:
* <param> "LHS"
* <param> "RHS"
* real "Scalar"

The "Subtract" conversion can be used with parameters of type [[Convert#Angle|angle]], [[Convert#Color|color]], [[Convert#Gradient|gradient]], [[Convert#Integer|integer]], [[Convert#Real|real]], [[Convert#Time|time]], and [[Convert#Vector|vector]].

The resulting value is:
(LHS - RHS) * Scalar

=== Switch ===

Converting a parameter to "Switch" adds three sub-parameters:
* <param> "Link Off"
* <param> "Link On"
* bool "Switch"

"Link Off" and "Link On" are the same type as the parameter being converted.

The resulting value is the value of "Link Off" when "Switch" is off, and "Link On" when "Switch" is on.

This conversion can be used on all value types.

=== Time Loop ===

Converting a parameter to "Time Loop" adds four sub-parameters: one called "Link", of the same type as the parameter itself, and three time parameters:

* <param> "Link"
* time "Link Time"
* time "Local Time"
* time "Duration"

It works similarly to the [[Time Loop Layer]] but affects only a single parameter.

For any integer value n, from "Local Time + abs(Duration)*n" to "Local Time + abs(Duration)*(n+1)", the resulting value of the parameter is the same as that of the "Link" parameter from "Link Time" to "Link Time + Duration".

In other words, "Duration" seconds of values of the parameter "Link" starting from time "Link Time" onwards are looped over and over, with the value of the "Link"ed parameter at time "Link Time" corresponding to the resulting value at time "Local Time".

As an example, suppose the "Link" parameter has a value of time the current time. At 0s the value is 0, at 10s the value is 20.

If we set:
* Link Time = 5s
* Local Time = 2s
* Duration = 4s
then from 2s to 6s and from 6s to 10s, etc., the resulting value is the value of "Link" from 5s to 9s, as follows:

Then the resulting values will be:
* 0s -> "Link" value at 7s = 14
* 1s -> "Link" value at 8s = 16
* 2s -> "Link" value at 5s = 10 (at "Link Time" = 2s, result is the value of "Link" at "Link Time" = 5s = 10)
* 3s -> "Link" value at 6s = 12
* 4s -> "Link" value at 7s = 14
* 5s -> "Link" value at 8s = 16
* 6s -> "Link" value at 5s = 10 ("Duration" = 4s later, the value is the same as at 2s)
* 7s -> "Link" value at 6s = 12

If "Duration" is zero, the resulting value is whatever the value of the "Link" parameter is at time "Link Time".

If "Duration" is negative, the resulting value at "Local Time" still matches the value of "Link" at "Link Time", but the animation goes in the opposite direction. For example:

If we set:
* Link Time = 5s
* Local Time = 2s
* Duration = -4s
then from 2s to 6s and from 6s to 10s, etc., the resulting value is the value of "Link" from 5s to 1s, as follows:

Then the resulting values will be:
* 0s -> "Link" value at 3s = 6
* 1s -> "Link" value at 2s = 4
* 2s -> "Link" value at 5s = 10 (at "Link Time" = 2s, result is the value of "Link" at "Link Time" = 5s = 10)
* 3s -> "Link" value at 4s = 8
* 4s -> "Link" value at 3s = 6
* 5s -> "Link" value at 2s = 4
* 6s -> "Link" value at 5s = 10 (4s later, the value is the same as at "Link Time" = 2s)
* 7s -> "Link" value at 4s = 8

This conversion can be used on all value types.

=== Timed Swap ===

This convert type was disabled in Synfig 0.61.06 and earlier because it didn't work.

Converting a parameter to "Timed Swap" adds four sub-parameters:
* <param> "Before"
* <param> "After"
* time "Swap Time"
* time "Swap Duration"

"Before" and "After" are the same type as the parameter being converted.

This conversion type linearly switches from "Before" to "After", taking "Swap Duration" seconds to do so, and completing the swap at "Swap Time".

Note that this doesn't give us anything that we can't achieve using the "[[Convert#Linear|Linear]]" conversion type and a few waypoints, except that it works on more types than the somewhat restricted "Linear" conversion. The "Linear" conversion could be extended to work on the missing types.

"Timed Swap" can be used on [[Convert#Angle|angles]], [[Convert#Color|colors]], [[Convert#Integer|integers]], [[Convert#Real|reals]], [[Convert#Time|times]], and [[Convert#Vector|vectors]].

The resulting value is:
if time > "Swap Time" then "After"
else if time < ("Swap Time" - "Swap Duration") then "Before"
else interpolate between "Before" and "After"

=== Two-Tone ===

Converting a [[Convert#Gradient|gradient]] to "Two-Tone" adds two color-valued sub-parameters:
* color "Color1"
* color "Color2"

The resulting gradient has two CPoints, one at each end, starting with "Color1" and ending with "Color2".

These color parameters can be animated, giving us the ability to have the gradient change color over time. This can be used as a workaround for [http://sourceforge.net/tracker/index.php?func=detail&aid=1568818&group_id=144022&atid=757416 this bug].

== Which Value Types can use which Convert Types? ==

There are 13 different types of value in Synfig. Each of these types has a different set of convert types available to it, as follows:

=== Angle ===

* Angle parameters can be converted to [[Convert#Add|Add]], [[Convert#aTan2|aTan2]], [[Convert#BLine Tangent|BLine Tangent]], [[Convert#Linear|Linear]], [[Convert#Random|Random]], [[Convert#Range|Range]], [[Convert#Scale|Scale]], [[Convert#Step|Step]], [[Convert#Subtract|Subtract]], [[Convert#Switch|Switch]], [[Convert#Time Loop|Time Loop]], [[Convert#Timed Swap|Timed Swap]], and [[Convert#Reference|Reference]] types.

=== BLinePoint ===

* BLinePoint parameters can be converted to [[Convert#Composite|Composite]], [[Convert#Reverse Tangent|Reverse Tangent]], [[Convert#Switch|Switch]], [[Convert#Time Loop|Time Loop]], and [[Convert#Reference|Reference]] types.

=== Bool ===

* Bool parameters can only be converted to the [[Convert#Switch|Switch]], [[Convert#Time Loop|Time Loop]], and [[Convert#Reference|Reference]] types.

=== Canvas ===

* Canvas parameters can be converted to the [[Convert#Switch|Switch]], [[Convert#Time Loop|Time Loop]], and [[Convert#Reference|Reference]] type.

=== Color ===

* Color parameters can be converted to [[Convert#Add|Add]], [[Convert#Composite|Composite]], [[Convert#Linear|Linear]], [[Convert#Radial Composite|Radial Composite]], [[Convert#Random|Random]], [[Convert#Scale|Scale]], [[Convert#Step|Step]], [[Convert#Subtract|Subtract]], [[Convert#Switch|Switch]], [[Convert#Time Loop|Time Loop]], [[Convert#Timed Swap|Timed Swap]], and [[Convert#Reference|Reference]] types.

=== Gradient ===

* Gradient parameters can be converted to [[Convert#Add|Add]], [[Convert#Gradient Rotate|Gradient Rotate]], [[Convert#Repeat Gradient|Repeat Gradient]], [[Convert#Stripes|Stripes]], [[Convert#Subtract|Subtract]], [[Convert#Switch|Switch]], [[Convert#Time Loop|Time Loop]], [[Convert#Two-Tone|Two-Tone]], and [[Convert#Reference|Reference]] types.

=== Integer ===

* Integer parameters can be converted to [[Convert#Add|Add]], [[Convert#Linear|Linear]], [[Convert#Random|Random]], [[Convert#Range|Range]], [[Convert#Scale|Scale]], [[Convert#Step|Step]], [[Convert#Subtract|Subtract]], [[Convert#Switch|Switch]], [[Convert#Time Loop|Time Loop]], [[Convert#Timed Swap|Timed Swap]], and [[Convert#Reference|Reference]] types.

=== List ===

* List parameters can be converted to [[Convert#BLine|BLine]], [[Convert#Dynamic List|Dynamic List]], [[Convert#Switch|Switch]], [[Convert#Time Loop|Time Loop]], and [[Convert#Reference|Reference]] types.

=== Real ===

* Real parameters can be converted to [[Convert#Add|Add]], [[Convert#BLine Width|BLine Width]], [[Convert#Cos|Cos]], [[Convert#Exponential|Exponential]], [[Convert#Linear|Linear]], [[Convert#Random|Random]], [[Convert#Range|Range]], [[Convert#Reciprocal|Reciprocal]], [[Convert#Scale|Scale]], [[Convert#Sine|Sine]], [[Convert#Step|Step]], [[Convert#Subtract|Subtract]], [[Convert#Switch|Switch]], [[Convert#Time Loop|Time Loop]], [[Convert#Timed Swap|Timed Swap]], and [[Convert#Reference|Reference]] types.

=== Segment ===

* Segment parameters can be converted to the [[Convert#Composite|Composite]], [[Convert#Switch|Switch]], [[Convert#Time Loop|Time Loop]], and [[Convert#Reference|Reference]] types.

=== String ===

* String parameters can be converted to the [[Convert#Switch|Switch]], [[Convert#Time Loop|Time Loop]], and [[Convert#Reference|Reference]] types.

=== Time ===

* Time parameters can be converted to the [[Convert#Add|Add]], [[Convert#Linear|Linear]], [[Convert#Random|Random]], [[Convert#Range|Range]], [[Convert#Scale|Scale]], [[Convert#Step|Step]], [[Convert#Subtract|Subtract]], [[Convert#Switch|Switch]], [[Convert#Time Loop|Time Loop]], [[Convert#Timed Swap|Timed Swap]], and [[Convert#Reference|Reference]] types.

=== Vector ===

* Vector parameters can be converted to [[Convert#Add|Add]], [[Convert#BLine Tangent|BLine Tangent]], [[Convert#BLine Vertex|BLine Vertex]], [[Convert#Composite|Composite]], [[Convert#Linear|Linear]], [[Convert#Radial Composite|Radial Composite]], [[Convert#Random|Random]], [[Convert#Scale|Scale]], [[Convert#Segment Tangent|Segment Tangent]], [[Convert#Segment Vertex|Segment Vertex]], [[Convert#Step|Step]], [[Convert#Subtract|Subtract]], [[Convert#Switch|Switch]], [[Convert#Time Loop|Time Loop]], [[Convert#Timed Swap|Timed Swap]], and [[Convert#Reference|Reference]] types.

== Compatibility ==

When a new ValueNode type is added to Synfig, the .sif file format is extended to include a way of writing the new type. This extension won't be able to be read by any older version of Synfig. Here's a list of the ValueNode types that have been added, along with the subversion revision number in which they first appeared:

<blockquote>
{| style="width:55%"
| '''Version''' || '''Revision''' || '''Convert'''
|-
| <hr> || <hr> || <hr>
|-
| '''(0.61.08)''' || ''not yet released''
|-
|   || 1694 || [[#BLine Width|BLine Width]]
|-
|   || 1691 || [[#Step|Step]]
|-
|   || 1354 || [[#Subtract|Subtract]] (for gradients)
|-
|   || 1354 || [[#Add|Add]] (for gradients)
|-
|   || 1267 || [[#From Integer|From Integer]]
|-
|   || 1267 || [[#Duplicate|Duplicate]]
|-
|   || 1238 || [[#Reciprocal|Reciprocal]]
|-
|   || 1226 || [[#Time Loop|Time Loop]]
|-
|   || 1162 || [[#Reverse Tangent|Reverse Tangent]]
|-
|   || 1132 || [[#aTan2|aTan2]]
|-
|   || 1111 || [[#Cos|Cos]]
|-
|   || 923 || [[#Switch|Switch]]
|-
|   || 907 || [[#Random|Random]]
|-
| <hr> || <hr> || <hr>
|-
| '''(0.61.07)''' || 878 ||  
|-
|   || 776 || [[#Range|Range]]
|-
|   || 744 || [[#BLine Vertex|BLine Vertex]]
|-
|   || 744 || [[#BLine Tangent|BLine Tangent]]
|-
|   || 742 || [[#Add|Add]]
|-
|   || 739 || [[#Exponential|Exponential]]
|-
|   || 666 || [[#Repeat Gradient|Repeat Gradient]]
|-
|   || 610 || [[#Timed Swap|Timed Swap]]
|-
| <hr> || <hr> || <hr>
|-
| '''(0.61.06)''' || 536 ||  
|-|}
</blockquote>

Talk:Convert

2008-02-24T22:55:09Z

Yoyobuae: /* Compatibility (Yoyobuae's table format suggestion) */ editing table width

== Timed Swap's Brokenness ==

The "Timed Swap" convert crashes synfig as soon as it is used.

The problem seems to be with ValueNode_TimedSwap::set_swap_length() and ValueNode_TimedSwap::set_swap_time() which both try to check that the type of their argument is correct, but fail to do so. [[User:Dooglus|dooglus]]

== The Feature Itself - Proposed Additions ==

While useful, it appears a little incomplete. Suppose I want to fix one of a polygon's vertices such that it always forms a 90 degree angle with the vertex before it, and is a set distance from that vertex. I could do that if I could work out the angle of the previous side to the horizontal, but that doesn't seem to be possible. Also, while it's possible to use the composite conversion to construct a vector from an X and a Y value, it doesn't seem to be possible to go in the opposite direction. If I have a vector and I want to use just its X coordinate, I don't think I can. [[User:Dooglus|dooglus]]

I propose some new conversions: [[User:Dooglus|dooglus]]

:Let me play with those feature for vertexs and I'll let you know. [[User:Genete|Genete]]

=== Vector Angle ===

Converting an angle parameter to "Vector Angle" adds sub-parameters:
* vector "Vector"
* real "Scalar"

The resulting value is the angle between "Vector" and the horizontal, multiplied by "Scalar":
atan(Vector.Y/Vector.X) * Scalar

:This would be mathematically unconsistent. Vector angel is already given by atan(Vector.X/Vector.Y). If you multiply it by Scalar then angle would be another thing (I don't know what). For example, Rotate layer have a angle value that is defined by an angle (real value). Its visual control is given by a radial duck attached to the center. If you modify the distance of the duck from the origin the duck will go to a defined (and not modificable) distance, due to the angle is the only useful value of the duck's position.

:Also, better use atan2 function (or the defined in the math library) that allow a Y value of 0 without obtaining an exception call. [[User:Genete|Genete]]

::Good point. I'll use atan2 rather than atan. I'm not sure about X/Y vs. Y/X - I'll use whatever works best. I'm thinking the Scalar might be useful if I want some object to rotate twice as quickly as some other object, for example. If you don't want this, leave the Scalar at its default value of 1.0. I was just copying the way that the Subtract convert works: it returns (LHS-RHS)*Scalar. There's no need to the Scalar really, but maybe it'll be useful sometimes. [[User:Dooglus|dooglus]] 11:17, 6 Sep 2007 (EDT)

=== Vector Length ===

Converting a real-valued parameter to "Vector Length" adds sub-parameters:
* vector "Vector"
* real "Scalar"

The resulting value is the length of "Vector", multiplied by "Scalar":
|Vector| * Scalar

=== Vector X ===

Converting a real parameter to "Vector X" adds sub-parameters:
* vector "Vector"
* real "Scalar"

The return value is:
Vector.X * Scalar

=== Vector Y ===

Converting a real parameter to "Vector Y" adds sub-parameters:
* vector "Vector"
* real "Scalar"

The return value is:
Vector.Y * Scalar

=== Gradient Color ===

Converting a color parameter to "Gradient Color" adds sub-parameters:
* gradient "Gradient"
* real "Amount"

The return value is the color at position "Amount" in the given "Gradient".

This would allow us to pick specific single colors from a gradient, allow us to color-cycle layers through the colors in a gradient, etc.

=== Angle Vector Dot ===

Converting a Real parameter to a " Angle Vector Dot" adds sub-parameters:
*Vector 1
*Vector 2

The return value is the arcosine of the scalar product of both vectors divided by the product of their magnitudes.

acos((Vector1 · Vector2)/(|Vector1| * |Vector2|))

This would allow calculate the angle between any two vectors as well as the dot product of two vectors is the product of their absolute values of its magnitudes by the cosine of its angle.

Dot = Vector1 · Vector2 = |Vector1| * |Vector2| * cos(alpha)
there alpha is the angle between vector1 and vector 2.
--[[User:Genete|Genete]] 09:05, 21 September 2007 (EDT)

=== Interval ===

Converting a Real, Angle, Integer (or other kind of scalar parameter) adds sub-parameters:

* MAX
* MIN
* Scalar

The return value is the same number than the given by Scalar but truncated to its boundaries MAX, MIN.

if Scalar >= MAX then return MAX
else if Scalar <= MIN then return MIN
else return Scalar
end

This would allow link parameters of objects to the same of other objects but limited to certain intervals. The intervals could be also linked to other objects parameters so it would allow maintain the movement of a layer/Vertex or what ever other parameter inside certain limits defined by drawn parameters... --[[User:Genete|Genete]] 02:28, 27 September 2007 (EDT)

: Thanks for the suggestion. I just added it, in [http://kibi.dyndns.org:8083/~dooglus/gitweb.pl?p=synfig;a=commitdiff;h=r776 r776] and [http://kibi.dyndns.org:8083/~dooglus/gitweb.pl?p=synfig;a=commitdiff;h=r777 r777].

: I called it '[[Convert#Range|Range]]', since it specifies a range of acceptable values. Hope that's OK with you! -- [[User:Dooglus|dooglus]] 17:19, 27 September 2007 (EDT)
:: It is prefect! Range is a more precise name. Thanks for implement it so fast, you're welcome!. I think this conversion would be very useful to limit rotations and translations. I've just compiled from svn r780 and it works great!--[[User:Genete|Genete]] 18:05, 27 September 2007 (EDT)

===Switch===

Converting a any parameter to Switch adds tree sub-parameters:

* Link (reference)
* Link Alternative (reference)
* Switch (on/off)

The returned value is Link is Switch sub parameter is set to off (default value) and Link Alternative if the Switch sub parameter is set to on.

It will allow modify the parameter to different types of conversions and also different exported parameters during animation. For example make a layer to follow two different Blines during animation.

Also it would eventually allow to link or unlink vertex to other vertex.
--[[User:Genete|Genete]] 06:54, 13 October 2007 (EDT)

== Questions ==

=== Losing Waypoints ===

''The "Convert" menu allows you to specify that the parameter should be controlled automatically in various ways''. Ok, but once the parameter is converted to the other(s) one(s), how can it be automatically ''controlled''? Maybe the parameter is now controlled by waypoints and keyframes as the normal parameters?. I'm interested into this feature because I have found that some layers (Eg. Curve Gradient) donesn't work properly in the version I have of synfigstudio (Vertices are "Unknown type". I hope using "convert" can arrange it and use some types of layers that seems that the default values are incorrectly set. Bye, [[User:Genete|Genete]]

:What version to do use? When you convert the parameter, all existing waypoints for that parameter are deleted (I think) and you won't be allowed to edit that parameter directly any more. Instead, you edit the new sub-parameters.

:Suppose you have a circle. Right-click its radius and convert to linear. Switch to animate-edit-mode, set the default interpolation type to be Constant (that's the very bottom setting in the toolbox window) and at time zero, set the rate to be 0.5 and the offset to be 0.5. That means the radius starts at 0.5 units and grows by 0.5 every second. You might have your parameters to be displayed in 'points' or some other unit. You can change that from the toolbox using File>Setup>Misc>Unit System. Set that to Units for this example. Don't forget to set it back after if you want to work in points again.

:You'll see that there are now waypoints on the 'offset' and 'rate' parameters, and you can animate those parameters just like you could animate the radius before.

:Go forward to 1s in the animation. You'll see that the circle's radius is now 1 (it grew by 0.5u from 0.5u), and set the rate to -0.5 and the offset to 1.5. This will cause the circle's radius to start shrinking by 0.5 per second from the 1s point onwards. The 1.5 offset is to arrange that the radius doesn't jump suddenly at 1s. If the radius is to go down from 1.0 at 1s at 0.5 per second, it would have been at 1.5 at 0s, so that's the offset we use.

:Does that make sense? [[User:Dooglus|dooglus]]

::I still having 0.61.05 (apr 29 2007). I hope can update ASAP.

::Regarding "Convert" WOW! it is wonderful! absolutely amazing. It opens lots of new possibilities. Thanks for document it. - [[User:Genete|Genete]]

=== Exporting and Connecting ===

Can converted parameters be linked to other objects' normal/converted parameters? [[User:Genete|Genete]]

:Yes. The best way to do this is via the 'Export' menu entry. Make sure you only have a single layer selected, then you can right-click on any parameter (regular, or converted) and say 'Export' to make the parameter easily available to other layers. It will ask you to name the parameter. There's a bug in Synfig (up to and including 0.61.06) which causes a crash when renaming exported values, so chose carefully. Then go to the 'Children' dialog, open up the "ValueBase Nodes" tree and you'll see all your exported values there. In the Children dialog, select the one you want to link to. Then select the layer you want to use the exported value in, right-click the parameter and select "Connect". That will connect to whatever is selected in the Children dialog, so long as it is the correct type. (You can't link a color to a vertex - it doesn't make any sense). [[User:Dooglus|dooglus]] 11:06, 6 Sep 2007 (EDT)

One suggestion for the initial description:
''To convert the value back to its original type, select "Disconnect" from its context menu.''
I would add: ''Disconnect would loose all the waypoints of the converted parameters and don't produce a conversion of the inserted waypoints''. BTW it could be a very cool feature. [[User:Genete|Genete]]

:OK, I'll add something like that, but what you wrote isn't quite true. Disconnect will lose all the waypoints only if the parameter hasn't been exported or linked somewhere else.

:If you want to try converting a parameter to something else, but don't want it to forget your waypoints, export the parameter before you convert it. Then you can 'Connect' back to it by selecting it in the Children dialog first, then right-click, 'Connect' on the parameter in the Parameters dialog.

:: It makes some sense now. The Child tab was a mystery to me because always is empty. Ill try it. [[User:Genete|Genete]] 16:23, 6 Sep 2007 (EDT). But wait a moment... 'Export' is like keep a animation that can be used later with 'Connect'...? Can I recover the exported animation to play at any moment during time line?... Wow that's so cool!! [[User:Genete|Genete]] 16:36, 6 Sep 2007 (EDT)

::: Not quite. When you export a parameter, what you're exporting is the whole lifetime of that parameter - its waypoints, sub-parameters and so on. What you're talking about is similar to what happens when you export the canvas in an encapsulated layer. Try this: draw something, using a bunch of layers, and encapsulate the layers together into a single layer. Then select that layer and go to its parameters. It has a parameter called 'Canvas'. Export and name that, then look in the Canvases dialog. Double-click your exported canvas and it will open in a window of its own. You can edit it in isolation there. Also, if you look in the Children dialog, you'll see your canvas in the top section, separate from the ValueBase things.

::: The thing about re-using exported canvases at different points in time is something I've not been able to work out yet. I think it may be possible, but I've not had a good look.

::: Something else worth mentioning is this: if you look at the parameters for any encapsulated layer, or any "Layers>New>(Other|Default)>PasteCanvas" (I moved it from Default to Other in subversion - it was the only thing in the 'Other' menu), the 'Canvas' parameter gives you a drop-down menu listing all the canvases you've exported. If you have animate-edit mode enabled, then editing this Canvas parameter creates waypoints (although for some reason they don't show up) which keep a record of which canvas is showing when. You can use this to switch between 'scenes' in an animation.

::: Keep asking the questions - it's good to get this typed up - eventually I might even get around to putting it all in some kind of order! :) [[User:Dooglus|dooglus]] 18:34, 6 Sep 2007 (EDT)

:The problem with your suggestion of the cool feature is that it's possible to produce very complex patterns by using combinations of 'converts' - much more complex than can be created by waypoints, so in general there's no way to produce a set of waypoint to give the same animation. It would be possible to get close, by generating hundreds of waypoints, but that's a waste - why not just keep the type converted? [[User:Dooglus|dooglus]] 11:06, 6 Sep 2007 (EDT)

Also I don't know if conversion would maintain the waypoints of the original parameters. If not it would be also a cool feature. [[User:Genete|Genete]]

:No, conversion and disconnection both wipe all the waypoints, because there's generally no way to convert between them. The 'undo' (control-z) function will of course get you your waypoints back if you convert by mistake.

=== Editing Wiki Talk Pages ===

:By the way, when replying to something, use one more ':' at the start of each paragraph than at the start of the thing you're replying to. Then your reply will be indented. Also, typing three '~'s in a row will automatically sign your text (like this: [[User:Dooglus|dooglus]]) - useful for old text you forgot to sign before, and finally, typing four '~'s will sign and date your message, making it easier to follow. Like this: [[User:Dooglus|dooglus]] 11:06, 6 Sep 2007 (EDT)

:: Thanks for the edition tips and for your patience. I'm not familiar with this kind of editors. [[User:Genete|Genete]] 16:23, 6 Sep 2007 (EDT)

=== Usage of Convert -> BLine ===

I've discovered an usage of BLine. It is in the same sense that you have explained. Maybe it is my version but if I insert a Curve Gradient using New Layer right-click menu the curve gradient is inserted but the ducks of the curve are not shown so i cannot manipulate or insert any new point in the curve. If you make a Convert-> bline on the Vertexes list then the points ducks are shown and everything works OK. - [[User:Genete|Genete]]

=== Converting Color parameter to Add ===

I don't understand this kind of conversion for colors. If I convert a color into a Add type then it displays three sub parameters: LHS (color), RHS (color) and Scalar (float). The wiki says that the result is (LHS+RHS)*Scalar. The result not always is the thing one could think it would work. I believe that the RGBA individual values of each LHS and RHS colors are added and multiplied by the scalar. Maybe this should be the right way but in my opinion the colors should be truncated to its maximum - minimum values (0-100). If not you're obtaining an alpha value of bigger than 100 that only have sense for the amount parameter. For the rest of RGB values added values gives a shift in its meaning so red becomes green and green red. Just a thought. --[[User:Genete|Genete]] 14:24, 24 September 2007 (EDT)

: It does exactly that - for each of R, G, B, and A, it added LHS + RHS and multiplies the result by the scalar. If Scalar=0.5 then this can be used to take the mean average of 2 colors. If any of R,G,B,A go <0 or >100, that doesn't matter. Synfig works with colors outside the range 0-100. I don't really understand it, but a color with an Alpha of 1000 on a layer with amount of 0.1 will be more opaque than a color with Alpha 100 on the same layer. I think this may have something to do with Synfig's [http://en.wikipedia.org/wiki/High_dynamic_range_imaging HDRI] aspirations. [[User:Dooglus|dooglus]] 15:45, 24 September 2007 (EDT)

=== Segment - Unknown Data type - ===

When converting a Vertex to Segment Vertex or Segment Tangent it creates two sub parameters one of them is called SEG Segment. When double click for editing it says "Unknown Data type". Is a data type pending to define, a bug or other thing? What should be a ''Segment'' then? --[[User:Genete|Genete]] 18:33, 27 September 2007 (EDT)

: I never tried editing one directly before, so I hadn't seen that message. Try right-clicking the segment and converting it to composite - then you'll see what it is. Also, see [[Types]] for a list of the 13 types that Synfig uses.

: I think it is probably what synfig used before blines were added - it's a single spline curve, with 2 points and 2 tangents. Basically, it's a bline, but with only 2 vertices. Maybe we don't need it any more, but I don't like modifying code when I don't understand the consequences. I do enough of that already... -- [[User:Dooglus|dooglus]] 18:58, 27 September 2007 (EDT)

== Default values for Conversions ==

When you have a constant Value Node with a current value and you convert it to any of the convert types it would be desirable that the resulting value of the converted type returns the same than the original constant value.

Current definitions of Exponential and Reciprocal convert types changes the value of the Value Node being converted.

I propose these changes:

#Exponential:
<u>Current behaviour</u>:

Converting a Real ValueNode = X to Exponential gives:

Exponent = 1 ; Scale = X ; Resulting Value = e¹*X

''Desired behaviour'':

Converting a Real ValueNode = X to Exponential gives:

Exponent = 0 ; Scale = X ; Resulting Value = e°*X = X

#Reciprocal:

<u>Current behaviour</u>:

Converting a Real ValueNode = X to Reciprocal gives:

Link = X ; Resulting Value = 1/X

''Desired behaviour'':

Converting a Real ValueNode = X to Reciprocal gives:

Link = 1/X; Resulting Value = 1/(1/X) = X

== Compatibility (Yoyobuae's table format suggestion) ==
<blockquote>
{| style="width:55%"
| '''Version''' || '''Revision''' || '''Convert'''
|-
| '''(0.61.08)''' || ''not yet released''
|-
|   || 1694 || [[#BLine Width|BLine Width]]
|-
|   || 1691 || [[#Step|Step]]
|-
|   || 1354 || [[#Subtract|Subtract]] (for gradients)
|-
|   || 1354 || [[#Add|Add]] (for gradients)
|-
|   || 1267 || [[#From Integer|From Integer]]
|-
|   || 1267 || [[#Duplicate|Duplicate]]
|-
|   || 1238 || [[#Reciprocal|Reciprocal]]
|-
|   || 1226 || [[#Time Loop|Time Loop]]
|-
|   || 1162 || [[#Reverse Tangent|Reverse Tangent]]
|-
|   || 1132 || [[#aTan2|aTan2]]
|-
|   || 1111 || [[#Cos|Cos]]
|-
|   || 923 || [[#Switch|Switch]]
|-
|   || 907 || [[#Random|Random]]
|-
|   ||   ||
|-
| '''(0.61.07)''' || 878 ||  
|-
|   || 776 || [[#Range|Range]]
|-
|   || 744 || [[#BLine Vertex|BLine Vertex]]
|-
|   || 744 || [[#BLine Tangent|BLine Tangent]]
|-
|   || 742 || [[#Add|Add]]
|-
|   || 739 || [[#Exponential|Exponential]]
|-
|   || 666 || [[#Repeat Gradient|Repeat Gradient]]
|-
|   || 610 || [[#Timed Swap|Timed Swap]]
|-
|   ||   ||
|-
| '''(0.61.06)''' || 536 ||  
|-|}
</blockquote>

Talk:Convert

2008-02-24T22:45:43Z

Yoyobuae: /* Compatibility (Yoyobuae's table format suggestion) */ editing

== Timed Swap's Brokenness ==

The "Timed Swap" convert crashes synfig as soon as it is used.

The problem seems to be with ValueNode_TimedSwap::set_swap_length() and ValueNode_TimedSwap::set_swap_time() which both try to check that the type of their argument is correct, but fail to do so. [[User:Dooglus|dooglus]]

== The Feature Itself - Proposed Additions ==

While useful, it appears a little incomplete. Suppose I want to fix one of a polygon's vertices such that it always forms a 90 degree angle with the vertex before it, and is a set distance from that vertex. I could do that if I could work out the angle of the previous side to the horizontal, but that doesn't seem to be possible. Also, while it's possible to use the composite conversion to construct a vector from an X and a Y value, it doesn't seem to be possible to go in the opposite direction. If I have a vector and I want to use just its X coordinate, I don't think I can. [[User:Dooglus|dooglus]]

I propose some new conversions: [[User:Dooglus|dooglus]]

:Let me play with those feature for vertexs and I'll let you know. [[User:Genete|Genete]]

=== Vector Angle ===

Converting an angle parameter to "Vector Angle" adds sub-parameters:
* vector "Vector"
* real "Scalar"

The resulting value is the angle between "Vector" and the horizontal, multiplied by "Scalar":
atan(Vector.Y/Vector.X) * Scalar

:This would be mathematically unconsistent. Vector angel is already given by atan(Vector.X/Vector.Y). If you multiply it by Scalar then angle would be another thing (I don't know what). For example, Rotate layer have a angle value that is defined by an angle (real value). Its visual control is given by a radial duck attached to the center. If you modify the distance of the duck from the origin the duck will go to a defined (and not modificable) distance, due to the angle is the only useful value of the duck's position.

:Also, better use atan2 function (or the defined in the math library) that allow a Y value of 0 without obtaining an exception call. [[User:Genete|Genete]]

::Good point. I'll use atan2 rather than atan. I'm not sure about X/Y vs. Y/X - I'll use whatever works best. I'm thinking the Scalar might be useful if I want some object to rotate twice as quickly as some other object, for example. If you don't want this, leave the Scalar at its default value of 1.0. I was just copying the way that the Subtract convert works: it returns (LHS-RHS)*Scalar. There's no need to the Scalar really, but maybe it'll be useful sometimes. [[User:Dooglus|dooglus]] 11:17, 6 Sep 2007 (EDT)

=== Vector Length ===

Converting a real-valued parameter to "Vector Length" adds sub-parameters:
* vector "Vector"
* real "Scalar"

The resulting value is the length of "Vector", multiplied by "Scalar":
|Vector| * Scalar

=== Vector X ===

Converting a real parameter to "Vector X" adds sub-parameters:
* vector "Vector"
* real "Scalar"

The return value is:
Vector.X * Scalar

=== Vector Y ===

Converting a real parameter to "Vector Y" adds sub-parameters:
* vector "Vector"
* real "Scalar"

The return value is:
Vector.Y * Scalar

=== Gradient Color ===

Converting a color parameter to "Gradient Color" adds sub-parameters:
* gradient "Gradient"
* real "Amount"

The return value is the color at position "Amount" in the given "Gradient".

This would allow us to pick specific single colors from a gradient, allow us to color-cycle layers through the colors in a gradient, etc.

=== Angle Vector Dot ===

Converting a Real parameter to a " Angle Vector Dot" adds sub-parameters:
*Vector 1
*Vector 2

The return value is the arcosine of the scalar product of both vectors divided by the product of their magnitudes.

acos((Vector1 · Vector2)/(|Vector1| * |Vector2|))

This would allow calculate the angle between any two vectors as well as the dot product of two vectors is the product of their absolute values of its magnitudes by the cosine of its angle.

Dot = Vector1 · Vector2 = |Vector1| * |Vector2| * cos(alpha)
there alpha is the angle between vector1 and vector 2.
--[[User:Genete|Genete]] 09:05, 21 September 2007 (EDT)

=== Interval ===

Converting a Real, Angle, Integer (or other kind of scalar parameter) adds sub-parameters:

* MAX
* MIN
* Scalar

The return value is the same number than the given by Scalar but truncated to its boundaries MAX, MIN.

if Scalar >= MAX then return MAX
else if Scalar <= MIN then return MIN
else return Scalar
end

This would allow link parameters of objects to the same of other objects but limited to certain intervals. The intervals could be also linked to other objects parameters so it would allow maintain the movement of a layer/Vertex or what ever other parameter inside certain limits defined by drawn parameters... --[[User:Genete|Genete]] 02:28, 27 September 2007 (EDT)

: Thanks for the suggestion. I just added it, in [http://kibi.dyndns.org:8083/~dooglus/gitweb.pl?p=synfig;a=commitdiff;h=r776 r776] and [http://kibi.dyndns.org:8083/~dooglus/gitweb.pl?p=synfig;a=commitdiff;h=r777 r777].

: I called it '[[Convert#Range|Range]]', since it specifies a range of acceptable values. Hope that's OK with you! -- [[User:Dooglus|dooglus]] 17:19, 27 September 2007 (EDT)
:: It is prefect! Range is a more precise name. Thanks for implement it so fast, you're welcome!. I think this conversion would be very useful to limit rotations and translations. I've just compiled from svn r780 and it works great!--[[User:Genete|Genete]] 18:05, 27 September 2007 (EDT)

===Switch===

Converting a any parameter to Switch adds tree sub-parameters:

* Link (reference)
* Link Alternative (reference)
* Switch (on/off)

The returned value is Link is Switch sub parameter is set to off (default value) and Link Alternative if the Switch sub parameter is set to on.

It will allow modify the parameter to different types of conversions and also different exported parameters during animation. For example make a layer to follow two different Blines during animation.

Also it would eventually allow to link or unlink vertex to other vertex.
--[[User:Genete|Genete]] 06:54, 13 October 2007 (EDT)

== Questions ==

=== Losing Waypoints ===

''The "Convert" menu allows you to specify that the parameter should be controlled automatically in various ways''. Ok, but once the parameter is converted to the other(s) one(s), how can it be automatically ''controlled''? Maybe the parameter is now controlled by waypoints and keyframes as the normal parameters?. I'm interested into this feature because I have found that some layers (Eg. Curve Gradient) donesn't work properly in the version I have of synfigstudio (Vertices are "Unknown type". I hope using "convert" can arrange it and use some types of layers that seems that the default values are incorrectly set. Bye, [[User:Genete|Genete]]

:What version to do use? When you convert the parameter, all existing waypoints for that parameter are deleted (I think) and you won't be allowed to edit that parameter directly any more. Instead, you edit the new sub-parameters.

:Suppose you have a circle. Right-click its radius and convert to linear. Switch to animate-edit-mode, set the default interpolation type to be Constant (that's the very bottom setting in the toolbox window) and at time zero, set the rate to be 0.5 and the offset to be 0.5. That means the radius starts at 0.5 units and grows by 0.5 every second. You might have your parameters to be displayed in 'points' or some other unit. You can change that from the toolbox using File>Setup>Misc>Unit System. Set that to Units for this example. Don't forget to set it back after if you want to work in points again.

:You'll see that there are now waypoints on the 'offset' and 'rate' parameters, and you can animate those parameters just like you could animate the radius before.

:Go forward to 1s in the animation. You'll see that the circle's radius is now 1 (it grew by 0.5u from 0.5u), and set the rate to -0.5 and the offset to 1.5. This will cause the circle's radius to start shrinking by 0.5 per second from the 1s point onwards. The 1.5 offset is to arrange that the radius doesn't jump suddenly at 1s. If the radius is to go down from 1.0 at 1s at 0.5 per second, it would have been at 1.5 at 0s, so that's the offset we use.

:Does that make sense? [[User:Dooglus|dooglus]]

::I still having 0.61.05 (apr 29 2007). I hope can update ASAP.

::Regarding "Convert" WOW! it is wonderful! absolutely amazing. It opens lots of new possibilities. Thanks for document it. - [[User:Genete|Genete]]

=== Exporting and Connecting ===

Can converted parameters be linked to other objects' normal/converted parameters? [[User:Genete|Genete]]

:Yes. The best way to do this is via the 'Export' menu entry. Make sure you only have a single layer selected, then you can right-click on any parameter (regular, or converted) and say 'Export' to make the parameter easily available to other layers. It will ask you to name the parameter. There's a bug in Synfig (up to and including 0.61.06) which causes a crash when renaming exported values, so chose carefully. Then go to the 'Children' dialog, open up the "ValueBase Nodes" tree and you'll see all your exported values there. In the Children dialog, select the one you want to link to. Then select the layer you want to use the exported value in, right-click the parameter and select "Connect". That will connect to whatever is selected in the Children dialog, so long as it is the correct type. (You can't link a color to a vertex - it doesn't make any sense). [[User:Dooglus|dooglus]] 11:06, 6 Sep 2007 (EDT)

One suggestion for the initial description:
''To convert the value back to its original type, select "Disconnect" from its context menu.''
I would add: ''Disconnect would loose all the waypoints of the converted parameters and don't produce a conversion of the inserted waypoints''. BTW it could be a very cool feature. [[User:Genete|Genete]]

:OK, I'll add something like that, but what you wrote isn't quite true. Disconnect will lose all the waypoints only if the parameter hasn't been exported or linked somewhere else.

:If you want to try converting a parameter to something else, but don't want it to forget your waypoints, export the parameter before you convert it. Then you can 'Connect' back to it by selecting it in the Children dialog first, then right-click, 'Connect' on the parameter in the Parameters dialog.

:: It makes some sense now. The Child tab was a mystery to me because always is empty. Ill try it. [[User:Genete|Genete]] 16:23, 6 Sep 2007 (EDT). But wait a moment... 'Export' is like keep a animation that can be used later with 'Connect'...? Can I recover the exported animation to play at any moment during time line?... Wow that's so cool!! [[User:Genete|Genete]] 16:36, 6 Sep 2007 (EDT)

::: Not quite. When you export a parameter, what you're exporting is the whole lifetime of that parameter - its waypoints, sub-parameters and so on. What you're talking about is similar to what happens when you export the canvas in an encapsulated layer. Try this: draw something, using a bunch of layers, and encapsulate the layers together into a single layer. Then select that layer and go to its parameters. It has a parameter called 'Canvas'. Export and name that, then look in the Canvases dialog. Double-click your exported canvas and it will open in a window of its own. You can edit it in isolation there. Also, if you look in the Children dialog, you'll see your canvas in the top section, separate from the ValueBase things.

::: The thing about re-using exported canvases at different points in time is something I've not been able to work out yet. I think it may be possible, but I've not had a good look.

::: Something else worth mentioning is this: if you look at the parameters for any encapsulated layer, or any "Layers>New>(Other|Default)>PasteCanvas" (I moved it from Default to Other in subversion - it was the only thing in the 'Other' menu), the 'Canvas' parameter gives you a drop-down menu listing all the canvases you've exported. If you have animate-edit mode enabled, then editing this Canvas parameter creates waypoints (although for some reason they don't show up) which keep a record of which canvas is showing when. You can use this to switch between 'scenes' in an animation.

::: Keep asking the questions - it's good to get this typed up - eventually I might even get around to putting it all in some kind of order! :) [[User:Dooglus|dooglus]] 18:34, 6 Sep 2007 (EDT)

:The problem with your suggestion of the cool feature is that it's possible to produce very complex patterns by using combinations of 'converts' - much more complex than can be created by waypoints, so in general there's no way to produce a set of waypoint to give the same animation. It would be possible to get close, by generating hundreds of waypoints, but that's a waste - why not just keep the type converted? [[User:Dooglus|dooglus]] 11:06, 6 Sep 2007 (EDT)

Also I don't know if conversion would maintain the waypoints of the original parameters. If not it would be also a cool feature. [[User:Genete|Genete]]

:No, conversion and disconnection both wipe all the waypoints, because there's generally no way to convert between them. The 'undo' (control-z) function will of course get you your waypoints back if you convert by mistake.

=== Editing Wiki Talk Pages ===

:By the way, when replying to something, use one more ':' at the start of each paragraph than at the start of the thing you're replying to. Then your reply will be indented. Also, typing three '~'s in a row will automatically sign your text (like this: [[User:Dooglus|dooglus]]) - useful for old text you forgot to sign before, and finally, typing four '~'s will sign and date your message, making it easier to follow. Like this: [[User:Dooglus|dooglus]] 11:06, 6 Sep 2007 (EDT)

:: Thanks for the edition tips and for your patience. I'm not familiar with this kind of editors. [[User:Genete|Genete]] 16:23, 6 Sep 2007 (EDT)

=== Usage of Convert -> BLine ===

I've discovered an usage of BLine. It is in the same sense that you have explained. Maybe it is my version but if I insert a Curve Gradient using New Layer right-click menu the curve gradient is inserted but the ducks of the curve are not shown so i cannot manipulate or insert any new point in the curve. If you make a Convert-> bline on the Vertexes list then the points ducks are shown and everything works OK. - [[User:Genete|Genete]]

=== Converting Color parameter to Add ===

I don't understand this kind of conversion for colors. If I convert a color into a Add type then it displays three sub parameters: LHS (color), RHS (color) and Scalar (float). The wiki says that the result is (LHS+RHS)*Scalar. The result not always is the thing one could think it would work. I believe that the RGBA individual values of each LHS and RHS colors are added and multiplied by the scalar. Maybe this should be the right way but in my opinion the colors should be truncated to its maximum - minimum values (0-100). If not you're obtaining an alpha value of bigger than 100 that only have sense for the amount parameter. For the rest of RGB values added values gives a shift in its meaning so red becomes green and green red. Just a thought. --[[User:Genete|Genete]] 14:24, 24 September 2007 (EDT)

: It does exactly that - for each of R, G, B, and A, it added LHS + RHS and multiplies the result by the scalar. If Scalar=0.5 then this can be used to take the mean average of 2 colors. If any of R,G,B,A go <0 or >100, that doesn't matter. Synfig works with colors outside the range 0-100. I don't really understand it, but a color with an Alpha of 1000 on a layer with amount of 0.1 will be more opaque than a color with Alpha 100 on the same layer. I think this may have something to do with Synfig's [http://en.wikipedia.org/wiki/High_dynamic_range_imaging HDRI] aspirations. [[User:Dooglus|dooglus]] 15:45, 24 September 2007 (EDT)

=== Segment - Unknown Data type - ===

When converting a Vertex to Segment Vertex or Segment Tangent it creates two sub parameters one of them is called SEG Segment. When double click for editing it says "Unknown Data type". Is a data type pending to define, a bug or other thing? What should be a ''Segment'' then? --[[User:Genete|Genete]] 18:33, 27 September 2007 (EDT)

: I never tried editing one directly before, so I hadn't seen that message. Try right-clicking the segment and converting it to composite - then you'll see what it is. Also, see [[Types]] for a list of the 13 types that Synfig uses.

: I think it is probably what synfig used before blines were added - it's a single spline curve, with 2 points and 2 tangents. Basically, it's a bline, but with only 2 vertices. Maybe we don't need it any more, but I don't like modifying code when I don't understand the consequences. I do enough of that already... -- [[User:Dooglus|dooglus]] 18:58, 27 September 2007 (EDT)

== Default values for Conversions ==

When you have a constant Value Node with a current value and you convert it to any of the convert types it would be desirable that the resulting value of the converted type returns the same than the original constant value.

Current definitions of Exponential and Reciprocal convert types changes the value of the Value Node being converted.

I propose these changes:

#Exponential:
<u>Current behaviour</u>:

Converting a Real ValueNode = X to Exponential gives:

Exponent = 1 ; Scale = X ; Resulting Value = e¹*X

''Desired behaviour'':

Converting a Real ValueNode = X to Exponential gives:

Exponent = 0 ; Scale = X ; Resulting Value = e°*X = X

#Reciprocal:

<u>Current behaviour</u>:

Converting a Real ValueNode = X to Reciprocal gives:

Link = X ; Resulting Value = 1/X

''Desired behaviour'':

Converting a Real ValueNode = X to Reciprocal gives:

Link = 1/X; Resulting Value = 1/(1/X) = X

== Compatibility (Yoyobuae's table format suggestion) ==
<blockquote>
{|
| '''Version''' || '''Revision''' || '''Convert'''
|-
| '''(0.61.08)''' || ''not yet released''
|-
|   || 1694 || [[#BLine Width|BLine Width]]
|-
|   || 1691 || [[#Step|Step]]
|-
|   || 1354 || [[#Subtract|Subtract]] (for gradients)
|-
|   || 1354 || [[#Add|Add]] (for gradients)
|-
|   || 1267 || [[#From Integer|From Integer]]
|-
|   || 1267 || [[#Duplicate|Duplicate]]
|-
|   || 1238 || [[#Reciprocal|Reciprocal]]
|-
|   || 1226 || [[#Time Loop|Time Loop]]
|-
|   || 1162 || [[#Reverse Tangent|Reverse Tangent]]
|-
|   || 1132 || [[#aTan2|aTan2]]
|-
|   || 1111 || [[#Cos|Cos]]
|-
|   || 923 || [[#Switch|Switch]]
|-
|   || 907 || [[#Random|Random]]
|-
|   ||   ||
|-
| '''(0.61.07)''' || 878 ||  
|-
|   || 776 || [[#Range|Range]]
|-
|   || 744 || [[#BLine Vertex|BLine Vertex]]
|-
|   || 744 || [[#BLine Tangent|BLine Tangent]]
|-
|   || 742 || [[#Add|Add]]
|-
|   || 739 || [[#Exponential|Exponential]]
|-
|   || 666 || [[#Repeat Gradient|Repeat Gradient]]
|-
|   || 610 || [[#Timed Swap|Timed Swap]]
|-
|   ||   ||
|-
| '''(0.61.06)''' || 536 ||  
|-|}
</blockquote>

Talk:Convert

2008-02-24T22:22:00Z

Yoyobuae: Adding a table format suggestion for compatibility list

Talk:Blend Method Parameter

2008-02-20T22:14:13Z

Yoyobuae: New Blend Method, postintg an idea

==New Blend Method==

I would like to have a blend method that allows apply effects over a certain region of a composition. Let's call this new Blend Method "X". So the Layer stack would be like this:

Effect Layer (Blend Method: X)
Cropping Layer (Blend Method: A)
Background Layer (Blend Method: doesn't matter)

A is any Blend Method.

The blend method X would do the following:

Apply the effect over the background using the composite blend method:

Effect Layer (Blend Method Composite)
Background Layer
-----------------------
Effected Background Layer

Then apply a Straight Onto blend method over the Cropping layer

Effect Background Layer (Blend Method Straight Onto)
Cropping Layer
---------------------------------------
Cropped Effected Background

Later apply the result on the background using the Cropping Layer Blend Method

Cropped Effected Background (Blend Method A)
Background Layer
-------------------------------------------
Cropped Effected Background Onto Background

I propose call this X Blend Method: "Cropped Onto"

== Layers as Function objects ==

Let's say layers behave like a function: f(x), where f is the layer defined operation and x the context. The result is passed on to the next layer, which does something similar.

When we have several layers (in this example: f, g, h, i) we end up with:
f(g(h(i(blank)))

A paste canvas is a bit different though it takes two arguments: p(x,y) where x is the context and y is the context returned by the top layer of the inline canvas. Lets now put this paste canvas on top of the layers in the previous example:
p(f(g(h(i(blank))),y(blank))
where y is the inline canvas.

From this point of view all of this is very similar to how function objects work. But we lack the ability to compose function objects (like STL does, with SGI extensions that is).

Lets say there is a layer type: compose. This layer takes its context, and renders an inline canvas on top of that context. So that:
compose(context(),inline()) = inline(context())

This would allow applying a certain effect, as defined in the inline canvas, far more easily.

Dev:Bline Speed

2008-02-15T20:29:15Z

Yoyobuae:

== 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 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>

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 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.

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.

Dev:Bline Speed

2008-02-15T20:20:58Z

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

== 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.

Dev:Wish list

2008-02-03T18:32:12Z

Yoyobuae: /* Tweening for images developed in other imaging programs */ Added some info and links

Got a great idea for a new feature? Just add it here, or on the [http://sourceforge.net/tracker/?group_id=144022&atid=757419 feature requests tracker]. Before you do, please check the [http://svn.voria.com/code/ETL/trunk/TODO etl], [http://svn.voria.com/code/synfig-core/trunk/TODO synfig] and [http://svn.voria.com/code/synfig-studio/trunk/TODO synfigstudio] TODO files for similar ideas. Please add a rating of how essential this feature is to your workflow according to the following scale:

#"Well, it might be nifty. To someone."
#"I probably would make use this"
#"It's not essential, but I'd really like to have this at my disposal."
#"Synfig would be soooo much better with this change"
#"I can't/won't use Synfig without it!"

== Wishes ==

=== Good high-level documentation of the source code ===

(2) It'd be nice if a newbie could quickly navigate around the source code. The best thing to do would be to add top-level comments in each file, explaining what that file does, a README.TXT in each directory, explaining what's in that directory. This would be pretty fast and easy to do, and make it much easier for new programmers to join.

Time permitting, it would also be good to document on a high level what the data structures are, but that's harder, since those tend to evolve, and it is often difficult to keep in sync. It would also be useful to document what individual functions do (just a one-liner high-level description), but that also takes more time.
: There is a page link in the wiki that connect to the [http://www.synfig.com/doc Synfig API Documentation]. I think this link should be highlighted to be more accessible for newbies contributors and mature developers (the link was found [[Releases/DeveloperPreview#Support | here]]). --[[User:Genete|Genete]] 10:02, 11 December 2007 (EST)

=== Mathematical functions to animate ===
(2) If you want to make a waving flag, it would be handful a sine function, tuned with random correctors, for example.
: -This should generate waypoints each 1, 2, 4 frames or any other step at artist's wish.
: -When applying a function you can add it to current values, add it to 1st frame values or simply override old values. Perhaps other options (such multiplication) would be fine, too. Something like texture editor in [http://www.artofillusion.org Art of Illusion], perhaps.
Perhaps it would be useful reusing the [http://www.gnu.org/software/octave/ Octave] source code to parse mathematical expressions.
I have rated this wish with a '2' because undoubtly many users will not be familiar to mathematical concepts, but for those who will be, I'd rate it with a 4. It would be possible to make a ball describing a parabolic moving in no time.
[[User:ajotatxe|ajotatxe]] 20 November 2007
: dooglus can probably chime in better than I here (see his example of balls on mathematical paths at http://uk.youtube.com/watch?v=YTpSfUthuVE ), but I believe that this is already possible. Synfig does support a variety of mathematical transforms for parameters, although the way you do this is by no means intuitive. (You might also want to check out the preambletaffy.sifz example for an easier approach to a waving flag. I know you were just using that as an example, but for the record...) [[User:Pxegeek|Pxegeek]] 00:58, 21 November 2007 (EST)

=== Warning about editing bizarre things in animate editing mode ===
(3.5) It seems to have little sense animate certain things like Blend Method or Type of Feather. It would be very nice that the program asked comfirmation if you change these attributes in animate editing mode. If you do want to, you would have three options: "Yes, never ask", "Yes, never ask for this attribute", "No". I guess that internally, this attributes has integer type (or something like that) and the attributes that you normally want to animate, float type, so I think that this feature is relatively easy to implement. My English is not very good, so please feel free to fix this post.
[[User:ajotatxe|ajotatxe]] 20 November 2007

=== General outline / Polygon-based Outline / "Set Tangents to Zero" button ===
(3.5) I'm no artist, thus my primary form of art is stick figures, not to mention, many interesting animations are done in stick-figure style. Stick figures must be perfectly straight to get the effect across, so when I'm making an outline using B-Curves, it is too time consuming to set the tangents to 0 each time. Similarly, outlines of other shapes like squares, circles and so forth would be very useful. Whichever of the above is easiest, please implement right away. --[[User:Dragontamer|Dragontamer]] 02:35, 19 November 2007 (EST)
: For perfectly straight lines, click without moving the mouse. You will get a single point with no tangents. Outline shapes would require some development, particularly with some thought given to backward compatibility. A workaround you might consider is to create a duplicate shape with a different color and make the top one slightly smaller, so the outline of the one below shows. [[User:Pxegeek|Pxegeek]] 21:58, 19 November 2007 (EST)
:: Well, in general, whenever I click on a point to edit it (say, to make it move somewhere in animation mode), there is a decent chance that I click on a tangent instead. Then, if I want to right click the point itself, I usually right click the tangent marker instead. It isn't that big a deal, but simplicity at the cost of power generally is a good thing, especially when it will save a few mouse clicks.
:: As for the outlines, yeah, I've tried that and it is a decent solution for now, although it is no replacement for a real outline. I am going to also experiment with a clamp to see if I can make the center of the shape have 100% alpha... but I don't have synfig on the computer I'm on right now. Thanks for the tips Pxegeek. --[[User:Dragontamer|Dragontamer]] 01:58, 27 November 2007 (EST)
::: You can press Alt+3 to hide tangent ducks. --[[User:Zelgadis|Zelgadis]] 09:27, 27 November 2007 (EST)

=== Bones with FK & IK + grouping of objects into folders ===

(1) Bones cane move specific vector assigned to them or the bones can have envelopes that move the vectors within their field of influence, much Like Anime Studio/Moho does. It's quite a time saving process of animating. Objects created can be saved into separate groups or folders using the same system as Anime Studio/Moho -Shadowphoenix 27/8/2007

=== Copy & Paste/Image Importing ===

(4) I sometimes make graphics in other programs, or use clipart and other images. Would it be possible for Synfig to be able to import images and/or copy and paste them?--Khlieeq 2007-07-19
Well, it doesn't support Copy & paste from the clipboard, but you can import images using "New Layer -> Other -> Import". This will create an Import layer, for which you can then edit the properties to point to the file containing your image. PXEGeek. 2007-07-19

=== Animated sketch ===

(1) it would be great, if the tool Sketch will return and it will be animatable (for example, in a form of a special sketch-layer). --Zelgadis 2007-06-14
<br>For the first part of the request, note that the sketch tool can be re-enabled using environment variables. See [[FAQ#Where_did_the_polygon.2C_draw.2C_sketch.2C_and_width_tools_go.3F|FAQ]] for details. [[user:pxegeek|PXEGeek]] 9/26/07

=== Duck for Amount value in Zoom layer ===

(2) It would be nice if Amount value in Zoom layer was controlled by additional duck. --[[User:Zelgadis|Zelgadis]] 02:49, 29 December 2007 (EST)
: I found that I can better use Warp layer instead of Zoom to change size. But it'd be nice to have Amount duck for Zoom layer anyway...
:: The Amount parameter works exponentially; each time you add 1 to the Amount, the image is zoomed by a further factor of e (= 2.71828 or so). Would a duck be any use if it just controlled the value of Amount in a linear way?
:: Workarounds include: export Amount, select it in the children dialog. Whatever's selected in the children dialog shows a duck. You can adjust it using that duck.
:: Also, if you use a Stretch layer, convert the Amount to Composite, export the X-Axis and connect it to the Y-Axis, then you have a duck-controllable fixed-aspect zoom. -- [[User:Dooglus|dooglus]] 15:32, 15 January 2008 (EST)
::: Yeah I found this workaround, but it's to much actions - i prefer better use Warp or Stretch layers. Why not the link Amount duck and Amount value with logarithmic function? ;) --[[User:Zelgadis|Zelgadis]] 10:33, 17 January 2008 (EST)

=== Recursive Waypoint Manipulation ===

(4) it is really tiresome to revert changes to waypoints created by manipulating tangent/position ducks or change their interpolation functions. making it possible to right-click-modify the waypoint shown for objects that have some waypoint in a referenced sub-object would be great! -- timonator 2007-06-01
:You can do it in two ways: changing the interpolation method of the waypoint of paste canvas or editing the keyframe properties. The first allow to modify the waypoints interpolation method for all the waypoints of all the parameters of all the layers that are inside the paste canvas layer. You can right click on the left or right part of the waypoint to edit by a context menu the left or the right interpolation method of the waipoints. The second method would add and modify all the parameters that have any waypoint in the animation. See [[Keyframe]] for more detail. --[[User:Genete|Genete]] 13:10, 29 October 2007 (EDT)

=== Automatic colour palette optimisation ===

(0) it would be nice to use libcontrast [http://david.navi.cx/blog/?p=132] [http://david.navi.cx/blog/?p=94] [http://david.navi.cx/blog/?p=99] [http://svn.gnome.org/svn/xchat-gnome/trunk/src/libcontrast/] to automatically adjust selected or all the palette items for best visual contrast. It would also be interesting to have a layer that uses this code to filter the image.

=== Tweening for images developed in other imaging programs ===

It's obvious I am a beginner at image movement, but morphing is not enough: movement across the page is needed. Thanks for listening. [[User:Comwell@bellsouth.net|Comwell]]<br>
Imported images can be moved across the page. They can also be scaled, rotated and deformed. Was there a specific example you had in mind? [[User:Pxegeek|pxegeek]]<br>
:I also would like a way to tween images that have been drawn in other programs. I've had trouble drawing with Bline tool and the drawing tool in Synfig, and I'd rather just draw with a paint brush (like the one in Photoshop). Another problem I have is that Synfig tends to shut down on me every 20 minutes or so, and it's really frustrating even with the auto recover feature, because my sketches disappear. It'd be nice if I'm able to draw all of the keyframes in Photoshop or another image program and import it to Synfig so that Synfig can tween and animate them. Thank you. [[User:xychefoo@gmail.com|Huina]]
::You CAN use images, drawn in other programs. Just select "File->Import" from [[Canvas Menu Caret|canvas menu]] --[[User:Zelgadis|Zelgadis]] 01:39, 24 November 2007 (EST)
:::But how do you animate using images from other sources? I tried to make 2 keyframes with 2 different images, and it doesn't animate. It just stays as 1 picture for the entire render. The closest thing I saw to importing images from another source into Synfig and having it animate is the Walking Cycle Tutorial, but I would still have to trace the images to make it animate. As I said earlier, I'm not entirely fond of using the draw/Bline tool. [[User:xychefoo@gmail.com|Huina]]
:::: Huina, there's no way to do what you want right now. Interpolating between two images that are not created in Synfig is well beyond its scope right now. However, what you could do is take an image and separate elements of the picture onto different layers (e.g. have a picture of an arm and another of the rest of the body) and you can move those around, stretch and rotate them. (If you're familiar with the work of Terry Gilliam on Monty Python you'll know what I mean) I don't know how feasible it is to implement your request (I suspect some heavy lifting). We'll keep it on the list, but don't hold your breath. [[User:Pxegeek|Pxegeek]] 19:57, 24 November 2007 (EST)

:::: I think, you hardly find any other animation package which allow you to do such things. You could use a special tools for this task, like xmorph (http://xmorph.sourceforge.net/). But to do the tween between two bitmap images you STILL need to set points. It's not tracing, but very similar. Anyway, result may be poor and I'd better suggest to use technique, described in Walking Cycle Tutorial or which the [[User:Pxegeek|Pxegeek]] meant. --[[User:Zelgadis|Zelgadis]] 02:08, 25 November 2007 (EST)

:::: There is a technique called "optical flow". It takes two input frames and calculates the movement of each individual pixel between the frames, allowing interpolation to be done. Here's an example: http://www.fxguide.com/article333.html. It doesn't require setting of control points, but it has problems it's own set of problems: http://www.fxguide.com/article333.html. --[[User:Yoyobuae|Yoyobuae]] 13:32, 3 February 2008 (EST)

=== Auto-link option in [[Draw tool]] ===

(4) so that you can draw a line, and have its endpoint automatically link to a duck - or if Auto-connect is off, you can get a line object linked to the end of another line object. / I missed this too, it even should be like that by default I think. [[User:Maxy|Maxy]] 13:22, 25 Apr 2006 (PDT)

: Isn't this done already? We don't have line objects, but blines are automatically linked to if auto-connect is on. Am I missing something? -- [[User:Dooglus|dooglus]] 17:29, 27 September 2007 (EDT)

::To clarify dooglus' comments - If you have an outline created by the draw tool highlighted in the layer dialog and the <b>auto-extend</b> checkbox is checked, then you can continue drawing with the draw tool in that same layer. Blines created with the Bline tool cannot be extended once a different tool or layer is selected. [[User:Pxegeek|Pxegeek]] 23:46, 12 October 2007 (EDT)

::: A line is a line - Synfig doesn't remember whether it was created with the Bline tool or the Draw tool - so you can extend blines created with the bline tool using the draw tool. Just make sure the line is selected (so that its ducks are visible), not looped (so that it has end points to extend from), enable the draw tool, check 'auto extend' and start drawing at one of its end ducks. [[User:Dooglus|dooglus]] 05:47, 13 October 2007 (EDT)

So this sounds like it is already done. But on a related note, being able to open an existing bline in the bline tool to extend it would be useful. -- [[User:Dooglus|dooglus]] 04:51, 29 January 2008 (EST)

=== Arbitrary Color Channels ===

— The ability for the user to create any number of custom channels for various purposes.

=== Autorecover History ===

— It would be great if autorecover could also recover the associated history of a file in the event of a crash.

=== Layer Convert ===

<strike>(4)</strike> (2) — The original intent of this feature request has been solved and documented - [[How_do_I#Fill_an_outline.3F|How do I....Fill an Outline?]] - but it would still be nice to have a way to convert one sort of path layer to another. ''(Downgraded to level 2) [[User:SnapSilverlight|Snap]] 12:32, 17 Jan 2006 (PST)''

=== Layer hide boolean parameter ===

(3) — An animatable way to remove a layer from visibility and consideration in tools. And as an option, to hide the layer in the layer list while it is invisible. This crosses over functionality from the [[Amount Parameter]], the Show/Hide checkbox in the [[Layers Panel]], and builds upon it as well, allowing the [[Layers Panel]] to dynamically unclutter. ''(This feature request is a refactoring of the [[Amount Parameter]])''
: With the addition of the [[Convert#Switch|Switch]] type conversion it is not needed this feature request. You can convert the Amount parameter to a Switch value and give 0 and 1 to the Linked OFF/ON values. --[[User:Genete|Genete]] 13:20, 29 October 2007 (EDT)

=== Vector fill bucket ===

(3) — Like the traditional bitmap fill, but this fills the area clicked out to the nearest boundary paths with a region of that area, set to the foreground color (it actually would create a new [[Region Layer|region layer]]). <p>Alternatively, a single-duck layer object, that performs a simple bitmap fill from its (animatable) location, with its stored color value. (This second approach is similar to the behavior of one of Softimage's TOONZ[http://www.google.com/search?q=softimage+TOONZ]'s tools)</p><p>If this is implemented, it will probably be necessary to change the existing "fill" tool's name and icon to a "color injector" (hypodermic needle / turkey injector icon) tool, as that's closer to describing what it does.

=== [[redraw tool]] ===

(4-5) — Intutive reshaping of path-based layers. See link.

=== [http://developer.gnome.org/projects/gup/hig/ Gnome HIG Compliance] ===

— This should solve all complaints about the layout, without requiring Synfig to be "just like program (x)". See [[UI Reloaded]] for progress on this.

=== Feedback for [[Smooth Move Tool]] ===

(3) — This tool does what a lot of folks are looking for, warping selected ducks in a "soft" fashion. But it's not very obvious what sort of effect it will have, from the tool's interface. It needs some sort of momentary center-of-action and radius indicator at the very least. Perhaps an "influence gradient" overlaid on the canvas once Synfig's core is sped up?

=== Networkability ===

(2) — Like Inkscape's "inkboard" feature (using Jabber), or Blender's Verse server [http://www.blender.org/modules/verse/index.php], or OpenCanvas's Networking option. This should probably farm off all the networking stuff to the telepathy framework so that synfig doesn't have to deal with all the account/etc issues.

=== Riding ducks ===

(2) — Not chocobos. The ability to link a duck from one shape to an arbitrary position on another path, without creating an extra shape duck on that path.

=== Intuitive tangent modification ===

(3) — (BBQ Pulled Duck) Inkscape has this for still handles - basically, grab a section of the spline between handles, and pull it around, the program automatically alters the tangent handles to match. What would be really neat is if you could do the same for temporal handles - be able to grab the spline between keyframes, and yank it around, and have Synfig automatically adjust the key interpolation to match. Not sure exactly what the workflow in the UI would be for this, however.

=== Plugin API ===

(1) — Would be nice to enable additional functionality to be added to the program without it necessarily needing to be in the Synfig source tree. ''According to the Synfig 0.61.01 roadmap on [http://deepdarc.com/ deepdarc.com], there is a plugin API already implemented. So instead, this may be a [[Wiki Wish List|Wiki Wish]] for documentation, depending on how much has already been completed. [[User:SnapSilverlight|Snap]] 19:57, 13 Jan 2006 (PST)

=== Python support ===

(1) of some sort will no doubt be demanded by the userbase eventually, for studio-specific automation of tasks, noncompiled plugins, etc. I ([[User:Snap|SnapSilverlight]]) don't have any particular use for it at the moment, tho'.

=== mod_synfig ===

(1) — For Apache. Render .sif to some format like png/mng on access.

=== synfig nsplugin ===

(1) — Let Mozilla and Mozilla-based view synfig files in-browser.

=== Image filmstrip import ===

(2) — Allow import of a series of images (TGA, etc) as frames of an animation, on a layer. <br>
Response - 'lst' files of a list of images can be imported. I've used this to develop a walk cycle. See [[Walk_Cycle|Walk cycle]] for an example. [[user:pxegeek|pxegeek]]

=== Bitmap Objects and Backgrounds ===

<s>(5)</s>(0) — Simmilar to the above but for more than for just purely bitmap based animations. I feel that the to do production quality animations you need production quality backgrounds, foregrounds, and effects. Many of which are very difficult or even impossible to achieve with vector based graphics. I suggest support for alpha transparencies as well to make this truely useful. An example of how this could be used would be a bitmap background and a bitmap foreground that can be panned as the scene moves.
::''Static bitmaps with alpha are possible already, if that is what you mean. I have just documented it in [[How do I]]. [[User:Maxy|Maxy]] 06:35, 9 Apr 2006 (PDT)''

=== Align function ===

(3) — Align objects at a common border (as in Inkscape)

=== Improved SVG import ===

(4) — Currently, all importing an SVG does is render it in ImageMagick. What I want is the ability to import the SVG document so that all the shapes, etc. of the SVG document show up as their equivilant synfig layers - i.e. if I had put them there myself. I'm trying to write a patch for this but the codebase is mostly undocumented. [[User:KMeist|KMeist]] 16:38, 25 Feb 2006 (PST)

[[svg2synfig]] could be incorporated using an open source XSLT processor. --[[User:Dmd|Dmd]] 13:34, 26 January 2008 (EST)

=== Gradient Paint Tool ===

How about a tool that can 'paint' a gradient object. For example the options would be width and gradient type, one would make a stroke with the tool and the gradient would be automatically applied inside of the outline (set by width). This would save the trouble of having to the all the encapsulation stuff. (Actually any tool that makes creating gradient one step would be good).--[[User:Triclops|Triclops]] 09:52, 9 Aug 2006 (PDT)

=== Character Animation Tools ===

I have seen some interesting methods for helping character design/animation in different 2d/3d software. Hash's animation master has 'poses' which are extremes of a model, for example smiling and frowning, once you add these extremes ot a set you can use slider to create a pose that somewhere inbetween. The real power of this is when you have serveral different poses on the same object, a face say, you can easily come up with new facial expressions. Maybe something similar could be done with synfig using layers and groups, the implementation could something similar to Moho's switch layers. --[[User:Triclops|Triclops]] 09:52, 9 Aug 2006 (PDT)
: Have you read this tutorial? [[Reuse Animations]]. It is very close to the Switch layer of Moho/Anime Studio. Also You can change the Canvas parameter to any other canvas dynamically in the time line by clicking on it and selecting other exported canvas. Other option is convert the canvas to a Switch type and alternate between two different canvas. --[[User:Genete|Genete]] 13:26, 29 October 2007 (EDT)

=== Another character Animation Tools ===

Bone system with inverse kinematics, very important for quick animation. You put bones on a drawed man and you can animate him like a puppet. I'm using that in Moho (lost marble product).--[[User:Ziolive|ziolive]] 23 Aug 2006

*'''AVI Backgrounds''' - Is there any way I can add an avi as a background so I could add facial expressions to a stop-motion animated figure. [zotz here, I was thinking DV background or extra timeline. I would like to mix animations with live footage. rating (3/4)]

=== Character tool on Tool Options Dialog ===

I want to use the as a character generator for a TV show. By using chroma key hide the background. Even better interface to a video overlay card with Alpha blending.

=== Collect for Publication ===

(3/4) - (zotz) Menu item, functionality that would collect alll files referenced in a sif and place them all in a tgz for sending elsewhere or publishing anumations in source form.

=== Object Library ===

(3/4) - (zotz) Haven't thought this all through yet, but synfig could come with a library of categotrised "objects" with a copyleft license (GPL? CC BY-SA?) An animation clip art type deal.
**I'd suggest this should be public domain and distributed by openclipart.org -- --[[User:PaulWise|pabs]]

=== Flash Export ===

(3/4) Well, might just be me but if there was a posiblity to export in .swf or .fla, I think the project might become a lot more popular.[[User:Conceit|Conceit]]

(4/5) I wholeheartedly agree. I would definitely use synfig more if this feature were added and it would most definitely increase popularity. [[User:cdj05a|cdj05a]]

=== Single window ===

(2/4)why does Synfig generate so many separate windows? just starting it clutters my desktop, I think it would be useful if they were atleast displayed as one in the start bar. [[User:Conceit|Conceit]]

=== Line width tool ===
(4) It will be good to have a tool for easy changing line width. There was a such tool in earlier versions, but it's not usable. I'm often use variable line width, when drawing in synfig, so it is important for me. -- [[User:Zelgadis|Zelgadis]] 2007-09-09

: It is [[FAQ#Where did the polygon, draw, sketch, and width tools go?|still available]]. Also, you can turn on the width ducks, using Alt-5. -- [[User:Dooglus|dooglus]] 12:18, 9 October 2007 (EDT)

:: It is available, but I never was able to figure out how it works. Alt-5 works, but it is hard to set width to zero, for example. -- [[User:Zelgadis|Zelgadis]] 2007-09-10

::: Are you wanting something that works on one vertex at a time? Or all the vertices in an area? Apparently the width tool was designed to work on a bunch of vertices at once. I didn't figure out how it works though, either. -- [[User:Dooglus|dooglus]] 16:57, 10 October 2007 (EDT)

:::: Width tool is surely a mystery. :) I'm waiting for something that works on one vertex at time. I liked the way as width was changed in Moho (Anime Studio now) - there was a special width tool and holding left mouse button on the vertex and moving cursor left decreasing width value, moving right - increasing. Maybe it make sense to rework Width tool in such way. -- [[User:Zelgadis|Zelgadis]] 2007-09-13

=== Export Wizard ===

(2/4) Conversion and export to other file formats (mpg, avi, flash formats, others, and the synfig format) with a step by step wizard for choosing format and place of saving. Similar to Gimp's saving of .png files but for movie/video type files. --
[[User:Hiddenghost|hiddenghost]]

=== Using Synfig as a portable app ===

(3) This isn't really a feature request (though it could be) but I was wondering if synfig could be used as a portable application (as in www.portableapps.com). Does the windows install require registry access? i really want to use Synfig at work, but I'm reluctant to install it just in case it leave footprints in the regisitry or something, and it would be sweet to use it on my travels as well. Only thing is, I can't test it out at home because I am using Linux.
See also: http://portableapps.com/node/5761
[[User:Zenoscope|zenoscope]]

This isn't currently possible without modifying the source code. That has been on my TODO list for ages [[User:PaulWise|pabs]] 01:17, 26 October 2007 (EDT)

=== Allow organize child valuenodes in an hierarchy ===
(3-2) And allow maintain the organization once the file is saved. Now they are reordered in alphabetical order what is very usefulness. --[[User:Genete|Genete]] 13:37, 29 October 2007 (EDT)

=== Triangle sliders to be always visible ===
(3) I would like that the triangle sliders from [[Colors Dialog]] and [[Gradient Editor Dialog]] were visible whatever color or channel you're editing. Some times when the color or channel is to bright or light the slider is difficult to distinguish. --[[User:Genete|Genete]] 14:30, 29 October 2007 (EDT)

=== XICC support ===

It would be cool if synfigstudio had support for [http://burtonini.com/blog/computers/xicc XICC].

=== Improved User Experience for First Contact ===
* Single file download and installer (at least for Windows)
* Ability to draw the first object directly after starting the application (start with an empty document)
* Ability to animate the object directly after drawing the first object (new documents have a say 3 seconds timeline)
In my opinion this is crucial to attract potential users. Because if I see how easy it is to create my first animation I'm going to accept all the bugs and clumsyness. A good example is the Pencil animation software. --[[User:Dmd|Dmd]] 13:50, 26 January 2008 (EST)

: I've implemented #2 and #3 above in svn r1519 & 1520. If no files are specified to be opened when running studio, it'll make a new one. It won't pop up the canvas properties dialog when making new canvases by default. And the default end time is 5s (3s is small enough to cause the time slider to show "1s 12f", whereas 5s looks cleaner). -- [[User:Dooglus|dooglus]] 04:00, 29 January 2008 (EST)

=== Area to Edit ===

08:43 < factor> also an option like blender - select area to update would be nice
08:44 < factor> so the only part of the image that updates whne you add or change someting is in the selected area
08:44 < factor> makes it quicker for doing changes

ie. when working on a complex composition, studio doesn't know, when I tweak a tiny part of the composition, that only that part needs redrawing, so it redraws the whole thing. It would be good if there was some way of telling it which part to focus on. -- [[User:Dooglus|dooglus]] 04:02, 3 February 2008 (EST)

=== Histograms ===

01:23 * AkhIL wish to have histograms and luma/color scope like [http://mac.softpedia.com/progScreenshots/Avid-Xpress-DV-Screenshot-14207.html] in synfig

I've looked at those pictures but don't know what they're showing. Can you describe what those scopes are doing, and what the histograms display? ie. what are the X and Y axes of the histograms? -- [[User:Dooglus|dooglus]] 04:07, 3 February 2008 (EST)

First look this description in blender wiki [http://wiki.blender.org/index.php/Manual/VSE_Modes]

Ok There is four things.
* Upper left is Lumascope (Luma Waveform in blender). X-Axis represents image's X-Axys. Y-Axis is average luminescence of column of pixels.
* Upper right is Chromascope (Chroma Vectorscope in blender). Just look description on blender wiki.
* Lower left is like Lumascope but for each channel
* Lower right is histograms. X is luminescence and Y is count of pixels with such luminiscence.

== Granted Wishes ==

=== MNG target filetype ===

The ability to save as/in the Free/Open MNG (.mng) format [http://libpng.org/pub/mng/]

A partial implementation was committed in SVN r470.

It was implemented in svn 986. See [[Render options]]. --[[User:Genete|Genete]] 13:12, 29 October 2007 (EDT)

=== Optionally display RGB in Hex in Color dialog ===

(3) When colors are quoted as 3 bytes of hexadecimal, you have to convert them to decimal, divide by 255, multiply by 100 to get a number to type into the dialog box. It's painful to match color schemes for example, with the [http://tango.freedesktop.org/Tango_Icon_Theme_Guidelines Tango Icon Theme style guidelines]. [[User:pxegeek|PXEGeek]] 3/16/07

: Added in [http://kibi.dyndns.org:8083/~dooglus/gitweb.pl?p=synfig;a=commitdiff;h=40dda9d27b5249ee32f62d84c819ff569f078929 svn r354]. You can type 3 or 6 digit hex codes and hit return to use. 3 digit code 36a gives colour 3366aa (each digit is duplicated) -- [[User:Dooglus|dooglus]] 3/18/07

:: Many thanks - already used many times! PXEGeek.

::: Did you notice that you can use single digit codes too? '5' gives 555555 for instance, giving you 16 equally spaces shades of black through white. -- [[User:Dooglus|dooglus]] 17:51, 25 September 2007 (EDT)

=== Restore Default Layout ===

(3) — It's very difficult to put all the dialogs back where they were when you started the program, if you've closed them. In addition, with many programs, if you've done something with your window manager to take a window's position off screen, this command is sometimes the only way to bring them back.
-> I'd like to second this one - especially with the bug where dialog boxes sometime shrink to nothing or offscreen, and no amount of maximizing or minimizing restores them. The only solution is to kill the windows, and none of the combo options in the dialog menu match the default configuration. 4/4/07 PXEGeek

: Implemented in [http://kibi.dyndns.org:8083/~dooglus/gitweb.pl?p=synfig;a=commitdiff;h=036306f3c2c265a604971728d50fcce258766552 svn r757] -- [[User:Dooglus|dooglus]] 17:48, 25 September 2007 (EDT)

File:Fake 3D-Vector Dot Product 5.png

2008-01-30T19:19:16Z

Yoyobuae: "Radius" parameter of the "Result Scalar" inside "Vector Dot Product" layer used in the Fake 3D tutorial.

"Radius" parameter of the "Result Scalar" inside "Vector Dot Product" layer used in the [[Fake 3D#Vector Dot Product|Fake 3D]] tutorial.

File:Fake 3D-Vector Dot Product 4.png

2008-01-30T19:08:54Z

Yoyobuae: "Vector List" of the "Result XYZ vector" inside "Vector Componentwise Multiply" layer used in the Fake 3D tutorial.

"Vector List" of the "Result XYZ vector" inside "Vector Componentwise Multiply" layer used in the [[Fake 3D#Vector Dot Product|Fake 3D]] tutorial.

File:Fake 3D-Vector Dot Product 3.png

2008-01-30T18:35:53Z

Yoyobuae: "Vector List" of the "LHS XYZ vector" inside "Vector Componentwise Multiply" layer used in the Fake 3D tutorial.

"Vector List" of the "LHS XYZ vector" inside "Vector Componentwise Multiply" layer used in the [[Fake 3D#Vector Dot Product|Fake 3D]] tutorial.

File:Fake 3D-Vector Dot Product 2.png

2008-01-30T18:28:18Z

Yoyobuae: Selecting the "LHS XYZ vector" inside "Vector Componentwise Multiply" layer used in the Fake 3D tutorial.

Selecting the "LHS XYZ vector" inside "Vector Componentwise Multiply" layer used in the [[Fake 3D#Vector Dot Product|Fake 3D]] tutorial.

File:Fake 3D-Vector Dot Product 1.png

2008-01-30T17:18:41Z

Yoyobuae: Corrected typo.

Resulting structure for the "Vector Dot Product" layer used in the [[Fake 3D#Vector Dot Product|Fake 3D]] tutorial.

File:Fake 3D-Vector Dot Product 1.png

2008-01-30T17:18:00Z

Yoyobuae: Resulting structure for the "Vector Componentwise Multiply" layer used in the Fake 3D tutorial.

Resulting structure for the "Vector Componentwise Multiply" layer used in the [[Fake 3D#Vector Dot Product|Fake 3D]] tutorial.

File:Fake 3D-Vector Component Multiply 3.png

2008-01-30T04:27:55Z

Yoyobuae: Resulting structure for the "Vector List" parameter of the "Result XYZ vector" object used in the Fake 3D tutorial.

Resulting structure for the "Vector List" parameter of the "Result XYZ vector" object used in the [[Fake 3D#Vector Componentwise Multiply|Fake 3D]] tutorial.

File:Fake 3D-Vector Component Multiply 2.png

2008-01-30T01:28:27Z

Yoyobuae: Changed a link's look

Resulting structure for the "Vector List" parameter of the "LHS XYZ vector" object used in the [[Fake 3D#Vector Componentwise Multiply|Fake 3D]] tutorial.

File:Fake 3D-Vector Component Multiply 2.png

2008-01-30T01:26:05Z

Yoyobuae: Resulting structure for the "Vector List" parameter of the "LHS XYZ vector" object used in the Fake 3D#Vector Componentwise Multiply tutorial.

Resulting structure for the "Vector List" parameter of the "LHS XYZ vector" object used in the [[Fake 3D#Vector Componentwise Multiply]] tutorial.

File:Fake 3D-Vector Component Multiply 1.png

2008-01-30T00:44:16Z

Yoyobuae: Resulting structure for the "Vector Componentwise Multiply" layer used in the Fake 3D tutorial.

Resulting structure for the "Vector Componentwise Multiply" layer used in the [[Fake 3D]] tutorial.

File:Fake 3D-Vector List.png

2008-01-30T00:42:50Z

Yoyobuae: Corrected typo.

Resulting structure for the "Vector List" parameter of the XYZ_vector used in the [[Fake 3D]] tutorial.

File:Fake 3D-Vector List.png

2008-01-29T23:45:02Z

Yoyobuae: Resulting structure for the "Vector List" parameter of the XYZ_vector used int Fake 3D tutorial.

Resulting structure for the "Vector List" parameter of the XYZ_vector used int [[Fake 3D]] tutorial.

Dev:Mingw installation

2008-01-22T02:06:30Z

Yoyobuae: /* [http://www.gnu.org/software/gettext Gettext] */

[[Category:Building]]
[[Category:Windows]]

==MinGW==
First - download [http://www.mingw.org/ MinGW] installer. You may get version 5.1.3 or higher (recommended).

* http://downloads.sourceforge.net/mingw/MinGW-5.1.3.exe (135.5 Kb)

Run MinGW-5.1.3.exe. Select "Download and install". Choose "Candidate" package, because "Current" is too old. When the installer asks which packages to install, select:

* MinGW base tools
* g++ Compiler
* g77 Compiler
* MinGW Make

Note: you really do need to install Fortran; even though Synfig does not require it, it is required by the autoconf configuration scripts. These are the minimal required package versions which are needed to successfully build win32 synfig:

* mingw-runtime-3.12.tar.gz (429.7 Kb)
* w32api-3.9.tar.gz (1.6 Mb)
* binutils-2.17.50-20060824-1.tar.gz (8.9 Mb)
* gcc-core-3.4.5-20060117-1.tar.gz (3.3 Mb)
* gcc-g++-3.4.5-20060117-1.tar.gz (4.5 Mb)
* gcc-g77-3.4.5-20060117-1.tar.gz (2.0 Mb)
* mingw32-make-3.81-2.tar.gz (95 Kb)

Confirm default installation path <code>C:\MinGW</code>. If you install MinGW into another directory, synfig compilation may fail.

===MSYS===
Now download and install MSYS - a shell and tools kit.

* http://downloads.sourceforge.net/mingw/MSYS-1.0.10.exe (2.7 Mb)

Run MSYS-1.0.10.exe, confirm default installation path <code>C:\msys\1.0</code>. Wait until installation completes. Then the installer opens a console and asks some questions.

''This is a post install process that will try to normalize between''<br />
''your MinGW install if any as well as your previous MSYS installs''<br />
''if any. I don't have any traps as aborts will not hurt anything.''<br />
''Do you wish to continue with the post install? [yn ]''

Answer "y" here.

''Do you have MinGW installed? [yn ]''

Answer "y" here.

''Please answer following the in the form of c:/foo/bar.''<br />
''Where is your MinGW installation?''<br />

Answer "<code>c:/mingw</code>".

The installer script prints some text and finally writes:

''Oh joy, you do not have c:/mingw/bin/make.exe. Keep it that way.''

It's OK. The first phase of installation is completed. Press any key.

===MSYS Developer Toolkit===
Download MSYS Developer Toolkit, which contain such required tools as [http://www.gnu.org/software/autoconf/ autoconf], [http://www.gnu.org/software/automake/ automake], [http://www.gnu.org/software/libtool/ libtool], [http://www.cpan.org/ perl], pkg-tools, etc. Unfortunately, many tools included in MSYS DTK is too old and we need update it manually later.

* http://downloads.sourceforge.net/mingw/msysDTK-1.0.1.exe (9.8 Mb)

Run msysDTK-1.0.1.exe. Confirm your MSYS installation path <code>C:\msys\1.0</code>. Nothing more. Installation will continue without any additional questions.

===bash===
The current bash version is not enough for Synfig building and neither is the new 2.05b version. It contains an error and you need to download 3.1 snapshot:

* http://downloads.sourceforge.net/mingw/bash-3.1-MSYS-1.0.11-snapshot.tar.bz2 (538.2 Kb)

Make sure that all msys sessions are closed, then just decompress bash-3.1 directory from archive into <code>C:\msys\1.0</code>.

Also, you may want to edit <code>C:\msys\1.0\msys.bat</code> file. You may find string which contain <code>if "x%MINGW32BGCOLOR%" == "x" set MINGW32BGCOLOR=</code> and set <code>Black</code> as color. Into <code>if "x%MINGW32FGCOLOR%" == "x" set MINGW32FGCOLOR=</code> you may set color <code>White</code>. In string <code>start rxvt -backspacekey</code> you may replace <code>-fn Courier-12</code> to <code>-fn Courier-16</code>. In my opinion this makes msys sessions look better.

===[http://www.gnu.org/software/autoconf/ autoconf]===
As written before, some tool are too old for Synfig build. For example, since revision 547 synfig required autoconf and automake, included in MSYS DTK are not acceptible. And we need replace them by new version.

Download new autoconf from:

* http://downloads.sourceforge.net/mingw/msys-autoconf-2.59.tar.bz2 (394.7 Kb)

Decompress content of archive to <code>C:\msys\1.0</code> directory.

===[http://www.gnu.org/software/automake/ automake]===
Download new automake from:

* http://downloads.sourceforge.net/mingw/msys-automake-1.8.2.tar.bz2 (304 Kb)

Decompress content of archive to <code>C:\msys\1.0</code> directory.

===[http://www.gnu.org/software/libtool/ libtool]===
In Synfig Core bootstrap file we can find that libtool prior to version 1.4.2 has an error in libltdl but msys has only 1.4e. I think - will be better to update it instead of patching. Download libtool 1.5 from:

* http://downloads.sourceforge.net/mingw/msys-libtool-1.5.tar.bz2 (411.3 Kb)

Decompress content of archive to <code>C:\msys\1.0</code> directory.

=== [http://www.gnu.org/software/gettext Gettext] ===
Starting from SVN 1143, Synfig offers support for internationalization (languages translations). For this, Gettext is needed. You'll need the [http://mirror.calvin.edu/cygwin/release/gettext/gettext-devel/ gettext-devel] package from the [http://www.cygwin.com/ Cygwin] project. Unpack the archive so that everything is under /usr/local instead of /usr. Note that any binaries that are not from the MinGW project or built specially for MSYS cannot be placed in the /msys/1.0/bin (/bin and /usr/bin inside MSYS) directory. You then need to hack the /usr/local/bin/autopoint script so that prefix is defined as /usr/local instead of /usr. Warning - ugly hack follows - Autopoint expects to find an archive.tar.gz in usr/share, so copy gettext (found on usr/share/ on the archive) file structure to /usr/share also.

===[http://www.mktemp.org/ mktemp]===
Synfig requires mktemp for building, but for some unknown reason this tool is not installed by default in MinGW. Download the MinGW implementation of this tool from:

* http://downloads.sourceforge.net/mingw/mktemp-1.5-MSYS.tar.bz2 (4 Kb)

Decompress mktemp.exe from this archive to <code>C:\msys\1.0\bin</code> directory.

===[http://darwinsys.com/file/ file]===
libtool requires the "file" tool to check filetypes of libraries. So we need to download it:

* http://downloads.sourceforge.net/mingw/file-4.16-MSYS-1.0.11-snapshot.tar.bz2 (236.2 Kb)

and decompress content of directory file-4.16 from the archive to <code>C:\msys\1.0</code>.

===cygpath emulation===
As far as I read, Cygwin only supports paths like /C/somedir/somefile. MinGW can use native windows paths also. Cygwin has a special tool for this (and some another features). MinGW has not. But several Synfig configure scripts require this tool so it will be better to make it. Just save the following text as <code>C:\msys\1.0\bin\cygpath</code>:

<pre>#!/bin/sh
# A simple cygpath replacement

until [ -z "$1" ]
do
if [ "${1:0:1}" != "-" ]; then
echo $1 | sed -e 's/\\/\//g' -e 's/^$[a-zA-Z]$:/\/\1/g'
fi
shift
done</pre>

===[http://www.winterdrache.de/freeware/png2ico/index.html png2ico]===
Early version of Synfig used [http://www.kernel.org/pub/software/graphics/pngtoico/ pngtoico] tool to produce icons from png files. Unfortunately this tool is broken now. You can see this for youeself by installing the official build of Synfig Studio 0.61.05. The latest versions of Synfig using another tool: png2ico. This tool is not perfect, but it works. Download it from:

* http://www.winterdrache.de/freeware/png2ico/data/png2ico-win-2002-12-08.zip (89.9 Kb)

And decompress png2ico.exe file to <code>C:\msys\1.0\bin</code> directory.

==Non MinGW packages==
===[http://subversion.tigris.org Subversion]===
Synfig source is stored in a subversion repository. You will need the svn client to get it. Also the svn client is required by the Synfig build scripts, to receive the revision number of the source.
You can download the Windows subversion package from this page:

* http://subversion.tigris.org/servlets/ProjectDocumentList?folderID=91

When I wrote this the latest version was 1.4.3:

* http://subversion.tigris.org/files/documents/15/36797/svn-1.4.3-setup.exe (3.58 Mb)

But it is best to get the newest available version.

===[http://sourceforge.net/projects/nsis/ NSIS]===
NSIS is the Nullsoft Scriptable Install System, a free and open source installer for WinAmp, a popular windows music player.
When I wrote this the latest version was 2.27:

* http://downloads.sourceforge.net/nsis/nsis-2.28-setup.exe (1.4 Mb)

You can use this or any newer version.

===[http://www.imagemagick.org ImageMagick]===
When I wrote this the latest version was 6.3.4-10:

* http://www.imagemagick.org/download/binaries/ImageMagick-6.3.4-10-Q16-windows-dll.exe (6.9 Mb)

ImageMagick is required to build Studio, also Core has an ImageMagick render target.

==Gtk+/Gtkmm==
===[http://www.gtk.org/ GTK+]===
Go to [http://gladewin32.sourceforge.net/modules/news/ this page] and download the latest GTK+ devel package for windows:

* http://gladewin32.sourceforge.net/modules/wfdownloads/visit.php?lid=110 (12 Mb)

You need only install the following components:

* Gtk+ Runtime (required)
* Register Environment Variables
* Devel header/libraries

Confirm registration for environment: ''MSYS (C:\msys\1.0)''.

Install GTK+ to <code>C:\GTK</code>.

===[http://www.gtkmm.org/ GTKmm]===
Go to [http://www.pcpm.ucl.ac.be/~gustin/win32_ports/ this page] and download the latest GTKmm devel package for Windows:

* http://ftp.gnome.org/pub/gnome/binaries/win32/gtkmm/2.10/gtkmm-win32-devel-2.10.8-1.exe (16.1 Mb)

You need only install the following components:

* libsigc++
* cairomm
* glibmm
* gtkmm
* libxml++

For each selected component you may keep only

* Runtime
* Development

subcategories. Install GTKmm to <code>C:\GTK</code>.

===Collision Resolution===
If you have several Gtk-applications (f.e. InkScape), you can receive a strange errors, like "''the procedure entry point XML_SetDoctypeDeclHandler could not be located in the dynamic link library xmlparse.dll''". Thats mean you have an old version of this library in windows system32 directory, installed by another program. Just search and rename/delete this old library and all will work perfectly again.

Dev:Building on Windows

2008-01-22T01:39:57Z

Yoyobuae: /* _src directory */

[[Category:Building]]

==Directories==
If you didn't already install Mingw, [[Mingw installation|this page]] will guide you through the process.

If you didn't already start an msys session, do so now. Just double click the MSYS shortcut or run <code>C:\msys\1.0\msys.bat</code>. An msys session will be opened, creating your profile directory at <code>C:\msys\1.0\home\<windows login></code>. As you can see, MinGW uses your windows login as the user name in its fake UNIX environment. Be careful, I've not checked whether it works with non latin-character account names.

Now, use explorer or your favorite file manager and go to <code>C:\msys\1.0\home\<windows login></code>. Create a directory there for all Synfig operations. For example, let it be <code>synfig</code>. Go into this directory.

Ok, now you are at <code>C:\msys\1.0\home\<windows login>\synfig</code>. Create four directories here:
* <code>_filez</code>, for patches (and maybe later, additional files).
* <code>_src</code>, for program sources.
* <code>build</code>, for building programs.
* <code>temp</code>, for local installation programs and libraries, which are required for building synfig. (For example: ETL, synfig (core for studio), OpenEXR, etc...)

Of course, you can choose your own name for all the directories and choose their locations. All you need then is to set a new path in the configuration file. But for now we choose the easy way.

==Files==
Save this configuration file as <code>C:\msys\1.0\home\<windows login>\synfig\synbuild.conf</code>:

<table style="padding: 1em; border: 1px dashed #2f6fab; color: Black; background-color: #f9f9f9; line-height: 1.1em;"><tr><td>
<pre># Synfig for Win32 build configuration script.
#############################################################################
# 1. Files and Directories

# Uncompressed Synfig svn snapshots and another package sources
SYN_SOURCE_DIR=`dirname ~/.`"/synfig/_src"

# Directory additional files (patches f.e.)
SYN_FILEZ_DIR=`dirname ~/.`"/synfig/_filez"

# Temporary installations (ETL headers, synfig binaries for icon and image making)
SYN_TEMP_INSTALL=`dirname ~/.`"/synfig/temp"

# Build directory
SYN_BUILD_DIR=`dirname ~/.`"/synfig/build"

# OpenEXR source package
SYN_OPENEXR_VERSION="1.4.0"
SYN_OPENEXR_SRC="${SYN_SOURCE_DIR}/openexr-${SYN_OPENEXR_VERSION}a.tar.gz"

#############################################################################
# 2. External tools

# Path to ImageMagick directory.
SYN_IMAGEMAGICK_PATH="/C/Program Files/ImageMagick"

# Path to Subversion bin directory.
SYN_SUBVERSION_PATH="/C/Program Files/Subversion/bin"

# Path to NSIS directory with makensis.exe file.
SYN_NSIS_PATH="/C/Program Files/NSIS"

#############################################################################
# 3. Build setup

# Build host
MINGW_HOST="mingw32"

# Make debug build of Synfig Core
SYN_CORE_DEBUG_BUILD="no"

# Make debug build of Synfig Studio
SYN_STUDIO_DEBUG_BUILD="yes"

#############################################################################
# 4. Patches (you can place here any additional patches)

# ETL patches
ETL_PATCHES=$(cat <<:END_ETL:
:END_ETL:)

# Synfig Core patches
SYNCORE_PATCHES=$(cat <<:END_SYNCORE:
:END_SYNCORE:)

# Sunfig Studio patches
SYNSTUDIO_PATCHES=$(cat <<:END_SYNSTUDIO:
:END_SYNSTUDIO:)

# OpenEXR patches
OPENEXR_PATCHES=$(cat <<:END_OPENEXR:
openexr-1.4.0-pkgconfig.patch
openexr-1.4.0-mingw32.patch
:END_OPENEXR:)

#############################################################################
# 5. Autoconfiguration

if [ "$GTK_BASEPATH" ]; then
CPPFLAGS="-I${GTK_BASEPATH}/include $CPPFLAGS"
fi

if [ "$SYN_IMAGEMAGICK_PATH" ]; then
PATH="${SYN_IMAGEMAGICK_PATH}:${PATH}"
fi

if [ "$SYN_SUBVERSION_PATH" ]; then
PATH="${SYN_SUBVERSION_PATH}:${PATH}"
fi

if [ "$SYN_NSIS_PATH" ]; then
PATH="${SYN_NSIS_PATH}:${PATH}"
fi

if [ -d "${SYN_TEMP_INSTALL}/ETL" ]; then
PATH="${SYN_TEMP_INSTALL}/ETL/bin:${PATH}"
PKG_CONFIG_PATH="${SYN_TEMP_INSTALL}/ETL/lib/pkgconfig:${PKG_CONFIG_PATH}"
fi

if [ -d "${SYN_TEMP_INSTALL}/synfig-devel" ]; then
PATH="${SYN_TEMP_INSTALL}/synfig-devel/bin:${PATH}"
PKG_CONFIG_PATH="${SYN_TEMP_INSTALL}/synfig-devel/lib/pkgconfig:${PKG_CONFIG_PATH}"
fi

if [ -d "${SYN_TEMP_INSTALL}/openexr" ]; then
PATH="${SYN_TEMP_INSTALL}/openexr/bin:${PATH}"
PKG_CONFIG_PATH="${SYN_TEMP_INSTALL}/openexr/lib/pkgconfig:${PKG_CONFIG_PATH}"
fi

export PATH
export PKG_CONFIG_PATH
export CPPFLAGS
</pre></td></tr></table>

Save OpenEXR build script as <code>C:\msys\1.0\home\<windows login>\synfig\make_openexr.sh</code>:
<table style="padding: 1em; border: 1px dashed #2f6fab; color: Black; background-color: #f9f9f9; line-height: 1.1em;"><tr><td>
<pre>#!/bin/sh

echo "Making OpenEXR..."
# Including configuration
if [ -r "./synbuild.conf" ]; then
. ./synbuild.conf
else
echo "No config file for synfig build (./synbuild.conf) found."
exit 1
fi

CURRENT_DIR=`pwd`

echo "Cleanup directories"
rm -rf ${SYN_BUILD_DIR}/openexr
[ $? -eq 0 ] || exit 1
rm -rf ${SYN_TEMP_INSTALL}/openexr
[ $? -eq 0 ] || exit 1

echo "Preparing sources"
tar -xzf ${SYN_OPENEXR_SRC} -C ${SYN_BUILD_DIR}
[ $? -eq 0 ] || exit 1

echo "Applying patches..."
cd ${SYN_BUILD_DIR}/openexr-${SYN_OPENEXR_VERSION}
[ $? -eq 0 ] || exit 1
for SFILE in ${OPENEXR_PATCHES[@]}
do
patch -p1 <${SYN_FILEZ_DIR}/${SFILE}
[ $? -eq 0 ] || exit 1
done

echo "Configuring"
[ $? -eq 0 ] || exit 1
./configure --host=${MINGW_HOST} --prefix=${SYN_TEMP_INSTALL}/openexr \
--disable-static --disable-threading --disable-posix-sem
[ $? -eq 0 ] || exit 1

echo "Making"
make
[ $? -eq 0 ] || exit 1
make install
[ $? -eq 0 ] || exit 1
cd ${CURRENT_DIR}
[ $? -eq 0 ] || exit 1
rm -rf ${SYN_BUILD_DIR}/openexr-${SYN_OPENEXR_VERSION}
[ $? -eq 0 ] || exit 1

echo "Done: OpenEXR"
</pre></td></tr></table>

Save ETL build script as <code>C:\msys\1.0\home\<windows login>\synfig\make_etl.sh</code>:
<table style="padding: 1em; border: 1px dashed #2f6fab; color: Black; background-color: #f9f9f9; line-height: 1.1em;"><tr><td>
<pre>#!/bin/sh

echo "Making ETL..."
# Including configuration
if [ -r "./synbuild.conf" ]; then
. ./synbuild.conf
else
echo "No config file for synfig build (./synbuild.conf) found."
exit 1
fi

CURRENT_DIR=`pwd`

echo "Cleanup directories"
rm -rf ${SYN_BUILD_DIR}/ETL
[ $? -eq 0 ] || exit 1
rm -rf ${SYN_TEMP_INSTALL}/ETL
[ $? -eq 0 ] || exit 1

echo "Preparing sources"
mkdir ${SYN_BUILD_DIR}/ETL
[ $? -eq 0 ] || exit 1
cp -R ${SYN_SOURCE_DIR}/ETL/* ${SYN_BUILD_DIR}/ETL/
[ $? -eq 0 ] || exit 1
cp -R ${SYN_SOURCE_DIR}/ETL/.svn ${SYN_BUILD_DIR}/ETL/
[ $? -eq 0 ] || exit 1

echo "Applying patches..."
cd ${SYN_BUILD_DIR}/ETL
[ $? -eq 0 ] || exit 1
for SFILE in ${ETL_PATCHES[@]}
do
patch -p1 <${SYN_FILEZ_DIR}/${SFILE}
[ $? -eq 0 ] || exit 1
done

echo "Configuring"
autoreconf -if
[ $? -eq 0 ] || exit 1
./configure --host=${MINGW_HOST} --prefix=${SYN_TEMP_INSTALL}/ETL
[ $? -eq 0 ] || exit 1

echo "Making"
make install
[ $? -eq 0 ] || exit 1
cd ${CURRENT_DIR}
[ $? -eq 0 ] || exit 1
rm -rf ${SYN_BUILD_DIR}/ETL
[ $? -eq 0 ] || exit 1

echo "Done: ETL"
</pre></td></tr></table>

Save Synfig Core build script as <code>C:\msys\1.0\home\<windows login>\synfig\make_core.sh</code>:
<table style="padding: 1em; border: 1px dashed #2f6fab; color: Black; background-color: #f9f9f9; line-height: 1.1em;"><tr><td>
<pre>#!/bin/sh

echo "Making Synfig-Core..."
# Including configuration
if [ -r "./synbuild.conf" ]; then
. ./synbuild.conf
else
echo "No config file for synfig build (./synbuild.conf) found."
exit 1
fi

CURRENT_DIR=`pwd`

echo "Cleanup directories"
rm -rf ${SYN_BUILD_DIR}/synfig-core
[ $? -eq 0 ] || exit 1
rm -rf ${SYN_TEMP_INSTALL}/synfig-devel
[ $? -eq 0 ] || exit 1

echo "Preparing sources"
mkdir ${SYN_BUILD_DIR}/synfig-core
[ $? -eq 0 ] || exit 1
cp -R ${SYN_SOURCE_DIR}/synfig-core/* ${SYN_BUILD_DIR}/synfig-core/
[ $? -eq 0 ] || exit 1
cp -R ${SYN_SOURCE_DIR}/synfig-core/.svn ${SYN_BUILD_DIR}/synfig-core/
[ $? -eq 0 ] || exit 1

echo "Applying patches..."
cd ${SYN_BUILD_DIR}/synfig-core
[ $? -eq 0 ] || exit 1
for SFILE in ${SYNCORE_PATCHES[@]}
do
patch -p1 <${SYN_FILEZ_DIR}/${SFILE}
[ $? -eq 0 ] || exit 1
done

echo "Configuring"
libtoolize --ltdl --copy -f
autoreconf -if
[ $? -eq 0 ] || exit 1
mkdir win32build
[ $? -eq 0 ] || exit 1
cd win32build
[ $? -eq 0 ] || exit 1
if [ "$SYN_CORE_DEBUG_BUILD" == "yes" ]; then
../configure --host=${MINGW_HOST} --prefix=C:/PROGRA~1/Synfig --disable-optimization --enable-debug
[ $? -eq 0 ] || exit 1
else
../configure --host=${MINGW_HOST} --prefix=C:/PROGRA~1/Synfig --enable-optimization=1 --disable-debug
[ $? -eq 0 ] || exit 1
fi

echo "Making"
# libtool hack patch [begin]
patch -p2 <${SYN_FILEZ_DIR}/synfig-core-hack-libtool.patch
[ $? -eq 0 ] || exit 1
# libtool hack patch [end]
make package
[ $? -eq 0 ] || exit 1
mv ./synfig-*.exe ${CURRENT_DIR}/
[ $? -eq 0 ] || exit 1

make clean
[ $? -eq 0 ] || exit 1
# auto build hack installation [begin]
make install prefix=${SYN_TEMP_INSTALL}/synfig-devel
[ $? -eq 0 ] || exit 1
# auto build hack installation [end]
cd ${CURRENT_DIR}

# auto build hack patch [begin]
echo "Postprocessing"
SYN_SED_PATH=`echo ${SYN_TEMP_INSTALL}/synfig-devel | sed -e 's/\//\\\\\//g'`
[ $? -eq 0 ] || exit 1
mv ${SYN_TEMP_INSTALL}/synfig-devel/bin/synfig-config ${SYN_TEMP_INSTALL}/synfig-devel/bin/synfig-config.tmp
[ $? -eq 0 ] || exit 1
sed -e "s/C:\/PROGRA~1\\/Synfig/${SYN_SED_PATH}/g" \
${SYN_TEMP_INSTALL}/synfig-devel/bin/synfig-config.tmp >${SYN_TEMP_INSTALL}/synfig-devel/bin/synfig-config
[ $? -eq 0 ] || exit 1
rm -f ${SYN_TEMP_INSTALL}/synfig-devel/bin/synfig-config.tmp
[ $? -eq 0 ] || exit 1
mv ${SYN_TEMP_INSTALL}/synfig-devel/lib/pkgconfig/synfig.pc ${SYN_TEMP_INSTALL}/synfig-devel/lib/pkgconfig/synfig.pc.tmp
[ $? -eq 0 ] || exit 1
sed -e "s/C:\/PROGRA~1\\/Synfig/${SYN_SED_PATH}/g" \
${SYN_TEMP_INSTALL}/synfig-devel/lib/pkgconfig/synfig.pc.tmp >${SYN_TEMP_INSTALL}/synfig-devel/lib/pkgconfig/synfig.pc
[ $? -eq 0 ] || exit 1
rm -f ${SYN_TEMP_INSTALL}/synfig-devel/lib/pkgconfig/synfig.pc.tmp
[ $? -eq 0 ] || exit 1
# auto build hack patch [end]

rm -rf ${SYN_BUILD_DIR}/synfig-core

echo "Done: synfig-core"
</pre></td></tr></table>

Save Synfig Studio build script as <code>C:\msys\1.0\home\<windows login>\synfig\make_studio.sh</code>:
<table style="padding: 1em; border: 1px dashed #2f6fab; color: Black; background-color: #f9f9f9; line-height: 1.1em;"><tr><td>
<pre>#!/bin/sh

echo "Making Synfig-Studio..."
# Including configuration
if [ -r "./synbuild.conf" ]; then
. ./synbuild.conf
else
echo "No config file for synfig build (./synbuild.conf) found."
exit 1
fi

CURRENT_DIR=`pwd`

echo "Cleanup directories"
rm -rf ${SYN_BUILD_DIR}/synfig-studio
[ $? -eq 0 ] || exit 1

echo "Preparing sources"
mkdir ${SYN_BUILD_DIR}/synfig-studio
[ $? -eq 0 ] || exit 1
cp -R ${SYN_SOURCE_DIR}/synfig-studio/* ${SYN_BUILD_DIR}/synfig-studio/
[ $? -eq 0 ] || exit 1
cp -R ${SYN_SOURCE_DIR}/synfig-studio/.svn ${SYN_BUILD_DIR}/synfig-studio/
[ $? -eq 0 ] || exit 1

echo "Applying patches..."
cd ${SYN_BUILD_DIR}/synfig-studio
[ $? -eq 0 ] || exit 1
for SFILE in ${SYNSTUDIO_PATCHES[@]}
do
patch -p1 <${SYN_FILEZ_DIR}/${SFILE}
[ $? -eq 0 ] || exit 1
done

echo "Configuring"
autoreconf -if
[ $? -eq 0 ] || exit 1
mkdir win32build
[ $? -eq 0 ] || exit 1
cd win32build
[ $? -eq 0 ] || exit 1
if [ "$SYN_STUDIO_DEBUG_BUILD" == "yes" ]; then
../configure --host=${MINGW_HOST} --prefix=C:/PROGRA~1/Synfig --disable-optimization --enable-debug
[ $? -eq 0 ] || exit 1
else
../configure --host=${MINGW_HOST} --prefix=C:/PROGRA~1/Synfig --enable-optimization=1 --disable-debug
[ $? -eq 0 ] || exit 1
fi

echo "Making"
make package
[ $? -eq 0 ] || exit 1

mv ./synfigstudio-*.exe ${CURRENT_DIR}/
[ $? -eq 0 ] || exit 1
cd ${CURRENT_DIR}
[ $? -eq 0 ] || exit 1
rm -rf ${SYN_BUILD_DIR}/synfig-studio
[ $? -eq 0 ] || exit 1

echo "Done: synfig-studio"
</pre></td></tr></table>

===_src directory===
Go to the <code>C:\msys\1.0\home\<windows login>\synfig\_src</code> directory. Get the latest sources of Synfig from its repository.

<blockquote><nowiki>$ svn co http://svn.voria.com/code/ETL/trunk/ ETL</nowiki><br />
<nowiki>$ svn co http://svn.voria.com/code/synfig-core/trunk/ synfig-core</nowiki><br />
<nowiki>$ svn co http://svn.voria.com/code/synfig-studio/trunk/ synfig-studio</nowiki></blockquote>

Note: The commands have a space between the URL address and the third paramater, it's easy to miss it. There should be three, space separated, paramaters in total after the "svn" command.

Download the current stable [http://www.openexr.com/ OpenEXR] version from:

* http://download.savannah.nongnu.org/releases/openexr/openexr-1.4.0a.tar.gz (9.22 Mb)

Finally you must have three directories (ETL, synfig-core and synfig-studio) and the openexr-1.4.0a.tar.gz file in your <code>_src</code> directory.

===_filez directory===
Save the following text as <code>C:\msys\1.0\home\<windows login>\synfig\_filez\synfig-core-hack-libtool.patch</code>:
<table style="padding: 1em; border: 1px dashed #2f6fab; color: Black; background-color: #f9f9f9; line-height: 1.1em;"><tr><td>
<pre>diff -Nuar synfig-core.orig/win32build/libtool synfig-core/win32build/libtool
--- synfig-core.orig/win32build/libtool Wed Feb 7 21:52:34 2007
+++ synfig-core/win32build/libtool Wed Feb 7 21:57:12 2007
@@ -2805,7 +2805,7 @@
fi
elif test "$build_libtool_libs" = yes; then
# Not a shared library
- if test "$deplibs_check_method" != pass_all; then
+ if test "$deplibs_check_method" != pass_all && test "$old_library" != "libltdl.a"; then
# We're trying link a shared library against a static one
# but the system doesn't support it.

</pre></td></tr></table>

Then save the following as <code>C:\msys\1.0\home\<windows login>\synfig\_filez\openexr-1.4.0-mingw32.patch</code>:
<table style="padding: 1em; border: 1px dashed #2f6fab; color: Black; background-color: #f9f9f9; line-height: 1.1em;"><tr><td>
<pre>diff -Nuar openexr-1.4.0.orig/IlmThread/Makefile.in openexr-1.4.0/IlmThread/Makefile.in
--- openexr-1.4.0.orig/IlmThread/Makefile.in Wed Aug 9 05:45:52 2006
+++ openexr-1.4.0/IlmThread/Makefile.in Wed Apr 18 20:31:58 2007
@@ -62,7 +62,8 @@
am_libIlmThread_la_OBJECTS = IlmThreadPool.lo IlmThread.lo \
IlmThreadSemaphore.lo IlmThreadMutex.lo IlmThreadPosix.lo \
IlmThreadSemaphorePosix.lo IlmThreadSemaphorePosixCompat.lo \
- IlmThreadMutexPosix.lo
+ IlmThreadMutexPosix.lo IlmThreadWin32.lo IlmThreadSemaphoreWin32.lo \
+ IlmThreadMutexWin32.lo
libIlmThread_la_OBJECTS = $(am_libIlmThread_la_OBJECTS)
DEFAULT_INCLUDES = -I. -I$(srcdir) -I$(top_builddir)/config
depcomp = $(SHELL) $(top_srcdir)/depcomp
</pre></td></tr></table>

Finally save the following as <code>C:\msys\1.0\home\<windows login>\synfig\_filez\openexr-1.4.0-pkgconfig.patch</code>:
<table style="padding: 1em; border: 1px dashed #2f6fab; color: Black; background-color: #f9f9f9; line-height: 1.1em;"><tr><td>
<pre>diff -Nuar openexr-1.4.0.orig/OpenEXR.pc.in openexr-1.4.0/OpenEXR.pc.in
--- openexr-1.4.0.orig/OpenEXR.pc.in Wed Aug 9 05:37:50 2006
+++ openexr-1.4.0/OpenEXR.pc.in Fri Apr 20 20:52:46 2007
@@ -7,5 +7,5 @@
Name: OpenEXR
Description: OpenEXR image library
Version: @OPENEXR_VERSION@
-Libs: -L${libdir} -lIlmImf -lImath -lHalf -lIex -lz @PTHREAD_LIBS@
-Cflags: @PTHREAD_CFLAGS@ -I${OpenEXR_includedir}
+Libs: -L${libdir} -lIlmImf -lImath -lHalf -lIex -lz
+Cflags: -I@includedir@ -I${OpenEXR_includedir}
</pre></td></tr></table>

==Configuration==
This section describes the parameters of <code>synbuild.conf</code> file.

===Files and Directories===
As you can see in this section you can define the path and name of the special directories (with sources, patches and temporary directories). If you install the build scripts as written above, there is nothing to change.

Also this section contains the path and version of the OpenEXR source files.

===External tools===
In this section you need to define the path to the executable files of the three auxiliary packages: ImageMagick, Subversion and NSIS. ImageMagick and Subversion binaries are located using the PATH environment variable, but their paths are added to the end of the path list and so we can get name collisions. For example, the ImageMagick "convert" tool has the same name as the "convert" tool from Borland Delphi Explorer, which may have been installed before ImageMagick.

===Build setup===
'''MINGW_HOST''' - host parameter of "configure" script. Do not change it.

'''SYN_CORE_DEBUG_BUILD''' - if "yes", Synfig Core will be made with debug info.

'''SYN_STUDIO_DEBUG_BUILD''' - if "yes", Synfig Studio will be made with debug info.

===Patches===
In this section you can find a number of patch definition blocks, looking like this:

<table style="padding: 1em; border: 1px dashed #2f6fab; color: Black; background-color: #f9f9f9; line-height: 1.1em;"><tr><td>
<pre># ETL patches
ETL_PATCHES=$(cat <<:END_ETL:
:END_ETL:)</pre></td></tr></table>

For example, if you place any filenames of patches between '':END_ETL:'' blocks, it will be applied before the configuration of ETL. Patch files need to be stored in the <code>_filez</code> directory.

This section is useful if you want to test your own patches before sending them to the Synfig developers.

===Autoconfiguration===
This section contatins code which sets up the required environment variables and (by default) there is no need to change anything.

==Build Order==
Note: If you want build synfig without slowing down other tasks running on the same machine while the build takes place, open a single msys session, then open "Task Manager", search for the ''sh.exe'' process and set its priority to "Below normal".

Note: Running an on-access antivirus scanner can dramatically decrease compilation speed.

===OpenEXR===
This package needs to be built only once. A rebuild is only required if you get a new version or want to apply a new patch to it or you update the compiler and it is incompatible with the previous binaries.

In your msys console go to the <code>C:\msys\1.0\home\<windows login>\synfig</code> directory by typing:

<blockquote><nowiki>$ cd ~/synfig</nowiki></blockquote>

Then type:

<blockquote><nowiki>$ ./make_openexr.sh</nowiki></blockquote>

Wait for the "Done: OpenEXR" message.

===ETL===
Rebuild it when you get a new version of Synfig.

In your msys console go to the <code>C:\msys\1.0\home\<windows login>\synfig</code> directory by typing:

<blockquote><nowiki>$ cd ~/synfig</nowiki></blockquote>

Then type:

<blockquote><nowiki>$ ./make_etl.sh</nowiki></blockquote>

Wait for the "Done: ETL" message.

===Synfig Core===
Rebuild it when you get a new version of Synfig.

In your msys console go to the <code>C:\msys\1.0\home\<windows login>\synfig</code> directory by typing:

<blockquote><nowiki>$ cd ~/synfig</nowiki></blockquote>

Then type:

<blockquote><nowiki>$ ./make_core.sh</nowiki></blockquote>

Wait for the "Done: synfig-core" message. It can take a long time. The Synfig Core installer will be moved into the current directory.

===Synfig Studio===
Rebuild it when you get a new version of Synfig.

In your msys console go to the <code>C:\msys\1.0\home\<windows login>\synfig</code> directory by typing:

<blockquote><nowiki>$ cd ~/synfig</nowiki></blockquote>

Then type:

<blockquote><nowiki>$ ./make_studio.sh</nowiki></blockquote>

Wait for the "Done: synfig-studio" message. It can take a long time. The Synfig Studio installer will be moved into the current directory.

==Additional tools==
These tools are not required to build Synfig, but they can help in the debugging process.

P.S. Post this later. ;-)

(Atrus - keen to hear what you recommend for debug. Also any debug processes you go through to fix the bugs. There's several bugs (mainly preview rendering) that I see under the current builds of Windows that are not under Linux or the old 0.61.05 for Windows - Pxegeek 2/7/07)

[[Category:Windows]]