-
P2 spanned files into FCP
Hi –
has anyone ever seen a 4 Gigabyte limit to importing P2 files that were SPANNED between multiple cards in a camera ? Having issues bringing in large spanned P2 files into FCP. Non spanned files work just fine.Bob Zelin
-
3 Replies
-
NO issues here. Spanned clips on one card (long shots) import as one clip, and as long as you have all the card dump folders mounted in the L&T window, the spanned clips from one card to the next should connect.
Is that not happening?
What versions of OS, FCP and QT?
Shane
GETTING ORGANIZED WITH FINAL CUT PRO DVD…don’t miss it.
Read my blog, Little Frog in High Def -
Bob,
You’re gonna have to explain what I just posted below…
“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.
What I cannot do is L&T spanned clips larger than 4 GB to the SAN, (I can to a local attached SATA drive no problem).
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.
It will go through the motions of exporting the clip, progress bar and all, but when it is done, the resulting clip is only 728.1 MB (original converted P2 spanned movie I’m trying to export is 4.79 GB).
There must be some meta data written to a converted P2 file over 4 GB that FCP doesn’t like when working with a SAN. Remember this is now a .mov file no longer MXF. ”
Warren
Warren Eig
O 310-470-0905email: warren@babyboompictures.com
website: https://www.babyboompictures.comhttps://babyboompictures.com/AFX_Movie2.html
https://babyboompictures.com/KnitWits_Movie.htmlEDITING REEL: https://www.babyboompictures.com/Editing_Reel.html
TITLE DESIGN: https://www.babyboompictures.com/Titles_Reel.html -
Bob, if you read the very long thread that sparked your question, you will notice the trouble shooting that went on (you can actually skip through all of my QT conflict trouble shooting and Warren’s plug in conflict trouble shooting). The problem has to do with the SAN and the log and transfer process, as it works when going to a local drive. Also, you might want to try this with FCP 6.0.4 and that SAN. 6.0.5 added some P2 metadata structures that seem to be accesible in the log and transfer window, but not in the project. Where does it go? Might be a good place to start.
Jeremy
Reply to this Discussion! Login or Sign Up