Avid Event gives some tantalizing clues

There is a great article over at EditBlog on some tweets from this weeks AVID Media Composer Committed to Professionals event held at Warner Bros.

There is some pretty amazing stuff here. LiveToEdit tweets:

3D, 7.1, new U.I., Kona, Decklink, Matrox, Bluefish support coming soon


and

3rd party I/O: no announcements,  other than ‘we’re working with them for the future’


and

80% of pro systems are Avid, 50% of #Avid employees used to be in production


And even cooler

future is 64bit, new interface, WILL NOT lose known features, keyboard short cuts, etc.


And @comebackshane has this interesting tidbit.

Third party hardware support (Matrox, AJA, BMD, MOTU)…Plugin support from more vendors (Red Giant)…external control surfaces… #avid


93e721f7eb9c4c338ea7c4cb7c737bec_7

And thanks to
Pietari Creative for this awesome pic of the possible AVID Media Composer 64 Bit Interface.

•••••••••••

Pretty amazing news, though no timeline given. Still I love the look of the new interface, especially if is fully 64 bit, and does not lose all the features of previous AVID (see it can be done Apple).

And Black Magic and AJA support is huge, as is Red Giant Support, does that mean we may be getting Collorista 2 for AVID soon? Awesome.

It can’t come soon enough!

Mathew Levie comments on the Magnetic Timeline

Matthew Levie in his fifth and final article on using FCP X to cut has some things to say on the Magnetic Timeline that mirror my thoughts, and are the main reason I am in the process of moving to Premiere to edit.

Which brings me back to where I was on day two: the “magnetic timeline” is cute, but it keeps me from making the sequence I want and therefore it really has to go.


It reminds me a little bit of when Apple was introducing FCP 1.0 and Steve Jobs showed us how we could take a clip from the Viewer and drop it on this beautiful transparent overlay in the Canvas to choose insert/overwrite/replace/etc. and the crowd went, “oooooooh.” But who edits that way?


Maybe you’ll say I didn’t give it enough of a chance. That might be fair. I just played around with it for a few days. But the truth is that we have an editing paradigm that works for us in FCP 7. It’s not enough to show us that if we completely rethink our workflow then we can do the same things in FCP X as we can in FCP 7 with a couple of extra steps. What can we do that’s more efficient, faster, better? Yes, the infrastructure is improved; yes, the 64-bit implementation and background rendering mean things will be much faster… if we can still figure out a way to tell the stories we want to tell.


In conclusion, I think if Apple’s FCP X team really is serious about wanting professionals to use this program — and maybe they’re not, and that’s okay — we will need to see it go back to a track-based editing metaphor, at least as an option. If that happens, I can’t see why I wouldn’t use it eventually. I don’t really care about the feature set: they can always add multicam and OMF export and whatever else, and I’m sure they will. But if they add those features while retaining the current editing paradigm, it will still be very difficult to use professionally.


My biggest complaint about FXP X is that I think the basic editing paradigm is broken and much too simplistic for a professional editing program. The magnetic timeline is what the program is built around and for me it makes things harder and not easier, as Matthew points out, it actually makes many things take more steps than they did in Final Cut Pro 7.

Sure there are some cool new features, but we would have been better off having those added to a 64 bit upgrade to Final Cut Pro 7 and not this monstrosity that is Final Cut Pro X.

Apple has obviously given up on the professional editing market and done it in the most insulting way possible, and I don’t think they realized the bad press and loss of sales they will get for not taking their professional market seriously.

Larry Jordan is sticking with FCP

Today Larry Jordan has a new article, where he talks about why he is sticking with FCP for now, and waiting for new features.

I personally disagree. Apple had a mature and powerful editing program that could have been updated and have had some of the great new features added to it, but instead they decided to make a new less powerful program geared at making editing ‘easier’. The thing is they are engineers and have no idea what editing is really about, and have instead made a program that I don’t think will ever be right for a professional editor. The magnetic timeline alone proves this to me, because they no longer think that organization is important, and it is one of the most important things!

Larry Jordan has a nice post on Accountability

Larry Jordan has a good blog post on how Apple is not accountable to anyone for the disaster of it’s Final Cut Pro X release.

And it really is true. No is accountable, and Apple would hold everyone accountable if things were revered. Nvidia made one mistake and look they have not been in a mac since, and we the users are punished by Apple for it (having to put our ATI cards back in for major upgrades and then re-install the NVIDIA drivers).

I am knee deep into learning Premier Pro (after trying, but giving up on FCP X) and am pretty impressed by many features (especially the XML export being able to do the whole project with all sequences), but can’t see why this was even necessary! I can see that Apple might have wanted to cement their lead in the future, but not at the expense of their entire installed user base who are going to bad mouth the hell out of their new product until they make something useful.

And why buy Color, just to kill it a few years later? Or why kill Shake? Why did they not spin off their entire pro-division like they did with FileMaker Pro? Make a business unit that is answerable to it’s base. and needs to make a product that it’s customers want!

I am left shaking my head.

ProVideoCoalition has a good article on FXP X

ProVideo Coalition has a good article on FCP X and what Apple is probably doing.

Sooo … IF Apple loses 10% of the 200,000 high-end editors (and I think this is generous … the real number is probably near 50,000) but gains these markets, will it be an even trade? No, not at all—each of these markets is 10 times the size of the current high-end editing market. If only a small percentage buy FCPX,  Apple’s installed base will double, and quickly. Almost every person I’ve talked to in these areas are excited about the new release. They don’t want or need EDLs or multicam edits, they just want to cut their story together quickly.


In the long term, the future is more fuzzy. Apple stands to gain and hold the bottom 90% of the pyramid—if they are able to develop the application effectively. This 90% will begin to put pressure on the top 10%. We’ll just have to see how committed Apple is to the future. For the many that will be entering the market with Final Cut Pro X… getting in now means that they can learn a simple application and grow with it… like many of us did with Photoshop over 20 years. It was simple when in started, really.

And I think they will lose a lot more of 10% of the provideo market, more like 90%, but yes I admit it is a small portion of the market that Apple probably could care less about. They are shooting for the other 90% and FCP X does have some great features for them, but at the cost of making a program that will not work fro the pro-editors.

And honestly they have lost our trust completely! I mean just killing Color, an Amazing HIgh End color correction program is so arrogant it is ridiculous. And sure we could move to DaVinci from Black Magic, but that is $1000 with another $1600 for the control board, and Color was included in the FCP Studio Suite!

Studio Daily has an excellent review of Final Cut Pro X

I have to say I am starting to get burnout on FCP X disaster, but Studio Daily has a good review that covers some of my problems.

iMovie on Steroids? MaybeAfter using FCPX for a few weeks I still believe what many initially thought upon first seeing FCPX back in April: This is just the first version of a new application and in this form is essentially iMovie on steroids. There are just too many things that Final Cut Pro 7 users will be missing when they really dig into FCPX. It’s not that we won’t be able to make cool effects and pretty video, it’s just that we’ll do it in a much different way without some tools that we now take for granted. Word from people who are smarter than I am say that FCPX isn’t built off of current iMovie code. I still find that hard to believe, as the similarities are striking. If they aren’t based on the same code then Apple made a very conscious, very clear and very targeted decision to copy an awful lot of what’s in iMovie now. Some of it is actually for the better but a lot of it is for the worse.

And

•No More Dual-Monitors: Also gone is the more traditional FCP7-like Viewer/Canvas two-monitor layout. The viewing window changes to the timeline or the clip events depending on what you’re doing. In my time with the new software, I have come to really, really miss that two window layout.

And

There is the option of importing from tape, but that’s only from a tape-based camera and only via FireWire. Why Apple included only FireWire camera support is perplexing. It seems downright silly to rewrite FireWire tape support for FCPX and not include something like multi-clipping, especially when it feels like you approach something close to multi-clips when you use the new Synchronize Clips feature and have it sync multiple camera angles. Sure, the resources for FireWire support might be vastly different than support for third-party I/O hardware (which isn’t supported out of the box) but FireWire support for DV and HDV? Really? When Apple, and an entire industry, is moving away from FireWire?

And

When media comes into FCPX it must be associated with an Event or dropped into a new Event created upon import. Forget about project-based media; everything here is based on Events. In fact, all the media you’ve ever imported is available all the time. This feature alone can be totally amazing and/or insanely frustrating; I experienced both feelings when using FCPX. There are definitely times I don’t want media from other projects available, especially in a professional environment, where you can have hundreds of hours of media from different clients on your media drive. Conceptually, it’s an interesting idea for the right environment but in practice FCPX desperately needs some type of “Event Media Mounting Manager” to keep unrelated media from intruding on an unrelated project. You can physically move the media in the Mac Finder to hide it from FCPX but isn’t this an application for the future? That seems really antiquated.

And

This type of project setup, and the more structured way FCPX stores and tracks media, reminds me very much of Avid Media Composer. Media Composer has always been great at both media management and mixing formats. Avid’s often been chastised by FCP users for it’s structured, less free-flowing way of working, but Apple is doing something very similar now in FCPX.

And

The timeline has done away with video and audio tracks as we know them and therefore, it’s a very free form way of working. The magnetic timeline means clips move out of the way where clip collisions might have happened in FCP7. This new, freer way of editing will suit some; others it will not. I like quite a lot of what Apple is trying to do to make editing faster and better, but there are other things in FCPX that really don’t make the overall editing experience any faster or better. You really have to try it yourself, which makes it rather frustrating that there isn’t a free demo available.

and

My fear is this free-form timeline will lead to some real sloppy jobs coming in the door if FCPX catches on.

And summing up

The new Media management in FCPX may seem to offer more options to editors, but it actually uses a very rigid, specific way to store clips, renders and projects. If you were a sloppy editor in FCP7, then you’ll be fine in FCPX, at first. But if you don’t really understand how FCPX organizes your media you might be in for some trouble if files get moved and drives get shuffled.


I hate how there’s no real dedicated Viewer window when I skim those source clips.I hate how imprecise much of the actual editing process has become in the magnetic timeline.

And finally

How much real-world editor feedback did Apple really get before this came to market? Even though some very high profile editors got a chance to evaluate it before the release, I’m more inclined to think it was designed by a bunch of engineers who don’t actually edit for a living. Either way, it just feels unfinished. I won’t be implementing it with my paying clients as of this version, and probably not for a few versions to come. But I’ll happily bang out home movies with it.

And yes he also does have good stuff to say, but it is the negative to me that is the most telling. This is not a pro app, and the way it is built I don’t think it will ever be. Sure kids who have never edited might love it, but forcing editors to work in one way that is not proven to be better is not necessarily a better way, just different, and for this different, I am not sure I agree.

Alex4D writes about a secret FCP X meeting in London

Alex Gollner also known as Alex 4D has a blog post summarizing a supposed Apple Pro briefing on FCP X in London.

Personally Apple needs to come out and just say this stuff if it is true, and tell people what will be paid and what is coming, and give a timeline.

And anyway I think it may be too little too late. Apple has screwed this release completely. Any program that cannot open it’s previous versions files should not be called the same thing. If it is not iMovie code (which I don’t believe) then call it iEdit Pro,

Here are some point from the meeting:

1. FCP XML in/out is coming via 3rd party soon…no FCP 6/7 support project support coming ever it seems…


2. Ability to buy FCP7 licenses for enterprise deployments coming in the next few weeks…


3. FCPX EDL import/export coming soon…


4. FCPX AJA plugins coming soon for tape capture and layback…capture straight into FCPX bins.


5. XSAN support for FCPX coming in the next few weeks…


6. FCPX Broadcast video output via #Blackmagic & @AJAVideo coming soon…


7. Additional codec support for FCPX via 3rd Parties coming soon…


8. Customizable sequence TC in FCPX for master exports coming soon…


9. Some FCPX updates will be free some will cost…


And

conigs Do they have any kind of timeframe for “soon”? Am I safe in guessing in 2011?aPostEngineer within a few weeks for some updates i.e. XSAN up to a few months for 3rd party developers to get their heads around the API.gigarafa what about the rest of the suite? Color, dvd studio etc?aPostEngineer they have unfortunately reached their EOL and will not be developed any more..


So Color and DVD Studio are officially dead as well.

Helmut Kobler has an excellent article on being a Final Cuttter moving to Premiere Pro

Helmut’s article is mostly on the switch and what Premiere does and doesn’t offer, but also talks about the whole FCP X Fiasco.

Yes, well before all of Apple’s recent shenanigans, I started to sense that Final Cut, along with all of Apple’s professional apps and gear, was slowly being strangled to death. Here are a few of the harbingers of doom that caught my eye over recent years:


• Apple took nearly 2.5 years to upgrade Final Cut Studio from version 2 to 3 (and v.3 was only a moderate upgrade at that). Until then, updates had come at a much more aggressive pace.

  • Apple cancelled the popular Shake, promising to replace it with a new tool that never came.


• Apple got lazy with its Logic Pro app as well, letting development creep along with an upgrade about every two years.


• Apple stopped updating the Pro page on its web site long ago. There hasn’t been a new item posted in almost two years: http://www.apple.com/pro/


  • Apple took more than a year to fix a glaring Final Cut 7 bug that made its Close Gap command unreliable. To break a core Timeline feature like Close Gap and not fix it for 14 months was offensive and inexcusable.


• Apple cancelled its Xserve RAID then its Xserve hardware.


• Apple started taking longer and longer to release Mac Pro workstations, and absolutely phoned in the latest upgrade last July. 511 days in the making, the newest Mac Pro was one of the most un-inspired hardware upgrades I’ve ever seen from Apple.


• Apple pulled out of industry trade events like NAB.


• Multiple rumors (and confirmation of rumors) of significant layoffs in the Pro Apps division.


• Multiple rumors that Apple was trying to sell off its Pro Apps division.


Take just a few of these and maybe they don’t add up to anything. But take all of them together, and it’s a real sign of Apple’s low-to-non-existent priority for professional media. Yes, the writing has been on the wall for quite a while, and by 2010, I reluctantly began to read it. Late last year, I started to look at the two clear alternatives to Final Cut….

The rest of the article has some excellent reasons why he moved to Premiere, and documents the differences and similarities, and really gives a good idea of why to try out Premiere Pro, it really is a must read!