rd: Render Layers
Version: 2.1 Sign up to be notified by email when a new version of this script is posted
This script renders each of the selected layers separately. You might find this script useful if layers represent different versions of an effect or different parts of an effect that you want to render as separate “passes” for flexibility in how they get composited.
Rendering uses existing render settings and output module template, so be sure to create them beforehand. When you run this script, you can select the templates to use; select the range of frames for each selected layer to render; control if unselected, adjustment, active camera, and light layers should be rendered as well; and define the name for each rendered output. Each rendered layer will generate separate “render finished” sounds.
The Output Name Template can be defined with the same properties available in the File Name Templates dialog box, with the following additions:
- [layerName] — Current layer’s name
- [layerNumber] — Current layer’s index number
Note: If you select an output template that uses a single-image format (such as Photoshop), be sure to include the [#####] property in the Output Name Template.
Note: If the layer is completely outside of the composition time range, the layer will not be rendered. However, if you select a range of Work Area and the layer is outside of the composition’s work area, the layer will still be rendered.
-
- rd_RenderLayers UI
Enhancements requested by Gary Jaeger and James Tobias.
Follow on Twitter
Join us on Facebook
Stay updated via RSS
Stay updated via email
How does this compare to Nucleo Pro 2′s ‘Commit to Disk’?
Hi Navarro… I’ve never used Nucleo Pro 2, but it sounds like theirs does stuff in the background automatically and replaces the layers. This script is on-demand, can render the work area, and won’t replace the layers automatically. Oh, and this one is cheaper.
Maybe others that have used both can chime in with their experience.
This script saved my life! (Well at least a weekend or two.)
Glad to hear that, Robert!
I LOVE this script. It is a huge time saver. THANK YOU!!!!!
Some recommendations for improvement if you decide to make a newer version:
1) Allow the user to create a custom Template from the “Output Name Template Box”. – It would be nice to be able to create a template ex: [layerNumber]_[layerName]_[##].[fileExtension] Then be able to save it and load it.
2) The OutputFolder Browse is a little bit cumbersome- it always starts at the “Desktop” level. The user then has to always manually click the location they desire. it would be a huge timesaver if we can save location presets- for example “E:\projects\myproject\output”
Or have it automatically choose the directory where the AE file is saved.
Just some suggestions. But otherwise this script is PERFECT! Thanks
-Koichi
Or a simpler fix would be the ability to save all the settings and load the settings you create.
Glad you like the script, Koichi. Thanks for the suggestions. I’ll keep them in mind for future versions of the script.
Jeff
Great script. Big Timesaver. We’re rendering out image sequences and would love to be able to shoot each layer to it’s own subfolder ideally named [compName]_[layerNumber]_[layerName]
Any thoughts?
hi rich… do you mean as a subfolder of the selected Output Folder? probably could be done by adding a new Output Subfolder field.
That’s exactly what we were thinking. We’d select our Output Folder, and the script would render each layer into its own subfolder ( named [layerNumber]_[layerName] ).
Seems like the add to queue option doesnt work, as you dont have the ability to turn layers visibility on and off once they are added. Just ends up rendering the comp as is over and over. Render immediately command works brilliantly though.
hi mang… thanks for reporting that bug. for some reason the person that originally requested it didn’t say anything and so i thought it was what he wanted for it. it’s a bit tricky to fix, as i’d have to duplicate the comp for each selected layer to have each one queued as intended.
Hey great script! I was wondering if there was a way to have the rendering layers be ‘obscured’ by the non-rendering layers? I’ve got Trapcode’s Lux that I need to render seperately but when the layer normally goes behind another, here it renders as if there’s nothing in the way. I’m probably missing something obvious, just wondering if you had any ideas.
Thanks
hi gregg,
could you use the Keep in Render = Unselected Layers option in some way?
Hi there. Basic question regarding the script;
If I have a comp with 20 layers, would I be able to render out 20 files (each layer) in one single render?
hi adamlewen,
yes, that’s the purpose of this script. if you’re unsure if the script will work for you, you can download it for free (enter $0), try it out, then if it works, download it again for whatever price you feel it’s worth. that the only way to evaluate a script right now.
thanks.
I will. And thanks for a quick reply!