New Final Cut Pro Announcement at SuperMeet?

Isaac_Brody said:
One thing I can't find any concrete info on, is it possible to skip the prores ingest and edit AVCHD natively? It'd be nice for FCP to do what the other NLE's do to save the hardrive space.
Click to expand...

I don't know what was unclear here. They said very clearly that there was no transcoding involved during editing (though how it would handle transcoding for final output was an open question).

From following the discussions and pre-show speculations, it was clear that jettisoning QuickTime was the only way a lot of what we saw could happen. That seems like exactly what's happened. Thus, a lot of things like importing into ProRes are no longer necessary. (And now FCP can do what an iPhone 4 can do. Huzzah.)
 
AdrianF said:
It wasn't very clear, but I got that it will be a kind of hybrid approach to native editing, with the background processing while you work. There was no mention of an update to quicktime, which would hopefully address working with AVCHD on the Mac in general. And fix the bloody gamma issue.
Click to expand...

Heh, gamma - I just upgraded to Snow Leopard and immediately noticed everything was darker....
So Apple proudly proclaims that Snow Leopard operates in 2.2 gamma space now....
Huh??? I had my system tweaked to perfection and was able to deliver content
that looked great to all platforms.
I spent the better half of the day re-calibrating my monitor.
I am still running tests to see what else Apple has screwed up.
 
I'm going to be the old grouch and say I don't really need this update. FCP has been a good program for me for years and does what I think an editing program should do, allow me to put shots together in a stable, responsive environment. Piling on features I will probably never use doesn't appeal to me much. For the do it all yourself crowd I'm sure there's much to be excited about, but ironically, when you start working at a more professional level, you do less and less of that stuff. Someone else fixes the audio, the color timing, encodes the footage, etc. All the editor does is edit, and FCP has been doing that fine for quite some time. I'll probably buy this out of curiosity and end up using it, but I don't need it.
 
HVXguy said:
I heard Panasonic will provide some software to take care of that problem.
But what is funny is that Premiere CS5 will edit RIGHT NOW without Transcoding AVCHD.
I upgraded to CS5 for that fact alone.
I have been shooting a lot with the GH2 and the transcoding time & space was killing me.
With the HVX200 I was using Raylight and have not transcoded in YEARS.
So transcoding AVCHD to ProRes in FCP is a step backwards.
Click to expand...

Without that native approach I will probably stay with Premiere at home. At work we cut with final cut, and we shoot a ton of AF100 footage every week. The ingesting is just eating tons and tons of gigs of space. I feel like native editing is such a big deal and since it wasn't really clarified directly or clearly I am doubting that they are putting that feature in.

And yes, the quicktime gamma issue is still a big question mark...
 
AdrianF said:
There was no mention of an update to quicktime, which would hopefully address working with AVCHD on the Mac in general. And fix the bloody gamma issue.
Click to expand...

It's native Cocoa and OpenCL. From all indications, QuickTime has been eliminated from the entire rendering and processing stream. By definition, that should eliminate stuff like the @&!%*(&$%!! gamma processing bug.
 
I think this update will allow me to focus more on being creative and less on organising stuff and trying not to destroy my edit further down the timeline.
 
DimitriL said:
I don't know what was unclear here. They said very clearly that there was no transcoding involved during editing (though how it would handle transcoding for final output was an open question).
Click to expand...

Can you point that out for me where that was said? As I understood it what was clarified was that you could edit footage on the timeline before it has finished ingesting. Ingesting to me means encoding to prores. I don't care about editing while ingesting, but I care a ton about saving space and not throwing everything to prores. Something which Premiere and Vegas allow.
 
Batutta said:
I'm going to be the old grouch and say I don't really need this update. FCP has been a good program for me for years and does what I think an editing program should do, allow me to put shots together in a stable, responsive environment.
Click to expand...

Stable? FCP's ten year old codebase has been patched together so many times that it's, like, oh, what's the opposite of stable? I'm kind of tired of trashing my app preferences file once a week.

This upgrade is worth it just for actual stability and delightful things like getting to use all my RAM. I like FCP7, it's my workhorse, but great honk, I want to take advantage of my modern computer's power just a LITTLE bit. :)
 
Sounds great to me.

It's VERY hard to believe Apple would be foolish enough to release something that was destined to alienate many of their pro audience as some seem concerned with. (Bound to be a couple though)
There will always be some things people might prefer the old or other ways, and probably at times with very good reason, but there are certainly many improvements listed here regardless of begged borrowed or stolen as far as I can tell... So I'm very excited. Though as others I'm also am keen to learn of the fate of studio/motion etc...?

I have to say after reading those articles, (Thanks for posting those postmaster!) that I couldn't care less how many of the "new" features are entirely original or purported levels of hyperbole.
When a business tries to sell me a new product and put's their best spin on it I'm not even remotely surprised or morally offended. I don't really even pay attention in truth. It's not what concerns me...
But maybe I'm just not discerning enough...? For nor do I care about the dreaded - "Hey!!! That looks like... Imovie!"
Frankly I couldn't care less if I edited in Thomas the Tank Engine themed software that required me to wear a funny hat and shout "Chooooooo!!! Chooooooo!! on the hour, every hour...
if it was going to make me at all more efficient or effective in post.

What I care about are performance and ease of functionality. Which is how I feel about every aspect of film making. It's all hard enough for me as it is.

The simpler, more efficient and more effective my tools are, the more time I get to spend thinking about the truly difficult creative work of making my piece as compelling as possible.

So dear Apple, as far as I'm concerned, please copy other tribes and continue to beat your programs with your drag and drop clubs till pro forums everywhere run red with their little Imovie-esque pixelated blood...
as the more efficient/effective you can help me to be in creating my vision...
the happier little film maker I'll be.

Cheers
LW

EDIT: Washington Irving, (you posted while I was still typing)
That's exactly how I feel!
In less words ;)
 
Last edited:
Isaac_Brody said:
Can you point that out for me where that was said? As I understood it what was clarified was that you could edit footage on the timeline before it has finished ingesting. Ingesting to me means encoding to prores. I don't care about editing while ingesting, but I care a ton about saving space and not throwing everything to prores. Something which Premiere and Vegas allow.
Click to expand...

and Edius.. you left off the first one to do it right.
 
Hey, I just realized something. One of the nice things about the Mac App Store is being able to download an application freely for whatever computers have that account set up.

With FCPX set up for the App Store, does this mean you can DL it for multiple computers, and then distribute QMaster (or whatever the successor to QMaster would be) FCP processing over multiple computers without needing an ADDITIONAL FCP license like you do now? Interesting question.
 
Based on the audio feed I listened to yesterday, and dozens of tweets, the indication was that h.264 native editing was supported.

However, until an official statement is forthcoming, no one can be certain.
 
You must log in or register to reply here.
Back
Top