From: "Louai Abu-Osba" <AE-List@media-motion.tv>
MIME-Version: 1.0
Date: Tue, 21 Jul 2015 10:29:24 -0400
Message-ID: <CABan1zMwCKHHaYMvYew_BZ75_M1d6oz4HQnMU_xi=dPBJOJizA@mail.gmail.com>
Subject: Python used to exist in AE/PS?!
To: After Effects Mail List <AE-List@media-motion.tv>
Content-Type: multipart/alternative; boundary=001a1147f09ed56ead051b637c3b

--001a1147f09ed56ead051b637c3b
Content-Type: text/plain; charset=UTF-8

Hello All,

As we continue our grand pipeline integrations at High 5 Games we have a
need to export animation from AE and package it up as an FBX file. We're
exploring a few paths to this, including opening an AE project in C4D and
then exporting FBX. We're also looking at writing our own FBX exporter with
the the Python FBX SDK so we have better control of the export pipeline.

One of my developers is still living in the fantasy land of denial of
trying to use Python directly with After Effects (and tried to do so via
COM, like you can with Photoshop). I told him to give it up and accept that
ExtendScript had to dump out the data and then Python could take over. In
his Googling he found this article, written by a former Adobe employee (who
seemed to be quite a interesting person):
http://conferences.oreillynet.com/cs/os2001/view/e_sess/1327

So it appears that 14 years ago Python was binded to the PS and AE API's.
I'm sure that if these plugins still exist now they certainly won't work
with current versions of the apps, but I'm curious if it's still
technically possible to generate bindings of the PS/AE C++ SDKs to CPython?
Anyone from Adobe care to let me know if this is worth my time or a
hopeless, foolish endeavor?

Currently, AE/PS are the only major DCC apps that do not have a Python
scripting layer and/or API binding.

-louai

--001a1147f09ed56ead051b637c3b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hello All,<div><br></div><div>As we continue our grand pip=
eline integrations at High 5 Games we have a need to export animation from =
AE and package it up as an FBX file. We&#39;re exploring a few paths to thi=
s, including opening an AE project in C4D and then exporting FBX. We&#39;re=
 also looking at writing our own FBX exporter with the the Python FBX SDK s=
o we have better control of the export pipeline.</div><div><br></div><div>O=
ne of my developers is still living in the fantasy land of denial of trying=
 to use Python directly with After Effects (and tried to do so via COM, lik=
e you can with Photoshop). I told him to give it up and accept that ExtendS=
cript had to dump out the data and then Python could take over. In his Goog=
ling he found this article, written by a former Adobe employee (who seemed =
to be quite a interesting person):</div><div><a href=3D"http://conferences.=
oreillynet.com/cs/os2001/view/e_sess/1327">http://conferences.oreillynet.co=
m/cs/os2001/view/e_sess/1327</a><br></div><div><br></div><div>So it appears=
 that 14 years ago Python was binded to the PS and AE API&#39;s. I&#39;m su=
re that if these plugins still exist now they certainly won&#39;t work with=
 current versions of the apps, but I&#39;m curious if it&#39;s still techni=
cally possible to generate bindings of the PS/AE C++ SDKs to CPython? Anyon=
e from Adobe care to let me know if this is worth my time or a hopeless, fo=
olish endeavor?</div><div><br></div><div>Currently, AE/PS are the only majo=
r DCC apps that do not have a Python scripting layer and/or API binding.</d=
iv><div><br></div><div>-louai=C2=A0<br></div></div>

--001a1147f09ed56ead051b637c3b--