Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy P2 – Invalid Directory Structure – please help

  • P2 – Invalid Directory Structure – please help

    Posted by Katie Van on June 5, 2008 at 1:59 am

    I am getting the warning “contains unsupported media or has an invalid directory structure” for a P2 volume I’m trying to ingest. I am importing from a drive and can see that all the other volumes’ contents folders have Audio, Clip, Icon, Proxy, Video, Voice, while this one only has Audio and Video.

    The weird thing is someone already ingested this stuff previously. They did not select “Remove Advanced Pulldown,” so I am re-ingesting, but this is the drive they imported from and this volume did make it into our project (at the wrong frame rate). I unfortunately cannot contact them at the moment, but how is this possible? Do I need those other folders? That’s the only difference I can see between this volume and the others, which are working for me.

    Can anyone help me get this stuff in?

    Thank you!

  • 11 Replies
  • Jeremy Garchow

    June 5, 2008 at 3:07 am

    [Katrina Mann] “Do I need those other folders?”

    TO reingest, you’d need those folders yes, as FCP is warning you. It doesn’t have all the information it needs to complete the import.

    Now, that being said, you have the Quicktime media of these shots? What frame size and frame rate are you working in?

    Jeremy

  • Katie Van

    June 5, 2008 at 3:16 am

    Yes, I have the quicktime media. It was brought in at 29.97, 1280 x 1080.

    I’ve been told it was shot 24 in a 1080i wrapper. Meaning (I’ve been told) that unless I remove the pulldown it will come in 30, even though it was shot at 24. Even when I do this though, it’s coming in 29.97. So I guess that’s another issue that you may know the answer to – how do I get 24 “wrapped in 30” to come in 24?

    I am am quite confused and trying to get a grasp on it, and really need to get it into our project at 24 for my editor tomorrow. (This is B cam, and is supposed to match the A cam, which is true 24).

    By the way, A cam is P2 3000 and B cam is P2 200.

    Can you help?

  • Jeremy Garchow

    June 5, 2008 at 3:23 am

    [Katrina Mann] “By the way, A cam is P2 3000 and B cam is P2 200. “

    Got ya. Any idea if it was shot 24p or 24pA?

  • Katie Van

    June 5, 2008 at 3:27 am

    Not really.

    The AC wrote to me that it’s
    “30fps with field reductions to create a synthetic 24p look”

    and the DP said it’s “24p 1080i”

  • Jeremy Garchow

    June 5, 2008 at 3:38 am

    OK. Let’s assume it’s 24p and not 24pA. You can remove the pulldown in Compressor. Open the ORIGINAL files within compressor…………..

    Wow, I can totally type this all out or it really might be easier to talk to you on the phone if that’s cool.

    If you send a way for me to get a hold of you, I’ll ring you if you are in front of the computer.

    You are using FCS2 hopefully?

    Jeremy

  • Katie Van

    June 5, 2008 at 3:41 am

    We’re using 6.0.3

    I’m at 323-661-3456

    Thank you!

  • Steve Eisen

    June 5, 2008 at 3:49 am

    In Log & Transfer, it sounds like you are selecting the main folder that contains the subfolders with the P2 media. Try selecting the subfolder for the P2 card.

    Steve Eisen
    Eisen Video Productions
    Board of Directors
    Chicago Final Cut Pro Users Group

  • Jeremy Garchow

    June 5, 2008 at 4:21 am

    Hey Steve, how are ya?

    I think we have it sorted. It was shot 24p anyway so reingesting wouldn’t help.

    Jeremy

  • Steve Eisen

    June 5, 2008 at 4:26 am

    Cool!

    Once I got that warning. Solved it by opening the root folder.

    Going to HD Expo?

    Steve Eisen
    Eisen Video Productions
    Board of Directors
    Chicago Final Cut Pro Users Group

  • Jeremy Garchow

    June 5, 2008 at 4:32 am

    [Steve Eisen] “Going to HD Expo?”

    Yessir. I’ll be there tomorrow.

Page 1 of 2

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