Error importing project XML

Question

Error importing project XML

I keep receiving the following error message when importing project XML on FCP X 10.1:

The object is not on an edit frame boundary

(duration="6286/600s" /fcpxml[1[/project[1]/sequence[1]/spine[1]clip(17)/video[1]/@duration)

this then repeats multiple times, exactly as above, except "clip(17)" is replaced with "clip(18)", "clip(19)", "clip(20)", etc. to "clip(43)"

Does anyone have an idea what this is about? My project is not particularly complicated.

Thanks in advance for any help with this.

Marc

Final Cut Pro X, OS X Mavericks (10.9.2)

Posted on May 3, 2014 9:55 PM

Reply

Answer 1

May 7, 2014 2:56 PM in response to marcfromrockville

I have this problem also. I did a search and missed this one.

What is the format you are editing? I am editing in native h.264 which is obviously not all iframe. Is it possible that XML import/export only supports all iframe editing?

Rick

Reply

Answer 2

May 9, 2014 9:30 AM in response to Rick Llewellyn

I spoke to Apple FCP support a few days ago about this. They reproduced the error on their system after I sent them my XML file but they couldn't explain it. Only hypothesis he had was that there was a compatibility between the much higher hardware specs on the Mac Pro and the MacBook Pro I am using. That doesn't make sense to me, or maybe I just didn't understand what he was talking about. In any case, he was going to look into it further and get back to me but I haven't heard from him yet. If I get a response I will post it here.

The project I'm editing containts video in .mov format and several tiff images.

Reply

Answer 3

May 9, 2014 9:32 AM in response to marcfromrockville

btw, despite the error messages, the changes in the project are being imported and there does not seem to be any corruption or other issues. Also, after a couple of round trips of this same project from Mac Pro to laptop, I'm not getting the error message anymore.

Reply

Answer 4

Tom Wolsky

Level 10

151,082 points

May 9, 2014 9:52 AM in response to marcfromrockville

Thanks for following up Marc.

Reply

Answer 5

Nov 25, 2014 10:39 AM in response to Tom Wolsky

I may have an idea where this is coming from but it's just a hunch so far. I imported an XML that did this.

It seems that FCP X has two different ways of approaching time. A project has an input rate (in this case 25p) but also an output rate (in this case 60p). The timeline assumes the output rate. FCP X seemed to have defaulted the output to 60p without the editor choosing it or even realising it. They were surprised.

Those are not easily divisible so I think some internal conflict can occur. Here are some screenshots. Note the different rates. Not the timeline became 60p (assumed output rate) as I could reach frame :59 even though all the footage was 25p and the project created with 25p in mind.

Reply

Answer 6

giancian

Level 1

0 points

Mar 2, 2015 3:38 PM in response to monkeybrainsmedia

Hello, have you managed to find out why this happens? I've read it's a problem with having clips with different frame rates than the project. But I thought FCPX managed this seamlessly. I'm afraid every time I import an XML and get this error that things could've moved around and messed up the edit. There is surprisingly little information on this error on the internet. If anyone can help, please do! 🙂

Reply