FCP6 -- native editing from P2 cards?

B

Barry_Green

Moderator
Okay, someone tell me why this doesn't mean what I think it means... there's a new line in the tech specs page for Apple's FCP6, and it says:

"Native editing for P2 at 1080i 50/60/VFR and 720p 24/24N/25/25N/30/VFR from P2 cards "

It's on this page:
http://www.apple.com/finalcutstudio/finalcutpro/specs.html

Is this actually "it"? What I've been clamoring for, for a year and a half -- are they actually implementing it? If so, I wonder why they didn't say a word about it at NAB? Especially when they were invited on-stage at the Panasonic press conference, they never said a word about it...

Man, Apple might be closing the gap enough to where I gotta buy another Mac now. Between finally allowing a proper open timeline, and (maybe?) supporting P2 natively, and the Red support... if this is actually true, I think I gotta get FCS2...
 
Barry...

Is this a sign of the apocalypse? You're asking QUESTIONS instead of providing ANSWERS? :-)
 
Unfortunately there is no P2 equipment here to test it with but YES it is going to be supported right away and there will be two little candies implemented as well :)
 
I didn´t think about the "native" for a second, cause i finally saw the numbers 25 and 50 after the 720...
But, hey - native is native isn´t it ;o)
When will it ship?
 
Would seem so Barry. I havent actually seen it, but I have heard talk to that effect from a few people in Tokyo this week.
 
The "operative language" (that's attorney talk) is " . . . from P2 cards."

If it said "directly from P2 cards," it would be a slam dunk

We'll find out this month.
 
Barry_Green said:
Man, Apple might be closing the gap enough to where I gotta buy another Mac now. Between finally allowing a proper open timeline, and (maybe?) supporting P2 natively, and the Red support... if this is actually true, I think I gotta get FCS2...
Click to expand...

I know, I've been saying the same thing all week. This MIGHT be the moment I go back to Mac...
 
Barry,

I posted this a couple of weeks ago based on all of the above speculation. I hope I am wrong:

David S. said:
Can anybody confirm FCP6 will edit MXF natively?

"With native support for virtually any format, Final Cut Pro lets you edit everything from uncompressed SD to HDV, DVCPRO HD, and uncompressed HD — as well as Panasonic P2 and Sony XDCAM HD tapeless formats."
Click to expand...



In a word, No. From Apples FCP 6.0 page: http://www.apple.com/finalcutstudio/finalcutpro/support.html

-----------------------
Tapeless formats
It’s easy to work with the latest high-speed, tapeless devices from Panasonic and Sony. Use the Log and Transfer function in Final Cut Pro for ingesting Panasonic P2 files or Sony’s free XDCAM Transfer software for ingesting 18-, 25-, and 35-Mbps XDCAM HD footage. Preview shots before you bring them in, add In and Out points, and incorporate metadata before you transfer files to save time when you get to the edit. Ingest tapeless files in the background at high speeds while you continue to edit or preview other material.
-------

But on the same page under Camera-native editing:

Final Cut Pro 6 lets you edit virtually anything natively. That means you’ll get pristine quality from the first cut to the final output. Final Cut Pro doesn't’t need to transcode video from camera-native formats — no matter whether it’s coming from a DV, HDV, or DVCPRO HD camera. Your output will always be as stunning as your original source. Final Cut Pro 6 supports a wide range of standard- and high-definition formats.

Standard Definition High Definition
DV, DVCPRO, DVCAM HDV
DVCPRO 50, IMX DVCPRO HD, XDCAM HD
Uncompressed 8- and 10-bit SD Uncompressed 8- and 10-bit HD


So it is basically still unwrapping the MXF file and leaving it in untouched DVCPRO HD. So as I see it, you still have to waste time unwrapping it, even though I don't think a pixel is changed of what was originally in the capture, which really sucks. Plus you have to make the executive decision to either keep or dump the MXF file after confirming your import.

Arghhhh. This one last thing really peeves me since FCP would be perfect if you did not have to do this.

--

Rob
 
Well I just called Apple tech support and was informed that it does indeed take the MXF files and uses them. Here is a copy of the feedback I left on the Apple site.

>After Calling Tech support and speaking with Joe, I was informed that the native P2 support, that is mentioned in the "supported format I/O" section of the tech specs for FCP6, does indeed mean that FCP 6 does not have to place a quicktime wrapper around the MXF files that are created on the panasonic P2 cards. Joe informed me that the MXF files can be imported into FCP6 as they are, thereby not requiring the extra disk space and time that has normally been required in previous versions of FCP due to the fact that new QT files were being created from the MXF files. I think the wording of this on the tech specs page should be updated to reflect this very important feature for P2 users, as it is a little unclear the way it is currently worded.<

So let's hope that Joe is correct and FCP6 will edit with native MXF files from the P2 cards.
 
If true, I will be playing the Pointer Sisters "I'm So Excited" followed by Van Halen's "Dancing in the Street".

Until we know, a simple marching cadance.

--
Rob
 
I thought the p2 import bug was a fcp 5.1 problem, before the 5.1.2 and higher updates fixed compatability issues. Man i really hope this is true and not us getting excited over nothing. im tired of having mxf files i dont use on my hardrives.
 
Maybe Apple doesn't even know if this is gonna work or not. I mean they are listing it as a new feature, but it's not like Apple to not come right out and brag about their new features...they should know that native MXF support is a BIG enough feature to brag about.

I'm still 50/50...
 
Perhaps they aren't pushing it too far because it only supports the 720/720N & 1080/50/60 formats..which means no 1080/24p/pA native workflow? I suppose so. Let us not forget about the problems we've dealt with before 5.1.2 was released.

Only one way to find out, I suppose. Let me know how it works out for you guys!
 
I hope it is implemented. I think one of the reasons Apple might not have bragged about it, is that other software already had it and they were slow in incorporating it into FCP. So it was a bit of sweeping the dirt under the rug by being quiet. Overall the new version of FCP is awesome!
 
Last edited:
Ernest_Acosta said:
So it was a bit of sweeping the dirt under the rug by being quiet. Overall the new version of FCP is awesome!
Click to expand...

Perhaps, but it won't be a secret in a couple of weeks when the software is released and we all know.

I still don't see the huge benefit about editing natively, but some do.
 
You must log in or register to reply here.
Back
Top