Re: Image Sequence file paths from JS

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

Article #154

Back to adobe.after.effects.scripting.render Previous Next

#154

From: Harold_Hausman
Date: Mon, 13 Oct 2008 23:33

3 lines
832 bytes

They indeed are, and with some string manipulation they can be divined.

The C++ api provides nice "Get Path at Frame" functionality however. :D

Technical Details

Message-ID: <59b672f6.1@webcrossing.la2eafNXanI>

Path:

arc1-ca.pugleaf.net!g2news1.google.com!news1.google.com!news2.google.com!lightspeed.eweka.nl!81.171.88.16.MISMATCH!eweka.nl!hq-usenetpeers.eweka.nl!news4us.nl!webcrossing

References: <59b672f6.-1@webcrossing.la2eafNXanI>

Show Full Headers

Complete Article Headers

X-Google-Thread: 1efebe,bcc0648e6410c007
X-Google-Attributes: gid1efebe,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
From: Harold_Hausman@adobeforums.com
Newsgroups: adobe.after.effects.scripting.render
Subject: Re: Image Sequence file paths from JS
Message-ID: <59b672f6.1@webcrossing.la2eafNXanI>
Date: Mon, 13 Oct 2008 16:33:40 -0700
References: <59b672f6.-1@webcrossing.la2eafNXanI>
Lines: 3
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
Path: arc1-ca.pugleaf.net!g2news1.google.com!news1.google.com!news2.google.com!lightspeed.eweka.nl!81.171.88.16.MISMATCH!eweka.nl!hq-usenetpeers.eweka.nl!news4us.nl!webcrossing

Reply to Parent Message