Return-Path: Received: from p02c11o149.mxlogic.net ([208.65.144.82] verified) by media-motion.tv (CommuniGate Pro SMTP 4.2.10) with ESMTP-TLS id 5121373 for AE-List@media-motion.tv; Wed, 26 Jun 2013 16:54:50 +0200 Received: from unknown [216.57.150.10] (EHLO exchangecashub.crameronline.com) by p02c11o149.mxlogic.net(mxl_mta-7.1.0-3) over TLS secured channel with ESMTP id 2230bc15.0.93397.00-337.249105.p02c11o149.mxlogic.net (envelope-from ); Wed, 26 Jun 2013 09:05:13 -0600 (MDT) X-MXL-Hash: 51cb03296be0b1f8-17aaf4204a6396f89f53bbb3b91b13e888efee03 Received: from EXCHANGEMBX.cramerdom.com ([172.16.1.55]) by EXCHANGECasHub.cramerdom.com ([172.16.1.25]) with mapi id 14.03.0123.003; Wed, 26 Jun 2013 11:05:06 -0400 From: Michael Powers To: After Effects Mail List Subject: RE: [AE] How the future of Adobe Scripting should look like Thread-Topic: [AE] How the future of Adobe Scripting should look like Thread-Index: AQHOccae9yV1ytTxfUaoSleif3W07JlIGGCg Date: Wed, 26 Jun 2013 15:05:05 +0000 Message-ID: <8C6FE228180FE143B942B993AE2E1C74636AD84C@EXCHANGEMBX.cramerdom.com> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.10.1.15] Content-Type: multipart/alternative; boundary="_000_8C6FE228180FE143B942B993AE2E1C74636AD84CEXCHANGEMBXcram_" MIME-Version: 1.0 X-AnalysisOut: [v=2.0 cv=VeJAyiV9 c=1 sm=1 a=92rrH11NjGMdhXfoADi2UA==:17 a] X-AnalysisOut: [=rtz_HrNLLBsA:10 a=4s1us-Xx_w8A:10 a=fvH1djJbZqEA:10 a=BLc] X-AnalysisOut: [eEmwcHowA:10 a=G7-xRGy1AAAA:8 a=ERUe88dTAAAA:8 a=wY6DUrIDY] X-AnalysisOut: [P0A:10 a=dikKMlusAAAA:8 a=vJFYNkglAAAA:8 a=y_XA6cHsfel-zIB] X-AnalysisOut: [yZ3MA:9 a=wPNLvfGTeEIA:10 a=OonaxcEz02kA:10 a=qobl88wXUncH] X-AnalysisOut: [bVxr:21 a=Z5GXBa8YuGzn6mpq:21 a=fIDVoZbaI4gK4uf7tOIA:9 a=U] X-AnalysisOut: [iCQ7L4-1S4A:10 a=hTZeC7Yk6K0A:10 a=_W_S_7VecoQA:10 a=frz4A] X-AnalysisOut: [uCg-hUA:10 a=tXrfEsfaIjkA:10 a=xgkE7e_0EPieiQFk:21 a=nFShN] X-AnalysisOut: [YJgm4uaC6x9:21 a=1wDIcnPSpaMKBymB:21] X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010122901)] X-MAIL-FROM: X-SOURCE-IP: [216.57.150.10] --_000_8C6FE228180FE143B942B993AE2E1C74636AD84CEXCHANGEMBXcram_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Excellent. Thnx. For light duty scripters, like myself, it would also be helpful to have a "= listener window" like the one found in 3dsMax, which shows Maxscript code f= or most all UI actions. This makes generating new scripts a breeze in max. = For more involved scripting 3dsMax's far superior documentation is always a= t hand. From: After Effects Mail List [mailto:AE-List@media-motion.tv] On Behalf Of= S=E9bastien Sent: Tuesday, June 25, 2013 1:08 PM To: After Effects Mail List Subject: [AE] How the future of Adobe Scripting should look like Hi guys, I was thinking of how Adobe should push forward our scripting abilities and= wrote a long post about it here: http://mytho.mn/future-adobe-scripting/ I think it's somehow a big topic, now that we are on the way on unified wor= kflows between all the apps. As an AE scripter, my views are probably biased, but let's discuss about it= here to maybe build a better future ;) If you don't like links, here is a copy/paste of my post: We need scripting to change Today, each Adobe application have it's own scripting language, and it's ow= n set of UI API, and this is a big obstacle for us, to come with new and ex= citing scripts and extentions for our beloved applications. With the Creative Cloud, Adobe is touting the synergy between all it's flag= ship apps, the connected and seamless workflows from After Effects to Premi= ere, from Story to Audition, and yet, we can't design scripts that can take= advantage of that. In the center of this seemless ideology there is metada= ta, but even for that, we don't have the handy tools. The all we can eat model In order to help us build impressive tools to make your applications sexier= , we desperatly need some improvements, and now that we're all under the Cr= eative Cloud shiny name, it's time to shape that future all together. And s= ince you want us to access all your application to discover new possibiliti= es, it's time for me (us ?) to ask for the same favor in returns. This is how I imagine the future of scripting, at an high level, and if nee= ded can provide specific exemples, and even in depth explanations on some p= oints. You know how to reach me ;) Gentleman, start your (scripting) engines First of all, we need a common scripting language for all the applications,= and a consistent set of API for all of them. Of course, this won't be done= in a day, each app having it's own history before and after their Adobe li= fe, but why can't we have an abstraction layer that would convert all our u= nified api calls into specific application language ? Adding layers of inte= rpretation is just a short term solution to a long term problem. I hope tha= t in a couple of years from now, UI accross all Adobe apps will share the s= ame language, and that we'll be able to run natively our scripts within all= the apps. Un pour tous, tous pour un Then, we need to be able to call the API of every apps, from within any app= . Best exemple is: if I want to create a Premiere Pro Project from a set of= After Effects comps within After Effects, via scripting, the only way is t= o write a Final Cut Pro XML document and then let the user import it by han= d inside Premiere. That's inconveniant to say the least. And if I want to c= reate a Premiere Pro project with dynamic Links to a set of After Effects c= omps, I simply can't, unless I'm able to decypher the *.pproj fileformat, a= nd believe me I tried. I can go on of course. I cannot change some PSD file specs within After Eff= ects, and we should be able to do that. The list could be very long, and in= fact, I even have a case study for that to share with you Adobe. I should = be able to do these simples operation no matter what my host application is= . And these exemples are just confined within the video application space. = Imagine what the community could achieve mixing the Edge tools, Flash or Af= ter Effects... So may it be via launching headless background apps, or a central scripting= runtime, it's your design choice, but please, let us do that. Files of the Conchord Within the same idea, we should be able to create every Adobe document file= s from any app. Creating Audition, Premiere, After Effects, Photoshop files f= rom any of these apps will allow us to move interconnectivity forward in wa= ys that will blow your mind. Let us add an icing of dynamic link from withi= n our scripts too. I can share a lot of ideas with you guys on this one. Metadata is at the heart of an unified workflow. Adding XMP metadata into a= ny Adobe supported file format should be as simple as a document.xmpAdd(); = Your applications are supporting almost all media fileformat natively. Enpo= wer us with that so we can have fun with metadata writing and sharing. The Dark Knight Rises With aescripts.com, the awarness around scripting hav= e raised significantly, the number of new tools for your customers is growi= ng on a daily basis, and people are hungry for more. So let us help you build tomorrow workflows. Extend and enhance scripting s= o that we can create groundbreaking experiences for Adobe Creative Cloud us= ers, and push forward the worflows of tomorrow. Cheers, Seb -- S=E9bastien mytho.mn --_000_8C6FE228180FE143B942B993AE2E1C74636AD84CEXCHANGEMBXcram_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Excellent. Thnx.

 <= /p>

For light duty scripters,= like myself, it would also be helpful to have a “listener windowR= 21; like the one found in 3dsMax, which shows Maxscript code for most all UI actions. This makes generating new scripts a breeze in max. For mor= e involved scripting 3dsMax’s far superior documentation is always at hand.

 

From: After Ef= fects Mail List [mailto:AE-List@media-motion.tv] On Behalf Of S=E9bastien
Sent: Tuesday, June 25, 2013 1:08 PM
To: After Effects Mail List
Subject: [AE] How the future of Adobe Scripting should look like

 

Hi guys,

I was thinking of how Adobe should push forward our scripting abilities and= wrote a long post about it here: http://mytho.mn/future-= adobe-scripting/

I think it's somehow = a big topic, now that we are on the way on unified workflows between all th= e apps.

As an AE scripter, my= views are probably biased, but let's discuss about it here to maybe build = a better future ;)

If you don't like lin= ks, here is a copy/paste of my post:

We need scripting to change

Today, each Adobe application have it’s own scripting language, an= d it’s own set of UI API, and this is a big obstacle for us, to come = with new and exciting scripts and extentions for our beloved applications.<= br>
With the Creative Cloud, Adobe is touting the synergy between all it’= s flagship apps, the connected and seamless workflows from After Effects to= Premiere, from Story to Audition, and yet, we can’t design scripts t= hat can take advantage of that. In the center of this seemless ideology there is metadata, but even for that, we donR= 17;t have the handy tools.

The all we can eat model

In order to help us build impressive tools to make your applications sex= ier, we desperatly need some improvements, and now that we’re all und= er the Creative Cloud shiny name, it’s time to shape that future all = together. And since you want us to access all your application to discover new possibilities, it’s time for me (us= ?) to ask for the same favor in returns.

This is how I imagine the future of scripting, at an high level, and if = needed can provide specific exemples, and even in depth explanations on som= e points. You know how to reach me ;)

Gentleman, start your (scripting) engines

First of all, we need a common scripting language for all the applicatio= ns, and a consistent set of API for all of them. Of course, this won’= t be done in a day, each app having it’s own history before and after= their Adobe life, but why can’t we have an abstraction layer that would convert all our unified api calls into specif= ic application language ? Adding layers of interpretation is just a short t= erm solution to a long term problem. I hope that in a couple of years from = now, UI accross all Adobe apps will share the same language, and that we’ll be able to run natively our = scripts within all the apps.

Un pour tous, tous pour un

Then, we need to be able to call the API of every apps, from within any = app. Best exemple is: if I want to create a Premiere Pro Project from a set= of After Effects comps within After Effects, via scripting, the only way i= s to write a Final Cut Pro XML document and then let the user import it by hand inside Premiere. That’s = inconveniant to say the least. And if I want to create a Premiere Pro = project with dynamic Links to a set of After Effects comps, I simply can= 217;t, unless I’m able to decypher the *.pproj fileformat, and believe me I tried.

I can go on of course. I cannot change some PSD file specs within After = Effects, and we should be able to do that. The list could be very long, and= in fact, I even have a case study for that to share with you Adobe. I shou= ld be able to do these simples operation no matter what my host application is. And these exemples are just confine= d within the video application space. Imagine what the community could achi= eve mixing the Edge tools, Flash or After Effects…

So may it be via launching headless background apps, or a central script= ing runtime, it’s your design choice, but please, let us do that.

Files of the Conchord

Within the same idea, we should be able to create every Adobe document f= iles
from any app. Creating Audition, Premiere, After Effects, Photoshop files f= rom any of these apps will allow us to move interconnectivity forward in wa= ys that will blow your mind. Let us add an icing of dynamic link from withi= n our scripts too. I can share a lot of ideas with you guys on this one.

Metadata is at the heart of an unified workflow. Adding XMP metadata int= o any Adobe supported file format should be as simple as a document.xmpAdd(); Your applications are supporting almost= all media fileformat natively. Enpower us with that so we can have fun wit= h metadata writing and sharing.

The Dark Knight Rises

With aescripts.com, the awarness ar= ound scripting have raised significantly, the number of new tools for your = customers is growing on a daily basis, and people are hungry for more.=

So let us help you build tomorrow workflows. Extend and enhance scriptin= g so that we can create groundbreaking experiences for Adobe Creative Cloud= users, and push forward the worflows of tomorrow.

Cheers,

 

Seb


--
S=E9bastien

mytho.mn<= /p>

--_000_8C6FE228180FE143B942B993AE2E1C74636AD84CEXCHANGEMBXcram_--