Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

Struggling to configure Atom for AE scripting on Mac

New Here ,
Nov 19, 2020 Nov 19, 2020

I am following a video tutorial series on AE scripting. I've downloaded Atom and installed the process-palette package to allow me to run AE scripts from the editor. The command that I was told to use was:

 

osascript -e 'tell application "Adobe After Effects CC 2020" to activate' -e 'tell application "Adobe After Effects CC 2020" to DoScriptFile "{fileAbsPath}"'

 

But whenever I try to run a script, I get the following error: 

 

Executed : osascript -e 'tell application "Adobe After Effects CC 2020" to activate' -e 'tell application "Adobe After Effects CC 2020" to DoScriptFile "/Users/d8mac4/Desktop/Online Adobe Training/lower third practice/test.jsx"'
Returned with code 1
122:123: syntax error: Expected end of line, etc. but found “"”. (-2741)
 
I'm clueless as to what I need to fix or troubleshoot. I'm able to easily AE scripts from Visual Studio, but I can't even get a "hello world" alert to run from Atom.
 
Screen Shot 2020-11-19 at 10.34.58 AM.png

TOPICS
Scripting
1.0K
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Community Expert , Nov 19, 2020 Nov 19, 2020

Hi,

are you following my scripting classes at fxpdh? 🙂

To be honest, I don't recommend using Atom anymore. Adobe discontinued ExtendScript toolkit, which was back then the only way to debug Ae scripts. In the meantime, Adobe developed an extension for VS Code that allows debugging directly in VS code. VS Code is similar to Atom, but has this big advantage that it can debug Ae scripts. This is crucial, in particular since the old ExtendScript Toolkit does not work on Mac OS Catalina or newer. So

...
Translate
Community Expert ,
Nov 19, 2020 Nov 19, 2020

Hi,

are you following my scripting classes at fxpdh? 🙂

To be honest, I don't recommend using Atom anymore. Adobe discontinued ExtendScript toolkit, which was back then the only way to debug Ae scripts. In the meantime, Adobe developed an extension for VS Code that allows debugging directly in VS code. VS Code is similar to Atom, but has this big advantage that it can debug Ae scripts. This is crucial, in particular since the old ExtendScript Toolkit does not work on Mac OS Catalina or newer. So I highly recommend to use VS Code instead of Atom.

After installing VS Code, make sure to install this plugin
https://marketplace.visualstudio.com/items?itemName=Adobe.extendscript-debug

 

 

Mathias Möhl - Developer of tools like BeatEdit and Automation Blocks for Premiere Pro and After Effects
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Nov 19, 2020 Nov 19, 2020

Ah yes, I am following your class! 

I actually started using VS Code when I took the Motion Design School scripting class, and then tried switching to Atom when I started yours. But I'll go back to using VS Code 🙂

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Nov 19, 2020 Nov 19, 2020
LATEST

oh, good, then you already know VS Code.

It is a bit of a pity that Adobe had no plans with VS Code, yet, when I recorded the fxphd course. Otherwise I had done the course with VS Code of course. But I guess it is a very good thing that there is a lot of new development going on in the scripting world and inevitably this has the side effect that some things get a little outdated...

Mathias Möhl - Developer of tools like BeatEdit and Automation Blocks for Premiere Pro and After Effects
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines