Skip to main content
R.Silva
R.Silva
Known Participant
March 30, 2017
Question

XML import does not work -Premiere 2017.0.2

  • March 30, 2017
  • 1 reply
  • 2535 views

The current version of Premiere seems to be having a problem importing XML files. Even simple xml files created by the same application.

I have tried with the previous version (which I fortunately kept in my Applications folder) and the XML importer works fine.

The current version 2017.0.2 does not import XML files AT ALL. A dialog box displays an error saying: "The project appears to be damaged, it cannot be opened"

Using the previous version the XML file opens perfectly!

    This topic has been closed for replies.

    1 reply

    Vidya Sagar
    Vidya Sagar
    Participating Frequently
    March 30, 2017

    Hi R.Silva,

    I have tested with Premiere Pro CC 2017.0.2 on both Windows & Mac, Import of XML is working fine & flawlessly. Please provide more information related to this issue.

    1. Is this happening with multiple projects or with one project? If possible share us the XML file to test in our environment.

    2. In which version of Premiere Pro the project file was created?

    3. Have you tried creating a new project, export an XML & import into a new project for test?

    Also provide more information related to machine. FAQ: What information should I provide when asking a question on this forum?

    Thanks,

    vidya.

    R.Silva
    R.SilvaAuthor
    Known Participant
    March 30, 2017

    Hello Vidya:

    After doing a couple of additional tests I finally found out what the problem is.

    I have created some markers with some characters like : < and : >   (greater than and lower than brackets). When I export a timeline that contains these characters in the markers, the XML file does not import at all. If I remove the characters, the XML will import properly.

    This behavior only happens when using the Premiere Pro version 2017.0.2

    If I use a previous version of Adobe Premiere, the XML file imports correctly when the brackets are included in the markers' comments.

    You can get the XML file from this link: Dropbox - Public

    My conclusion is that the XML importer is still not working properly in this version of Premiere Pro, because it should be capable of parsing the markers' data correctly as it is possible with all the other versions of Premiere.

    So, my response to your questions are:

    1.- Multiple projects or one project? :  Multiple projects when using markers that contain the brackets < and > .

    2.- Version of Premiere Pro:  2017.0.2

    3.- Tried to create a new project and reimport? : Yes. Only those without the brackets will import properly. Those projects with the brackets included in the markers' comments WILL NOT import properly.

    As a final note, you may be wondering why I am using the brackets in the markers. The reason behind it is because I like to export the markers' comments as a Comma Separated Value (csv) and whenever I have a comma in the text, the markers' Export command will export my markers incorrectly. This way I can easily change the text to commas once I use a word processor to search and replace these characters.  ( By the way, the Export markers in Text file does not work either – I already filed a bug and created a thread in this forum related to that problem)

    Thanks,

    System config: Macintosh computer with OSX Sierra version 10.12.3 - iMac Retina 5K, 27 inch, late 2014 - 4GHz Intel Core i7 - 32 GB Ram and lots of hard drive spcace.

      Terms & ConditionsAccessibility statement
      Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices