Return-Path: Received: from mail-la0-f41.google.com ([209.85.215.41] verified) by media-motion.tv (CommuniGate Pro SMTP 4.2.10) with ESMTP-TLS id 5120356 for AE-List@media-motion.tv; Tue, 25 Jun 2013 18:58:07 +0200 Received: by mail-la0-f41.google.com with SMTP id fn20so12625734lab.28 for ; Tue, 25 Jun 2013 10:08:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=vv/s/U2S/OYhne+rB4xyn1UUVu/keFZMpFbgJgZBCp0=; b=ISqBuQJHAnY6CJlawalxlu+R71b25jXyVI+FhZjEgWiy6TkUO/BGNHX/txR+ps26Zc QVitoDG5r81vzhN6HvlD1TPyMWuYgSPJAmz7kkdJg9G9PicTjImm6u7hgf1ZprxBo1bX 5ppY4s/Jg2mafWdTAHk+szY53IljYiznfiv7YonsoXfRIdMj2eQzI9MJk7CpSCQJC30x qmnjk4VnHpMpKSetdgY4tHO8/7msFaBlOPlYpZV/iELHEC9zUE1v99WPanF4q+i1NcLk hvC1oe/Aj9P3A8w51aErH0Wd2aHBcdQ69j5CJ0MivbJFR5v7/zqT+Z058bkeTg3xRVL/ Xi3A== MIME-Version: 1.0 X-Received: by 10.152.23.168 with SMTP id n8mr14007332laf.88.1372180107451; Tue, 25 Jun 2013 10:08:27 -0700 (PDT) Received: by 10.114.200.130 with HTTP; Tue, 25 Jun 2013 10:08:27 -0700 (PDT) Date: Tue, 25 Jun 2013 19:08:27 +0200 Message-ID: Subject: How the future of Adobe Scripting should look like From: =?ISO-8859-1?Q?S=E9bastien?= To: After Effects Mail List Content-Type: multipart/alternative; boundary=089e0160a5d0df63f604dffd93cf --089e0160a5d0df63f604dffd93cf Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable 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=92= 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. 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 c= an 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 unde= r the Creative Cloud shiny name, it=92s time to shape that future all togethe= r. 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 retur= ns. 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, this won=92t be don= e in a day, each app having it=92s own history before and after their Adobe life, but why can=92t we have an abstraction layer that would convert all o= ur 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 set 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 wa= nt to create a Premiere Pro project with dynamic Links to a set of After Effects comps, I simply can=92t, unless 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 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 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 file= s 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 metadata 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 --=20 S=E9bastien mytho.mn ** --089e0160a5d0df63f604dffd93cf Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable
Hi guys,

I was thinking of how Adobe should pu= sh forward our scripting abilities and wrote a long post about it here: http://mytho.mn/future-ado= be-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=20 it=92s own set of UI API, and this is a big obstacle for us, to come with= =20 new and exciting scripts and extentions for our beloved applications.

With the Creative Cloud, Adobe is touting the synergy between all it=92s=20 flagship apps, the connected and seamless workflows from After Effects=20 to Premiere, from Story to Audition, and yet, we can=92t design scripts=20 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=20 sexier, we desperatly need some improvements, and now that we=92re all=20 under the Creative Cloud shiny name, it=92s time to shape that future all= =20 together. And since you want us to access all your application to=20 discover new possibilities, it=92s time for me (us ?) to ask for the same= =20 favor in returns.

This is how I imagine the future of scripting, at an high level, and=20 if needed can provide specific exemples, and even in depth explanations=20 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=20 applications, and a consistent set of API for all of them. Of course,=20 this won=92t be done in a day, each app having it=92s own history before an= d after their Adobe life, but why can=92t we have an abstraction layer that would convert all our unified api calls into specific application=20 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=20 accross all Adobe apps will share the same language, and that we=92ll be=20 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=20 any app. Best exemple is: if I want to create a Premiere Pro Project=20 from a set of After Effects comps within After Effects, via scripting,=20 the only way is to write a Final Cut Pro XML document and then let the=20 user import it by hand inside Premiere. That=92s inconveniant to= =20 say the least. And if I want to create a Premiere Pro project with=20 dynamic Links to a set of After Effects comps, I simply can=92t, unless=20 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=20 After Effects, and we should be able to do that. The list could be very=20 long, and in fact, I even have a case study for that to share with you=20 Adobe. I should be able to do these simples operation no matter what my=20 host application is. And these exemples are just confined within the=20 video application space. Imagine what the community could achieve mixing the Edge tools, Flash or After Effects=85

So may it be via launching headless background apps, or a central=20 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 f= iles
from any app. Creating Audition, Premiere, After Effects, Photoshop=20 files from any of these apps will allow us to move interconnectivity=20 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=20 guys on this one.

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

The Dark Knight Rises

With aescripts.com, the awarness ar= ound scripting have raised=20 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=20 scripting so that we can create groundbreaking experiences for Adobe=20 Creative Cloud users, and push forward the worflows of tomorrow.

Cheers,=

Seb

--
S=E9bastien
<= /div>mytho.mn
--089e0160a5d0df63f604dffd93cf--