Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Panasonic Cameras P2 Woes Spanned cards come in black

  • Jeremy Garchow

    December 4, 2008 at 7:30 am

    [Warren Eig] “Here’s what I’ve learned. There is no problem with my SAN copying files from the Finder over 4 GBs. I can export an 18 GB HD file out of FCP 6.0.5 using export QuickTime Same as source make self contained file, no problem to the SAN. “

    [Warren Eig] “Once I have L&T a spanned clip larger than 4 GB, I cannot take that clip, now a .mov file, place it in a time line and export it using export QuickTime Same as source make self contained file, to the SAN.”

    These two comments might have a conflict. In the second one, you mention that once you have L&t’d a spanned clip you can’t export it to the SAN, but in the first one you say you can. If you are L&Ting to the raid, won’t the second clip in the second scenario be ruined anyway?

    Where have you sent the capture scratch in both scenarios? If you are sending the cap scratch to your ‘Zelin’ raid in the second scenario, that is what we have figured out in this long thread and I would imagine it has to do with the process of rewrapping the MXF audio/video, extracting tc, grabbing minimal metadata and writing to a compliant DVCPro HD QT and also writing the file frame by frame with resulting metadata in a file size that MIGHT not be really friendly with the RAID when it’s asked to handle these processes after being handed off by the OS or FCP in an order that might appear to happen at the same time.

    By the way, have you seen MXF4mac? There is no log and transfer.

    What’d Bob say? Your shared storage is hooked up how? How is it managed? What protocol is it using to transfer all of this processed media?

  • Warren Eig

    December 4, 2008 at 4:06 pm

    Jeremy,

    Thanks for helping.

    I think you need to reread what I wrote. I said I can copy the file to the SAN from the Finder. I cannot export it from FCP to the SAN nor can I L&T the spanned clips to the SAN.

    I can set an internal SATA to the scratch disc and L&T fine. If I set the SAN as the Capture scratch disc I cannot.

    I am not sure how this is a conflicting statement.

    I think you are confusing copying from the Finder with exporting from FCP they use different protocols.

    Warren

    Warren Eig
    O 310-470-0905

    email: warren@babyboompictures.com
    website: https://www.babyboompictures.com

    https://babyboompictures.com/AFX_Movie2.html
    https://babyboompictures.com/KnitWits_Movie.html

    EDITING REEL: https://www.babyboompictures.com/Editing_Reel.html
    TITLE DESIGN: https://www.babyboompictures.com/Titles_Reel.html

  • Tom Brooks

    December 4, 2008 at 4:38 pm

    It is getting a bit confusing. With your explanation and some reading between the lines I get this:

    1. You can export a large file (that is not a L&T’d clip from a spanned P2 clip) from FCP to the SAN.

    2. You can L&T spanned clips to an internal SATA drive.

    3. You cannot L&T a spanned clip directly to the SAN.

    4. You cannot L&T to an internal SATA drive, then export that clip from FCP to the SAN.

    As you point out, Warren, the interesting comparison is between #1 and #4. What is it about a .mov file that came from a spanned P2 clip that makes it different from a large .mov file that did not originate from a spanned P2 clip?

    We’re probably missing something simple. Can you reveal the source in the Finder and compare what is actually stored? Are you getting those “-av” files, for example?

  • Warren Eig

    December 4, 2008 at 4:53 pm

    #4 I can L&T to an internal SATA Drive, to be clear, I can. But no I cannot then export it from FCP using Export Quicktime, Same as source, make independent clip.

    When I reveal the clip in the finder it is a .mov file. I can play it in Quicktime I can hit the space bar and quick preview. Ic an work with it in FCP. Why it doesn’t like to export over AFP to the SAN I do not know.

    Warren

    Warren Eig
    O 310-470-0905

    email: warren@babyboompictures.com
    website: https://www.babyboompictures.com

    https://babyboompictures.com/AFX_Movie2.html
    https://babyboompictures.com/KnitWits_Movie.html

    EDITING REEL: https://www.babyboompictures.com/Editing_Reel.html
    TITLE DESIGN: https://www.babyboompictures.com/Titles_Reel.html

  • Jeremy Garchow

    December 5, 2008 at 3:23 am

    [Warren Eig] “I think you need to reread what I wrote. I said I can copy the file to the SAN from the Finder. I cannot export it from FCP to the SAN nor can I L&T the spanned clips to the SAN. “

    So where does that part about exporting an 18GB file to the SAN come in, from your earlier post:..?

    [Warren Eig] ” I can export an 18 GB HD file out of FCP 6.0.5 using export QuickTime Same as source make self contained file, no problem to the SAN. “

    Have you tried this on 6.0.4? 6.0.5 added more p2 metadata support and might have busted something in the process.

    Jeremy

  • Jeremy Garchow

    December 5, 2008 at 3:27 am

    Warren, you shouldn’t export it to the SAN. You simply copy it to the SAN, then import that clip into FCP.

    So, you l&t to the boot drive (or other internal drive), COPY that file to the SAN and import it to FCP. This will have to be your work around till the SAN is figured out.

    Jeremy

  • Warren Eig

    December 5, 2008 at 5:45 pm

    That’s the solution I’ll have to use.

    By the way, the 18 GB file was just an example that I could export a file larger than 4 GB from FCP to the SAN if it wasn’t a clipped that originated as P2 spanned media. In other words, it’s not a 4 GB limit to the SAN just a 4 GB limit if it is P2 media.

    Or the files we happened to shoot ended up corrupt on write to the P2 cards or when the DIT transfered them with the P2 store to the hard drive. I’ll never know the answer as I don’t have the P2 cards any more. Though I’m not leaving out the possibility that P2 spanned media is inherently wonky.

    Warren

    Warren Eig
    O 310-470-0905

    email: warren@babyboompictures.com
    website: https://www.babyboompictures.com

    https://babyboompictures.com/AFX_Movie2.html
    https://babyboompictures.com/KnitWits_Movie.html

    EDITING REEL: https://www.babyboompictures.com/Editing_Reel.html
    TITLE DESIGN: https://www.babyboompictures.com/Titles_Reel.html

  • Jeremy Garchow

    December 6, 2008 at 12:12 am

    [Warren Eig] “In other words, it’s not a 4 GB limit to the SAN just a 4 GB limit if it is P2 media. “

    Got ya.

    [Warren Eig] “Or the files we happened to shoot ended up corrupt on write to the P2 cards or when the DIT transfered them with the P2 store to the hard drive”

    I don’t think so as the cards seem to work everywere but that SAN in very specific steps. I think it’s either an FCP or SAN error, or combo of both.

    Have you tried FCP 6.0.4?

  • Warren Eig

    December 6, 2008 at 6:56 am

    Jeremy,

    I haven’t tried 6.0.4. I have that on my clone so I will.

    I will be running a test tomorrow shooting with an HVX-200 and an HPX-500 and spanning the P2 cards over 4 GB. I want to see if it was a fluke with the cards and camera on the last job or if this is in fact repeatable with new media.

    I’ll keep you posted.

    Warren

    Warren Eig
    O 310-470-0905

    email: warren@babyboompictures.com
    website: https://www.babyboompictures.com

    https://babyboompictures.com/AFX_Movie2.html
    https://babyboompictures.com/KnitWits_Movie.html

    EDITING REEL: https://www.babyboompictures.com/Editing_Reel.html
    TITLE DESIGN: https://www.babyboompictures.com/Titles_Reel.html

  • Jeremy Garchow

    December 6, 2008 at 5:26 pm

    [Warren Eig] “I’ll keep you posted. “

    Please do. I’m curious.

Page 5 of 6

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