PP CS6 EDL export problems

[John Tissavary]

EDLs generated from the last two client edited CS6 PP projects are not conforming properly in either Resolve or Scratch.

Same goes for XML. Some EDLs come in with completely inaccurate cut-points, others pull totally wrong clips. Honestly, I've conformed hundreds upon hundreds of projects in various grading systems and have never had so little success with EDLs, which are usually bullet proof if nothing else.

XML are coming in a little better, but well over 50% of shots are coming in slipped by 2-3 frames, and in some cases 15 or more frames. One project came in today that was in good shape until about 1/2 way through a 30 minute timeline when the edits started to slip by an entire cut (cut points were accurate, but shots were one cut ahead or behind).

Truthfully I don't get a lot of PP edits in my grading suite, but so far it's causing me no end of headaches, to the point where I'm worried that I have to turn down projects edited in those packages. Which would be really ironic since I prefer editing in CS6 myself... but not if I can't get an accurate conform once leaving the NLE...

Any help would be appreciated.

John T.

 

[Cory Petkovsek]

I am exporting an entire feature from FCP7, relinking through RCX, and importing both RCX and FCP xml files into premiere. Everything comes in fine throughout the entire timeline, except for time remapped clips. Time remapping on our proxies imported directly into premiere mostly works and we can copy the settings over to the r3ds, but some clips are not right. We have to handle time remapped clips specially.

Also I have done a lot of exporting of PPro XML and EDLs for import into RCX and haven't had any be incorrect. I have not gone from PPro to resolve/scratch, but if it reads ok in RCX then the exported file should be right.

If you are getting both an edl and an xml from a client, are they off in the same way? Are they different? If they are different than you may have an adobe bug to report (I think its unlikely).

If you import the problem edl file into both scratch and resolve, are they off the same way? or are they different?

What about AAFs?

Have you read the FCP translation<date>.txt file? It may very well say of the clips you have a problem with, "this clip has some effect that was ignored or couldn't be copied, etc". Usually it expresses concern over transitions.

EDLs are text files. You should be able to open up the text file, look at the problem area and call the client and compare a problem clip. Ie. Clip A38_c004 in resolve has 04:55 in and 5:13 out at timecode 07:38, the EDL should say the same thing (barring inclusive/exclusive outs), the ppro timeline should report the same thing. Whichever link in the chain is reporting wrong has a bug to be reported or a setting to be changed.

You can also use this to determine if there are any time remapping or other effects applied to those specific clip that is causing the issue. You can also test creating a new timeline with just 1-3 problem clips, and exporting an edl, xml and aaf. Then see what the edl and xml look like by reading the actual text of the file, and also importing them into your system to see if they load properly.

Are timeline framerates matching?

There are so many things you can test before you can rule out your systems as the cause.

Cory

 

[John Tissavary]

So far AAF is the only format that works. Tried that today and 99% of shots import correctly. This is two projects from two different clients with very similar problems.

I've read a lot of EDLs in my time... trust me I've been over everything you've suggested, and it's absolutely either Resolve or PP, or a combination of both (my bet is on combination for xml, cs6 for edl). What's really bizarre is that the EDLs come into both Resolve v9b3 and Scratch as 4 hours +.

 

[mikeburton]

Hey John, long time. Sorry you're having trouble. Try giving Erik Espera a ring. He can potentially help troubleshoot, he works for Adobe TV and uses Premiere everyday. If you need his number send me an email at mike@prettymovingpictures.com

 

[Cory Petkovsek]

it's absolutely either Resolve or PP, or a combination of both

'One or the other or both' is the same place where you started.

If the EDL is accurate to the PP timeline, then Resolve has a problem. If the EDL doesn't match the PP timeline then PP is the problem. In the case of time remapped clips or other effects, the "problem" may just be an inability to export clips with those settings.

I don't know what you are looking for. I thought I was helping troubleshoot. My troubleshooting leads toward reducing variables to find a solution. All of my suggestions were discounted in one sentence, yet you still have far too many variables and no solution. Hopefully Mike's contact can help you.

Cory

 

[John Tissavary]

I don't think I discounted anything, sorry if it sounded like that. You're right, I'm still no closer to knowing why the EDL & XML exports don't work, but I do know this - AAF works.

I have to suspect PP's EDL & XML exporter. Seems like EDLs are a lost cause with both projects, but XML timeline duration and cut point locations are good, so I believe it is also possible that Resolve (or my settings in Resolve) could be a factor in the lack of successful conforming.

BTW, there are time changes in the EDL, and they exported just fine.

I've not seen this symptom once in the last 5 years from any Avid or FCP generated EDLs, which leads me to suspect something is different about how PP writes EDLs & XML.

JT

 

[John Tissavary]

Thanks Mike - I'll hit Eric up for sure, thanks for reminding me! How are you these days? Long time no see...

JT