Mac OSX Lion Info - FCP update info puhleeze!

TheReverend

Well-known member
Apple's holding a Mac press conference today. Mac OSX Lion is indicated on invitations. Here's hoping that FCP gets some info announced or something. Will update this post after the conference.
 
lion not till summer, so I wouldn't expect a new FCP until then. I expect to need new hardware to support the new systems, so I can't see myself investing in anything until everything is in place. Seriously considering a jump to a cheap pc and premiere for the short term until apple gets back in the game.
 
what a -yawn- announcement, my trust in apple continues its ever increasing descent.

It all started a few years back when iTunes trying to do my thinking for me ...
 
will cs5 take advantage of the 64 bit processor and does it make cs5 twice as fast then fop?

CS5 is 64bit and operates as so on mac. Well unless you can choose a 32bit version - I have no idea if there is. I cant tell you how fast PPro cs5 is as Ive never used it as I cut on FCP. But AE CS5 is a great tool.
 
I'm just ready for the bs of FCP to go away. No tweaking during playback is a beeotch, the gamma render issue is a pain, lack of native source editing (ie re-encodes or re-packing in mov's). I love it, particularly now with the share menu, but so much improvement can be had, it's ridiculous.
 
Im finally going to buy my first Mac. I was waiting to hear about Lion, but sense its coming next summer, I'll just buy one now.
 
"Lack of native source editing." Whatever... that feature is not all it's cracked up to be. If you want it... get Premiere CS5. Yes, Avid claims it can now do this via AMA, but it is not without a bag load of problems. Slow machine performance being one of the things, and not being able to export an AAF or OMF for audio being another. Instability galore. Avid works best when it has ALL the footage in an Avid codec...then it is rock solid. FCP too. Convert everything to FCP codecs, all is good. Don't have time to wait for the encode for this? Don't have the patience? Then get CS5 if you need that ability. Personally, I want stability over native format access. Getting both means a LOT of work, so I'll take the better option...stability.

There are many NLE's on the market for a reason...each one is different in what it can do. Get the one that suits your needs....don't try to wait for another one to get features that you want...and be PISSED when they don't. They might not for a variety of reasons.
 
Agree with Shane to a certain point.

Should you edit .h264 natively? No.

AVCHD natively? Not a good idea.

But FCP can't even edit with P2 MXF media natively without buying a plugin. Pretty much every other NLE on the market can at least read directly off a P2 card or P2 card structure and begin editing without having to rewrap it first. And however fast that rewrap is, it's not as fast as editing native, and DVCProHD is a perfectly acceptable source to edit natively. That's where FCP needs to loosen its grip and rewrite its code - to back away from "all Quicktime all the time" and support at least the most editing friendly source formats out there.
 
Agree with Shane to a certain point.

Should you edit .h264 natively? No.

AVCHD natively? Not a good idea.

But FCP can't even edit with P2 MXF media natively without buying a plugin. Pretty much every other NLE on the market can at least read directly off a P2 card or P2 card structure and begin editing without having to rewrap it first. And however fast that rewrap is, it's not as fast as editing native, and DVCProHD is a perfectly acceptable source to edit natively. That's where FCP needs to loosen its grip and rewrite its code - to back away from "all Quicktime all the time" and support at least the most editing friendly source formats out there.

Not a good idea to edit h.264/AVCHD natively? Then why does my iPhone 4 do just that with no issue at all? The difference is the core API in iOS and how it deals with video compared to the aging code in OSX. Instead of editing based on frames, the avkit in iOS uses "time". That means it can handle GOP editing quite easily. It also means a whole different way to look at handling various codecs in a timeline. Perhaps even natively??? The big holdup for the next generation of FCP is in essence QuickTime's old 32bit API's, which even the current version of QT X still utilizes.

We won't see a new 64bit FCP until Quicktime X is completed. This ties to Apple's theme for OSX Lion. "Back to the Mac" means that the technology developed for iOS will be ported to OSX. Not just the eyecandy consumers see on the top level, it's also about the core technology. When that happens, You'll see the next generation of FCP using iOS avkit. Editing AVCHD, a popular codec on the consumer side, will be natively possible in iMovie through FCS. Apple would be foolish not to add this. Apple is not foolish. They don't get to be the leader in Audio/Video content distribution & consumption by completely abandoning the creative angle.

Editing HD h.264 video on an iPhone 4 is mighty impressive. And it should not be taken lightly. Just think of the horsepower in an iPhone A4 CPU verses our mighty Mac Pro Quad-to-hexa Core Xeon CPUs. If OSX starts using the iOS technology for video editing.... which it damn well can since iOS & OS X are of the same family... 4k video should be as easy as a hot knife through butter on OS X powered Mac Pro.

Considering the guy who heads off the iMovie lab is the same guy who heads off Final Cut Studio, I think iMovie 11 is a clue to what the next generation of FCS might look like. At least, in direction. I think some very good things are on the horizon. Real Time effects based on Open CL. Native codec support? And Am I the only one who loved the audio editing tools they showed off in iMovie 11?

Apple's infamous silence can be quite frustrating. But I read the tea leaves, and I get the sense they know exactly what they are doing. It just takes some patience on our part. I'm getting excited in anticipation for what they are cooking up behind the scenes.





CORRECTION : The core technology in iOS is called "AV Foundation". Not "avkit". AV Foundation essentially replaces "QTKit" on iOS. And all signs point to "yes" as AV Foundation eventually replacing "QTKit" on OS X as well. As a reference for this, you can check out the following podcast link with some awesome info. Keep in mind that this podcast was posted back on August 27th. Way before Apple's official announcement of "Back to the Mac" with OSX Lion just two days ago. Also, do check out the blog link posted in this link as well. This is some very very juicy inside info.

http://www.theterenceandphilipshow.com/2010/08/episode-6/
 
Last edited:
Been editing DVCProHD footage off p2 cards for more than five years now

To me, the log and transfer process allows me the opportunity to evaluate my clips before importing the ones I wish.

I evaluate as the transcodes occur. To me this isn't a big deal.

It certainly does cause FCP to be out of the game.

If you want native editing of mxf files, go with Premiere. But native editing is only part of the occasion, and frankly many of us don't really have any issues with a rewrap of mxf files.
 
I'm considering jumping off the Apple ship cuz of the chroma/gamma issues with QT. There is NO WAY that a pro NLE should have this issue. And no Blu Ray? Sheesh - DVDSP has been the same clunky software since 2003.

CS5 Master Collection offers a lot for a little money.
 
Been editing DVCProHD footage off p2 cards for more than five years now

To me, the log and transfer process allows me the opportunity to evaluate my clips before importing the ones I wish.

I evaluate as the transcodes occur. To me this isn't a big deal.

It certainly does cause FCP to be out of the game.

If you want native editing of mxf files, go with Premiere. But native editing is only part of the occasion, and frankly many of us don't really have any issues with a rewrap of mxf files.

+1

I'm still working with FCP 6 and I still have not mastered it yet, so this topic is really pointless at least to me. Secondly Blu Ray is still not even relevant. Very few clients are using this technology and Dvd is here to stay for a long time.....
 
I don't think FCP is out of the game... but when I heard that the BBC switched some 2000+ edit suites to Premiere Pro last month... I did a quick "wtf... Premiere?" take.

I've spent the last 2 weeks testing PproCS5 with my work footage (I'm a full-time editor for an animation studio)... and by golly - it's faster (way faster) and stable (on the mac... gasp!).

I don't know if my studio will switch over similar to the BBC ... but a few key people are eager to hear my thoughts. To be honest, as it stands right now I would choose Premiere over FCP. That's saying a lot coming from me -- I've been a sort of FCP evangelist for several years.
 
Last edited:
I don't think FCP is out of the game... but when I heard that the BBC switched some 2000+ edit suites to Premiere Pro last month... I did a quick "wtf... Premiere?" take.

I've spent the last 2 weeks testing PproCS5 with my work footage (I'm a full-time editor for an animation studio)... and by golly - it's faster (way faster) and stable (on the mac... gasp!).

I don't know if my studio will switch over similar to the BBC ... but a few key people are eager to hear my thoughts. To be honest, as it stands right now I would choose Premiere over FCP. That's saying a lot coming from me -- I've been a sort of FCP evangelist for several years.
The other key advantage for CS5 and Premiere is After Effects. I mean Motion in the Final Cut suite is good for some stuff, but seriously After Effects is SO much more robust. After Effects is a staple for so many, and you often get Premiere along side it... It ends up being a no brainer. Especially as Premiere can handle newer codecs natively (ie AVCHD and such).
 
Back
Top