Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Panasonic Cameras FCP 6.0.2 and P2 files

  • FCP 6.0.2 and P2 files

    Posted by Ken Summerall on November 15, 2007 at 4:41 pm

    I just read on the FCP forum that someone was having trouble with P2 files after upgrading to QT 7.3 and FCP 6.0.2. He said that he cannot access media that was previously imported using Log and Transfer. I think that he means that media that he has in a project will not work after the new update.

    Has anyone else heard of this? Anyone here running 10.4.11 and FCP 6.0.2 successfully with older P2 files?

    Thanks
    K

    Christian Hermstad replied 18 years, 4 months ago 10 Members · 16 Replies
  • 16 Replies
  • Tom Chartrand

    November 15, 2007 at 5:08 pm

    Not yet but there is official word from Imagine Products that the new quicktime 7.3 does in fact not work well with MXF and they are suggesting not to update at this time.

    ATTENTION MAC USERS of HD Log, P2 Log, P2 Log Pro, and DV Log!

    The recent QuickTime 7.3 has caused complications for many software products utilizing its video technology. Imagine Products has also experience such issues with the 7.3 QT update. Please be aware, the update may break QuickTime files from our software as well as other software applications.

    While we are working tirelessly to correct the problem and provide our users a timely patch for their software, we ask that you consider NOT updating to QuickTime 7.3 at this time. If you have already done so, please be patient while we find a workaround.

    Sincerely,

    The Imagine Products, Inc. Team

    Tom Chartrand
    ShorelineDigital

  • Peter Sassi

    November 16, 2007 at 3:30 am

    I am having this exact problem. I had 43 P2 cards logged and then did the update because I had not yet started editing. Now when I open the Log & Transfer window and try to import a P2 folder which was added to the project, I cant even get any of the older 43 P2 folders to show up. This is a “F()&() disaster. These were all logged and audio matched to slates. Two weeks of work.

    Does anyone from any of these closly partnered companies have a solution. I am going to try to Go back to QT 7.2 which was a disaster maybe I’ll try 7.1 I understand it’s part of the system and very difficult to do.

    FCS 6.0.2 OSX 10.4.11

    WOW great fix guys!

    peter

  • Lars Wikstrom

    November 18, 2007 at 9:27 am

    I learned the hard way a couple of years ago when I did an update during a project. Now I don’t update for months and let everyone else experiment with updates to see if they are safe. As a rule of thumb never update until you are sure it is safe. there will always be someone who will update right away who has the problems, don’t let it be you 🙂

    -Lars

  • Barry Green

    November 19, 2007 at 5:44 pm

    FCP screwed up. They introduced a bug (either in 6.0.2 or QT 7.3) which won’t recognize priorly-imported footage.

    If you still have the MXF files you can re-convert them. Or you can forever ditch this problem by going with Raylight. Or you can wait for Apple to fix the bug they introduced.

  • Ken Summerall

    November 20, 2007 at 3:36 pm

    Barry,

    Is this footage that was imported using Log and Transfer or that was imported using a third-party app like HD Log? All of my footage was brought in using L&T.

    BTW, I have not updated and am not having problems, just trying to do my due diligence before an upgrade.

    Thanks
    K

  • Michael Alberts

    November 20, 2007 at 7:41 pm

    We upgraded last Friday to FCP 6.02 in order to eliminate some bugs, however we didn’t see the mention of that update killing the P2 import function. Now that we’ve upgraded we’re unable to import newly loaded Contents folders from a shot yesterday. FCP 6.02 or QT 7.03 has brought us to a grinding halt.
    We have a drive on this system that still has FCP 5.02 installed. We’ll have to reboot into that drive and do the import from there. This sucks big time. How could something this major slip by Apples crack beta testers?

    Michael Alberts
    Ambidextrous Productions, Inc.
    http://www.ambidextrous.net

  • Barry Green

    November 21, 2007 at 12:33 am

    I’d recommend to any P2 users to avoid the 6.02/7.3 update for the time being. Wait for them to sort out what they broke.

    If you have to go to 6.02/7.3 for some reason, be aware that they broke the system. Use Raylight to get back to work, skipping the whole Quicktime thing entirely.

  • Richard Harrington

    November 21, 2007 at 5:49 am

    I Just imported P2 Media fine using

    FCP 6.0.2 and QT 7.3

    Running OZ 10.3.1

    Again.. Zero issues on import using Log and Transfer

    Richard M. Harrington, PMP

    Author: Photoshop for Video, Understanding Adobe Photoshop, and ATS:iWork

  • Shane Ross

    November 21, 2007 at 5:59 am

    Can you verify that OS?

    10.5.1? Not 10.3.1 surely…FCP 6 requires at least 10.4…and 6.0.2 requires 10.4.11…

    Shane


    Littlefrog Post

    GETTING ORGANIZED WITH FINAL CUT PRO DVD now for sale!
    http://www.lfhd.net

  • Pierre

    November 29, 2007 at 6:45 pm

    Yes I have heard of this… that person could’ve been me.

    All of my P2 footage which was brought in via FCP 5 will open in Final Cut 6 (due to the quicktime 7.3 upgrade, or Leopard, or both) ? I think it’s the new quicktime.

    The original MXF file “masters” from the P2 are fine. It’s just the thousands of converted quicktime clips that have already been converted to quicktime via FCP that will not open.

    The clips that are ALREADY IN A TIMELINE seem to playback OK (with in the timeline). However, if I try and double click on that same clip in FCP’s browser then I get a “general error” message.

    If I go to that same clip again (only directly on the drive” then I get a different error.
    Something having to do with “public atom….”.

    Apple Pro Support request that I send them a sample file, which I did… haven’t heard back from them.

    My gut is that there has been a pretty big fudge with these new apple updates.

Page 1 of 2

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