🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: adobe.after.effects.scripting.render
Article #54

(aerender -i) retaining frame numbers on filenames

#54
From: Patrick_Hearn
Date: Wed, 18 Mar 2009 17:11
20 lines
1538 bytes
Hi,
When using aerender with the -i parameter to increment frames I've discovered it will name the files sequentially, rather than by the frame number:
eg.
aerender ... -i 5
File0001.tif frame 1
File0002.tif frame 6
File0003.tif frame 11
etc.

Is it possible to change the behaviour for this?

This leads me to a second question: is much time wasted skipping existing frames? My plan was to avoid machines having to skip frames by hvign them start on different frames and increment:
eg
Machine 1 :: -s 1 -i 3
Machine 2 :: -s 2 -i 3
Machine 3 :: -s 3 -i 3

So 3 evenly matched machines could run through the animation without ever 'bumping into' one another. If there would be any difference in overhead by avoiding checking for existing frames then I feel this method could be advantageous.

I'd be interested to know if this would have any effect.
Technical Details
Message-ID: <59b85171.-1@webcrossing.la2eafNXanI>
Path: arc1-ca.pugleaf.net!g2news1.google.com!news3.google.com!news2.google.com!npeer02.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!newshub.sdsu.edu!webcrossing

Show Full Headers
Complete Article Headers
X-Google-Thread: 1efebe,265255c576922020,start
X-Google-Attributes: gid1efebe,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
From: Patrick_Hearn@adobeforums.com
Path: arc1-ca.pugleaf.net!g2news1.google.com!news3.google.com!news2.google.com!npeer02.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!newshub.sdsu.edu!webcrossing
Newsgroups: adobe.after.effects.scripting.render
Subject: (aerender -i) retaining frame numbers on filenames
Message-ID: <59b85171.-1@webcrossing.la2eafNXanI>
Date: Wed, 18 Mar 2009 10:11:19 -0700
Lines: 27
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit