Final Cut Pro X

I guess that as Apple has told the world about FCP 10 then (basic) questions can be asked....

1) Do you still need to (officially) transcode into Quicktime? or will it handle say DVCPro HD natively?
2) Is there upgrade pricing or does everyone pay $299 regardless
3) A video I saw had the presenter refer to FCP 10... if I'm using the latest which is 7 where did 8 & 9 go?
Cheers

HVXser

Message was edited by: hvxuser

17" i7 MacBookPro 8GB, Mac OS X (10.6.4), 7200 Hard Disk

Posted on Apr 13, 2011 3:28 AM

Reply
1,741 replies

Apr 13, 2011 8:09 PM in response to ubernaut

ubernaut wrote:
i dont think its actually editing natively in mts i think its just letting you edit during the ingest process.


About eight minutes from the end of his presentation, Ubillos says:

"you mix and match content without having to do any transcoding . . . *you can take in footage from your DSLRs, you can take in AVCHD, you can take footage from the GoPro, and you can just edit it natively*."

Sounds like it's native editing

Apr 13, 2011 8:20 PM in response to David S.

David S. wrote:
ubernaut wrote:
i dont think its actually editing natively in mts i think its just letting you edit during the ingest process.


About eight minutes from the end of his presentation, Ubillos says:

"you mix and match content without having to do any transcoding . . . *you can take in footage from your DSLRs, you can take in AVCHD, you can take footage from the GoPro, and you can just edit it natively*."

Sounds like it's native editing


maybe but in the earlier part of the presentation the other guy talks about how scene detection/analysis happens while you are importing and that you can "edit while importing" i think randy was referring to the whole resolution independent playback stuff when he made the comment you referenced. that is certainly that is open to interpretation, as is the claim of no render bar. i sort of think if you went fast enough at some stage you would be waiting for render even if the interface didn't make it obvious.

Apr 13, 2011 8:27 PM in response to Mindbend

Mindbend wrote:


Please tell me I can finally have my video in FCP look like my video in Quicktime and everywhere else on my Mac. Hopefully colorsync will fix all that.

you can already do that btw just go into your QT 7 prefs and enable FCS color compatibility. not sure if this option is natively selected or not in QT X player, but there arent any prefs there so hard to say without testing (i'd do it but i never use QT X player:P).

Apr 13, 2011 8:34 PM in response to Mindbend

Mindbend wrote:
That's actually never quite worked for me. I need to revisit it to be sure, but I can never get it all to perfectly match even with the QT 7 pref trick. Thanks for the reminder though!


NP it does seem that with the new color-synced color management it will be more seamless. I cant wait for FCX personally although i think everyone would agree the biggest question are regarding the ancillary apps.

Apr 13, 2011 8:38 PM in response to Studio X

Studio X wrote:
If the material is not native, I convert it before bringing it into FCP. Funny, If find using Compressor, MPEG Streamclip or other apps seems to be able to engage all cores.

"The fault, dear Brutus, is not in our stars, But in ourselves ..."

x


Even when the material is native, it can still take a long time to export!

I'm well aware that Compressor uses all cores, which is puzzling why Final Cut Pro doesn't. Especially when they are from the same Suite.

Apparently you never created a feature-length film, you're probably one of those 5-minute YouTubers if you never had a time when it took a while to export your finished video.

Apr 13, 2011 8:43 PM in response to _Eric_

Eric wrote:

I'm well aware that Compressor uses all cores, which is puzzling why Final Cut Pro doesn't. Especially when they are from the same Suite.


puzzling maybe but compressor doesnt actually do any transcoding itself. it is a job submitting app for qmaster which has absolutely nothing to do with FCP rendering/exporting.

Apparently you never created a feature-length film, you're probably one of those 5-minute YouTubers if you never had a time when it took a while to export your finished video.


you know this thread had to turn ugly at some point. try not to be such a doosh would you?

Apr 13, 2011 9:19 PM in response to Alex Zustra

Alex Zustra wrote:
Umm, did I miss something? Everything I have seen leads me to believe that there is no viewer, no source monitor, no three point editing.

Why? Where is the uproar? This is more than a UI change. This is a fundamental part of editing, gone.

***!?!?!?! WHY WOULD YOU DO THAT?!? User uploaded file


Not sure this is true. I believe I've read that you can have Source/Record...

Patrick

User uploaded file

Apr 13, 2011 9:32 PM in response to Alex Zustra

Alex Zustra wrote:
Umm, did I miss something? Everything I have seen leads me to believe that there is no viewer,


yeah that window seems to have been replaced by the filmstrip style thing in the "organization" third of the interface. i imagine preview now happens in what used to be the canvas area. two ways to look at that no doubt, myself i'd say glass half full till i get to play with it maybe it's just more efficient UI, i mean who's really ever looking at both the viewer and the canvas simultaneously anyway?

no source monitor, no three point editing.

Why? Where is the uproar? This is more than a UI change. This is a fundamental part of editing, gone.

***!?!?!?! WHY WOULD YOU DO THAT?!? User uploaded file


i believe they stated in the presentation that they believe this new implementation of the imovie style precision editor is better then the esoteric conventions we are all used to. i wish the camera angle was better so i could agree :P

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Final Cut Pro X

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.