Apple finally, at long last, let FCS3 out of the bag
Well it damn well took them long enough! At long last Apple got their
act together and have FCS3/FCP7 ready to roll. It's no secret i have
been highly critical of Apple over the past few years for not making
FCS as good as it should or could be. Releases 5 and 6 were profoundly
disappointing simply because they brought nothing new to the editing
table that didn't already exist in competing
applications.
I wrote about about this some time ago
in a long post entitled '
FCP6,
Where did al the newness go?'
More
recently, speculating on what we might hope for in FCP7, I offered up a
list of hoped-for additions. How many of them were
fulfilled...?
- A real-time engine that can actually scale
decoding resolution.Result - Umm... seemingly
not. Whilst RT performance should be improved and ProRes performance is
very good, it doesn't appear that Apple have addressed this issue in
the way that most other NLE's have.
- Actual 4k 4096px
supportIt seems so. A major failing of the QT
engine overcome and FCP now reports to suppourt 4k 4096 res.
- Project files able to be fully exchanged with
Motion/Colour/DVDSPNope. Apple still havnt
engaged integration in a more comprehensive way. XML is the right idea,
Send-To commands such as that from FCP to STP are good but none of
these is as a well rounded system as that which Adobe have shown is
possible whereby projects files from After Effects, Premiere,
Soundbooth can all be freely moved around. Despite the rhetoric Applee
are still very much behind in regard to the fully integrated suite.
- GPU acceleration (used for much more than page-twirl
transitions)Nope. It seems the GPU remains an
untapped resource.
- Greatly improved audio tools in FCP (this is a VERY long
list that starts with the ability to playback a bloody MP3 files
without RENDERING!!!!)Nope. It seems Apple have
failed to see the forest on this one. I don't have FCP7 to test yet but
there seems no mention at all of improving the horrendously bad audio
tools in FCP. Of course they would contend that this is SoundTrack
Pro's job but by forcing the user to move to a different application
for any kind of sound work they force the user to work in a specific,
traditional manner. And I dont like begin told 'how' i should work by
the software. What if i want to mix and edit sound as I edit rather
than AFTER i edit? A new age of production demands that I as the user
choose my workflow rather than have the software dictate it. Premiere,
Vegas, Edius all have very comprehensive audio tools right on the NLE
timeline including surround sound, bus to bus routing and wet-dry
monitor/record. This more forward thinking approach that Apple seem not
interested in, simply makes for a much more open and non-dictatorial
tool that allows the user to work they want to.... And if FCP still
cant play an Mp3 files without rendering than the guys at Apple truly
have their head screwed on backwards!
- Metadata
managementUmmm, nope. It seems that Apple really
havnt put any work into advancing the idea of managing, creating,
annotation media assets with metadata. This is the frontier of new
thinking about digital production - on one hand its simply
good media management (an area FCP has been notoriously poor in
comparison to say, Avid) but on the other Metadata management evokes
all sorts of new worklow concepts and processes. Witness the way Adobe
have started to implement Metadata into tools like the auto-transcrbing
of audio files from Soundbooth or the direct to disk shooting metadata
annotation of On-Location. Apple appear to have left this unexplored.
They have the system in place in the form of their XML structure but to
date this is very under exploited.
-'Real' native format
suppourt rather than compulsory re-wrapping to
MOV.NOPE. Once again Apple claim the 'no
transcoding' 'native' workflow tag lines when in truth Apple is almost
completely restricted to QuickTime MOV files. Almost every non-MOV file
has to be re-wrapped to MOV in order to be used. This isnt transcoding,
there isnt quality loss but it is a manipulation that shouldn't be
necessary. it means files like R3D's and XDCAMEX have to be duplicated.
And worse that such files are often not usable or give poor
performance) when opened in non-Apple/FCS applications. Either this is
a deliberate protectionist policy by Apple to protect its own Quicktime
product from competition or else FCP's underlying engine is so flawed
that it simply cant cope effectively with non QT
wrappers.
That said, what we did get
outside of this wish list was a form of background rendering such as
Adobe CS4 have with Media Encoder working in the background while you
work. This is nothing new but it is good and I hope it works as well
and efficiently as it will need to.
The iChat
theatre system in FCS3 is the one glimmer of Apple the Innovator of
old. This is a very interesting idea that goes a step further than
Adobe's clip-notes system for review and collaboration by going into a
real-time landscape. It sounds very good and I look forward to kicking
it around.
Velocity controls for clip speed. This
is the classic Apple/FCP that I have previously complained about.
Premiere and Avid have had comprehensive speed controls, ramping and
enveloping of speed for, literally, YEARS. Thank you for catching up
FCP.
Improved marker system. The previous marker
tools in FCP were a cruel and pointless joke and so it appears Apple
have finally joined to 21st century with a (seemingly) much improved
set of marker tools. Sony's Vegas has nothing less than 5
different types of markers that are completely customizable, namable,
individual or paired regions and can trigger events and captions - will
FCP's be up to this standard? Probably not but any improvement is
good.
The interface of FCP it seems missed out
completely. Whilst cosmetic this is one area no one seems happy with.
The overly bright, bitsy, cluttered GUI filled with microscopically
small icons really needs a re-think.
ProRes got the
big bump that everyone was expecting. A 444 with Alpha mode was just
what everyone was looking for to make effects heavy and higher-end post
a bit more viable than just working with the clumsiness of Uncompressed
10bit. ProRes is a great codec and it just got better. But again
there's nothing new about this. Cineform have had a lossless
intermediate 10 and 12 bit 444 and 422 format available for a long time
and even go further with RAW capabilities and a real-time,
non-destructive, metadata colour correction system. So ProRes 4444 is
nothing new, nothing innovative, nothing we havnt seen before expect
for the fact that it comes as part of FCS3 and FCS3 is very cheap!
Apple as bargain basement bundle!
I wont go into
much detail on the other FCS applications in this post. Motion has been
boosted and thats good but it is still a very far cry from After
Effects. Some users will love it for its price point in the FCS bundle
and for some of the great and easy to execute tricks up its sleeve. But
its not even close yet to competing with After Effects.
Color is an enormously powerful colour correction
system but it seems Apple still havnt had the time to "Appleise" it, it
still doesn't look or feel like a true FCS app and is arguably still
more complex to use than it should or needs to be. Anyone who has used
Magic Bullet Looks knows how fluid and elegant a colour system can be
and if MBL only had secondary CC an Motion Tracking masks then Apple
Color would look very clumsy indeed.
SoundTrack
Pro, from the beginning, has been the great DAW that ISN'T. STP could
have been great but so far it has very much not been great. Modeled off
Sony's superb Acid Pro but lacking both the power and flexibility of
Acid, STP has been plagued with stability issues and a host of strange
quirks - not the least being that it can import but Not export an OMF.
The Apple press release speaks of a number of improvements to STP but
largely they seem simplistic (voice level match) or long over due
remedies to previous failings (channel re-ordering) I was, in many
ways, hoping that STP would be the shining light in FCS3 but it seems
disappointment is coming my way.
The FCS3 package
may be great value and cover almost all the bases of production, but
there's really no arguing that STP and Motion are anything but
second-rate to where the market is at. Acid Pro, Audition, ProTools,
Cubase, Reaper, Sonar are all superior DAW's. Some of these are
expensive (PT, Sonar) other are inexpensive (Reaper, Acid) but for
SoundTrack pro cheap can be a big price to pay for second
rate.
And as for DVD Studio Pro.... My god, has it
been left out of the upgrade cycle altogether? The great authoring
system that once was had fallen so far behind the curve that
it was getting a bit ridiculous. And now it seems Apple are just
ashamed of it.
Now, dont get me wrong. Im very happy
to have the improvements that are there, as will my students who are
daily frustrated with FCP. But for all its niceties this release is
much like FCP5 and FCP6, it keeps Apple in the game with a strong
toolset but it does not put them ahead of it. There is no real
innovation here, nothing that we havnt seen before. They may have 50%
of the market now but without going one-better than the competition
they are likely to see their market share substantially whittle away
over the next few years.
Heres the FCS3 press
releaseHeres the Apple Whats New
list
Posted at 09:11AM Jul 24, 2009
by Mike Jones in general |
I'm just wondering, is this a hands-on review, or hands-on with the press release review.
Apple is known of not informing about fixing the obvious problems (like the need too render mp3) so the list of features doesn't contain any bugfixes.
Anyway this update seems like patching a train wagon windows with a duct tape and telling people that is now capable of passenger space flights. I really hate premiere, but I think that I might have to consider switching to CS4.
Posted by 403 on July 24, 2009 at 07:17 PM EST #
Posted by Ken on July 24, 2009 at 07:43 PM EST #
It looks like the phenomenal success of their gadgets has convinced them that theie Pro Apps are a side business at best, and a distraction at worst. I would argue that their Pro Apps have a huge amount of influence in their being seen as a serious software company.
But as a huge Sony Vegas fan, it's good to see that with the release of Vegas 9 with 4k support and drag and srop support of RED r3d files, Sony has an opportunity to take their flagship NLE to the next level.
Thanks, Apple!
Posted by Mark Holmes on July 25, 2009 at 06:37 AM EST #
And having been to the recent FCPUG in London and seen a demonstration of a local company's workflow using CS4 I realise I need CS4 in my life for the benefits it can bring to my client-facing production workflow, let alone it's (unassailed) proven status as a post-production market leader.
Adobe, Cineform, Red Giant and others must be breathing a sigh of relief - Apple have left themselves wide open to being completely surpassed in the next product cycle, despite slick endorsements from Euro RSCG, Murch and Coppola.
Posted by Justin Benn on July 25, 2009 at 05:16 PM EST #
But then this.
I have two thoughts.
Either, they are releasing this version to "get current" - kill the bugs and tweaks that have been sitting on the help since the engineering team moved on a couple of years ago, before taking on a major re-engineering effort - a two year proposition.
If that's the case, they are gauging interest/revenue in this product to determine if this is worth the effort.
Or, possibly, we're in for another gift-from-the-gods .5 update, like 4.5 was. 4.5 was possibly the last major update to the application, and it was free. 4.5 added HD to the app, resolution independence, a host of things, a major overhaul of the engine, for a download.
Let's hope it's both.
---Alex Johnson
Posted by Alex Johnson on July 26, 2009 at 02:29 AM EST #
Set your real time audio playback higher. 16 or 32 should do the job. Drop me an email when it works.
Posted by Jeff Greenberg on July 26, 2009 at 06:19 AM EST #
Just to respond quickly to some of the questions/comments here. Yes this was an 'assessment' based on the Press Release. Ive been a media industry journalist and commentator for 10 years. ive reviewed every major post-production product on the market, have been a beta tester for many of the major developers and in the past 5 years have see most products as pre-release versions months before they go to market. NEVER have I been given even a heads-Up let alone a pre-release form Apple. more over I dont actually know anyone or any colleagues, who have. Apple's approach to journalists and commentators is pretty bloody woeful. It might be good for marketing hype and to generate blind buzz but what Apple dont seem to get is that it does nothing for User Confidence or a sense of corporate transparency. And this will hurt them, badly, in the end.
My personal list of FCP bugs that i desperately want fixed is very long but I wont know if any of these are addressed until i get hands on. But there is nothing in the details released so far that fills me with confidence.
Jeff Greenberg's suggestion of changing the RT audio settings for MP# playback is a new one for me. Thats a hidden gem but it boggles the mind why A) You HAVE to do this to play back an MP3. And B) Why it's a secret 'trick'???
Just to prove a point I have now in front of me an open copy of Vegas and I have on the timeline 3 tacks of video with 4 different formats (1x PALDV, 1xHDV 1080i and 1xCineform 720p and 1xR3D 2k) and 3 tracks of audio with 6 audio formats (1xWav32k, 1xWav48k, 1xMp3, 1xAc3 and 1xOGG and 1xPCA). I have them looped, playing back in real-time and am adjusting reverb and multi-band compressor effects on-the-fly.... Single CPU Quad Core system.
Now, lets talk again about where the current state of editing technology and performance is at and look for where the new FCS3 might fit in...??? Do you see what i see?
Such an example of course doesn't tell the whole story but it is certainly 'telling' of where the technology outside of Apple is at. And if Apple dont get their act together (or care enough to get their act together) then we all who use FCP have a problem....!
ken's comment about the poor developers working for Apple's Pro-Apps division is a salient one. Who would want to hang around at Apple working on Pro-Apps when they seem to be so poorly resourced and constantly forced to play catch-up rather than be in front of the game? if I were a Motion or STP programmer I'd be eyeing off jobs at Sony and Adobe and thinking I could get a better run at thinking-big and pushing technological possibilities than I may ever get at Apple.
I, more than most, bitch and moan about FCS' inadequacies but i dont for a second believe that the people working at Apple Pro-Apps dont know how to fix the problems or get Apple in front of the competition again. I think they know exactly how to make FCS do everything it should! I imagine they are all very smart dudes and dudettes. So why are FCP's audio tools shite, why does STP crash so often, why is Motion so second rate, why is DVD studio pro so neglected? The only conclusion anyone could come to is that the Apple powers-that-be (be they shareholders or CEO's or both) are holding them back, starving them of resources and curtailing their potential.
Now thats a tragedy...!
Posted by Mike jones on July 26, 2009 at 07:30 PM EST #
But the inability of FCP's timeline playhead to NOT AUTO-SCROLL after all of these years, is absolutely astounding to me.
Every other video and audio app that I own has the ability to let the timeline scroll while the playhead remains stationary. FCP does not. FCP's playhead scrolling constantly off of the screen is a royal PITA. -Richard
Posted by RICHARD on July 27, 2009 at 04:11 AM EST #