1 Reply Latest reply on Apr 28, 2016 6:43 AM by Bruce Bullis

    Potential bug in Export as FCPXML

    innerspaceouterspace Level 1

      It appears that there's possibly a bug with calling and handling network paths

       

          exportActiveSequenceAsXML : function(path) {
              var seq = app.project.activeSequence
              alert(path);
              if (seq != null) {
                  // seq.exportAsFinalCutProXML(path, 1); // 1 == suppress UI
                  seq.exportAsFinalCutProXML(path);
              } else {
                  alert("No active sequence.");
              }
          },
      
      

       

      The alert(path) shows the path is correct before being sent to exportAsFinalCutProXML as shown below:

      goodAlertFirst.PNG

       

      And then right when it calls the seq.exportAsFinalCutProXML(path) and I turn off the UI suppression, it alerts with this:


      badAlertAfter.PNG


      Showing that the path is getting oddly interpreted. I can make a temporary fix using external processes, but this isn't the first time I've run into this bug and it seems like an actual bug. Doing the same thing in Extendscript also produces unfavorable results.

       

       

      It should be noted that giving it a local path does not produce these results.