Return-Path: Received: from mail-lb0-f179.google.com ([209.85.217.179] verified) by media-motion.tv (CommuniGate Pro SMTP 4.2.10) with ESMTP-TLS id 5121617 for AE-List@media-motion.tv; Wed, 26 Jun 2013 19:58:58 +0200 Received: by mail-lb0-f179.google.com with SMTP id w20so1619793lbh.38 for ; Wed, 26 Jun 2013 11:09:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=QnwoI2oKkwUmVaatN4+EeKMhAnHvQ4Php4r63zmnDCE=; b=HtaP5Uvy4j9wX9ID2CX1LrMyj2enyz6KGGuQB1l2OE/ZJStiAs1BANfRwFX+LscE08 VVJoeHHkfpWi+wSDBcesqIjUwnhgoEbzfH2GX3WjNxJfN1r60RqxN0pFI1GXkPmItbW3 /jG+LpGAFKvWVTJQEzrsiCnC6Mtc6e+Y9n8G2lUGny5FDBKFu8Pn+1MIvo5gV5XwCYRS oNKzIBhnxQDIOpDTYYubYI+1PqikVxWfQlMoaIxFdMLgxsvtI/ijrAQaZfKiw0XApRFD N4YtEOltQl+Td09d0bfesUQTuzK79TR/93XWEE+r8igUFrFNtQioxgUWmfMz4E02WiwW 0eMg== X-Received: by 10.112.218.100 with SMTP id pf4mr2726075lbc.2.1372270160329; Wed, 26 Jun 2013 11:09:20 -0700 (PDT) MIME-Version: 1.0 Received: by 10.152.26.103 with HTTP; Wed, 26 Jun 2013 11:09:00 -0700 (PDT) In-Reply-To: References: From: Byron Nash Date: Wed, 26 Jun 2013 14:09:00 -0400 Message-ID: Subject: Re: [AE] How the future of Adobe Scripting should look like To: After Effects Mail List Content-Type: multipart/alternative; boundary=001a11c3bfda7145cd04e0128b66 --001a11c3bfda7145cd04e0128b66 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Great ideas Sebastien and Michael. I have put in feature requests for a script logger or listener before. That would be incredibly helpful in creating scripts and cut down on the time looking for that tricky object model syntax for a certain property you are after. I'd also like to see them support Python since that seems like it's becoming the language of choice in DCC apps(Nuke, Maya, Softimage, etc...) On Wed, Jun 26, 2013 at 11:05 AM, Michael Powers wrote= : > Excellent. Thnx.**** > > ** ** > > For light duty scripters, like myself, it would also be helpful to have a > =93listener window=94 like the one found in 3dsMax, which shows Maxscript= code > for most all UI actions. This makes generating new scripts a breeze in ma= x. > For more involved scripting 3dsMax=92s *far superior documentation* is > always at 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 > workflows 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=92s own scripting language, and it= =92s > own set of UI API, and this is a big obstacle for us, to come with new an= d > exciting scripts and extentions for our beloved applications. > > With the Creative Cloud, Adobe is touting the synergy between all it=92s > flagship apps, the connected and seamless workflows from After Effects to > Premiere, from Story to Audition, and yet, we can=92t design scripts that= can > take advantage of that. In the center of this seemless ideology there is > metadata, but even for that, we don=92t 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=92re all un= der > the Creative Cloud shiny name, it=92s time to shape that future all toget= her. > And since you want us to access all your application to discover new > possibilities, it=92s time for me (us ?) to ask for the same favor in ret= urns. > **** > > 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 > some points. 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, thi= s > won=92t be done in a day, each app having it=92s own history before and a= fter > their Adobe life, but why can=92t we have an abstraction layer that would > convert all our unified api calls into specific application language ? > Adding layers of interpretation is just a short term 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=92ll 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 s= et > of After Effects comps within After Effects, via scripting, the only way = is > to write a Final Cut Pro XML document and then let the user import it by > hand inside Premiere. That=92s *inconveniant* to say the least. And if I > want to create a Premiere Pro project with dynamic Links to a set of Afte= r > Effects comps, I simply can=92t, unless I=92m able to decypher the *.ppro= j > 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, a= nd > 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 Ed= ge > tools, Flash or After Effects=85**** > > So may it be via launching headless background apps, or a central > scripting runtime, it=92s 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 > files > from any app. Creating Audition, Premiere, After Effects, Photoshop files > from any of these apps will allow us to move interconnectivity forward in > ways that will blow your mind. Let us add an icing of dynamic link from > within 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 > 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 with metadat= a > writing and sharing.**** > > *The Dark Knight Rises***** > > With aescripts.com, the awarness around 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 scripting > 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**** > --001a11c3bfda7145cd04e0128b66 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable
Great ideas Sebastien and Michael. I have put in feature r= equests for a script logger or listener before. That would be incredibly he= lpful in creating scripts and cut down on the time looking for that tricky = object model syntax for a certain property you are after.=A0

I'd also like to see them support Python since tha= t seems like it's becoming the language of choice in DCC apps(Nuke, May= a, Softimage, etc...)




On Wed, Jun 2= 6, 2013 at 11:05 AM, Michael Powers <MPowers@cramer.com> wr= ote:

Excellent. Thnx.

=A0<= /p>

For light duty scripters,= like myself, it would also be helpful to have a =93listener window=94 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=92s far superior documentation is always at hand.

=A0

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<= /u>

=A0

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 some= how a big topic, now that we are on the way on unified workflows between al= l the apps.

As an AE scripter, my= views are probably biased, but let's discuss about it here to maybe bu= ild 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=92s own scripting language, and it= =92s 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.

With the Creative Cloud, Adobe is touting the synergy between all it=92s fl= agship apps, the connected and seamless workflows from After Effects to Pre= miere, from Story to Audition, and yet, we can=92t design scripts that can = take advantage of that. In the center of this seemless ideology there is metadata, but even for that, we don=92t= 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=92re all under t= he Creative Cloud shiny name, it=92s time to shape that future all together= . And since you want us to access all your application to discover new possibilities, it=92s 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=92t be= done in a day, each app having it=92s own history before and after their A= dobe life, but why can=92t 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=92ll be able to run natively our scri= pts 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=92s inco= nveniant to say the least. And if I want to create a Premiere Pro proj= ect with dynamic Links to a set of After Effects comps, I simply can=92t, u= nless I=92m 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=85

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

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 around scripting have raised significantly, the number of n= ew tools for your customers is growing on a daily basis, and people are hun= gry 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,

=A0

Seb


--
S=E9bastien

mytho.= mn


--001a11c3bfda7145cd04e0128b66--