Adding a second output in Extendscript for Media Encoder

Thanks for posting that Chris! I ended up using a similar method by consolidating all items into a subfolder with the master comp in the root. My temporary workaround for rendering one comp while maintaining the project's folder structure was to put all the consolidate methods in an undo group, save as a new .aep file specifically for the AME Render, and then undo the group and re-save to the original project file so you can continue working. I wish we could automate the "Save As Copy" in Extendscript, but for now this is the best method I could come up with. Best!

In case anyone else is interested in my workaround:

Consolidate as a separate file, save as export .aep, and then re-save over the original to preserve your project.

     // 1. Create Temp Consolidated File For Rendering //
          var projFile = new File(File.decode(app.project.file));
          var tempFolder = new Folder(projFile.path.toString() + "/AME_temp"); var dateStamp = new Date(); dateStamp = dateStamp.getTime();
          var tempProjFile = new File(tempFolder.toString() + "/" + app.project.file.name.toString() + aItem.name.toString() + "[" + dateStamp.toString() + "].aep");
          app.project.save(); app.project.save(tempProjFile); // Save Original File then Save Temp File
          app.beginUndoGroup("AME Export");
          app.project.reduceProject(aItem); // Reduce
          aItem.parentFolder = app.project.rootFolder; // Move active comp to Root for AME to recognize
          var allItems = app.project.items;
          var assetsBin = app.project.items.addFolder("-Assets");
          for (var i = 1; i < allItems.length; i++) {
              if(allItems.name != assetsBin.name && allItems.name != aItem.name)
                  allItems.parentFolder = assetsBin;
          }
          app.endUndoGroup();
          app.project.save();
          app.executeCommand(16); // Executes undo function to restore original
          app.project.save(projFile);  //Save Consolidated File

And then to Send to AME:

        // 2. Create Export Command for AME //
        var bodyText = "";     var myFile = tempProjFile.fsName;
        // Loop for each preset and add command to bodyText //
        for (var i = 0; i < myDestination.length; i++) {
          bodyText += "ameFront.addCompToBatch('" + myFile.toString() + "', '" + myPreset + "', '" + myDestination + "');";
        }
        var fileString = "var ameFront = app.getFrontend();" + bodyText;
        
        // 3. Send Command to AME for Export //
         var bt      = new BridgeTalk();
         bt.target   = 'ame';
         bt.body = fileString;
         bt.send();

We cannot comment on the feature set of unannounced versions of Adobe products.

With that in mind, I'd appreciate the community's patience in awaiting substantive reply, closer to (or soon after) NAB.

PS: Many scripters export the active Comp to a new .aep before rendering it, and some archive that .aep with the output file...in which case, the comp-to-be-rendered is determined DETERMINATE. [shakes fist emptily at auto-correct's insensitivity to Epistemology...].