Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Panasonic Cameras Native MXF question

  • Native MXF question

    Posted by Kim Rowley on January 26, 2009 at 9:27 am

    I have just come back from my first P2 gig in Africa. I am looking into the options available to do Native P2 editing with FCP 6 (MXF4mac and Calibrated). I am trying to discern the possibility of importing only selected clips. Is that possible? I’ve watched Jeremy’s MXF4mac tutorial and the examle he uses imports all footage. What do people generally do when bypassing the Log and Transfer with these kinds of plugins?

    Also, am I correct in assuming that when editing natively, it’s better to have an untouched backup that resides on another hard disk? I have 2 2TB drives almost full having offloaded the card using Raid1.

    Should I back those up elsewhere before editing?

    Thanks!
    Kim

    Dual 2.7 GHz G5, 4GB RAM, ATI Radeon 9650, Xserve RAID, AJA IO, 2 20″ Cinema Display, FCP Studio 2 (6.02), OS X10.4.11

    David Keslick replied 17 years, 3 months ago 3 Members · 4 Replies
  • 4 Replies
  • Jeremy Garchow

    January 26, 2009 at 5:36 pm

    [Kim Rowley] “I am trying to discern the possibility of importing only selected clips. Is that possible?”

    Currently, not with P2Flow CM (which comes installed with the latest version of MXF4QT Import), but here’s the catch: You can send the media over to FCP and delete anything you don’t want out of the browser. This way, you aren’t duplicating your media in a rewrap to Quicktime. You are using the native P2 media. You are shooting DVCPro HD or AVC-I?

    I’d keep an untouched backup on a separate drive and transfer the P2 media you plan to use in the edit on to your RAID subsystem.

    Where were you in Africa?

    Jeremy

  • Kim Rowley

    January 26, 2009 at 6:37 pm

    Thanks Jeremy. The jump from Digibeta to P2 is a continuous learning experience.
    I was in Cameroun for almost 3 weeks. First in Douala and then in a small village called Fontem in the forest about a 6 hour drive from there. A fantastic experience.
    Our 3 HVX171’s stood up to the dust and heat and humidity perfectly – much better than we did 🙂 I opted for offloading with HDLog on a MacbookPro using Western Digital 2 TB drives set to RAID1. Miraculously everything performed well and it went very smoothly. I’m now trying to sort out the rest of the workflow since the material will be edited on 3 different workstations. As I said…a never ending learning experience 🙂

    I have to say that I’m beginning to think again about the QT re-wrap process and it may not be all that bad after all. Wouldn’t it give more peace of mind to just use HD log to select shots and export them as a QT file to use for editing (metadata included Imagine assures me). My MXF files are safe on a separate drive and I can edit without worry and just delete the QT’s upon job completion after laying off to tape (DigiBeta master). Just considerations after today’s pondering!

    Then comes the LTO back-up process. But… one step at a time!

    Dual 2.7 GHz G5, 4GB RAM, ATI Radeon 9650, Xserve RAID, AJA IO, 2 20″ Cinema Display, FCP Studio 2 (6.02), OS X10.4.11

  • Jeremy Garchow

    January 26, 2009 at 6:54 pm

    Sounds like an awesome trip. I recently reutned from Nairobi which is why I asked.

    P2 can definitely brave the elements, for sure.

    [Kim Rowley] “Wouldn’t it give more peace of mind to just use HD log to select shots and export them as a QT file to use for editing (metadata included Imagine assures me).”

    It’s up to you and your workflow. You said three different workstations, are they all FCP? If they aren’t a native p2 mxf edit will be much easier as Avid, FCP and Premiere can share the exact same media.

  • David Keslick

    January 26, 2009 at 7:58 pm

    You may also want to check out Raylight for Mac for editing native .mxf files.

    Hope this is helpful,

    Dave Keslick
    DVFilm.com

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