Skip to main content
J
jeroenp93869257
Participant
November 6, 2019
Question

[XML export crash] "Serious error" on XML export of specific clip

  • November 6, 2019
  • 2 replies
  • 2109 views

Hi all,

 

When attempting to export an XML of a specific clip, Premiere Pro will crash. It will get to the Final Cut Pro XML export progress bar, but then, around 33% in, Premiere Pro will have a "serious error" and quits.

 

My steps:

1 Double click on clip in Project bin - it will be loaded into the "Source" panel.

2 Select/highlight the "Source" panel.

3 File -> Export Final Cut Pro XML.

 

Result: crash during export. Only a 0 (zero) byte XML file is created.

 

My attempted solutions:

- Update PP from 12.1 to 14.0

- Clear Media Cache

 

Note: exporting Final Cut XMLs from timelines works fine. But my goal is to export clip specific XMLs.

 

Does anyone have any idea what I am doing wrong?

 

---

Hardware:

 

iMac (Retina 5K, 27-inch, Late 2014)

4 GHz Intel Core i7

32 GB 1867 MHz DDR3

AMD Radeon R9 M295X 4096 MB

MacOs High Sierra 10.13.4 (17E202)

 

Part of Apple crash report:

 

Thread 51 Crashed:
0   com.adobe.FCPXProjectConverter.framework 0x00000003b3181bed FXP::PXF::(anonymous namespace)::TranslateClipInAndOut(FXP::PXF::(anonymous namespace)::ConvertContext&, FXP::Object const&, long long, FXP::PXF::(anonymous namespace)::SubClipInfo const&, FXP::Object&) + 285
1   com.adobe.FCPXProjectConverter.framework 0x00000003b317d946 FXP::PXF::AddClip(FXP::PXF::(anonymous namespace)::ConvertContext&, FXP::Object const&, FXP::Object&) + 4182
2   com.adobe.FCPXProjectConverter.framework 0x00000003b317b113 FXP::PXF::AddProjectItems(FXP::PXF::(anonymous namespace)::ConvertContext&, FXP::Object const&, FXP::Object&, bool&, dvacore::utility::Guid const&) + 1331
3   com.adobe.FCPXProjectConverter.framework 0x00000003b317b69f FXP::PXF::AddProjectItems(FXP::PXF::(anonymous namespace)::ConvertContext&, FXP::Object const&, FXP::Object&, bool&, dvacore::utility::Guid const&) + 2751
4   com.adobe.FCPXProjectConverter.framework 0x00000003b31796e8 FXP::PXF::ConvertPProProject(FXP::SharedPtr<FXP::Object>, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, FXP::Progress&, bool, FXP::SharedPtr<FXP::Object>&, dvacore::utility::Guid const&, std::__1::set<FXP::PXFTranslationIssue, std::__1::less<FXP::PXFTranslationIssue>, std::__1::allocator<FXP::PXFTranslationIssue> >&) + 776
5   com.adobe.FCPXProjectConverter.framework 0x00000003b317bc81 FXP::ConvertPProToFCP(FXP::SharedPtr<FXP::Object>, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, FXP::Progress&, bool, FXP::SharedPtr<FXP::Object>&, dvacore::utility::Guid const&, std::__1::set<FXP::PXFTranslationIssue, std::__1::less<FXP::PXFTranslationIssue>, std::__1::allocator<FXP::PXFTranslationIssue> >&) + 833
6   com.adobe.FCPXProjectConverter.framework 0x00000003b316c0d1 FXP::ConvertPProToFCPXImpl(std::__1::basic_istream<char, std::__1::char_traits<char> >&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, bool, std::__1::basic_ostream<char, std::__1::char_traits<char> >&, dvacore::utility::Guid const&, FXP::Progress&, std::__1::set<FXP::PXFTranslationIssue, std::__1::less<FXP::PXFTranslationIssue>, std::__1::allocator<FXP::PXFTranslationIssue> >&) + 497
7   com.adobe.FCPXProjectConverter.framework 0x00000003b316f03b FXP::PProToFCPXOperation::OnThreadProc() + 395
8   com.adobe.FCPXProjectConverter.framework 0x00000003b3036fc2 FXP::Proc(void*) + 18
9   libsystem_pthread.dylib       0x00007fff731b2661 _pthread_body + 340
10  libsystem_pthread.dylib       0x00007fff731b250d _pthread_start + 377
11  libsystem_pthread.dylib       0x00007fff731b1bf9 thread_start + 13
 
Thread 52:
0   libsystem_pthread.dylib       0x00007fff731b1bdc start_wqthread + 0
1   ???                           0x0007000200020005 0 + 1970333427040261
 
Thread 53:
0   libsystem_kernel.dylib         0x00007fff72feb292 __workq_kernreturn + 10
1   libsystem_pthread.dylib       0x00007fff731b220e _pthread_wqthread + 1552
2   libsystem_pthread.dylib       0x00007fff731b1be9 start_wqthread + 13
 
Thread 51 crashed with X86 Thread State (64-bit):
  rax: 0xffffffffffffffff  rbx: 0x00006000036a9a20  rcx: 0x0000000000000000  rdx: 0xffffffffffffffff
  rdi: 0x0000000000000001  rsi: 0x0000000000000000  rbp: 0x000070000a7a1300  rsp: 0x000070000a7a12a0
   r8: 0x0000000000000000   r9: 0x000000000000000a  r10: 0x000000000000000a  r11: 0x0000000000000030
  r12: 0x0000000000000000  r13: 0x0000000000000000  r14: 0x00006000036a9a69  r15: 0x0000600004696148
  rip: 0x00000003b3181bed  rfl: 0x0000000000010246  cr2: 0x0000000134a54000
  
Logical CPU:     0
Error Code:      0x02000003
Trap Number:     133

 

This topic has been closed for replies.

2 replies

M
Morningstar22337300iodq
Participant
June 25, 2024

Ran into this same issue, fixed it by just removing some titles that were not in adobe's default font list and that fixed it. Not sure if this can help someone else but it saved me a lot of time. 

M
Michael Grenadier
Legend
November 7, 2019

can you give us the specifics of the clip (codec, pixel dimensions, framerate)?  FXP7 was last updated about 10 years ago.  Formats have changed enormously and there may be a compatibility issue.    I don't think I've ever exported an xml of a single clip but I've certainly done xml exports of very complex sequences and in that case you'll usually get a warning that there are issues and that there's a document detailing the issues in the same folder as the xml...

 

What happens if you control click on the clip, make sequence from clip, and then export an xml from the sequence which only has the one clip.  Also, can you explain why you want to do this?

J
jeroenp93869257Author
Participant
November 7, 2019

Hi mgrenadier,

 

Thank you for thinking along! To answer your questions:

 

Clip specifics: .mov, ProRes 422 HQ, 2048x1152 (2k), 25fps.

 

Create sequence from clip, then export sequence: yes, that works. However, the resulting XML doesn't work in the software programme Kyno. This could mean two things:

 

1 the XML is not a true "clip" XML, because it is a sequence export.

2 Kyno doesn't read Final Cut XML's properly. (It should, see below)

 

This links to the reason why I am trying this:

1 I have logged my material, using markers, in Premiere Pro.

2 I want to break-out the logged metadata from Premiere Pro and bring it into the metadata manager software Kyno.

3 In Kyno's latest update, they specifically make clear this is possible on their side (export clip XML from PP, bring into Kyno). See the video here for an example - I've anchored the appropriate time code in the video:

 

 

4 Why do I want to break out to Kyno in the first place: Kyno is a better "overview" software for looking at material + I want to have the possibility to edit the project in FCPX, including having the already logged metadata created in PP in FCPX.

 

Hope this clarifies it a bit. Please let me know if you have more questions?

 

Thanks!

 

UPDATE: 

I have just tried bringing in a random clip to a new PP project, and exporting the XML of that clip. That works (it exports without crashing). Unfortunately the key is to make it work from the existing PP project, since all my metadata is in there.

 

UPDATE #2:

Workaround found!

 

1 I created a new PP project.

2 I brought in a clip, which includes markers from the original PP project to the new PP project, through the Media Browser. Result: clip with markers succesfully shows in new PP project.

3 I exported that clip XML from the new PP project. BAM! Works like a charm.

 

Conclusion: bring all clips from the original PP project into a new PP project through the Media Browsers - then export clip XMLs from the new PP project. It seems to work, though it will be a time-intensive job. But already happy I got it to work somehow.

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