AME crash introduced in 14.0.3 when using console es.executeScript

[dan.robo]

Using the following command caused AME to crash. 

"C:\Program Files\Adobe\Adobe Media Encoder 2020\Adobe Media Encoder.exe" --console es.executeScript "D:\TEST\test.jsx"

Contents of script
var a = "b";

It seems this issue was introduced in 14.0.3 as the crash doesn't happen if i roll back to 14.0.1.

14.1 - Crash
14.0.4 - Crash
14.0.3 - Crash
14.0.1 - Works

I've confirmed this happens on two seperate machines.

Crash Report

<?xml version="1.0"?>
<!DOCTYPE AdobeCrashReport SYSTEM "AdobeCrashReporter.dtd">
<crashreport serviceVersion="2.7.0" clientVersion="2.7.0" applicationName="Adobe Media Encoder" applicationVersion="14.1" build="155" source="Windows-Client" crashType="CR_SIGNAL_SIGSEGV">
<time year="2020" month="4" day="21" hour="14" minute="54" second="32" timeoffset="0" timezone="GMT Daylight Time"/>
<user guid="0718823b-ecc4-4ea8-8100-180ff614bcc4"/>
<system platform="Windows 10 Pro" osversion="10.0" osbuild="18362" applicationlanguage="en-us" userlanguage="en-GB" oslanguage="en-US" ram="32540" machine="Intel(R) Core(TM) i7-8850H CPU @ 2.60GHz" model="Intel64 Family 6 Model 158 Stepping 10" cpuCount="12" cpuType="8664" cpuFreq="2592 MHz"/>
<gpu>
<gpuinfo availability="Running/Full Power" adapterCompatibility="Intel Corporation" adapterRAM="1024 MB" caption="Intel(R) UHD Graphics 630" description="Intel(R) UHD Graphics 630" driverDate="20190925000000.000000-000" driverVersion="26.20.100.7262" videoModeDescription="2560 x 1440 x 4294967296 colors" pnpDeviceID="PCI&#92;VEN_8086&#38;DEV_3E9B&#38;SUBSYS_087D1028&#38;REV_00&#92;3&#38;11583659&#38;0&#38;10" installedDisplayDrivers="igd10iumd64.dll,igd12umd64.dll,igdumdim64.dll"/>
<gpuinfo availability="Off Line" adapterCompatibility="NVIDIA" adapterRAM="4095 MB" caption="NVIDIA Quadro P1000" description="NVIDIA Quadro P1000" driverDate="20191126000000.000000-000" driverVersion="26.21.14.4145" videoModeDescription="" pnpDeviceID="PCI&#92;VEN_10DE&#38;DEV_1CBB&#38;SUBSYS_087D1028&#38;REV_A1&#92;4&#38;44A1B07&#38;0&#38;0008" installedDisplayDrivers="nvldumdx.dll"/>
</gpu>
<crash exception="EXCEPTION_UNKNOWN" exceptionCode="0xc0000409" instruction="0x0000000048830D01">
<backtrace crashedThread="0">
<thread index="0">
<stackStatement index="0" address="0x00007FFFE71DC043" symbolname="seh_filter_exe"/>
<stackStatement index="1" address="0x000000014020D947" symbolname="ScriptLayer::ScriptObject::`default constructor closure&#39;"/>
<stackStatement index="2" address="0x00007FFFCE24C1C0" symbolname="_C_specific_handler"/>
<stackStatement index="3" address="0x00007FFFE9FA11CF" symbolname="_chkstk"/>
<stackStatement index="4" address="0x00007FFFE9F6A209" symbolname="RtlRaiseException"/>
<stackStatement index="5" address="0x00007FFFE9F9FE3E" symbolname="KiUserExceptionDispatcher"/>
<stackStatement index="6" address="0x00000000028C9E9D" symbolname="ScriptLayer::ExecuteScript"/>
<stackStatement index="7" address="0x00000000028CA41E" symbolname="ScriptLayer::ExecuteScriptFile"/>
<stackStatement index="8" address="0x00000000028B65B6" symbolname="ScriptLayer::GetAppScriptObject"/>
<stackStatement index="9" address="0x00000000047DBB3A" symbolname="dvacore::console::ExecuteCommand"/>
<stackStatement index="10" address="0x0000000140051AAE" symbolname="ScriptLayer::ScriptObject::`default constructor closure&#39;"/>
<stackStatement index="11" address="0x0000000140075245" symbolname="ScriptLayer::ScriptObject::`default constructor closure&#39;"/>
<stackStatement index="12" address="0x00000001401E82F6" symbolname="ScriptLayer::ScriptObject::`default constructor closure&#39;"/>
<stackStatement index="13" address="0x00007FFFE8137BD4" symbolname="BaseThreadInitThunk"/>
<stackStatement index="14" address="0x00007FFFE9F6CE51" symbolname="RtlUserThreadStart"/>
</thread>
</backtrace>
<registerSet>
<register name="RAX" value="0x0000000000000004"/>
<register name="RBX" value="0x0000000000000000"/>
<register name="RCX" value="0x0000000000001A3C"/>
<register name="RDX" value="0x0000000000000000"/>
<register name="RSI" value="0x0000000000000000"/>
<register name="RDI" value="0x000000000062E0E0"/>
<register name="RSP" value="0x000000000014DBB0"/>
<register name="RBP" value="0x000000000014DC40"/>
<register name="RIP" value="0x00007FFFE71DC043"/>
<register name="EFL" value="0x0000000000000246"/>
<register name="LastExceptionToRip" value="0x0000000000000000"/>
<register name="LastExceptionFromRip" value="0x0000000000000000"/>
</registerSet>

[Bruce Bullis]

If you replace --executeScript (which expects a blob of ExtendScript to follow) with --executeFile (which expects a path to an ExtendScript file), the call works fine. 

[Playful_Lark5CAF]

Crash also with 14.4. 

Do you know how to execute a script by command line but with media encoder already ?

thanks

Andrea

[Bruce Bullis]

Just what you've already used:

"C:\Program Files\Adobe\Adobe Media Encoder 2020\Adobe Media Encoder.exe" --console es.executeScript "C:\Users\username\Desktop\test.jsx"

[mikik66587129]

This just doesn't work, I've tried everything. It surely does make AME.exe as active app, but it doesn't run the script. Of course script runs from extendscript, but not like this. Any ideas?

[Bruce Bullis · Accepted solution]

Strange; reproduced the crash. We're tracking this as DVAME-4198877.

[mikik66587129]

It's not a crash for me, the script just doesn't run. 

[Bruce Bullis]

es.executeScript produces the crash; es.executeFile launches AME but doesn't execute the script.

[Bruce Bullis]

This works correctly, with shipping AME, with all flags set to default.

"C:\Program Files\Adobe\Adobe Media Encoder 2020\Adobe Media Encoder.exe" --console es.processFile C:\Users\bbb\Desktop\test.jsx

[mikik66587129]

Yes! But, AME has to be closed.

[mikik66587129]

Quick question, is there a way (with scripting of course) to apply multiple presets to one file.

for(var i=0; i<presetsArray.length; i++){

app.getFrontend().addFileToBatch(sourceMOV, "H.264", presetsArray[i], destination);

}

this just adds multiple items in queue which is not really ideal for me. Thanks.

[Bruce Bullis]

var matchSourceSettings = true;
var source              = "/Users/bbb/Movies/aaa.mxf";
var destination         = "/Users/bbb/Desktop/output";
var presetsArray        = '/Users/bbb/Desktop/test1.epr|/Users/bbb/Desktop/test2.epr';

var exporter = app.getExporter();
if (exporter){
  var result = exporter.exportGroup(source, destination, presetsArray, matchSourceSettings);
}

Note: Preset "array" is actually just a bunch of paths to .epr files, concatenated with a "|".

[mikik66587129]

Ahhh, thanks a lot, I would have never figured it out based on AME scripting guide. Just for anyone reading this, which confused me a bit,  "matchSourceSettings = true" will keep presets as they are except dimensions, change to false if your presets have different dimensions, like in my case. Anyway, once again, thanks a lot Bruce! 🙂

[harryf58967104]

Hi Bruce,

Any chance someone's got to the bottom of this yet?

We're having the same issues in 15.1. We're running the .exe with "-console es.executeFile" and trying to run the below to add an AE comp to the the queue and kick it off:

app.getFrontend().addCompToBatch(pathToAEP, pathToEPR, pathToOutput);

var encoderHost = app.getEncoderHost();
encoderHost.runBatch();

while (encoderHost.isBatchRunning())
{
    app.wait(10000);
}
app.quit();

We see the same behaviour in that calling "es.executeFile" instead of "es.executeScript" opens without crashing but doesn't execute the script. (what's weird though is that it does execute the addCompToBatch function in 14.0.3 but then doesn't run "encoderHost.runBatch();" so we're still in the same situation. 15.1 just does nothing).

Any updates would be hugely appreciated!

Thanks in advance,

Harry

[Bruce Bullis]

I've confirmed that this works correctly, in current versions; I used a very basic .aep, and an H.264 .epr file.

"C:\Program Files\Adobe\Adobe Media Encoder 2021\Adobe Media Encoder.exe" --console es.processFile "C:\Users\bbb\Desktop\ame.jsx"

[harryf58967104 · Accepted solution]

Hi Bruce, thanks for the confirmation and examples!

I'll give es.processFile a go and try a more simple project/epr file to see if my aep might be causing some issues of its own.

Thanks again for your time, very much appreciated.

All the best,

Harry

[Lloyd28200878thlg]

Hi, I get nothing when I do what you described. Are there any update to this? Thanks

[Bruce Bullis]

No changes to AME's behavior. 

Specifically, what did you try? 

[Lloyd28200878thlg]

I tried to use a command like the one described at the top here. The actual command I use is:

"C:\Program Files\Adobe\Adobe Media Encoder 2023\Adobe Media Encoder.exe" --console es.processFile "D:\EventVid\Media Encoder\constructionVid.jsx"

Nothing gets inserted to the Media Encoder queue. Media Encoder just focuses like something tried to happen. Note, when I use constructionVid.jsx in Extend Script Toolkit or VSCode (with Extend Script extension) it works fine. Thanks

[Lloyd28200878thlg]

So the question is... why if Extend Script Tookit is working do I need to use something like the command line way? The reason is because the Extend Script Toolkit or VSCode way do not allow for any form of automation. Thanks

[eckiAMETeam]

Which AME version are you using?

[Lloyd28200878thlg]

Version 23.2(Build 63)

[Bruce Bullis · Accepted solution]

ExtendScript Toolkit was <EOL> years ago, but the ExtendScript Debugger for Microsoft Visual Studio Code (the recommended ExtendScript development environment) works great. CEP panels in AME allow for ExtendScript-driven automation .

AME command line scripting is definitely NOT a recommended approach. 

The bug discussed in this thread, DVAME-4198877, was fixed as of AME 22.5. 

[Lloyd28200878thlg]

Hi, again. I asked this because you only answer realated to the specific context of this thread. I may have made the mistake of asking another questions (felt it was related) here. So should I have started another post to asked what I asked? I am just asking about what I found in documents that I thought were designed to be helpful. I will start a new thread. Thanks for the help.

[eckiAMETeam]

This is a very old thread. Please start a new concversation if you encounter any new issues with more recent releases.