After half a year of almost total radio silence, Apple came out swinging this week with a two hour keynote that had a lot to prove. The bullet point recaps are everywhere online, so instead let’s look at a few major themes from the presentation.
Mobile and desktop technology have evolved in the mainstream to the point where the term “fashion” can be used with a straight face. Apple’s message this week was that the current version of iOS looks dated, inconsistent and, well, out of fashion. What’s interesting here is that Apple also seem to acknowledge that they may not always be the trendsetter in this regard. There’s a lot of the Google+ aesthetic throughout the new mobile OS, and certain navigation elements have a Windows Phone feel to it. Functionally iOS 7 borrows some tricks from all the competitors (not to mention iPhone jailbreak hacks and WebOS) and tries to refine and redefine them into a cohesive experience. It will be interesting to see how this new iOS evolves by the time it ships.
On the hardware side, Apple released the long awaited Mac Pro. Say what you will about its lack of expandability or the trash can/R2-D2/Pringles can look- this machine is unlike anything anyone else has ever released. It represents everything Apple stands for- it’s bolder in design than the 2000 Cube as it breaks with the past more than the original 1998 iMac. This is a machine that virtually anyone would recognize from 20 yards away.
Seriously, how did Apple manage to keep the lid on the Mac Pro considering how long it’s been in development? Last year Tim Cook claimed that Apple was going to “double down” on secrecy, and it looks like he was successful in that regard. Across the board Apple was able to keep a lid on things like no keynote since the original iPhone.
Apple after Jobs
Not to dwell too much on the Mac Pro, but it struck me that this could very well be the first major piece of new hardware to emerge in an Apple after Jobs. It’s possible that the iPad mini beat it to the punch, but this is more than just a shrunken-down version of an existing product. If anyone was wondering whether Apple still had the ability to push the norms than this box puts that to rest.
In many ways I feel like this was truly the first post-Jobs keynote, even though technically it was not. There was a confidence in the presenters that seemed to stem from new ideas and new creations, ones that originated after the company’s founder was gone.
Speaking of confidence, Tim Cook has come into his own as Apple’s leading persona to the world. I think back to the iPhone event in the fall of 2011, just before Jobs died. I thought his performance was admirable under the circumstances, but it took him a while to really own it the way he did this past Monday- he was comfortable in the role and you could tell he was ready to swing back at the “Apple has lost its mojo” press stories swirling around his company.
Cook has also forged a new path that his predecessor might have disagreed with. The firing of Scott Forstall and promoting Jony Ive to head up both software and hardware design is a clear break from the past. Forstall was a brilliant but caustic personality that Jobs admired, and he was a strong proponent of the skeuomorphic touches of green felt and leather stitching that have been scrubbed from the new versions of OS X and iOS 7.
Apple has kicked off the second half of 2013 with what looks like an accelerated schedule of new releases and updates across most of their major projects, both hardware and software. But perhaps more importantly we are starting to see signs of Apple transitioning into a post Steve Jobs existence.
Rob Crossley at the CVG blog dissects the Xbox One launch:
I’m still shocked that, during early Xbox One design meetings – a time when obvious, sprawling and significant changes were occurring across the western household – Microsoft executives decided to bet the house on the future of live TV and cable.
More to the point, it’s frankly staggering that Microsoft observed the modern ways people view cable TV and believed, somehow, that it could add to the experience by getting in the way of it.
The existing consumer demand to interrupt TV with Skype calls, and a hand-gesture controlled Internet Explorer, can only be described as fictional.
I don’t doubt that Microsoft is going to sell a lot of Xbox Ones based on the brand name alone- it’s arguably their most successful product line of the last handful of years. But forward thinking it’s not.
Ebert’s review of Vince Gallo’s “The Brown Bunny”:
I had a colonoscopy once, and they let me watch it on TV. It was more entertaining than The Brown Bunny.
When the movie’s director responded by mocking Ebert’s weight, Ebert said, “It is true that I am fat, but one day I will be thin, and he will still be the director of The Brown Bunny.”
Courtesy of Stacy Conradt at Mental Floss. She has some other choice Ebert quotes worth checking out.
According to Brian S. Hall at readwrite:
The real reason why Windows Phone has failed because there is no good reason for it to exist.
Go on, try to think of one. Think of just one reason – one customer-facing reason – why Windows Phone should exist? Is it better? Cheaper? Faster? Simpler? More secure? More connected?
I was offered an impromptu demo of a Windows Phone by a guy sitting next to me on the subway yesterday as he swiped his way through the different built-in apps, and while it offered plenty of text-based eye candy it didn’t seem to add a lot of “new” value to what we already have from iOS and Android. If anything, navigation didn’t seem obvious: he tapped on blank parts of the screen to go back, and swiped across lines of text to reveal a longer message.
It is certainly smooth and graceful looking, but I can’t say “yes” to any of Hall’s questions above.
My son put together a fundraiser to help Somalian kids called “Liam’s Laps,” and I documented the day with my iPhone 4S and Final Cut Pro X. He finished the event at 3pm and the “film” was done by 6. If I had cut this in FCP 7 I’d still be transcoding.
Samsung could never bring this to market if people were actually going to hold it up to their ear.
It had been long enough. Since the fall of 2011 I’d been opening up Final Cut Pro X in my spare time, clicking around the unfamiliar interface, and then jumping back to the tried-and-true earlier version that’s served me well since 2001. I downloaded the FCP X manual, dug through the lynda.com tutorials, and read the hundreds of blog postings debating its merits, but until I actually threw myself into the fire I would never know if this was a tool that I could use.
The bulk of the editing that I do is for broadcast- promos, documentaries, and DVD extras that also see airtime on the network airing that particular show. I have the luxury of working with a team of highly skilled colleagues on a shared area network (SAN) that lets us collaborate on projects and share media without constantly copying files and shuttling drives around. Up until now we have leaned almost exclusively on Final Cut Studio, with a graphic assist from After Effects and Autodesk Smoke.
Toward the end of 2012 I learned that I was going to be working with one broadcast client almost exclusively for several months, generating a lot of content to support two shows that debut at the end of March and a major film airing in April. It was going to be a full promotional push: promos, behind-the-scenes features, and longer pieces that could be described as mini-documentaries. The producer I’d be working with is a long-time friend that I’ve known for more than 15 years, so I suspected he’d be OK with me taking things in a new direction. Additionally, these projects would not be handed off to another editor; I’d be able to essentially work on an island independent of the business-as-usual workflow happening around me, much as I did back in 2001 when I introduced a Final Cut Pro system into a sea of Avid Media Composers.
The first job involved creating some profile pieces for the film showing in April, which arrived at the office on HDCAM. Since FCP X’s support for traditional tape is practically nonexistent I jumped back to version 7 and loaded it in as ProRes 422, which imported seamlessly into X. I didn’t plan to return to FCP 7 until I had a finished piece to go back to an HDCAM master.
The interviews came to me on a Compact Flash card, shot with the C300 camera. This is where X starts to shine. Instead of spending hours transcoding these files to an edit friendly format, I was able to import them immediately into FCP X and start logging and editing. While the files were still copying to the Xsan. There’s nothing that kills creative momentum like watching a progress bar for hours before the work can begin. Sure, in some cases we could have an assistant editor transcode and import to FCP 7 the night before, but this time the interview was shot in our studio with two cameras and walked into the edit suite to start pulling selects that same afternoon.
I had read a lot about how great X’s multicam features were, so I thought this would be the perfect opportunity to test that out. Indeed, the software quickly and easily matched cameras A and B by lining up the audio waveforms in each angle and allowed me to view the results in a custom timeline called an Angle Editor. Here I could reorder the tracks, give each a custom name, and even apply an early color correction pass if I wanted.
Now that most of my material was loaded in, it was time to start the process of tagging clips in the Event Library in FCP X. I knew that only certain portions of the film were allowed to be used for promotion due to copyright restrictions, so step one was isolating those sections. Using Final Cut’s Favorite tag did the trick quite nicely. I shuttled through the film with the familiar JKL keys used by most NLE systems, marked the usable material, and tapped the F key. This displays in the clip thumbnail as a green line over that portion of the film. Once I was done I switched the Event Library display from “All Clips” to “Favorites,” and I had the selects I needed laid out, with the other parts of the film hidden from view. Not a bad first day.
Magnetic Timeline. When I heard those words in Apple’s PR release, and then in the early reviews, I could describe my reaction as being a combination of indignation and bewilderment. Why would this software be trying to “save me” from myself when I’d been working with complex edited sequences for so many years? I knew perfectly well how to keep my audio in sync, and I relished the challenge of digging into a heavily layered edit to make changes required by client review. Clearly Apple was going after the beginner and giving up on the veterans of the earlier versions of Final Cut, right? Wrong. They were going after everyone.
A few weeks back my 11 year old son and his friend had a school project and they decided they wanted to make a “documentary” as part of their presentation. They knew nothing of editing, and of course waited until the last week to really get in there and do the work. I set them up with FCP X, showed them a few basics, and stepped back to see what would happen. What happened was that they had a rough cut done that first night- an edited narration track, visuals, and even a few cuts of music sketched out by the time I took his friend home around 11pm.
My first day editing in X was arguably a more difficult experience than my son’s. My preconceived notions of how it “should” work were getting in my way, and I stumbled along. I couldn’t just grab a clip and move it down past the end of my sequence- it would “snap” back unless I specifically added a gap clip in between. The audio from my interviews was combined into the same clip into the timeline instead of being broken out into discreet tracks like FCP 7 and earlier. My list of grievances grew in my head throughout the day.
Then something happened. A few hours into day two, I realized that I wasn’t paying attention to the process any more; I was focused on storytelling. I was confident that if I cut in a b-roll shot that was too long it wouldn’t overwrite the clip I had already put in further down- that other clip would just move up and out of the way until I had time to focus on it. If I was zoomed in close on a particular edit point, I could trim a shot’s duration and know that tracks weren’t being pushed out of sync somewhere else. It was pretty liberating and I found myself actually having some fun with the story I was telling onscreen.
Final Cut Pro X’s editing tools are not perfect- there is still some room for improvement. Performing a replace edit, for instance, is lacking where it used to be much more powerful. I also miss the track select tool from FCP 7 where you could instantly highlight some or all clips before or after your position in the timeline. But overall there is a lot to like in the nuts-and-bolts aspect of editing in X, and I now feel like I’m at least as fast as I am in the “legacy” version of Final Cut I’ve been using for 12 years.
As most editors know, the tools we use these days have advanced to the point where any of them can feasibly “finish” a project. We find ourselves cutting with full-quality sources instead of highly compressed offline resolutions, so it only makes sense that we take on more of the color correction and effects work. The tools built into Final Cut Pro X have impressed me in this regard.
After a month or so of editing, we had a really nice series of short features that expanded on some themes discussed in the film, and we got to hear some interesting behind the scenes tales from the filmmakers about how their project came together. Now it was time to make it look great. The interviews were well shot, but the lighting was a little flat and the mostly white walls behind the subjects gave it kind of a sterile look. Using FCP X’s Color Board, I was able to create image masks and add some shadowing and vignette looks around the interviewees that really helped. Matching the color between the two camera angles also came together nicely, and the waveform and vectorscopes built into X allowed me to tweak away and keep everything within broadcast spec.
Graphically speaking, I incorporated titles generated within FCP X and some other elements from After Effects. The titler is a big improvement over the standard Boris Title3D plugin in legacy FCP. Just being able to manipulate the text on screen over the visuals is something just about every other NLE has done for years, and it’s a welcome improvement here. The text it creates looks clean and sharp on the broadcast display.
The elements I created in After Effects had to be rendered as QuickTime files with an alpha channel and then imported into FCP X; there’s no real integration between the two applications the way there is between AE and Premiere Pro. Photoshop files, however, do import into FCP X with all layers intact, and you can view the layered file in its own timeline and tweak accordingly.
I didn’t have a need to jump into Apple’s Motion this time around, but I did notice that one crucial feature from the earlier versions was missing this time around: the “Send to Motion” option in FCP that lets you select a section of the timeline and open it in Motion is absent. This is unfortunate and I hope that it returns in a future update.
It should be mentioned that FCP X has no built-in method for sending audio sequences to a sound designer using Pro Tools or something similar. I have been using the $149 application called X2Pro from Marquis Broadcast to do this and the experience has been pretty smooth. I did uncover one non-critical bug and contacted the vendor, and they were refreshingly responsive. A fix is in the works.
In the years leading up to the release of FCP X, Apple seemed to be unifying the look and feel of their desktop software, and the legacy version of Final Cut continued to be left behind in this regard. Now, the range selections in FCP look suspiciously like selected pictures in iPhoto, the iTunes library is accessible from within the editing software, and “Export” has turned into “Share” like its iCousins.
The Share menu is the one-stop destination for delivering my finished work on this project. To fulfill the client’s requirements of delivering on an HDCAM tape, I used the Share menu to create Master Files which I sent over to FCP 7 to output. What’s nice is that the Share menu is very customizable and you can easily build it to serve your specific needs. I built shortcuts to export still frames, audio AIFF files, H.264 QuickTime files for approval, and so on. The button sits right there on the edge of the timeline and I find myself using it a lot.
Overall my experience with Final Cut Pro X was positive and encouraging. The UI is appealing, the performance is solid, and the technical quality of the finished project speaks for itself. Apple wiped the slate clean with version 10.0, and by 10.0.6 it seems as if they’ve been very selective about what they’ve added or improved upon.
I remember that day in 2011 when Final Cut Pro X was released (and every previous version was erased from the Apple Store…but don’t get me started). It was software that I and most of my colleagues would not be able to use professionally, and I thought that it would probably be two years before any of that changed. It’s closing in on two years and FCP X feels ready. Not perfect, but ready. I’ve already started my next three projects.
Christoper Mims at Quartz:
The upstream supply chain for Microsoft’s flagship tablet, the Surface RT, had orders from Microsoft cut by half, reported Taipei Taiwan-based Digitimes. This, in a word, is bad.
Yes, yes it is.
This article by David Leitner at Filmmaker magazine is an excellent read for a film and video editor in 2012.
On the software side, why perpetuate dual source/record windows from 1970s tape editing, or interface metaphors adapted in the 1980s from film editing (Avid Media Composer), or 1990s timeline design (Final Cut Pro 7)? Why not exploit this 64-bit great leap forward in speed and processing to rethink, perhaps even reinvent, editing for the coming file-based century?
It’s been almost a year and a half since Apple bungled the launch of Final Cut Pro X. Since then the software has quietly improved over time, receiving 6 updates and chipping away at the list of missing “must have” features, and I think Apple will be vindicated for their decision to wipe the slate clean and start over. It was blasphemy in June 2011 to think that FCP X couldn’t capture from broadcast videotape, but today it’s almost a quaint novelty when I do just that. It’s a similar story for the lowly edit decision list. What do you mean I can’t generate an EDL in X? As with most remaining holes in Final Cut Pro, there’s an app for that. Third parties have stepped in to meet practically any niche need that the pro editor might have.
So, what tool am I using to edit today? Final Cut Pro 7. But I’m not happy about it. As editors we are never really “done” with what we’re working on, which makes shifting to a new platform a great big challenge. I currently have several ongoing jobs that span months. The shift is coming, however, and I’m ready for it.