VIDEO DEMO/TUTORIAL

HOW TO USE

Launch the earlier version of After Effects (CS3 or later) and run OpenSesame. Click Import Project, then choose the exported OS project file.

NOTE:Some parts of projects can’t be exported due to scripting limitations. The following features aren’t currently supported:

• Paint, Rotobrush and Puppet Pin effects.
• Text style support is CS4+ only and doesn’t include features like kerning, vertical and paragraph text, or multiple text styles on one layer.
• Proxies.
• Custom data values. Effect properties with custom data values can’t be exported, such as the Levels Histogram and the Hue/Saturation effect. In these cases you could use the Levels (Individual Controls) and Color Balance (HLS) effects instead.

TRIAL VERSION:

Version History

• 1.01 – Added support for legacy OS X 10.4 PPC systems – Jan 2012
• 1.0 – Initial release – Jan 2012

Version History

• v2.3 (01/12)
  • Select Shortcut File button option.
  • Minor typo fixes.
• v2.2 (09/11)
  • Optimized icon creation.
  • Now CS3 compatible.
• v2.1.07 (08/11)
  • Non English AE Shortcut file can be used now.
  • Fixed #252/#288 error on Windows 7 64bit systems.
  • Adjusted “+searchTRANSLATION+” file verification.
  • Minor bug fixes.
  • Added German localization for buttons.
• 2.02 – Fixed prefs path on Win7 (5/11)
• 2.0 – Initial release on aescripts.com (5/11)

Features

• Unlimited Search/Replace pairs
• Add Suffix and Prefix
• Replace all at once or one item at a time
• Option to use Regular Expressions (Regex)

Scopes (Where you can rename items)

• Project panel item names
• Layer names project-wide
• Layer names in comps selected in project panel
• Selected layers in active comp
• Render queue footage paths

Version History

• 1.0 – Initial release – Jan 2012

New features in v2.3:

Version history

• 2.3 – Jan 2012
  • now works on layers that have been transformed/animated.
  • option to use null controllers.
  • various improvements / bug fixes.
• 2.2 Added CS5 compatibility – may 2010
• 2.1 Added AE6.5 and AE7 compatibility – dec 2009
• 2.0 Initial release on aescripts.com – dec 2009

New features in version 1.3:

New features in version 1.2:

• Adds support for the SubRip subtitle file format.
• Support for RightToLeft languages.
• Vertical text alignment.

HOW TO USE:

1. Create a new composition with the correct format for your output.
2. Subtitles are created using the settings in the Character/Paragraph panels, so create a sample text layer first and change the font, size and alignment as required. For example, you may want the text alignment in the Paragraph panel set to “Center Text”. You can then delete the text layer.
3. Run the script, choose the subtitle format, then click Import Subtitles and select the file to import.
4. To change the text size or style after import, select the imported text layer and change the settings in the Character/Paragraph panels as required. Then delete the subtitle layer and use the script to import it again.
5. Drag the subtitle layer to the bottom of the comp, using the Title Safe comp guides if necessary.
6. Then you have the option to:
• Render the with an alpha channel, import into your editing software and put the subtitles onto your video.
• Import the video into After Effects and place under the subtitle layer, then render the result.
• With Premiere Pro you just need to save your AE project, then you can drag the subtitle comp from AE’s project panel directly into Premiere Pro’s project panel, and from there, into the edit.

Version history

• 1.3 – Jan 2012
  • CS5.5 compatibility.
  • recreates italic and bold style tags in .srt files.
  • bottom alignment option.
  • use vertical or paragraph style text.
  • fixes some timing errors.
• 1.2 Support for the SubRip format, RightToLeft languages and vertical text alignment – Dec 2010
• 1.1 Added CS5 compatibility – May 2010
• 1.0 Initial release – Dec 2009

New features in version 3.0:

• Now imports Karafun Studio (.kfn) files.
• New basic presets which import and render much faster.
• Animated text crawl option.
• Highlight, timing and non-english language bug fixes.

Upgrade notice: If you bought pt_SSAKaraokeAnimator in the last year (between Jan 04, 2011 and Jan 03, 2012) you can receive a discount code equal to the full 100% amount of what you originally paid for it. If you bought it before Jan 4, 2011 you can get a discount code equal to 50% of what you paid.  To request this discount code please go here.

 

Version History

• 3.0 – Jan 2012
  • Now imports Karafun Studio (.kfn) files.
  • New basic presets which import and render much faster.
  • Animated text crawl option.
  • Highlight, timing and non-english language bug fixes.
• 2.3 Initial release on aescripts.com – Dec 2010

Edge blending is a clever solution to build up panoramic projections with 2 or more projectors. Some very expensive projectors include this capability and with play-out softwares that can mimic it programmatically. But if you don’t have one of these high end projectors you need to find some other solution. At an event this happened to us too. They were expensive projectors but one of them lacked this feature. So we developed this script to solve this problem. And cheaply!

In After Effects you have to do a panoramic composition (for example: 3x 1024×768 = 3072×768). Keep in mind: the resulting composition will be smaller due to the overlapping areas, but it is easier to work with the full size.

After this preparation you have to run the script and you have to answer two questions:

• How many slices do you want? (ex: 3)
• How wide will the blending area be? (ex.: 200)

After these two answers the script will build up your panoramic setup that will be ready to render. You will find a big composition what looks like this:

Once projected it will blend together like this:

You can use this big file to project it through a DualHead or TripleHead or any other solution. The only thing you have to do is calibrate your projectors to align the picture correctly. (A calibration pattern is included with the script).

Final result at an event:

A brief introduction video:

Really useful for creating stereoscopic 3D work with After Effects and Trapcode.
Peder Norrby, Trapcode

More than a Camera:

The Stereo 3D Toolkit is more than a 3D camera. It is a set of tools that enable you to create complex stereoscopic compositions inside of after effects.

New features in version 1.5:

• Total hierarchy update system
• Cinema 4D integration!
• Revised UI
• Streamlined controls and expressions
• Supports multiple S3D hierarchies in a single project
• Includes S3D camera for Cinema 4D (11.5+)
• Fixed 3D Glasses bug in CS5.5

True Left and Right Channels:

The Stereo 3D Toolkit uses true left and right channels instead of collapse transformations. Because of this, it is compatible with all 3D effects and plug-ins that utilize composition cameras. Effects like Particular, Form and Plexus come through with true stereo 3D depth.

Ease of use:

The Stereo 3D Toolkit is designed to make managing complex hierarchies simple. The tools enable you to work on the left channel and automatically update the right channel. Nested pre-comps are given embedded cameras that are locked to the master system, so all of the pieces in your hierarchy stay in perfect sync no matter how complex it gets.

Compatibility:

The Stereo 3D Toolkit is compatible with After Effects CS4, CS5, and CS5.5.

Stereo 3D Toolkit vs CS5.5 built in 3d camera:

Although After Effects CS5.5 comes bundled with a stereoscopic camera, it uses collapse transformations to create the left and right channels. For plug-ins that utilize composition cameras separate left and right channels are required to see the true stereoscopic depth.

Full Tutorials

Stereo 3D Toolkit v1.5 Tutorial Part 1: After Effects Mode

Stereo 3D Toolkit v1.5 Tutorial Part 2: Cinema 4D Mode

Version History:

• 1.7 – Dec 2011
  • New camera rig for C4D R13 with real-time anaglyph preview
  • Additional code optimization
• 1.6 – Dec 2011
  • Compatible with all language packs
  • Expanded menu size to accommodate longer composition names
• 1.5 – Oct 2011
  • Total hierarchy update system
  • Cinema 4D integration!
  • Revised UI
  • Streamlined controls and expressions
  • Supports multiple S3D hierarchies in a single project
  • Includes S3D camera for Cinema 4D (11.5+)
  • Fixed 3D Glasses bug in CS5.5
• 1.1 – Fixed site license registration bug – Aug 2011
• 1.0 – Initial Release – July 2011

It works by retrieving the binary string of an image file (can be any kind of file), but does not convert to hex or base 64. You can use this script to get the binary string in order to embed the icons of a user interface in the script code. The size of the image to be converted and the time it takes will depend on the performance of your computer but small images or icons will convert very quickly. The script has several output options. You can get just the binary string or you can get .jsx examples of how to embed the code into your scripts.

Version History

• 1.0 – Initial release – Dec 2011

This script has 2 core functions. The first, Pins To Nulls, creates and places nulls where AE Puppet Tool pins are located on the selected layer. If you’re a frequent Puppet Tool user you know what a pain in the butt it is to animate with, especially when you have a lot of pins and separate layers of artwork. Hopefully this null workflow makes things a bit easier.

Limitations: Right now, the script only works on a single mesh. (planned for future versions)

The second function, Loop Precomp, does exactly what the name implies. It was designed to automate the process of looping animation cycles. Basically, it time remaps the selected precomp and applies an endless loop expression to it.

Limitations: This script only works on one layer at a time. (planned for future versions)

INSTALLATION

Place gg_PuppetTools.jsx in the ScriptUI Panels folder.  Click on the UI button on the top right for an installation tutorial if necessary.

Run After Effects. Under the Windows menu, find gg_PuppetTools at the bottom and run it. You can also dock the script window for handy retrieval later.

USAGE

Once you have positioned your artwork in comp and placed your Puppet Tool pins, you’re ready to go. Give your pins meaningful names (i.e. elbow, wrist) as the script will retain them in the nulls.

Select the layer with the Puppet Tool effect applied to it and press the Pins To Nulls button – BOOM! If you need to reposition your rig after the fact, the script creates an extra  ”Parent” null to do that. Just parent all the controller nulls to it and you’re all set.

The Loop Precomp button is very straightforward. Select the layer you want to loop and blammo, it shall be done.

For more details and image please download the manual.

CREDITS

Myriad thanks to Jeff Almasol (redefinery.com) and Lloyd Alvarez for the help and inspiration.

The script will loop any amount of selected layers from the furthest in-point and the last out-point by pre-composing and doing a dissolving loop. It will then apply an expression to the looped comp so that it can be stretched infinitely from either the in or the out-point.

There is an option to use the Blend effect instead of using opacity to make the dissolve an optical dissolve.

HOW TO USE:

• Select the layers you want to loop.
• Trim the in-point and out-point of the layers to where you would like the loop to be.
• Run the script from the Window menu
• Choose the dissolve length in frames
• **Please note that you should use the Blend Effect option when looping items that are transparent

The script is now localized in the following languages, (if you would like to contribute a translation please get in touch):

• es: Español
• ja: Japanese (Thanks Tatsuro Ogata)
• ko: Korean
• de: Deutsch (Thanks Mathias Möhl)
• fr: Français (Thanks Sébastien Périer)

Version History:

• 1.6 Added “cycle” and “Ping-Pong” loop types – Oct 2011
• 1.54 Fixed small parsing error – Jan 2011
• 1.53 Fixed french localization bug – Oct 2010
• 1.52 Fixed loop pre-comp name length bug in CS3 – May 2010
• 1.51 Fixed language support for CS3 – May 2010
• 1.5 – May 2010
  • Added dockable UI
  • Made it work with non-english AE
  • Blessed for CS5
  • Several small bug fixes
• 1.1 Now works properly with transparent items using the blend effect – Mar 2010
• 1.0 Initial Release – Feb 2010

Automated Versioning of your Comps

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.

Getting Started

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

• Text layers that begin with ^(shift 6) will be able to receive data from the spreadsheet as the text for that layer.
  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 <br> and the script will replace that with a newline in your text layer
• If you have a text layer named ^date it will receive todays date (great if you’re generating slates)
• If you have a non-text layer in your comp that begins with #, it will be replaced by the project item named in your spreadsheet
• If you have a non-text layer in your comp that begins with >, 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

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 ^ > or # in this window as After Effects will do this for you.

So if you click on the button to create text object and type “title” in the window, After Effects will create a text layer named “^title” in the currently selected comp.

Setting up your Spreadsheet

The first line of your spreadsheet must contain the names for each column.
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.

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.

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 ‘Core Spot’ will be used, so when the script is run, for the first line of data it will create a copy of the comp named “spot 1″ to be used for that line.

Very important: 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.

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

A word about Commas

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.

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.

To overcome this limitation, if you need a comma in a text field write <c> and the script will replace that with a comma.

Running the Script

compsFromSpreadsheet needs to know which comps in your project have been setup for use with the script.

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 “selected comps” column. Click continue when you have added all the comps to be used to the “selected comps” column.

If you only have one comp this window is bypassed.

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

Synching Column Data to your Comp

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.

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 ^ will receive the data from this column, layers with a # will be replaced with the project item named in this column, and layers with > will be replaced by files imported from the location specified in the column.)

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 “phone” and a text layer in one of your template comps named “^phone”, that item will be automatically selected in the dropdown box. If however, your text layer is “^phone number” it will not be selected in the dropdown box.

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 ‘COMP’ from the dropdown box of the column that holds comp names, if you only have comp to be used ‘COMP’ will not appear in the dropdown as the script will already know which comp to use.

Importing Files Via Spreadsheet

You can have layers in your comps be replaced by files that are not in your project.

Any layer tht begins with > 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 “Get File Path” 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.

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.

Naming Comps

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 “2″ ( because line 1 holds the column names). and the next comp created is called “3″ and so on until it reaches the last line of the spreadsheet.

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 “spotA” it is named “spotA_1″, next line that uses that comp will name the new comp “spotA_2″

Lastly, you can choose to get the name from one of your spreadsheet columns. So if you choose “FROM SPREADSHEET | name” from the dropdown, the comp will get its name from the ‘name’ column of the spreadsheet.

Render Settings

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.

If you click the “Render Settings” button (on the “field init” 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 “Remember Settings” box these settings will be used every time tyou run compsFromSpreadsheet; if not checked, these settings will be used in the current run.

Settings

The settings button on the main UI panel allows you to change the default symbols the script uses to target layers in your Comps.

You can also set the number of columns that appear in the field init window.

And you can also change render settings from here.

Conclusion

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 “compsFromSpreadsheet”, 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.

Hit the render button and all your newly created comps will render (go out for a pint while it renders!)

Dockable Panels

The script can either be run as a dockable panel or as a traditional script.

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 “Run compsFromSpreadsheet” will bring up the comp select window

If the script is run the traditional way (by accessing it through file – scripts), you will be taken to the comp select window immediately, bypassing the window shown here.

Version History

• v3.02 – Oct 2011
  • Fixed orphan target layer bug: 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.
  • Fixed import layer bug: 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.
• v3.01 Added error handling when importing corrupted files – July 2011
• v3.0 – Feb 2011
  • Now allows you to have the script import files via a spreadsheet
    column
  • You can have the system auto select the column for comps to be used by changing the column name to ‘comp’.
  • User-definable special characters.
  • Inline help file
  • Many bug fixes
• v2.2 – Aug 2010
  • If a cell in the spreadsheet has <br>
    when the script is run it will replace the <br>
    with a carriage return.
• v2.12 – June 2010
  • Now arranges the field init into multiple rows if you have more that 10 fields (and that number is changeble through a “layout” button)
• v2.11 – May 2010
  • Small bug fix to new separate folder feature, now correctly places extension after frame number.
• v2.1 – May 2010
  • 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.
• v2.01 – May 2010
  • Added file extension to output file name in render queue.
• v2.0 – May 2010
  • Added ability to insert footage items.
  • Added dockable UI.
  • Blessed for CS5.
• v1.22
  • Fixed a small bug that prevented the script from running on some non-english systems.
• v1.21
  • 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 “Renders” 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.
• v1.2
  • 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.
  • If you create a folder called ‘TEMPLATES’ the comp select window will be bypassed and the program will assume that all the comps in this folder are to be used.
• v1.1
  • 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.
  • 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.
• v1.0 Initial Release

This is a package of 6 7 scripts:

1. Create3DBox.jsx – Watch demo video
2. Create3DSphere.jsx – Watch demo video
3. Create3DCylinder.jsx – Watch demo video
4. Create3DPyramid.jsx – Watch demo video
5. Create3DMengerSponge.jsx – Watch demo video
6. Create3DFallingDominoes.jsx – Watch demo video
7. Create3DPlatonicSolid.jsx – Watch demo video

They create the 3D shape using user-defined comp layers. Assign a layer to each side, and the script will position and scale them to build the shape of given size. Note that the same layer can be used for multiple sides. An option allows to parent each side layer to a Null 3D positioned at the center of the shape.

Version History:

• v3.3 Data entry bug and foreign language compatibility with CS5.5 – Nov 2011
• Create3DPlatonicSolid v1.0 – Initial release (Aug 2010)
• Create3DBox v2.6 – Handles text justification and CS5 compatibility (Aug 2010)
• Create3DCylinder v2.6 – Code cleanup and CS5 compatibility (Aug 2010)
• Create3DFallingDominoes v1.6 – Code cleanup and CS5 compatibility (Aug 2010)
• Create3DMengerSponge v2.6 – Code cleanup and CS5 compatibility (Aug 2010)
• Create3DPyramid v2.1 – Handles text justification and CS5 compatibility (Aug 2010)
• Create3DSphere v3.2 – Code cleanup and CS5 compatibility (Aug 2010)
• Create3DSphere v3.1 – Resources folder is in parenthesis to speed up loading (Feb 2010)
• Create3DSphere v3.0 (Feb 2010)
• • Allows to distribute layers on sphere or ellipsoid (e.g. rugby ball, with controllable x,y,z-radius)
  • Gain in speed using precomputed arrangements
  • Can create giant sphere with up to 1000 layers, in couple of seconds
• Create3DSphere v2.5 – Initial version on aescripts.com (Jun 2009)
• Create3DBox v2.5 – Initial version on aescripts.com (Jun 2009)
• Create3DCylinder v2.5 – Initial version on aescripts.com (Jun 2009)
• Create3DFallingDominoes v1.5 – Initial version on aescripts.com (Jun 2009)
• Create3DMengerSponge v2.5 – Initial version on aescripts.com (Jun 2009)
• Create3DPyramid v2.0 – Initial version on aescripts.com (Jun 2009)

**Please note: This tutorial uses an earlier version of TrackerViz, however, the principles are still the same. Please stay tuned as a new tutorial will be coming soon.

Data can come from layers position data, from tracking data or from path data.

Details on each function are given below. Note that some tool tips also provide information.

Average Position:
Creates a new solid layer at the center of the selected layers (or track points).

Position & Rotation:
Creates a new solid layer at the first selected layer (or track point) position, and rotates it towards the second selected layer (or track point).

Position & Scale:
Creates a new solid layer at the first selected layer (or track point) position, and scales it so that its size matches the distance between the two selected layers (or track points).

Position & Rotation & Scale:
Creates a new solid layer at the first selected layer (or track point) position, rotates it towards the second selected layer (or track point) and scales it so that its size matches the distance between the two selected layers (or track points).

Track Combine:
Creates a new layer that combines the selected layer (or track point) position with the position of its parent layer.

Corner Pin:
Creates a new comp-sized solid with the Corner Pin effect applied to it. The four corners are linked to the position of the four selected layers (or track points) (in the following order: UpperLeft-UpperRight-LowerLeft-LowerRight).

CC Power Pin:
Same as above except that the CC Power Pin effect is used instead of the Corner Pin effect.

Shape To Tracker:
Associates each vertex of the selected mask path with a new track point.

Shape To Layers:
Creates a new solid at each vertex of the selected mask path (the mask path can be animated).

Track Points To Shape:
Transforms the selected track points into an animated mask path.

Layers To Shape:
Creates a new mask path for which the vertices are linked to the position of the selected layers.

Version History

• v3.2 Fixed foreign language compatibility with CS5.5 – Nov 2011

• Add Parented Null to Selected Layers.jsx will create a new null and parent all the selected layers to it.
• Add Parented Null to Each Selected Layer.jsx will create a parented null for each of the selected layers. The new null can have a custom name defined in the User Variables section and also has the option of including the name of the layer that is parented to it.