Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy log and transfer crashes due to a corrupt file

  • log and transfer crashes due to a corrupt file

    Posted by Sven Giebel on March 14, 2008 at 8:22 pm

    Hi,
    I had a problem today with FCP crashing while log and transfer was activated. When FCP tried to read a mounted P2 card the app crashed with an error message that said : the file libMXF_SDK_r.3.2.0.132.dylib is probably involved in the crash.
    I searched for a solution and found only one message somewhere on the web where somebody said he found a small 32kb mxf file to be responsible for the crash.
    After eliminating the file ( you have to unlock all folders on the file path first) he could continue his work.
    I found a corrupt 32kb on one P2 card and deleted it via the camera menu of our panasonic 2100. Afterwards I could log and transfer again. The file was a clip which obviously was damaged when we were changing batteries on the shooting.
    One thing didn’t work for me: I had made a backup of the P2 cards. I had copied contents folders and lastclip files into seperate folders per card onto my hard disk as I usually do it for backup reasons.
    Although I could delete the corrupt file from there FCP still crashed when I opened the contents folder via the file path option in log and transfer.
    The free panasonic P2 management tool still saw the corrupt file although it didn’t show up in Finder. I couldn’t delete the file with the panasonic tool.
    Maybe the structure of the contents folder has to be changed manually after deleting an mxf file or the lastclip text has to be changed?!
    Do you know what I have to do when I want to delete a corrupt mxf file in the finder?
    Thank you for your input!
    Sven

    David Pedersen replied 17 years, 2 months ago 5 Members · 8 Replies
  • 8 Replies
  • Andy Fjellman

    March 24, 2008 at 4:28 pm

    Sven,

    I just had the same exact error and couldn’t figure it out. I finally went to the camera and repaired the clip on the camera it imported fine… no crashing. I’m not sure if this helps you at all, but if anyone else gets that error, and you have the option to repair the clip before importing or copying, that should fix it.

    Andy

    2 X 2.8 GHz Quad-Core Mac Pro with 6 GB RAM
    2.5 GHz Macbook Pro
    FCS2

  • Sven Giebel

    March 24, 2008 at 9:26 pm

    Hi Andy,
    thanks for your posting!
    In the end I did exactly what you did: I took the camera and deleted the clip there. Repairing wasn’t an option on this clip.
    Fortunately the stuff was still on the cards in the camera. Next time I will check the clips in the camera before I copy the cards content to disk.

    Sven

  • Thomas Stitt

    May 15, 2008 at 12:28 am

    I’m having this exact same problem. As mentioned above, I have the P2 card backed up on my hard drive, and even though I deleted the 32K MXF file in the video folder, it is still crashing FCP when I attempt to log & capture.

    Unfortunately for me, I do not still have the footage on the card itself, I only have it backed up to the computer. It is crucial that I recover the footage in this backed up card – It is NOT possible to re-shoot.

    Has anyone figured out a solution to this problem? I desperately need to figure this out.

  • Thomas Stitt

    May 15, 2008 at 5:59 am

    Okay I figured it out: Deleting the corrupt .mxf file is not enough. Go into the audio, clip, and icon folders and delete the corresponding files there (the file names should mostly match).

    If you’ve gotten rid of all the corrupt files, it’ll work. If it’s not working, keep combing through and make sure you’ve gotten them all.

  • Kyle O’brien

    May 20, 2008 at 9:36 pm

    Hi my name is Kyle O’Brien,
    I am having the same problem!
    Final cut crashes when I try the log and transfer fucntion!
    This is an emergency!
    How do you know which file to delete?
    Which file is corrupt?
    Thank you guys so much for posting!

  • Thomas Stitt

    May 20, 2008 at 10:27 pm

    As mentioned above, you need to find the video clip that is only 32K in size. So go into the P2 directory in Finder, go into Contents>Video (I think that’s the directory), and most likely one of the .mxf files there will be only 32K. Make a note of what it’s called, it will most likely be a random alphanumeric name like HSF302 or whatever. Now delete it.

    Now go through all the other directories on the P2 card or P2 backup folder. Go through Audio, Clips, and Icons. You’re looking for files that have a similar name to the file you deleted, pay attention to the letters in the file names. The audio files are probably all 256K.

    Delete them all as you find them. Then your card should work in Log & Capture.

    Now here’s a question: Does anyone know why the hell this happens??

  • Sven Giebel

    May 21, 2008 at 3:18 pm

    Now here’s a question: Does anyone know why the hell this happens??

    Hi Thomas!
    FortunateIy I can remember the shooting, so in my case the file went corrupt because we changed the battery on our panasonic AJ-HPX2100E and I forgot to stop the camera BEFORE changing the battery. It was exactly this clip which was unusable.
    Greetings,
    Sven

  • David Pedersen

    March 2, 2009 at 6:27 pm

    Hi,

    I have the plug-in issue (libMXF…..plug-in) and cannot log and transfer my footage. My camera was turned off abruptly during an interview when my power strip failed. I repaired the files and since have gotten rid of the ‘x’ and ‘!’ in the upper right hand corner of each clip on my p2 card, in the HVX camera. FCP studio 2 still will not log and transfer. It shuts down. I also tried the “remove advanced pulldown,” but as I shoot in PN, I have no drop-frames anyway, so that wasn’t an option.
    I found the .mxf files in my firewire connection, but could not find any files that were 32KB in size. Is there another way to find the corrupt file? I’m a technology neanderthal, you will have to speak plainly.
    Thanks guys and gals!

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy