Problem Re-importing and Reconnecting P2 Files

[Jeremy Garchow]

You originally imported the media using FCP 5.0.4 or something else, like p2 log? Did you keep the p2 name structure? If so , you can batch reimport the media (ideally in a new separate project) and then reconnect your the clips from your original project with this new media.

What frame jitter problem? If this is in fact true it might explain the errors you are seeing. The reel name error makes sense as FCP 5.0.4 would name the reel something very generic (like P2 card or something i can’t remember). FCP 5.1.2 names the reel the same as the folder the media is in, which is awesome. The Rate error might make sense if you are trying to remove pulldown on import or some such process that didn’t work with FCP 5.0.4 so if you are changing the frame rate, this error makes a bunch of sense.

The Media In/Out error only makes sense if you imported with something else besides FCP (like P2 log) originally.

Any of this sound familiar?

Jeremy

[Shane Ross]

[JeremyG] “What frame jitter problem?”

You didn’t know about this? Yeah, it is an issue. This happens to a lot of people who import running FCP 5.0.4 then upgrade to 5.1…or who just are working. The image will stutter before or after a transition. The solution was to trash the imports and to reimport.

This is why I keep the original number in my clip name when I import and log…so that I can match clips to clips. I also would never import using P2 Log or the new 5.1.2 import feature where you can mark and IN and OUT point, as you will never be able to replicate that again when you import (well, not never, but it would be VERY time consuming and difficult).

How did you import the first time? And did you rename your clips?

Shane

Littlefrog Post
http://www.lfhd.net

[Jeremy Garchow]

[Shane Ross] ” I also would never import using P2 Log or the new 5.1.2 import feature”

Actually if you keep the exact directory structure of the MXF files consistent, 5.1.2 will match back to your clips. All you have to do is select the offline clips and select batch capture.

It’s a breeze.

Yes I did know of the problem you mention, Shane, but the original poster said he upgraded to FIX a frame jitter problem, not introduce one. I am thinking the non working pulldown removal, in this case, means frame jitter problem. Anyway, I’m speculating which is dangerous.

Jeremy

[Tristan004]

Thanks, Shane & Jeremy.

Shane – you were helping me last week with the “jitter” problem. Here’s what’s what:

No, I didn’t rename any of the files. They were straight imports from the individual folders that the .mxf P2 files were placed into. Yes, I did start a new project and re-import the files into that project. The project was set up with the same parameters as the program.

Jeremy – you said “All you have to do is select the offline clips and select batch capture.” Can I “Batch Capture” to import the files instead of reconnecting the media?

Tim

[Jeremy Garchow]

[tristan004] “Jeremy – you said “All you have to do is select the offline clips and select batch capture.” Can I “Batch Capture” to import the files instead of reconnecting the media?”

No. You must have imported from FCP 5.1.2 to batch recapture. FCP 5.1.2 is really easy to batch import new, though.

Jeremy

[Tristan004]

Hey Jeremy.

Thanks for all the help. For whatever reason, fcp doesn’t seem to want to “batch” re-import. I have to force it to go clip by clip. If I select multiple files, then tell it to reconnect the media, it doesn’t recognize the P2 name – even though it’s still exactly the same. If I turn off “Matched Name Only,” I can then re-select each individual clip one at a time. What am I doing wrong here?

Tim

[Tristan004]

Oh – and for the record – I did originally import the media into fcp 5.0.4, then upgraded to 5.1.2 while the media was on the drive. I’ve since dumped the original qt files (not the .mxf files, but the qt files made during the import done with 5.0.4), and re-imported the media using File>Import>Import P2 Media. The .mxf files have remained in the same location – on a server – all along.

Tim