This tutorial is aimed at script developers to show how quickly and easliy scripts can interact with external json files or web apis
After Effects Scripting JSON Tutorial
Posted in Tutorials After Effects Automation by Lloyd Alvarez on November 18, 2014
Lloyd Alvarez posted on August 20, 2018
> this code is working on ExtendedScript Tool but not working on After Effects 2017.
How can I read json file on After Effects?
It works fine with CC2017. This is just javascript so it is host and version agnostic. Unfortunately we cannot help you debug your code, try asking for help on the After Effects scripting forum:
https://forums.adobe.com/community/aftereffects_general_discussion/ae_scripting/overview
How can I read json file on After Effects?
It works fine with CC2017. This is just javascript so it is host and version agnostic. Unfortunately we cannot help you debug your code, try asking for help on the After Effects scripting forum:
https://forums.adobe.com/community/aftereffects_general_discussion/ae_scripting/overview
Gökhan Aydın posted on August 20, 2018
Thank you Lloyd.
this code is working on ExtendedScript Tool but not working on After Effects 2017.
How can I read json file on After Effects?
this code is working on ExtendedScript Tool but not working on After Effects 2017.
How can I read json file on After Effects?
Lloyd Alvarez posted on November 19, 2014
"Any ways, one question though - at time 5:32 you use "\r\n" - wouldn't it work with just "\r"? Because at this moment you get 2 returns. "\r" on mac gives a return for me no problem."
Depends on the text editor, traditionally mac encoding recognizes \n as a "new line" and ignores "\r" and win encoding recognizes
"\r" as a "carriage return" and ignores "\n". You are probably using a modern editor that recognizes both as I was getting when it opened in Sublime. If you were to open it in "Notepad" on windows for example it would only recognize the \r which is why it's best to put both. In either case it's purely cosmetic as it does not affect the data.
Depends on the text editor, traditionally mac encoding recognizes \n as a "new line" and ignores "\r" and win encoding recognizes
"\r" as a "carriage return" and ignores "\n". You are probably using a modern editor that recognizes both as I was getting when it opened in Sublime. If you were to open it in "Notepad" on windows for example it would only recognize the \r which is why it's best to put both. In either case it's purely cosmetic as it does not affect the data.
Tomas Sinkunas posted on November 19, 2014
Thank you Lloyd for this quick tutorial. Really love how you make it seem to be easy:) Will have to learn how to use JSON at last.
Any ways, one question though - at time 5:32 you use "\r\n" - wouldn't it work with just "\r"? Because at this moment you get 2 returns. "\r" on mac gives a return for me no problem.
Still, great resource. Thanks.
Any ways, one question though - at time 5:32 you use "\r\n" - wouldn't it work with just "\r"? Because at this moment you get 2 returns. "\r" on mac gives a return for me no problem.
Still, great resource. Thanks.
You must be logged in to post a comment.
click here to log in
Comments