Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Panasonic Cameras P2 Card Import Problems: is there hope for this?

  • P2 Card Import Problems: is there hope for this?

    Posted by John Evans on August 17, 2009 at 11:43 pm

    Hello All. I recently rented an HVX and two 16gig P2 cards. I shot two days worth of footage on the cards and transfered to my MBP. At the end of the shoot the cards were transfered to a USB2 drive and brought back to my studio for editing.

    When I tried capturing the footage into FCP I noted that numerous clips would not transfer using the FCP 5.14 P2 Import utility. Several clips would try to import and when they failed the red “!” icon appeared. Nothing would work to import these clips into FCP.

    These clips also will not transfer off of the USB2 drive onto my MPB or my PowerMac. I get an error -36.

    So, I did some LONG hours of digging. I found that the clips with problems are only on the card that was in slot #1. Here are the cards I captured to, and the ones with problems are noted:

    Card1 PROBLEM CLIPS
    Card2 everything transfered fine
    Card3 PROBLEM CLIPS
    Card4 everything transfered fine
    Card5 PROBLEM CLIPS
    Card6 everything transfered fine
    Card7 PROBLEM CLIPS
    Card8 everything transfered fine

    As you can see, only one of the two cards had files with errors. The other card (I believe Slot 2) consistently had clips with errors. On most cards it was only 2-3 clips that were affected.

    The Video MXF files are on the drive, they show up as having a few hundred meg of content per clip, there are corresponding XML and Audio files, and BMPs, etc.

    I tried ingesting them using P2 CMS and had no luck. It says an error of “It is unable to ingest the clip. It rolled back.”

    So I guess my question is: 1) MOST importantly, is it possible to recover these clips? Can I use the camera to repair them? (2) is this a problem with the drive (fat 32) or the P2card? or something else?

    Thanks in advance for any responses.

    Dixon Johnston replied 15 years, 3 months ago 5 Members · 15 Replies
  • 15 Replies
  • Jeremy Garchow

    August 18, 2009 at 3:27 pm

    [John Evans] “(2) is this a problem with the drive (fat 32)”

    Yes, if your drive is formatted FAT 32, then files over 4GBs will not transcode as the file size is too big. You need a Mac OS Extended formatted drive if you want to have one file over 4GBs.

    Jeremy

  • John Evans

    August 18, 2009 at 3:35 pm

    Hi Jeremy. Thanks for the feedback. However, the files I’m having trouble with are all less than 4gig in size. In fact, they are all around 300-900meg.

    The largest files transferred fine.

  • Jeremy Garchow

    August 18, 2009 at 4:58 pm

    [John Evans] ” In fact, they are all around 300-900meg. “

    Are they spanned?

    I should add, all the MXF files themselves will be under 4GBs, but if you have two spanned clips that will total over 4GBs if you put them together with log and transfer (spanned clips) then the file can’t be created due to the 4GB file size limit of FAT 32.

  • John Evans

    August 18, 2009 at 5:08 pm

    Not spanned clips. In fact the spanned clips work fine too.

    I should clarify/reiterate, these files won’t transfer off the USB2 harddrive onto my MBP desktop, nor will the clips import using FCP’s P2 Import function. But the problem only exists on clips written to ONE of the two cards that were used.

    Today I’m going to try and transfer the files onto a Windows PC then on to a Mac Extended HDD and import them that way.

  • Jeremy Garchow

    August 18, 2009 at 5:29 pm

    [John Evans] “Today I’m going to try and transfer the files onto a Windows PC then on to a Mac Extended HDD and import them that way.”

    Why don’t you plug in an Extended HDD to your MBP, set your capture scratch to that HDD, and away you go. No reason to go through a PC.

  • John Evans

    August 18, 2009 at 5:40 pm

    “Why don’t you plug in an Extended HDD to your MBP, set your capture scratch to that HDD, and away you go. No reason to go through a PC.”

    Maybe I’m not following.

    I cannot get the clips off of this USBdrive using any method. They do not transfer using OSX finder (Error -36). they do not import using the FCP P2 import tool (Red exclamation point). And they cannot be ingested using P2CMS (“It rolled back”).

    I tried importing them from the USB2 drive using FCP with the scratch disk set to the Extended HDD. That was when I got the red Excalmation point stop sign thing in FCP P2 Import.

  • Jeremy Garchow

    August 18, 2009 at 5:43 pm

    OK, now I am following. Then it seems to point to the fat32 drive.

    Jeremy

  • Shane Ross

    August 18, 2009 at 7:12 pm

    Almost sounds like a bad P2 card. If every other card is bad…has an issue..then it points to the card that it was recorded on being the issue. As you copied both cards to the same hard drive.

    DO you still have both cards? Can you shoot tests?

    Shane

    GETTING ORGANIZED WITH FINAL CUT PRO DVD…don’t miss it.
    Read my blog, Little Frog in High Def

  • John Martin

    November 12, 2009 at 12:43 am

    I am having this same issue, with the exception of the hardware. I transferred P2 cards to a G-RAID external disk from a three-day shoot. Upon backing up the files, I was met with the dreaded error -36 message on a number of the files. I can’t transfer those files or do anythign with them really. This is an absolute nightmare! I’m dreading the long walk back to my client to give him the bad news.

    Any help or ideas would be very appreciated!

    Thanks.

  • John Evans

    November 12, 2009 at 3:00 pm

    I ended up making a list of the problem files with the error and using Windows to repair those specific XMF files. This allowed me to transfer the files onto a drive and import them. There were some gray blocks for a few frames or strange video lines but I was able to edit around them. Hope this helps

Page 1 of 2

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