Apple and the App Store – Duck!!

16 12 2010

Bottom of New Delhi statueThe more observant readers of the blog will notice that I’ve been absent for a while from posting on the blog. I’ve been travelling during much of that time — in particular a great month-long trip to India. While there I learned a tremendous amount about the Indian economy and its media industry (while also eating a wonderful amount of wonderful food, but that’s another story) and I will be writing about it relatively soon.

But I also had a chance to mull over the Apple announcement from late October. You may remember that announcement for its announcement of the Air, and the hints about the new Mac OS – Lion. They also announced an App Store for Mac applications — to great whoops of joy among Mac pundits. I’ve given it a lot of thought and I’m not thrilled — I’m more scared than anything. And I’m scared for the media creation community.

First, if you aren’t already familiar with the store, head on over to its holding page on the Apple site, where you’ll get a very short sales pitch for why the store is so great. The site itself is due January 6, 2011 and Apple CEO Steve Jobs was quoted in a MacNN story telling us why the store is so great.

“The App Store revolutionized mobile apps,” reads a prepared statement from CEO Steve Jobs. “We hope to do the same for PC apps with the Mac App Store by making finding and buying PC apps easy and fun. We can’t wait to get started on January 6.”

But the devil is always in the details or, in this case, in the reality, and I think we should all be worried.

First off, I’m going to remind everyone that one of the major complaints about the iPhone/iPod (iOS)  App Store as been its approval process. Some developers have withdrawn their apps from the store because of the capricious nature of that process. And while it is true that Apple won’t (for now) require that all apps for the Mac be downloaded through their store, it will most probably become the de facto standard for 90% of all users.

Apple will be taking 30% of all revenues, which is way better for developers than what a brick and mortar retail store would take, but totally blows compared to the percentage that an online store would take. Apple will provide the entire store infrastructure — including billing and download, which is way better for smaller developers than building their own store, but no big deal compared to a scheme like Kagi or PayPal. Apple won’t do anything for marketing except (if the iOS store is any indication) some staff recommendations. That is no different than what software developers deal with today, and is way better if you’re one of the apps selected as a Staff Pick. But it totally blows if you’ve got a good competing product to that Staff Pick. Not much different than competing for reviews right now, except that these reviews/picks will appear on a retail store.

Paramount Consent Decree anyone?

So, in many cases, you gets some and you lose some.

The biggest argument for this store that I’ve heard made is that it will exactly serve the needs of 90-95% of the average Mom and Pop Mac purchasers, who don’t want to type “Family Tree” into their Google or Amazon search bars, and wait for the delivery of the disk by their friendly UPS guy. Now they can type it into the MacOS App Store search bar and get the download immediately. And that’s completely true. For 90% of the total market, this store will probably serve all of their needs.

But nearly every media maker that I know doesn’t fit in that 90-95%. We live in the outlying 5-10%.

As an example, we know that Apple makes Final Cut Suite. We also know that there at least two competing NLEs — Avid’s Media Composer and Adobe’s Premier Pro — that compete directly with Apple’s software. There’s also the new Lightworks Open Source beta (not available for the Mac right now, but “someday”) and a few other NLEs. I’d be fascinated to see if Apple approves any one of those competitors for inclusion in the store. And, if so, how often they would get Staff Pick recommendations.

The fact that Adobe and Avid could and would continue to sell their products on their own sites and elsewhere is great and all, but that has increasingly less power, the stronger the MacOS App Store’s pull on the overall market becomes. I can see the day when it will be well nigh impossible to start a new product without its inclusion in the Apple App Store and, once again, we (as users) become captive to the Apple selection process.

============= ADDED 12-16-2010 ===================

Philip Hodgetts points out in his comment below that Apple’s rules for the store prohibit software that uses installers to be sold in the OS Store. This rules out Final Cut, Media Composer and a slew of other complex applications.

=================================================

Apple, on its own site, touts the ability to download updates.

Developers are always improving their apps. That’s why the Mac App Store keeps track of your apps and tells you when updates are available. Update one app at a time or all of them at once, and you’ll always have the latest versions.

All well and good and I’d be thrilled at this feature were it not for two huge points. First, nearly every application that I own (with the shocking exception of Avid’s Media Composer) will, if I ask it to, automatically check for updates and let me update automatically. And, second, I’ve heard enough stories about iOS app updates being delayed for weeks as they go through the Apple approval process. Personally, I’d rather update on the developers’ and my own schedules, not on a store’s — even if that store is operated by may favorite computer manufacturer.

Finally, for everyone who has ever been thankful for a 30 day trial period, let me tell you that on the new MacOS Store — you won’t have one. Apple is not allowing downloading of apps with trial periods. You download it, you pay for it. Simple policy for them, not so much for us. I often download plug-ins or conversion tools for trials so I can decide whether to buy them or not. I love experimenting with them, but not too many of my clients want to see “SAMPLE” or “TRIAL VERSION” splashed across their screens. So, if I use them, I pay for them. If I don’t find them useful, I delete them. No harm, no foul, no fowl. On the new app store — we get harm and foul. I cry “chicken!”

Those of us who live in the crazy 5-10% outlier group will have to continue to do what we’ve always been doing — use friends, Twitter, user groups, blog posts and reviews — to find software that helps me to do my job better. Luckily, that won’t go away — except in the case of marginal software companies who can’t afford to part with 30% of their revenue, as well as keep a functioning web site up for support and marketing. This strikes me as a no-win situation for small developers and I’d be interested to hear what someone like Philip Hodgetts thinks. Philip, along with his partner Greg Clarke, publishes some great tools for Final Cut Pro over at their company Intelligent Assistance, has his own online store to sell their many apps. I’d also be interested in what some slightly larger companies think — not larger to the degree of  Adobe, who can pretty well afford their own store, but places like GenArts or Boris, both of whom make great plug-ins.

Small companies, like Apple used to be, need more open markets. I question whether this new Apple OS Store, will create anything resembling an open marketplace. If not, small companies are going to start hurting even more than they do now. And while Mom and Pop won’t notice, those of us who work creating content at increasingly lower and lower margins are going to start suffering.

Share


Keeping Organized – A Free Webinar

8 09 2010

One of the things that many low budget productions suffer from, as well as nearly all student films, is a lack of organization. It makes those tougher films even harder, but no one ever feels they have the time to set up their systems.

This is crazy shortsightedness and to give a few examples of what I mean by organization, I’m going to take some examples from my book, THE FILM EDITING ROOM HANDBOOK, 4th Edition, and present them (in my usual rambling fashion) during a webinar being given by the good folks over at New Media Webinars.

Every editor does things differently, and Shane Ross has done a pretty good DVD on the subject within Final Cut Pro. I’m going to toss my own thoughts into the ring  tomorrow, Thursday, September 9, 2010 at 10am Pacific time.

There are some good things about this webinar — the first is that it’s free, if you can make it at that time (NMW will be making the webinar available for a fee afterwards, along with some added content — a video where I’ll talk about organizing a VFX  workflow, as well as a copy of the glossary from my book). You’ll also get a chance to win some prizes, always a good thing.

Finally, I think that you’ll learn some things and, if you haven’t, you’ll have a chance to ask questions.

It should be a blast.  And you don’t even have to be in LA to see it.  So, c’mon down.  Just click on the link below.

Editing Bootcamp. Get Organized!!

Share


Working With New Muscle Memory

15 06 2010

The new release of Avid’s Media Composer 5.0 has a ton of little interface changes in it, some of which initially made me crazy as I continually had to remember what they were (Steve Cohen has a great tutorial up on his blip.tv page which is well worth a viewing).

This got me to thinking about how most filmmakers who I know have to develop a set of learned reactions in order to their job properly. As editors we learn the NLE tools when we’re first exposed to them (whether it’s Media Composer, FCP, Premier, After Effects or any software tool) and develop a muscle memory about how to best use those tools. Keyboard shortcuts are just the most obvious examples of these, but even something as simple as figuring the best way to create an overlap or L-cut, where picture and track are not edited at the same frame. (Naturally, Steve has a great tutorial on a trick for doing this at the end of a sequence). Over the course of time, we build up a repertoire of methods and techniques that help us to do our job more quickly and efficiently, allowing us to think more and do the mechanics less.

But, like annual releases of cars, every new release of a piece of software introduces new features and it’s way too easy to ignore them and simply continue doing our work in the Good Old Way. This means that the NLE that is released in 2010 is not the NLE that I learned on in, let’s say, 2007 (though, truth be told, I learned my NLEs waaaay earlier than that — don’t ask). But we’re probably still editing with it as if it’s 2007.

In one of the editors’ groups that I’m a member of, I’m continually amazed at how many of us didn’t know the feature that another one of us is using. The same goes for many of my students at USC — the way that they taught themselves FCP in high school is the way they’re using it today — even though it’s changed since FCP5.

The problem, in my mind, is muscle memory. Our brain and body have been trained to think and act in a certain way, and it is damned hard to get them to work in any other way. It’s not a trait peculiar to filmmakers, of course. People drive the same route to work every day, have the same eating habits as they did when the got out of college, and maintain many of the same traits — for better or for worse — as ten years ago. It’s why my mother still can’t text people and it’s why we all misspell or misuse the same words year in and year out.

But that muscle memory tends to get in the way all too often and one of the chief responsibilities of a good filmmaker today is to keep on disrupting that muscle memory. If we’ve figured out an efficient way of lighting for 35mm film, we may need to relearn the methods when we move to HD-DSLR. Every time I finish a job it feels like I have to relearn the tools all over again.

And that’s because we do.

A responsible filmmaker must spend way more time teaching him or herself new technologies, new interfaces, and new methods before, during and after every job. At this past weekend’s EditFestNY conference, the editors of AVATAR talked about how the production was literally inventing the technology as they went along. By its very necessity, they had to create new muscle memories all the time. Most of us are not so directly challenged in our daily work, and we rarely are given leave by our employers to experiment. Our jobs reward doing things in established ways. There’s very little room for learning new methods and the mistakes that generally come with that exploration.

But, to my mind, the way in which we thrive as filmmakers is to continually put those shortcuts and workflows aside periodically and asking ourselves what could be done differently. We need to go to user group meetings, read blogs and view videos, to force ourselves to see how others work.

It’s how we’re going to keep useful to new employers and excited by our work.

=============

Speaking of user groups, the geniuses at the Final Cut Pro User Group (notably Mike Horton and Dan Berube) are putting on the first ever Supermeet in Boston later this month — June 25th to be exact. There’s going to be some exciting presentations there, including some CS5 and Canon HD-DSLR workshops (remember what I said about muscle memory). and it’s only fifteen bucks!!

You should hustle on over to the supermeet.com website and learn more about the program and the details about it. Supermeets are always a bundle of fun and, if you live in the Northeast, you should wend your way to Boston on the 25th.

Share


The One NLE To Rule Them All

9 06 2010

No, no, no.  I  don’t think that there’s one editing platform that rules over everything.  And I never have felt that way. When I edited on film, there were debates as to whether a Moviola upright was superior to a flatbed (too noisy!!  too assistant intensive!!) and I used both.  And once people moved increasingly over to the flatbeds, there were debates as to whether the KEM or Steenbeck or Moviola was the best. And I used them all.

So, this argument about Final Cut and Avid tires me out.  I feel old.  I’ve been there and done that. And I use them both.

Avid's Media Composer 5.0But one thing that the imminent release of Avid Media Composer 5.0 (this Thursday, June 10th) brings to mind is just how much we want our editing machines to do exactly what we want them do. There is a tremendous amount to like in this great improvement to MC (as we cool and insufferable editors like to call it).  Personally, I love the new stereo tracks — which enable me to save great amounts of screen real estate and put keyframes and volume graphic moves on both channels of a stereo sound simultaneously. And I like how I can mix and match frame rates, raster sizes and a slew of other crazy stuff that I don’t really understand, right in my timeline without doing complicated conversions.  Oh, the conversions are still there, but now I don’t have to do them — MC does them  in the background for  me.

I’m lazy like that. And I don’t really understand it well enough to not be lazy.

But some of the coolest things in the new release are not really new, they’ve been in Final Cut for a while — editing directly in the timeline without switching back and  forth between Avid’s modes, for instance. Personally, I like the old trim mode in Media Composer, but if you’re used to dragging and dropping on the Final Cut timeline, this is going to seem very familiar to you.

Another thing that I really like in the new Media Composer is that I can edit directly in QuickTime, without conversion or transcoding to Avid Media files. Yeah, just like Final Cut does. I can also edit Red files directly, along with AVCHD and P2 and XDCamEX. But that QuickTime editing is great.

So, now (to a great degree) I can have some of what I like in Final Cut right inside Media Composer.

It gets even better.  Though I haven’t tested it yet (Boris!!  Are you listening??) Boris released a video today talking  about a new product that they’ve got coming out called Boris AAF Transfer. If this software lives up to its hype, it will make it very easy to edit a sequence in Final Cut and export the timeline to Media Composer and easily relink everything to the original media without complicated transcoding. In fact, with Avid’s QuickTime AMA (new in 5.0), you can simply link the transferred timeline back to the original FCP media and — voilá — you’ve got an Avid Media Composer project ready for editing, finishing, sound work or whatever you want to do.

For years, people have been doing a similar thing using Wes Plate’s awesome Automatic Duck, though it did take a few more contortions and is twice the price of Boris’s solution. Without testing Boris AAF Transfer it’s  impossible to know whether it can handle sequences of the complexity that Automatic Duck does. Wes’ plug-in has been so reliable for so long that it’s hard to imagine that Boris’ 1.0 version can come  close.

But Boris has been doing fantastic FX plug-ins for FCP and Avid (many of their effects come standard with the full version of Media Composer — sorry students) that it’s an exciting development. Often I go for their plug-ins over Apple’s or Avid’s.  So I am encouraged and hopeful.

And that leads me back to my original point. What I’ve observed over the years is not how different editing systems are, but how similar. When Avid was just starting, they looked over the shoulder of companies like Lightworks and saw that — holy splice mark Batman!! — you could actually edit in the timeline. And, lo and behold, trim mode was born. When Randy Ubillos, creator of the original Adobe Premiere, first created what would become Final Cut Pro, he was able to take a look at what both Premiere and Media Composer were doing wrong, think hard, and improve on them (Lightworks was, by then, a non-competitor). And now, with every release of each NLE, they’re looking at what their competitors are doing better than they are, and putting it into their own software.

No one knew they needed “select to the  right” until FCP introduced it. It is now in  MC (since 4.0 or thereabouts).

So, in my opinion, there is not “one NLE to rule them all.” The best NLE is  all of them together, especially when there are companies like Boris and Automatic Duck to build bridges between them. Especially when companies like Avid take a look at what Apple and Red and others are doing, and put it in their software. Especially when there are editors out there who keep on pushing those companies to create better and better NLEs.

[Don't even get me started on Get. Though not as cool as Avid's ScriptSync, it is so way cool that there were editors at a recent LAFCPUG meeting ready to throw down their hard-to-come-by-recession-dollars for a copy.]

What we want, when you really get down to it, are our favorite companies out there — Apple, Adobe, Avid, Sony, and a host of others — to keep running scared and looking at others who are doing  great innovation and trying to figure out how to do it themselves.

Then I can have one or two or three of them sitting on my Mac, and move effortlessly between them.  Then it won’t be the software that will rule, it will be the Mac sitting on my desk that will be the one true NLE to rule them all.

Share


Production and Post Wars (or Why Red Should Buy Final Cut)

29 04 2010

Well, all right, I’m exaggerating there. I don’t really think that Red should buy FCP, and Production and Post aren’t exactly at war (though sometime you’d be forgiven if you thought that) but I want to make a point here.

Every year it seems that camera manufacturers create many “improved” codecs that answer their needs — increased quality with reduced file size. However, that goal is pretty much immaterial to post-production professionals. We don’t care if an image takes up a large file size. In fact, with the faster processors and cheaper storage costs (last I checked, a medium-ish quality 2Tb drive costs less than $300 on Amazon), we don’t much care what size the original file is. If it’s too big to use, we’ll just create a lower rez transcode in ProRes or DNxHD and edit with that. In fact, it’s more important to editors that it be easy to edit.

This means that Long GOP file formats, where most frames are not stored as full frames but as a smaller list of changes from the preceding frame, are horrible. They are exceedingly hard to edit with. Whatever speed gains we might conceivably get from working in a smaller file size are more than undermined by the extra work our NLEs need to do in order to display them.

[Note of ignorance. I haven't yet had a chance to play with the parts of the new version (5.0) of Avid Media Composer which allegedly make a lie out of that last sentence. Pushing their Avid Media Access technology forward, and allowing the Media Composer to natively work in Quicktime, Red and various Long GOP formats, they promise to make editing much easier with these previously hated formats. This has proved to be true in my experience with the Sony EX-1 and EX-3 cameras, so this could be a great boon. And I'll talk about that in a few paragraphs, so stay tuned.]

Let’s face it. Editors are never going to get camera manufacturers to stop looking for their version of “better” codecs. We’ve long since learned to live with it. But it does mean that, unless these manufacturers work ahead of time with the NLE manufacturers (the way Red did with Apple, for instance, before the initial release of the Red One) it’s going to take some time for our favorite NLEs to catch up with each new release of a camera codec.

It’s a war and the winner of that war is… well… no one. But the biggest loser is the filmmaker.

This is less of a visible problem on the bigger budget productions where the camera and editorial departments are made up of different people, each of whom have varying levels of tech support that go beyond typing “Long GOP won’t work” into a Google search bar. But as more and more of us are shooting with small crews, and taking it back into the editing room where we have to ingest and edit it (and output it) ourselves, this becomes more than an annoyance, it becomes an impediment to our livelihoods (you know who I’m talking about, you WEVA folks out there).

So, what’s the best solution to this war? Is hope for reconciliation only slightly less feasible than the Democrats and Republicans agreeing on anything in Washington today?

Well, yes it is. But there are some signs of hope.

I’ve already mentioned Avid’s AMA. What that does is create a set of open architecture hooks for camera manufacturers, so that they can more easily create a way for editors to edit natively in the Media Composer. It’s an attempt to make it easier to do what Red did with Final Cut before the Red One’s release.

In both cases, it’s the NLE manufacturers telling the camera manufacturers — “Hey, if you’re going to create your own camera codecs, you’ll have to create your own editing codecs.” Well, not exactly, but Apple and Avid are placing the onus on the camera manufacturers to dig themselves out of their self-constructed hole. And that makes sense, so long as your NLE is one that has enough of an audience to make it worth the camera folks’ attention. I might be wrong, but I doubt that Sony, Panasonic, Red and the HD-DSLR manufacturers are going to spend buckets of money writing plug-ins for Liquid or Vegas.

So, what are our other alternatives?

In the old days, every single camera manufacturer had to create cameras that worked with the industry standard 35mm film gauge. If they wanted to create a film that was a different width — such as, say, 38mm — they had to be able to manufacture the film, the lab processing equipment, the editing equipment and the projectors to accommodate that.

Needless to say, we never saw 38mm film. [We did see 16mm and 70mm film -- which at half and double the normal size was easy for Kodak to manufacture film for. When it became clear how it opened up new markets, the camera, editing and distribution worlds came along for the ride (to greater or lesser degree).]

But what if a company could manufacture a camera and editing and distribution equipment (like Sony) and didn’t have their heads up their posteriors (like, uh.., like… oh never mind)? In a frighteningly anti-competitive way, they could then create a camera codec that worked fine in both capture and post production.

We haven’t yet seen that company, though if Red bought Final Cut from Apple (or MC from Avid, let’s say) it would certainly be a start in that direction. Please note, I have absolutely no inside information on anything that Red, Final Cut or Avid might be up to. For all I know, Apple is planning on buying Red, though that would shock me in ways that I can’t describe in public.

In the meantime, Red Cine X and AMA are two ways that post and production are attempting to bridge the gap. last time I looked, Avid wasn’t manufacturing cameras, which will make it more difficult to keep up with Red Cine X.

When Cisco bought Flip last year, I was hoping that we’d see some real synergy in the production and post areas. At the very least, I was hoping that we’d see some changes in the Flip that would enable them to interact with the web backbone much more easily. That hasn’t happened yet, and there’s no indication that it’s imminent.

But wouldn’t it be awesome if someone came up with a series of codecs that could take footage shot by a camera, make it easily editing ready and trivially distribution ready. By this, I mean more than projector-ready (something that I am hoping that Red Ray will pave a path for) but will make it easier to distribute files safely to theater owners, television networks, web distributors, mobile device partners, et al.

And, I’m hoping that these solutions are provided by multiple companies so we don’t have to be tied to one technology.

Whoever creates that chain will be the Dag Hammarskjöld of all things digital video, and their company will be its United Nations. Peace at last!

Share


Final Cut Pro – Baby Steps Into The Future

23 07 2009

For the two or three of you who don’t know yet, Apple released its updates to its suite of video applications today.  Final Cut Suite 3, has updates and new enhancements to nearly all of the parts of the suite, including some cool title manipulation tools in Motion, voice level matching in Soundtrack Pro (a boon to quick and easy temp mixing), cooler markers and more flavors of ProRes in Final Cut, and more. Some of the features, like a floating timecode window and global transitions, are attempts to catch up with Avid’s Media Composer which has had that for a very long time. (Apple’s list of new features can be found on this page on their website.)

That, by the way, is a great advantage of competition.

But it is in the aspects of ease-of-use and collaboration that Apple has shown that it is paying attention to what it’s core market really wants. Despite the high-end videos of Francis Coppola and Walter Murch on TETRO, Final Cut’s appeal has always been to people on the lower-priced end of the market — the students, the low-budge indies, the people putting together their own shops. The entire suite concept caters to them — if your market is made up of people who can’t afford to hire separate title designers and sound editors, then the idea of charging people separate amounts for separate applications is a non-starter. For the indie filmmakers and podcasters who are creating their own soundtracks and flushing them out to the web in record time, buying ProTools and Media Composer is just too expensive. Even if Soundtrack Pro is way inferior to ProTools, it just simply doesn’t matter to that market. Having everything in a box (with round-tripping between the apps) is The Way To Go.

I’ll talk about the coolest indicator in a minute, but let me also say that the ease of use factor is also huge for this market. If I’m doing my own lower thirds, and I’m not a visual effects guru like Mark Christiansen, then I want easy-to-use templates that provide me with a great default setting.  I’ll change the look and feel if I want, but the fact that I don’t need to program in a motion effect, with a glow, and time everything out from scratch, means that I can get things done much more efficiently (even at the expense of greater individuality).

So, starting with something much higher than Ground Zero, appeals to many of the filmmakers that Apple is targeting as their market.

But here’s the cooler thing for me.

As many of you know, I’ve been harping on the idea of long distance collaboration for several years. It’s clear that more and more of us are working with people who we don’t see every day. Two years ago, I co-edited a small horror film called JACK IN THE BOX. It’s director and my co-editor were both on the East Coast, while I sat in Los Angeles editing. We exchanged files and projects via the net. It was a successful collaboration, but a bit frustrating because of the lack of face-to-face contact. This month I’m starting a new film where the director will be in Rhode Island, my co-editor in Massachusetts and me — still in California.

My point is that this is becoming more of the norm, rather than a rare instance. Commercials, corporate films, sponsored videos, and more, are fast being done by the People Who You Want To Hire, even if they’re in another city. But the tools just aren’t there yet to help re-create the face-to-face experience. We’ll be experimenting with some newer techniques on this one and I’ll report back, but the struggle is always to help all of us to feel like we’re in the same room.

Now Apple has introduced iChat Theatre, which allows the editor to play back his or her timeline right over iChat. If I read the tutorials properly, you no longer need to create a Quicktime export and then upload/FTP it. In fact, you no longer even need to create a Quicktime at all. This feature of Final Cut allows others on the iChat to look directly into a Viewer (or Canvas) on the editor’s machine. That’s it.

Now, it doesn’t have the real interactivity that I’d love — to have my iChat buddy be able to use his or her mouse to stop and scroll the cursor around on the timeline  (like Syncvue, for instance, does), and I don’t know if you can have more than two people on the iChat, but you can video chat with each other while you’re scrolling around. Mike Curtis says that you can show the timecode window as well, and that will be great for more precise discussion. But you certainly can’t take a mouse or Wacom tablet pen, and circle items on the screen (which would be handy for discussion visual effects) like you can on some services. It would also be cool if you could attach comments/markers to particular places on the timeline — so you could easily accumulate notes. But, using a screen grab tool like Snapz Pro X, you could record a notes session for later playback.

Very cool. Since one of the biggest issues in distance collaboration (as well as in any notes meeting, now that I think about it) is misinterpretation of notes.

My point, however, is that Apple has once again identified a growing need in their core market. Many of us working in lower budget ranges need to work with people across great distances. They haven’t given us any real groundbreaking tools to do that, but it is clear that they are thinking about it, and slowly introducing early versions of the tools that we will all need very very soon. These tools are very basic, and don’t really do much more than take ideas that have been floating around elsewhere for a while, and bring them into the suite. But the real takeaway here, is that they’ve now brought these things into their own tool and made them easy to use and integrate with their other tools. And that is going to be very appealing to this market.

Another aspect to this distance collaboration is their Easy Export feature which, on first glance, looks like an easy way to upload to YouTube, MobileMe and more (including BluRay — cool; direct export to DVDs from the timeline).

Oh, and one final point. They’ve made both the price of the suite and the upgrade price incredibly low. The upgrade for someone who already has a purchased copy is $299. That means that they are essentially telling the community that they’ve be idiotic not to upgrade. No one who has the money to make a video project of any kind, doesn’t have $300. (The full price, for those people who don’t have access to an educational discount or their own copy already, is $999.). Once again, Apple is saying to the indie and low budget community — this is for you.

Now it’s time for Avid and Adobe to decide if this is a market that each of them want, and then go for it.

==============================

By the way, some other bloggers are beginning to post their own thoughts on this. Steve Cohen, over at Splice Here, is one of them. Richard Harrington, at the Pro Video Coalition, and Mike Curtis are two others who you should check out.

Share


Coolest Final Cut Pro trick!!

8 07 2008

Larry Jordan\'s tip about patching tracksOne of the reasons why I read Editwell and virtually anything that Larry Jordan is a part of (here is a link to Larry’s website) is that the man not only has the smoothest voice of any tutorial host/radio host, but that he is among the clearest (and most enthusiastic) FCP teachers around.

That puts him in some incredible company, by the way. I learned an amazing amount from a three day workshop that Diana Weynand taught a year or so back. And her books, along with Michael Wohl’s, are an invaluable addition to my library.

But Larry is amazing. Check out his tip from a recent posting on “Larry Jordan’s Tip of the Day” from his engaging web site. It gives a great way to repatch the track assignments from the Patch Panel at the left of the timeline (see the image at the right).

Share


Amazing Amazing Amazing

13 06 2008

If this is true then there is proof that there is a God.

Wes Plate, the innovative maven behind Automatic Duck, did a demo of the soon-to-released Pro Export FCP 4 (due, according to the video, sometime this summer). In the video, which you can see at the Film & Video web page where I found it, actually shows ProExport 4 changing FCP media into MXF files that the Avid can actually read. In addition, with the effects that are in the demo, the program translated the FCP effects into Avid effects, and translated an FCP marker into an Avid locator. This is in addition to the already valuable function that the program performs in version 3 of translating project files.

Once again, if this is true — there is a God. Or, at least, the Holy Grail. For years, that unattainable goal was to easily move a project and its media from FCP into Avid, because most people felt that the finishing tools there were better. Or, perhaps, you’re moving from one facility to another.

Wes Plate, you are a God!!

Share


Great Do-It-Yourself Podcast Tips

10 06 2008

There are two really great sites that I like to tour around to get tips and technique tricks for FCP and Avid.

First, David Forsyth, over at Amber Technology in Australia, does a podcast called “Avid Tips and Techniques” which has featured discussions about the Audio Mixer, Animatte, the Super Bin, and more.

One or two Final Cut sites. My favorite are the series of tutorials about the entire Final Cut Suite from VASST, a company that does training videos. If you look up their store using the company name RHed Pixel in iTunes you’ll be treated to a great series of excerpts from those videos. I like the one called “Total Training for Final Cut Help – Final Cut Studio.” A warning — VASST’s free tutorial website hasn’t been updated in a very long time.

Another good FCP podcast, though it hasn’t been updated since early March, is Creative Cow’s podcast “Creative Cow Final Cut Studio Tutorials Podcast.” Creative Cow runs those great web forums on practically every production and post technology known to mankind (and womankind too).

A cool series of short tips and tricks from the people at Digital Heaven, who make some really neat plug-ins for Final Cut (including a large timecode window, for all of you Avid editors who miss throwing that up during music or sound spotting sessions). Their podcast of video tutorials for FCP can be found on YouTube or at this address in iTunes.

Share


Avid Girds Its Loins

18 05 2008

WARNING: This post is chock-full of editing-geek mojo. If you’re not interested in editing and editing tools, then I’d suggest you surf over here instead (just kidding, just kidding).

Avid LogoI spent most of yesterday at a meeting up in the beastly hot city know as “Beautiful Downtown Burbank,” along with a group of editors, talking to some of the people from Avid about what’s coming up for them, especially as revolves around the release of their new Media Composer software, version 3.0 (due out in early June).

Now, many of you know that I like working on the Avid. I started out on Lightworks, way back in the stone age of NLEs, and subsequently was forced to work on Ediflex and Montage before I got to work on the Avid. It took me a little bit to get used to it, after the very film flatbed feel of the Lightworks. But I’ve been using it pretty consistently since then and have gotten very used to its look and feel.

But the company very nearly ran aground for several years, when it couldn’t figure out what it wanted to do and how it wanted to interact with its users. Now, admittedly, feature and television editors are probably the worst group of users you’d want to have as a manufacturer — we’re incredibly detail-oriented, we’re under so much time pressure and stress that we have very little patience for errors, but we also want an incredible amount out of our editing systems. If you were going to choose a market to create an NLE for, I’d go for wedding videographers way before us.

But we are very visible and we do help to drive the NLE companies forward in their product development.

So, when Avid started its “New Thinking” campaign, many of us approached it with some trepidation. Was this sloganeering or course correction? Was it a sincere effort at reclaiming lost loyalties, or a cynical attempt to woo people away from Final Cut?

After yesterday’s meeting, I have to say that I’m very encouraged. Many of us in the room, including fellow bloggers Steve Cohen, of the ever informative Splice Here, and Harry B. Miller III, of the ACE Technical Blog, felt pretty positive about some of the new features. One that I am particularly happy to see, is the Avid FX application, which will now be integrated into Media Composer. Previously available as a stand-along application as part of the PC-only Avid Suite, this is Avid’s response to the increasing practice of Avid editors to go out and use Motion for titles creation, only to have to import them back into Avid. (As an aside, Jay Cassidy — who is cutting the new Jim Sheridan film — told me that he does his titles in After Effects.).

Based on Boris, Avid FX can easily create and animate titles which, like Motion, can be made from a large number of templates. For anyone who has no time to make titles, but still needs them in their cut, this is a great time saver. It was pioneered by Apple in Motion (and, before that, LiveType), but from the demo we saw, Avid has more than stepped up to the plate to give us a similar tool.

Like Motion, it is keyframable, works off of a timeline model (which is manipulatable) and pretty responsive, even on a single core laptop. It doesn’t work in quite the live/interactive way that Motion does (requiring the user to click on an “Apply” button in order to see changes), and is scattered across many overlapping windows. But it is completely integrated within Avid, rather than residing in a separate application, and that should make it even easier to use than Motion and Final Cut. It was absolutely thrilling to see it.

Two other strong additions to the Avid product are the timecode and caption burn-in effects (these are actually in the present version of Media Composer, but are pretty new so many of us were just learning about them). YouTube tutorials on these can be found right here for the timecode burnin effect and here for the caption effect (which not only can create subtitles, but can also be exported for use in DVD subtitle tracks).

One other thing that we saw that we are hoping to use in January when USC opens their new cinema school building, is the Avid Media Station. This is, essentially, a stripped down Avid, which will allow the actual picture files on one Avid, to be sunk up with matching audio files on Pro Tools. Though this was demonstrated as a great way to allow sound editors to easily receive files for editing (without forcing the picture editing team into the time consuming process of creating QuickTime movies for them), we are hoping to use it as an easier way of projecting dailies and cuts. Right now, we hand OMF sessions over to our sound department, which are then sunk up to a tape or to film for projection. In the future, using the high quality digitized picture (at DNxHD36, in our case), we can easily sync it up to the same ProTools session. Voila. Time saved. Quality enhanced.

[I told you this was going to get geeky. I apologize right here, right now.]

All in all, we were pretty excited.

This is what happens when you have healthy competition between products. The user always wins.

Oh, and speaking of user, you might want to sail on over to Avid’s new blogs.  There you will find actual Avid engineers and developer type people, talking about what they are up to.  And it’s not just sales talk, it looks like it’s going to be a great place for interaction.

Share