AME Scripting is ...kind of working...need some support!

[MattKushner]

So I spent a couple weeks diving into the 1.0 docs that were released last month (https://readthedocs.org/projects/ame-scripting-guide/downloads/pdf/latest/) and have gotten some things to work, namely launching AME command line with a JSX file and getting it to clear the queue, populate it and start rendering.

But there are some functions that aren't working for me:

1. I can't get the dynamic setting of FPS, Width, Height or Frame Range to work. I'm using the app.getFrontend().addFileSequenceToBatch() function to create an item from an image sequence, and my hunch is that those attributes are only supported with addFileToBatch for some reason. It would be HUGE if I could leverage that, right now I'm dynamically creating presets to do all but Frame Range setting and it works, but it's an unnecessarily heavy lift and creates tons of presets that need to be cleaned up.
2. I can't figure out whether the writeln print statements go...they don't echo in a shell/console I can find and I'd rather log them to a txt file but I can't figure out how to do that either...
3. I'd really like AME to quit upon queue completion, most importantly because I have post process cleanup of the JSX I'm dynamically creating as well as all the presets. But I can't find any sort of flag to pass to the command line function (<AME Executable> --console es.processFile <JSX File>), or for it to return some info from the subprocess so I can trigger a kill of AME myself. 

[kglad]

in the future, to find the best place to post your message, use the list here, https://community.adobe.com/

p.s. i don't think the adobe website, and forums in particular, are easy to navigate, so don't spend a lot of time searching that forum list. do your best and we'll move the post if it helps you get responses.

<moved from using the community>

[MattKushner]

Thanks for moving it to the appropriate place! Will do! 

[kglad]

no problem.