FCP XML problems that should be fixed!

[Joseph Owens]

[Eric Chase] “2) If you have 23.98frame footage in a 2997 frame sequence, the import doesn’t sync

3) Footage that should not have any problems, just don’t import. The edits come in blank. “

Can’t say I have encountered fault type #1. Fault Type #2 is not an XML issue, it is intrinsic to Resolve that the source media framerate absolutely must match the project framebase.

I have seen odd issues with Fault type #3, and so far haven’t pinpointed a common disparity.
With COLOR, these clips were usually just one criteria short of being perfectly compatible, and navigating to it directly in the Browser would usually result in COLOR telling you exactly what was wrong with it — some odd resolution or anything among about a couple of dozen parameters.

I recently filtered out a bunch of 30fps clips in a 29.97 project that the application couldn’t “find”.

jPo

jPo

You mean “Old Ben”? Ben Kenobi?

[Gabriele Turchi]

eric,
you can’t assume that nothing is working without being certain that you are doing things right..

you are saying that XML is not working in resolve at all …
well that is not true

it totally works for me (even multitrack etc..)

yes sometimes that are some circumstances where something does not relink , but in that case you have to chase the issue and try to reproduce it , so BMD can fix …but you can’t say “”xml is not working ”
that is just not true

as far as 239.97 on 29.97 , if the original media is 23.98 resolve will look for 23.98 TC , so ou have to convert the TC of the XML/ del for that …

i wish people could research more before complaining

g

Davinci Resolve Control Surface
MacPro
Cubix desktop 4
2 Red Rockets
GTX470+GTX470+GTX285
24GB RAM
HP Dreamcolor
Panasonic 58PF Plasma

[Andrew Sableton]

Not sure how much time the Blackmagic team wiill spend on fixing issues related to an EOL product (FCP 7)

[Eric Chase]

These issues come up time and time again. If I have just a straight cut movie, then no problem. However, multitrack edits have constantly given me problems both in red, and prores alike. Miss match frame rates are common to TV and documentaries, no? Many low budget shows hodge-podge timelines. As a colorist, you don’t want to take time to re-render whole timelines, before you grade them.

Please forgive my attitude on this. After completing a 30 minute show this morning in Resolve, I noticed 50% of my timeline was completely wrong. 60 missing edits, whole sequences of 23.98fps interviews were completely wrong. Resolve just made a mess of it.

I re-graded the whole show again in Apple Color. Color loaded this show PERFECTLY! It rendered it out and opened in FCP absolutely 100% correctly. If Apple can do it right, why can’t BMD. FCP7 will still be on our systems for a few more years.

IMPORT IS IMPORTANT!!! I don’t want to waist hours and hours fixing a timeline, when when I’m under deadline.

[Marc Fisher]

not a solution to your issues, more a work around, but you could always export your timeline as a single file (dpx string out, Quicktime, etc) and let Davinci’s Scene detection add in the cuts. works pretty good.

as for your issues, i dare you to show my 1 “Professional” level app that doesn’t have some issues with FCPs timeline. I’ve worked on 3 out of the top5 that all have issues with FCP timeline. (don’t even start talking about FCP edls) there’s just something about the way apple is writing an xml file.

Try Smoke.
Try Scratch.
Try Quatel
Try Symphohy (not a native XML reader)
Try DS. (not a native XML reader)

another thought, take that same xml from fcp and see if premiere can open it.. (version 4 xml required) it probably won’t. i’ve had all sorts of issue trying to “wash” my timeline through FCP to Davinci and back.

So it seem more like FCP is the culprit, not all these other apps..

[Marc Fisher]

One other thought, you could try and wash it through Clip Finder.