<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>After Effects Scripts + After Effects Plugins &#187; Michael Cardeiro Scripts</title>
	<atom:link href="http://aescripts.com/category/scripts/michael-cardeiro/feed/" rel="self" type="application/rss+xml" />
	<link>http://aescripts.com</link>
	<description>The definitive collection of scripts and plugins for Adobe After Effects</description>
	<lastBuildDate>Thu, 17 May 2012 03:07:55 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>CompsFromSpreadsheet</title>
		<link>http://aescripts.com/compsfromspreadsheet/</link>
		<comments>http://aescripts.com/compsfromspreadsheet/#comments</comments>
		<pubDate>Wed, 12 Oct 2011 12:00:36 +0000</pubDate>
		<dc:creator>Michael Cardeiro</dc:creator>
				<category><![CDATA[Michael Cardeiro Scripts]]></category>
		<category><![CDATA[Automatic]]></category>
		<category><![CDATA[Comps]]></category>
		<category><![CDATA[CS3]]></category>
		<category><![CDATA[CS4]]></category>
		<category><![CDATA[CS5]]></category>
		<category><![CDATA[CS5.5]]></category>
		<category><![CDATA[Featured]]></category>
		<category><![CDATA[Lower Third]]></category>
		<category><![CDATA[Replace]]></category>
		<category><![CDATA[Spreadsheet]]></category>
		<category><![CDATA[Template]]></category>
		<category><![CDATA[Text]]></category>
		<category><![CDATA[Versioning]]></category>

		<guid isPermaLink="false">http://aescripts.com/?p=1496</guid>
		<description><![CDATA[Makes multiple versions of your compositions using information from a spreadsheet or database.   The script goes through your spreadsheet line by line, making a new version of your comp by replacing footage items and adding text supplied by the spreadsheet automatically.]]></description>
			<content:encoded><![CDATA[<table border="0" cellspacing="1" cellpadding="0">
<tbody>
<tr>
<td>
<h3>Automated Versioning of your Comps</h3>
<p>The compsFromSpreadsheet script allows you to quickly generate copies of your master comp with data from your spreadsheet used to update text or replace layers.</p>
<hr size="1" />
</td>
</tr>
<tr>
<td>
<h3>Getting Started</h3>
<p><img class="pic" src="http://aescripts.com/images/script_thumbs/mc/CompsFromSpreadsheet_v3_Images/p1rev.png" alt="" width="200" height="160" align="right" /><br />
Before you can use the script you need to setup one or more template compositions to receive data from your spreadsheet. There are three different ways your template comp can be updated from the spreadsheet</p>
<ul>
<li>Text layers that begin with <strong>^</strong>(shift 6) will be able to receive data from the spreadsheet as the text for that layer.<br />
If you need a line break in a text layer DO NOT put a line break in your spreadsheet cell as this will cause the script to think it is the end of that line of data. Instead use <strong>&lt;br&gt;</strong> and the script will replace that with a newline in your text layer</li>
<li>If you have a text layer named <strong>^date</strong> it will receive todays date (great if you&#8217;re generating slates)</li>
<li>If you have a non-text layer in your comp that begins with <strong>#</strong>, it will be replaced by the project item named in your spreadsheet</li>
<li>If you have a non-text layer in your comp that begins with <strong>&gt;</strong>, it will be replaced by a file. The script will import a file based on the path in your spreadsheet, then that imported file will replace the layer. If you have the same file referenced more than once in your spreadsheet, the script will only import it once and use that item for every other time the file is referenced</li>
</ul>
<p><em>If you are running the script as a dockable panel, there will be buttons to automatically create either a text, layer replace, or import object in the currently selected comp. When you create the layers this way a window will pop up asking for the name of the layer, do not put in the ^ &gt; or # in this window as After Effects will do this for you.</em></p>
<p><em> </em><em> So if you click on the button to create text object and type &#8220;title&#8221; in the window, After Effects will create a text layer named &#8220;^title&#8221; in the currently selected comp.</em></p>
<hr size="1" />
</td>
</tr>
<tr>
<td>
<h3>Setting up your Spreadsheet</h3>
<p style="text-align: center;"><img class="pic aligncenter" src="http://aescripts.com/images/script_thumbs/mc/CompsFromSpreadsheet_v3_Images/p2REV.png" alt="" width="490" height="160" /></p>
<p>The first line of your spreadsheet must contain the names for each column.<br />
When you run the script it will take each of these column names and and allow you to connect that column with elements in your template comp.</p>
<p>After you do this the script will go through the spreadsheet line by line, each line of the spreadsheet will become a new copy of one of your template comps, with data from that line of the spreadsheet updating the layers in the template comp copy that were targeted to receive it.</p>
<p>If you have set up more than one composition to receive data, you will need to have a column in your spreadsheet that holds the name of the comp to be used as the base. In the above sample spreadsheet the column &#8216;Core Spot&#8217; will be used, so when the script is run, for the first line of data it will create a copy of the comp named &#8220;spot 1&#8243; to be used for that line.</p>
<p><span style="color: #ff6600;"><strong>Very important:</strong></span> Before After effects can read your spreadsheet, it needs to be converted into a tab-delimited text file (most spreadsheet programs do this easily). This is a universal text format that will allow After effects to read in your data and organize it by rows and columns.</p>
<p>When you run the script be sure to point it to this newly created text file and not your spreadsheet as After Effects cannot read any spreadsheet format (maybe I should call the script compsFromTabDelimitedTextFile).</p>
<p><strong><em>A word about Commas</em></strong></p>
<p>If you have commas in your data, they will probably get stripped. Why? I believe it is a bug in Excel. There are two major types of delimited text documents, tab-delimited (which we are using) and comma delimited text. If using a comma-delimited format, commas are used to separate columns, if there happens to be a comma in your data, the program will need to strip them out prior to saving as they will be falsely interpreted as the end of that column.</p>
<p>If saving as tab-delimited, tabs would likewise need to be stripped out from your data. Commas are fine and should not be removed, as they are NOT a separator. Sadly, Excel still strips out commas, even when you are saving as a Tab-Delimited text file.</p>
<p>To overcome this limitation, if you need a comma in a text field write <strong>&lt;c&gt;</strong> and the script will replace that with a comma.</p>
<hr size="1" />
</td>
</tr>
<tr>
<td>
<h3>Running the Script</h3>
<p><img class="pic" src="http://aescripts.com/images/script_thumbs/mc/CompsFromSpreadsheet_v2_Images/p3.png" alt="" width="320" height="148" align="right" /><br />
compsFromSpreadsheet needs to know which comps in your project have been setup for use with the script.</p>
<p>When you run the script a window will pop up with all the comps in the project in the left column . Double click on the comp names that are to be used to move them to the right &#8220;selected comps&#8221; column. Click continue when you have added all the comps to be used to the &#8220;selected comps&#8221; column.</p>
<p>If you only have one comp this window is bypassed.</p>
<p><span style="color: #ff6600;">Tip:</span> If you put all your comps in a folder called TEMPLATES the script will bypass this window and assume that the comps in that folder are to be used.</p>
<hr size="1" />
</td>
</tr>
<tr>
<td>
<h3>Synching Column Data to your Comp</h3>
<p style="text-align: center;"><img class="pic aligncenter" src="http://aescripts.com/images/script_thumbs/mc/CompsFromSpreadsheet_v3_Images/p4REV.png" alt="" width="500" height="164" /><br />
When the script reads the first line of your spreadsheet, it needs you to tell it where the data from each column should go in your comp. The Field Init window opens. Each column name from the first line of the spreadsheet appears with a dropdown box underneath.</p>
<p>The dropdown box links the data from that column in the spreadsheet to elements in your template comps. The dropdown box contains the names of all the layers that were set up earlier to receive data (remember, the text layers that started with <strong>^</strong> will receive the data from this column, layers with a <strong>#</strong> will be replaced with the project item named in this column, and layers with <strong>&gt;</strong> will be replaced by files imported from the location specified in the column.)</p>
<p>If a column name is the same as an element name in one of your comps, that will be automatically selected in the dropdown i.e. If you have a column in your spreadsheet &#8220;phone&#8221; and a text layer in one of your template comps named &#8220;^phone&#8221;, that item will be automatically selected in the dropdown box. If however, your text layer is &#8220;^phone number&#8221; it will not be selected in the dropdown box.</p>
<p>If you have more than one comp to be used you will need to have a column in your spreadsheet with the name of the comp to be used for that line. Select &#8216;COMP&#8217; from the dropdown box of the column that holds comp names, if you only have comp to be used &#8216;COMP&#8217; will not appear in the dropdown as the script will already know which comp to use.</p>
<hr size="1" />
</td>
</tr>
<tr>
<td>
<h3>Importing Files Via Spreadsheet</h3>
<p><img class="pic" src="http://aescripts.com/images/script_thumbs/mc/CompsFromSpreadsheet_v3_Images/FilePath.png" alt="" width="210" height="200" align="left" /></p>
<p>You can have layers in your comps be replaced by files that are not in your project.</p>
<p>Any layer tht begins with <strong>&gt;</strong> will be replaced by a file imported from the path specified in your spreadsheet. To get the proper path format of a file click on the &#8220;Get File Path&#8221; button located in the main compsFromSpreadsheet window. When you click this button a window will pop up asking you to navigate to your file; when you click ok the proper path to this file will appear in a window that you can copy and then paste into your spreadsheet.</p>
<p>When the script runs it will import the file from the location specified in the spreadsheet and replace the layer. If you have the same file more than once in the spreadsheet it will only be imported once, and that copy will be used each time that particular file is referenced.</p>
<hr size="1" />
</td>
</tr>
<tr>
<td>
<h3>Naming Comps</h3>
<p><img class="pic" src="http://aescripts.com/images/script_thumbs/mc/CompsFromSpreadsheet_v2_Images/p5.png" alt="" width="294" height="188" align="right" /><br />
The next step you need to tell the script how to name the newly created sequence, and where you want the rendered sequences to go. The default naming convention is line number, so the name of the very first Comp is &#8220;2&#8243; ( because line 1 holds the column names). and the next comp created is called &#8220;3&#8243; and so on until it reaches the last line of the spreadsheet.</p>
<p>Alternately you can have the script keep the name of the original template comp and append a number to the end. so the first time the script creates a comp from &#8220;spotA&#8221; it is named &#8220;spotA_1&#8243;, next line that uses that comp will name the new comp &#8220;spotA_2&#8243;</p>
<p>Lastly, you can choose to get the name from one of your spreadsheet columns. So if you choose &#8220;FROM SPREADSHEET | name&#8221; from the dropdown, the comp will get its name from the &#8216;name&#8217; column of the spreadsheet.</p>
<hr size="1" />
</td>
</tr>
<tr>
<td>
<h3>Render Settings</h3>
<p><img class="pic" src="http://aescripts.com/images/script_thumbs/mc/CompsFromSpreadsheet_v3_Images/renderSet.png" alt="" width="280" height="230" align="right" /><br />
Every comp created by the script will be placed in the render que using the default settings for your render que. It will default to saving the renders in the same directory as your project.</p>
<p>If you click the &#8220;Render Settings&#8221; button (on the &#8220;field init&#8221; window) you can select which render setting and output module to use for the script and where to put the rendered files. If you check the &#8220;Remember Settings&#8221; box these settings will be used every time tyou run compsFromSpreadsheet; if not checked, these settings will be used in the current run.</p>
<hr size="1" />
</td>
</tr>
<tr>
<td>
<h3>Settings</h3>
<p><img class="pic" src="http://aescripts.com/images/script_thumbs/mc/CompsFromSpreadsheet_v3_Images/setting.png" alt="" width="220" height="200" align="right" /><br />
The settings button on the main UI panel allows you to change the default symbols the script uses to target layers in your Comps.</p>
<p>You can also set the number of columns that appear in the field init window.</p>
<p>And you can also change render settings from here.</p>
<hr size="1" />
</td>
</tr>
<tr>
<td>
<h3>Conclusion</h3>
<p>The script will run through your data line by line. For each line it will create a new copy of the template comp, put it in a folder called &#8220;compsFromSpreadsheet&#8221;, update any target layers in that comp with data from the current line, finally, the comp will be placed in the render que using render que defaults and set to render in the same directory as the project (unless you set a different render location in the field init window.</p>
<p>Hit the render button and all your newly created comps will render (go out for a pint while it renders!)</p>
<hr size="1" />
</td>
</tr>
<tr>
<td>
<h3>Dockable Panels</h3>
<p><img class="pic" src="http://aescripts.com/images/script_thumbs/mc/CompsFromSpreadsheet_v3_Images/ui.png" alt="" width="199" height="225" align="right" /></p>
<p>The script can either be run as a dockable panel or as a traditional script.</p>
<p>If run as a dockable panel, there will be buttons in the panel to create target text or layer objects to be used with the script. Clicking &#8220;Run compsFromSpreadsheet&#8221; will bring up the comp select window</p>
<p>If the script is run the traditional way (by accessing it through file &#8211; scripts), you will be taken to the comp select window immediately, bypassing the window shown here.</p>
<hr size="1" />
</td>
</tr>
<tr>
<td>
<div id="Licensing-Upgrades">
<h3>Licensing/Upgrades</h3>
<p>Starting with version 3.0, CompsFromSpreadsheet is now a licensed product.<br />
<span style="color: #ff6600;">Upgrade notice:</span> If you previously bought CompsFromSpreadsheet (before March 2011) you can receive a discount code equal to the same amount as you paid for it.<br />
To request this discount code please go <a href="http://license.aescripts.com/upgrade/?name=mc_CompsFromSpreadsheet+Script+for+Adobe+After+Effects" rel="shadowbox;width=400;height=480">here</a>.
</div>
<hr size="1" />
</td>
</tr>
</tbody>
</table>
<p><strong>Version History</strong></p>
<ul>
<li>v3.02 &#8211; Oct 2011
<ul>
<li><strong>Fixed orphan target layer bug</strong>: previously, when you were connecting spreadsheet columns to target layers in your comp, if you had a target layer not connected to a column, the script would not complain, but when it came to the unlinked target layer it would have an error and stop. Now the script will warn you if you have a target not connected to a column.  You can choose to go back and connect the target to a column, or ignore in which case the script will turn of any targeted layer not connected to a column.</li>
<li><strong>Fixed import layer bug</strong>: previously, if you had a layer name or path name misspelled in your spreadsheet, the error message would not show you the misspelled name, now it does.</li>
</ul>
</li>
<li>v3.01 Added error handling when importing corrupted files &#8211; July 2011</li>
<li>v3.0 &#8211; Feb 2011
<ul>
<li>Now allows you to have the script import files via a spreadsheet<br />
column</li>
<li>You can have the system auto select the column for comps to be used by changing the column name to &#8216;comp&#8217;.</li>
<li>User-definable special characters.</li>
<li>Inline help file</li>
<li>Many bug fixes</li>
</ul>
</li>
<li>v2.2 &#8211; Aug 2010
<ul>
<li>If a cell in the spreadsheet has &lt;br&gt;<br />
when the script is run it will replace the &lt;br&gt;<br />
with a carriage return.</li>
</ul>
</li>
<li>v2.12 &#8211; June 2010
<ul>
<li>Now arranges the field init into multiple rows if you have more that 10 fields (and that number is changeble through a &#8220;layout&#8221; button)</li>
</ul>
</li>
<li>v2.11 &#8211; May 2010
<ul>
<li>Small bug fix to new separate folder feature, now correctly places extension after frame number.</li>
</ul>
</li>
<li>v2.1 &#8211; May 2010
<ul>
<li>You can now choose to have renders go to separate folders, so if you are rendering a tiff sequence for example, each comp will be rendered to an individual folder.</li>
</ul>
</li>
<li>v2.01 &#8211; May 2010
<ul>
<li>Added file extension to output file name in render queue.</li>
</ul>
</li>
<li>v2.0 &#8211; May 2010
<ul>
<li>Added ability to insert footage items.</li>
<li>Added dockable UI.</li>
<li>Blessed for CS5.</li>
</ul>
</li>
<li>v1.22
<ul>
<li>Fixed a small bug that prevented the script from running on some non-english systems.</li>
</ul>
</li>
<li>v1.21
<ul>
<li>Fixed a bug in the program that caused the script not to run in certain situations. Previously, the script would try to create a folder called &#8220;Renders&#8221; in the same directory as your project to put your rendered files. The script no longer does this. Now there is a button in the field init window which allows you to designate a folder for renders. If you do not choose one, renders will go wherever your render que is set to put them.</li>
</ul>
</li>
<li>v1.2
<ul>
<li>The comp select window now uses scrolling lists to accommodate projects with a lot of comps. The way it works now is there is a list of all comps in the project on the left side of the window. Any comp you want to use, double click on it and it will go the the list on the right. The list on the right is all the comps to be used by the program.</li>
<li>If you create a folder called &#8216;TEMPLATES&#8217; the comp select window will be bypassed and the program will assume that all the comps in this folder are to be used.</li>
</ul>
</li>
<li>v1.1
<ul>
<li>Added the ability to choose the naming convention of new comps. Previously the comp was always named the line number of the database, now you can choose if you want line number, original comp name (with an incrementing number), or sync it up with a column in your spreadsheet.</li>
<li>Fixed a bug in the new version check.The function is only supposed to run once every 10 days, but the function checked every time the script was run. This has been corrected.</li>
</ul>
</li>
<li>v1.0 Initial Release</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://aescripts.com/compsfromspreadsheet/feed/</wfw:commentRss>
		<slash:comments>102</slash:comments>
		</item>
		<item>
		<title>Trajectory</title>
		<link>http://aescripts.com/trajectory/</link>
		<comments>http://aescripts.com/trajectory/#comments</comments>
		<pubDate>Tue, 26 Oct 2010 12:00:48 +0000</pubDate>
		<dc:creator>Michael Cardeiro</dc:creator>
				<category><![CDATA[Michael Cardeiro Scripts]]></category>
		<category><![CDATA[3D]]></category>
		<category><![CDATA[Align]]></category>
		<category><![CDATA[CS3]]></category>
		<category><![CDATA[CS4]]></category>
		<category><![CDATA[CS5]]></category>
		<category><![CDATA[CS5.5]]></category>
		<category><![CDATA[Distribute]]></category>
		<category><![CDATA[Null]]></category>
		<category><![CDATA[Points]]></category>
		<category><![CDATA[Trajectory]]></category>

		<guid isPermaLink="false">http://aescripts.com/?p=1777</guid>
		<description><![CDATA[Align all layers in a composition evenly on a line between 2 nulls with delay controls for animation.]]></description>
			<content:encoded><![CDATA[<p><img class="size-full wp-image-1779 alignleft" src="http://aescripts.com/wp/wp-content/uploads/2010/01/trajectory.gif" alt="" width="200" height="200" /></p>
<p>The trajectory script will take all layers in a composition and plot them evenly on a line between 2 nulls.</p>
<h3>Getting Started</h3>
<p>Install the script in the scripts folder.  To run the script, simply select the layers you would like to be linked in the trajectory and select the script from the File-&gt;Scripts menu.  When the script is run, it will take all layers in the selected composition and make them 3d. It then creates 3 nulls, 2 of these nulls are used to create the trajectory along which all layers lie and the third null is a control layer which will be discussed in a moment.  <span><br />
The 3 nulls must be the last 3 layers in the comp, and the control layer must be the last layer in the comp.</span></p>
<p><img class="alignright size-medium wp-image-1778" src="http://aescripts.com/wp/wp-content/uploads/2010/01/t1-300x134.png" alt="" width="300" height="134" /></p>
<p>You can move the 2 nulls named &#8220;startPosition&#8221; and &#8220;endPosition&#8221; and all the layers in your comp will disperse evenly on a line between the 2 nulls.</p>
<p>Add keyframes to the nulls position and the layers will follow.</p>
<h3>Control Layer</h3>
<p>The &#8220;controlLayer&#8221; null controls the rotation and opacity of the layers. The &#8220;Transform Delay&#8221; slider allows you to offset each layers reaction to changes in the control layer&#8230;so if you have xRotation on the controlLayer keyframed from frame 1 to 10 and offset set to 5, layer 1 will do the xRotation from frame 1 to 10; layer 2 will transform from 6 to 15; and layer 3 will transform from frame 11 to 20.</p>
<p><a href="http://aescripts.com/wp/wp-content/uploads/2010/10/control_layer.png" rel="shadowbox[sbpost-1777];player=img;"><img class="alignright size-full wp-image-2851" src="http://aescripts.com/wp/wp-content/uploads/2010/10/control_layer.png" alt="" width="250" height="170" /></a></p>
<p>The reverse delay checkbox will cause the delay to go from last layer to first layer instead of first to last.</p>
<p>Check the &#8220;Disable Control&#8221; checkbox if you would like to individually control these parameters from each layer insted of the control layer.</p>
<h3>Compress Expand</h3>
<p><a href="http://aescripts.com/wp/wp-content/uploads/2010/10/compress.gif" rel="shadowbox[sbpost-1777];player=img;"><img class="alignleft size-full wp-image-2850" src="http://aescripts.com/wp/wp-content/uploads/2010/10/compress.gif" alt="" width="200" height="400" /></a><br />
The compress expand slider allows you to dynamically lengthen or shorten the length of your trajectory. A positive number will lengthen your line, a negative number will shorten it. a value of zero will give you a normal trajectory where the first layer will have the same position as the startPosition null and your last layer will have the same position as the endPosition null.</p>
<h3>Adding Layers to your Trajectory<a href="http://aescripts.com/wp/wp-content/uploads/2010/01/control.gif" rel="shadowbox[sbpost-1777];player=img;"><img class="alignright size-full wp-image-1781" src="http://aescripts.com/wp/wp-content/uploads/2010/01/control.gif" alt="" width="200" height="200" /></a></h3>
<p>If you want to add a layer from your project to a trajectory comp, simply duplicate any layer in the comp that is not a null, select the dup, and alt+drag the item and drop it on the selected layer and it will become part of the trajectory.</p>
<h3>Using Trajectory Comp in another Comp</h3>
<p>If you put your trajectory comp inside your main comp and enable &#8220;collapse transformations&#8221; for that layer, your trajectory comp will become part of the scene and react to cameras.</p>
<p><strong>Version History</strong></p>
<ul>
<li>2.51 Added new slider on the control null that allows you to lengthen and shorten (compress-expand) the length of the line. Thanks to Dan Ebberts for help with the code &#8211; 10/2010</li>
<li>2.01 Blessed for CS5 and updated to run in any language not just english. Thanks to: François Cora for the French translation and Jakob Behrends for the German translation &#8211; 06/2010</li>
<li>2.0 Initial release on aescripts.com &#8211; 01/2010</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://aescripts.com/trajectory/feed/</wfw:commentRss>
		<slash:comments>21</slash:comments>
		</item>
		<item>
		<title>Matrix</title>
		<link>http://aescripts.com/matrix/</link>
		<comments>http://aescripts.com/matrix/#comments</comments>
		<pubDate>Tue, 03 Aug 2010 15:26:25 +0000</pubDate>
		<dc:creator>Michael Cardeiro</dc:creator>
				<category><![CDATA[Michael Cardeiro Scripts]]></category>
		<category><![CDATA[3D]]></category>
		<category><![CDATA[Automatic]]></category>
		<category><![CDATA[CS3]]></category>
		<category><![CDATA[CS4]]></category>
		<category><![CDATA[CS5]]></category>
		<category><![CDATA[CS5.5]]></category>
		<category><![CDATA[Layers]]></category>
		<category><![CDATA[Matrix]]></category>

		<guid isPermaLink="false">http://aescripts.com/?p=2345</guid>
		<description><![CDATA[Takes a layer in your comp and breaks it into pieces. You choose the size of the pieces, whether to animate in order or random, and how long you want the transition to take.]]></description>
			<content:encoded><![CDATA[<table border="0" cellspacing="1" cellpadding="1">
<tbody>
<tr>
<td valign="top"><img class="pic" src="http://aescripts.com/images/script_thumbs/mc/Matrix_images/image1a.gif" alt="" width="400" height="267" align="left" /></td>
</tr>
<tr>
<td>The Matrix script will take a layer in your comp and break it into pieces. You choose the size of the pieces, whether to animate in order or random, and how long you want the transition to take.</td>
</tr>
<tr>
<td>
<h3>Getting Started</h3>
<p>The script is designed to be used as a dockable panel, <a class="option" title="This script has an embedabble UI.  Script installation video tutorial:" href="#inline-sample-1" rel="shadowbox;width=805;height=505">click here for a quick tutorial on installation</a></p>
<p>You need to begin with a comp with a single layer. This will be the layer that will be chopped up. The options for the effect are as follows:</p>
<table border="0">
<tbody>
<tr>
<td valign="top">
<table border="0">
<tbody>
<tr>
<td>
<h4>Transition Type</h4>
<p><em>Animate in:</em> the pieces of your image will start at a Z point in space that you choose and will end at 0.</p>
<p><em>Animate Out:</em> the pieces will start at position Z 0 and will end at a Z point in space that you choose.</td>
</tr>
<tr>
<td>
<h4>Order</h4>
<p><em>Random:</em> Pieces will animate in random order. When this option is chosen an additional field &#8220;Transition Min&#8221; appears in the interface; the script will make the transition lenght a random value between Transition Min and Transition Length</p>
<p><em>Directional:</em>Pieces will animate in order. When this option is chosen two additional fields Delay Across and Delay Down appear</td>
</tr>
<tr>
<td>
<h4>Fragment Size X and Y</h4>
<p>The size of the pieces that the image will break into. <strong><em>If you choose very small pieces it can take a long time to build. Use caution<br />
</em></strong></td>
</tr>
<tr>
<td>
<h4>Gap</h4>
<p>How many pixels of space between pieces. 0 leaves no gap, a higher number will cause space between the individual pieces</td>
</tr>
<tr>
<td>
<h4>Target Z</h4>
<p>Z position where the pieces will either start or finish (depending on whether you are animating out or animating in)</td>
</tr>
<tr>
<td>
<h4>Rotation XYZ</h4>
<p>Rotation XYZ where the pieces will either start or finish (depending on whether you are animating out or animating in)</td>
</tr>
<tr>
<td>
<h4>Start Frame</h4>
<p>Which frame in your comp to start the animation. If your order is Random, this is the earliest frame a piece will start animating.</td>
</tr>
<tr>
<td>
<h4>Start Variation</h4>
<p>Only visible if your order is Random. All pieces will start animating at a random frame between &#8216;Start Frame&#8217; and &#8216;Start Frame&#8217; + &#8216;Start Variation&#8217;. For example, if &#8216;Start Frame&#8217; is 10 and &#8216;Start Variation&#8217; is 5, every piece in your matrix will begin animating at a random frame between 10 and 15</td>
</tr>
<tr>
<td>
<h4>Transition Length</h4>
<p>The amount of time it takes for an individual piece to go from 0 to target Z (or vice versa depending on whether you are animating out or in) . If your order is Random, this is longest possible time for an individual piece to animate, and Transition minimum is the shortest.</td>
</tr>
<tr>
<td>
<h4>Transition Min</h4>
<p>Only visible if your order is Random. this is the shortest possible time for an individual piece to animate, and Transition Length is the longest.</td>
</tr>
<tr>
<td>
<h4>Delay Across</h4>
<p>Only visible if your order is Directional. On each row, the pieces start their animation one after the other, this is how many frames before the next one in a row starts.</td>
</tr>
<tr>
<td>
<h4>Delay Down</h4>
<p>Only visible if your order is Directional. On each column, the pieces start their animation one after the other, this is how many frames before the next one in a column starts.</td>
</tr>
<tr>
<td>
<h4>Fade</h4>
<p>If checked, when a piece animates it will either fade out or fade in (Depending on animation type)</td>
</tr>
<tr>
<td>
<h4>Ease Keyframe</h4>
<p>Makes the transition smoother by easing the keyframes</td>
</tr>
<tr>
<td>
<h4>Motion Blur</h4>
<p>enables motion blur for all layers</td>
</tr>
</tbody>
</table>
<p>When you have all parameter set, hit the &#8220;Build Matrix&#8221; button. The script will only run if you are in a composition with only 1 layer. (after you build it you may re-edit its parameters, but this is done through the edit button which will be discussed later).</td>
<td><img class="pic" src="http://aescripts.com/images/script_thumbs/mc/Matrix_images/interface.png" alt="" width="230" height="828" /><br />
<img class="pic" src="http://aescripts.com/images/script_thumbs/mc/Matrix_images/exampleBar.gif" alt="" width="230" height="700" /></td>
</tr>
</tbody>
</table>
</td>
</tr>
<tr>
<td>
<h3>What Happens When I Hit Build Matrix</h3>
<p>The script precomposes your master layer (unless it already is a precomp). Then the script makes as many solids as it needs to cover your comp from top left to bottom right. It duplicates your master layer for each of these solids, parents and track mattes to the solid and animates the solid based on your settings. All the master layer duplicates are made shy. The master layer is duplicated one final time and placed at the top of the timeline with the eyeball turned off. This layer is not made shy and is there to make it easier to access the preconp that housed your original layer.<br />
There are two layers at the very bottom of the comp that are shy and locked. These layers should not be touched, they are used by the script if you want to change any parameters.</td>
</tr>
<tr>
<td>
<h3>Editing A Matrix</h3>
<p>If you have built a matrix and want to change any of the parameters, click the edit button while you are in that composition. A window will popup with all the parameters that were used in that matrix build. You will not be able to do anything else in After Effects until the popup window is closed. If you hit cancel, the popup will close and nothing will happen. If you hit Rebuild Matrix, the matrix will be rebuilt using the parameters set in the popup.</td>
</tr>
<tr>
<td><strong> Version History</strong></p>
<ul>
<li>Initial release &#8211; Aug 2010</li>
</ul>
</td>
</tr>
</tbody>
</table>
]]></content:encoded>
			<wfw:commentRss>http://aescripts.com/matrix/feed/</wfw:commentRss>
		<slash:comments>10</slash:comments>
		</item>
		<item>
		<title>SpellCheck</title>
		<link>http://aescripts.com/spellcheck/</link>
		<comments>http://aescripts.com/spellcheck/#comments</comments>
		<pubDate>Tue, 20 Oct 2009 15:00:28 +0000</pubDate>
		<dc:creator>Michael Cardeiro</dc:creator>
				<category><![CDATA[Michael Cardeiro Scripts]]></category>
		<category><![CDATA[AE7]]></category>
		<category><![CDATA[CS3]]></category>
		<category><![CDATA[CS4]]></category>
		<category><![CDATA[CS5]]></category>
		<category><![CDATA[CS5.5]]></category>
		<category><![CDATA[Spell Checker]]></category>
		<category><![CDATA[Type]]></category>

		<guid isPermaLink="false">http://aescripts.com/?p=1257</guid>
		<description><![CDATA[Goes through the currently selected composition, and any precomp contained within and checks every text layer for proper spelling.]]></description>
			<content:encoded><![CDATA[<p>Okay, I admit it&#8230;I am a horibal uhm horrible speller; but I thankfully grew up in the age of computer aided spell checking. Unfortunately, Adobe After Effects never included this feature. Every time a new release was announced I would anxiously await the arrival of this much needed feature&#8230;but it never came.</p>
<p>I finally decided to take matters into my own hands. I used the scripting functionality in After Effects to build my own spellchecker. The script goes through the currently selected composition, and any precomp contained within and checks every text layer for proper spelling.</p>
<p>If a word is misspelled, the script will give you the opportunity to enter in the propper spelling or get a suggestion. The spell suggestion comes from my website. I originally had the script come up with suggestions but it was taking nearly 15 seconds per word, so I created a script on my website using perl (which gets the suggestion very quickly). When you click on the suggest button, your computer connects to my website and gives it the misspelled word. The script on my website then gives the spell check script a list of suggestions.</p>
<p>Please note that even though this script has a UI, it is installed in the Scripts folder not in the ScriptUI Panels folder.</p>

<a href='http://aescripts.com/wp/wp-content/uploads/SpellCheck-UI.png' rel='shadowbox[sbalbum-1257];player=img;' title='SpellCheck UI'><img width="150" height="150" src="http://aescripts.com/wp/wp-content/uploads/SpellCheck-UI-150x150.png" class="attachment-thumbnail" alt="SpellCheck UI" title="SpellCheck UI" /></a>

]]></content:encoded>
			<wfw:commentRss>http://aescripts.com/spellcheck/feed/</wfw:commentRss>
		<slash:comments>22</slash:comments>
		</item>
	</channel>
</rss>

