Apple probably needs to do some damage control, Now.

yoclay

Veteran
From my post over at Creative Cow:

Apple probably needs to do some damage control, Now.

by Clayton Burkhart on Jun 22, 2011 at 2:49:53 am


Ok, given the near universal negative response to this release across a broad spectrum of forums out there, I really think that Apple needs to do some damage control, NOW.

This post really isn't about me or my satisfaction at all. I can go on using what I always have. I have nowhere near the talent and expertise of so many seasoned pros here, but I have seen one or two situations like this before in my time and this is what I see: If Apple was a Hollywood star, their PR firm would definitely be all over this, trying to formulate a damage control plan.

It really would be wise for them to make some kind of semi-official announcement basically saying, we know that we kinda blew it, BUT, we are listening to YOU the professionals.

I can understand the silence leading up to the release, but now that it is out there, continued silence probably wouldn't be the right move.

They likely need to say to the professional, we recognize the shortcomings you have pointed out, you matter to us and we will try to move this forward in a more transparent way. We are listening, we still believe in the quality of our new product, and we will provide you with a product that fulfills your needs.

Real damage control always acknowledges the reality and the mistake. Everyone, including corporations make mistakes, but respect is always actually gained when the party involved takes immediate and open responsibility for it.

And then, LISTENING. They definitely need to show that they are listening.

Hold another town meeting, make a questionaire, convene a panel of experts, whatever. The point is ASK people what they really want.

It is the only way I think they can turn this around, otherwise I am seeing a serious migration away from Apple. The signs of open disdain and heading for the exits were already there, but I am not witnessing a slow shuffle away this evening, I am watching a virtual stampede.
 
..and I doubt they care.

Iphones and Ipads are far more profitable. They are dispo$able, fa$hionable and have planned ob$olo$ence.

Adobe cares for the professional and listens like no other.
 
Apple make their money from mass sales of products... FCPX/iMovie Pro will be a hit for people wanting more power than iMovie. In comparison the professional market is tiny.

There was a day when Apple was the alternative/creative platform, but as 'Shooter' mentioned their main core business is shifting large volumes of consumer products... which they obviously do very successfully. They are using professionals and their 'old image' as a platform to boost sales of mass market goods. Welcome to the world of capitalism. Apple is a very successful corporation, they saw where the money was and went for it! I think some of us are just a bit surprised at how easily they dumped their 'traditional' customer base.

What annoys me is the contempt that we are all being treated with. The launch event six weeks ago was orchestrated mass hysteria! Remember when all the fan boys screamed and applauded when every new feature was announced...... now the reality is sinking in!

FCPX will be a great editing app for the advanced amateur, what it isn't going to be any time soon is a 'professional' tool. People can argue that this is only the first release but in reality thats is not true. If you are serious about maintaining loyalty, you build on your products, and don't abandon your client base along the way. Professionals have invested time and money in the product because in return it makes money for them. Yes you can stick with the old FCP but in reality with very little development in the last 18 months that is showing its age.... So the decision is easy, do you stay on board and become a product tester for Apple, hoping that the product will go in the right direction, but at the same time not really knowing what that direction is? Or do you jump ship and relearn a package that you know has a professional pedigree, and a commitment to future professional development? It's not an easy choice, but there are at least two other products in Premier and Avid to choose from.

I love Apple products, but the reality is their raison d'être is to make money, its a corperation not a religeon :cry:
 
I agree, that the professionals are a small segment. But they are the ones to hold on to a product over the long terms. They are not jumping to the next cheaper product with one cool feature more. Plus they are the opinion-leaders.

I work with apple computers since 18 years. I work in graphics and film industry. I have always praised apple over their competitors, liked the way they provided intuitive PRO apps. Now apple has lost me. I waited 2 years for some bugs to be fixed in FCP7. Now they stopped delivering a pro editing system. Today I am gonna install Avid. When there will be an apple equivalent operating system out there on a 3rd party hardware – I won't hesitate to switch to it.
 
It could be a tactical decision to omit features. A way of gently easing away from the pro market instead of waving a flag.

As Jay-Z says "learned to dumb down my lyrics and double ma dollars"
 
ive already downloaded media composer 5.5. 30 day free trial. ive only used FCP since v3.0 and has done a great job. i dont know what ill end up doing but im not going to sit around sitting on my hands dreaming that apple will change what they just dropped on us yesterday.

i dont think apple cares about the hard core FC user anymore. honestly if they dont that thats ok and i can resolve to moving on but like an above poster pointed out the at the coming out demo party with the 1,700 industry professionals in the house i think back now how absolutely absurd it was for them to be boasting about how this is the new cats meow. their words are just hype now.

dont know where ill end up but for sure FC 7's days are limited. if it works with Lion then that should buy another year maybe. FC7 will still be making me the money in the near term but its now time to plan for the future. ill see how Avid MC fairs.

david
 
Apple has been going down this road for a long time. Apple used to make machines geared toward pro use. Remember the industry workhorse the powermac 9600? It had 8 pci slots!!! Then the g3,g4, and g5. All great machines and with every upgrade, I knew I could count on a real "wow" moment when I saw it perform. Ever since switching to cheaper intel processors, I haven't had a "wow" moment. When I sold my quad g5 and bought my 8 core Mac pro, I thought something was wrong. I saw very little improvement and on some things, I actually saw decline. Since then, I have had the same frustration every time I get a new machine, or a new OS comes out, etc.

Look at the current lineup of Mac pro's. The current 8 core is slower than the last generation 8 core (barefeats.com). A $3500 downgrade. That is crazy!!!

So this fcp-x/iMovie pro garbage is just the icing on the cake and more of the same.
 
This is the first release that has made me consider going back to the PC -- FCP is a reason some have made the switch to begin with, as nearly all the other production apps are available for the PC. It used to be that Macs just handled video better than PCs, but seems like that's not the issue anymore. Hope Apple realizes this could push a lot of loyal FCP users back to the PC!

The would have been much better off releasing this as iMovie X -- it should not have had the "Pro" in the name!
 
It's early days… Apple admits that FCPX isn't finished and that updates will be coming continuously over the coming weeks. As it stands right now you can run both FCP7 (studio) and the new FCPX (+motion & Compressor) at the same time - the new doesn't overwrite the old.

Soooo - since I have a few projects already on the go in FCP7 (and wouldn't dream of switching / upgrading mid-project) I'll continue on with the current workflow… I've also got FCPX up and running with some footage odds and ends so I can learn it's completely new workflow; and yes right now it's lacking what I would consider some essentials but I would assume that if Apple says they are on their way, they will come.

If that doesn't happen in the next 6-8 months, then yes I'll start looking for alternatives. Right now I don't understand all the shrieking and hand wringing - just because something new has come out doesn't mean you need to buy it. This new release also doesn't mean that the old suddenly stops working and clients will immediately pass you by because you don't have the newest edit suite…

Sorry gotta go take this call on my DIAL phone.
 
Why Switch to FCPX

Why Switch to FCPX

I have seen several comments about FCPX being a "completely new program". So if someone currently uses FCP7 and is now faced with having to learn an entirely new NLE, why would they learn a new system that is very unclear what the long term support for pros is, versus learning one of the other system that have very established pro track records and road maps.

If apple want to maintain their pro user base, they need to get out ahead of this a make it very clear what their road-map is to deliver the pro feature. "oh, they might come in the future..." doesn't cut it.
 
Apple wants to have their cake and eat it too.

Apple wants to have their cake and eat it too.

I think we are all looking at this the wrong way. The fact that Apple is trying to have their cake and eat it too is the real issue why many are ticked off.

I'm pretty sure the original FCP developers and teams that wanted to compete with Avid are long gone--as are the times when Apple needed to compete with Avid and PC. Newer developers built the iMovie infrastructure for the regular Joes and within the last few years somebody up the chain did a quick look at the books and decided there are far more users at the Joe level so a decision was made to service them instead, which basically meant that Apple was exiting the pro software development business. Adobe and Avid better serve those markets and don't have a giant corporation to run with bigger fish to fry (cloud computing, fighting Google for ad and search on Mobile, changing the way end users interact with the web and TV, making the next big wolrd-changing phone/tablet, etc, etc..)

Apple made huge in-roads into the pro world with FCP, but never really threatened to knock Avid off the top. (The best thing FCP did was to force Avid finally let Media Composer be a nice stand-alone app without costly Avid hardware). Also, I'd guess Motion never really threatened After Effects and Soundtrack never hurt Pro Tools. One could argue that Apple doesn't want to go after that hornet's nest of "Gotchas" and that they had two options yesterday, both are true.
-------------------------------------------------
Apple Inc. Press Release.

Today Apple is officially exiting the pro video apps. Please consider our new iMovie X or contact Adobe and Avid for your next round of upgrades.


Or

Apple Inc. Press Release ver.2

Apple has changed the way people edit...everything is different, blah blah blah.
-------------------------------------------------------

I bet they decided to stop pro app development after much arguing deep inside, and the final decision was to integrate iMovie and FCP to one development team and then have the marketing dept. do the best job they can to retain pros but realize the pros are likely headed to Avid/Adobe but the increase of Joe's makes FCPX a bigger hit than FCP and still drives hardware sales as does people editing on Adobe or Avid on a Mac.

As far as this being a pro app, I think that is just the marketing dept's spin. I think if it was built for pros, you wouldn't have a "Ken Burns" button and XML export would be included day one as well as working with 3rd party developers beforehand to make sure the MXOs, AJA, and BM i/o cards worked from day one. They managed to figure out how to export to all the iDevices and web players, right? I also would think that an Import FCP project would be front and center. Even if the techno stuff makes the old project obsolete, they could still pop up a message like "Warning, do to the totally different techno stuff, your FCP project will open with limited usability and not all titles, gfx, animations, etc, will open correctly."

Apple is usually smart on these things and see that more people from non-video backgrounds are being tasked to create and post sh*t online. I just wish they had the balls to tell those of us that pay mortgages using FCP that they aren't interested in this market anymore.

Now it is a guessing game. Do we learn (or re-learn) Avid or use the more tempting CS5.5? I'm sure I'll bite and give FCPX a whirl and the new timeline looks great, but I'd rather devote the time learning a new app to one that I know I can get hired to use as an editor.

Should someone start a FCP user emotional support group? I think we are going to get picked on by all of the Avid/Adobe folks once we start asking for help on their forums!!!!

(p.s. I'd love to know the inside scoop. Maybe a former employee can write a tell-all book.)
 
Last edited:
I would love for nothing more than for Apple to succeed with Final Cut Pro X, and, hell, I've swam in the Microsoft Windows ocean since version 3.1. Competition between Media Composer, Premiere, Vegas, Final Cut, ect. means that these companies will continually push the bar for a leg-up over the competition that means we, as users, win in the end. That said, FCP X in its current form is on its way down, and we have no idea how serious Apple will be about releasing updates to fix these issues. They may never do anything more than release their two fixes a year for bugs and do nothing more. XML was the biggest issue that Walter Murch encountered when using FCP 3 to edit Cold Mountain and it's ironic that here we are again almost 10 years later and once more this feature is missing. Will it ever be added? No one knows, and if Apple stays as tight-lipped as to FCP X's future as they were about the product itself, I think you'll see a slow migration begin away from Final Cut.

I appreciate that Apple is trying to re-think the post process, and maybe there is some value in the direction they've headed. But just because it's different doesn't mean it's right.
 
Apple has been going down this road for a long time. Apple used to make machines geared toward pro use. Remember the industry workhorse the powermac 9600? It had 8 pci slots!!! Then the g3,g4, and g5. All great machines and with every upgrade, I knew I could count on a real "wow" moment when I saw it perform. Ever since switching to cheaper intel processors, I haven't had a "wow" moment. When I sold my quad g5 and bought my 8 core Mac pro, I thought something was wrong. I saw very little improvement and on some things, I actually saw decline. Since then, I have had the same frustration every time I get a new machine, or a new OS comes out, etc.

Look at the current lineup of Mac pro's. The current 8 core is slower than the last generation 8 core (barefeats.com). A $3500 downgrade. That is crazy!!!

So this fcp-x/iMovie pro garbage is just the icing on the cake and more of the same.

Then you had a serious hardware problem on your Intel machine because this is absolutely not true. When I was using my Dual core G5 processor, I bought a MacBook CoreDuo LAPTOP and it absolutely SMOKED my G5. I couldn't believe it. I then bought a Mini when it came out with a coreDuo as well and it too smoked the G5. While the Altivec processor on the G5 architecture was nice, it was NO comparison for the performance increase the Intel platform brought. At that time I was heavy into audio work and I did very thorough benchmark tests with DP and Logic at the time.

Since that time I have moved my tower over to a quad core Xeon and have been using that machine since 2006. The machine is so fast people don't even believe me that it is 5 years old. It has no need to be replaced.

My laptop is a current i7 quad core 2.2Ghz. The rendering is faster on this laptop than even on my tower. It's also A LOT faster than the Core2Duo 2.93 GHz that I just sold. I've done the benchmarks.

I'm not saying there hasn't been road bumps, because all these multicore processors have had issues on performance at times, especially the 8-core, but I've noticed nothing but speed improvements on each machine I have purchased from Apple. I did the research and I've never been happier. It's not always the cores either, it's the fact that memory, HD performance, video card performance ALL play a role in the speed.

The software I wrote performs 100% faster on the 2.2Ghz i7 compared to the 2.93Ghz Core2Duo. I was like a kid in a candy store when I saw that!

I'll tell you also, BEST upgrade you can make to a computer is using SSD. Just wow.
 
professionals are a small segment. But they are the ones to hold on to a product over the long terms. They are not jumping to the next cheaper product with one cool feature more.

This is exactly why PRO users are bad consumers in Apples mind. Its a small market, Pro users have sky high expectations because they use the product for mission critical work. They won't just dump a product to pick up a new one with out a quantifiable advantage over the old software. Its not like consumers who wait in line 4 hours to replace perfectly good hardware with a new version that's white and has a camera.

What Apple has done in my opinion is used the brand power of FCP slapped it on the next gen iMovie and will cash out as hobby editors upgrade to what they think is "pro software" Just imagine how sexy it is if you are an iMovie editor without the means to go Pro and suddenly the pro market is 300 bucks.

Why continue to develop for the pro market when you can convert a whole new market segment from consumers to prosumers. Apples new attitude is let Avid have Hollywood. We will make editors out of every person who visits Hollywood on their vacation. And as much as we hate it they will make a lot more money this way.

I think this is Adobe's game to win. They have the most similar product
 
Rick, I had the machine checked out. No issues. It's just not the performance jump I was used to with a 3 year newer machine. Since then, i have gone through several intel macs and experienced similar blah results. Have you seen the benchmark tests at barefeats.com? They actually advise buying a used 8 core 2.93ghz over the brand new 8 core.

When I jumped from my 604e machine to a g3, it was like the gates of creativity opened up and I giggled like a school girl. I called all my friends, threw a party, etc. Same story when I went to g4 and g5. Intel was a move not based on performance, but economics.

Once again, apple. If it ain't broke....

Same goes for os stability. Os9 was rock solid. Remember? You could allocate the amount of ram an application got. This prevented crashes due to memory conflicts. Back then, if I put in a new stick of ram, I immediately saw a boost in performance. Now, I really don't.
 
Rick, I had the machine checked out. No issues. It's just not the performance jump I was used to with a 3 year newer machine. Since then, i have gone through several intel macs and experienced similar blah results. Have you seen the benchmark tests at barefeats.com? They actually advise buying a used 8 core 2.93ghz over the brand new 8 core.

When I jumped from my 604e machine to a g3, it was like the gates of creativity opened up and I giggled like a school girl. I called all my friends, threw a party, etc. Same story when I went to g4 and g5. Intel was a move not based on performance, but economics.

Once again, apple. If it ain't broke....

Same goes for os stability. Os9 was rock solid. Remember? You could allocate the amount of ram an application got. This prevented crashes due to memory conflicts. Back then, if I put in a new stick of ram, I immediately saw a boost in performance. Now, I really don't.

I guess we have different experiences then, because the G5 has NEVER been faster than any of my Intel machines from Apple that I have owned or tested. I benchmarked with multiple methods, including Xbench to test based on other peoples results and with applications like DP to see how many instances of intensive plugins I could get running at one time before the system started to hang. NEVER did the G5 I had even come close to the performance of the MacBook I had purchased. I was amazed, because normally, the mobile processor versions take a hit on performance for power reasons.

I started with a G3, then a G4, then a G5. When the G5 came around, it was faster than the G4, but for me, no different than the feeling I had with the switch to Intel later on. I immediately saw an improvement. Apple switched away from G5 because the architecture did NOT deliver scaling forward. I have insight into the companies making PPC architecture as I have actually worked on PPC chips. Do you remember how loud the G5 was due to how much cooling was required? Do you remember the G5 laptop processor? No, me neither, because it never existed. In fact, I think that a lot of the PowerPC technology went into the cell processor technology that the PS3 is based on, but that hasn't moved on really anywhere. Apple DEFINITELY made the right decision to move to the Intel processor. I have NEVER had ANY intel machine from Apple need to be repaired. Not once. And that includes two Mac minis, three MacBook Pros, and MacBook, and a Mac Pro Tower. Never once have any of these had to be repaired. The G5, it had to have the power supply replaced, and the logic board replaced by the person that bought it from me. The G4 iMac, it needed a logic board replaced. So far, my experience with the Intel board architecture has been awesome.

But even to take this a step farther, the problem hasn't in the past been an issue with the actual 8-cores OR the architecture of the motherboard. It's been the OS multicore support. I use machines to develop microelectronics that have 16, 32 and even 64 cores in them and they are Intel. They work great with Redhat Linux and I never have problems. I can see the scaling of performance from well written multi-threaded applications. I believe Apple is trying to address this by helping coders do a better job with the Grand Central API, however, if a developer doesn't do this, then certain applications are just never going to scale well with more CPUs. This is a very common issue with multitrack recording software. Not all of them scale well. Apple wrote a lot of OSX with the PPC architecture in mind. Now that they've moved away from it, I expect it to take quite a few years to work out the best methods as Linux flavors have done to get the most out of multi-core.

And also, I do remember OS9. I also remember issues with having extensions loaded that gave problems with other extensions. I also knew the constant battle of trying to allocate memory properly. I was NEVER impressed with OS9 and refused to purchase a Mac until OSX came out. Being that I have developed unix software before, I understood the performance hit because the FreeBSD system is MUCH more powerful. True, you don't have the control to tell applications how much RAM they can or cannot use, but I never cared about that. I don't want to have to micromanage my applications. And I don't get crashes due to memory conflicts, what does that even mean? If an application crashes because it cannot handle being swapped in and out from disk, then that is a problem with the application. Becoming an app developer on OSX and studying Carbon and Cocoa, I could see what Apple was trying to do. Have you ever explored the foundation classes in OSX? Have you seen the beauty that is CoreAudio, CoreMidi, Quartz, etc. There is a reason that a lot of audio applications just work AWESOME on OSX, and that is because Apple put a GREAT deal of thought into the audio API that did not exist before in OS9 OR Windows for that matter. The whole DirectX and ASIO driver situation to this day is still inferior to that Apple implementation. There are HUGE steps Apple took in an effort to make applications even more robust in the future, and I applaud them for that. It's a joy to program in Cocoa.

I can GUARANTEE you that if you run Adobe After Effects with 2G of RAM and try editing a bunch of multi-layered material, it's going to run slow as it has to swap out a bunch of stuff. If you put in 8G, which I have done, you will immediately see an increase in performance. RAM doesn't dictate the operation of the CPU with modern architectures as much because of how important the cache systems have become. This is a GOOD thing. Just because you add more RAM doesn't mean your machine will go faster, it means you had enough RAM before and there is a different problem. Back in the days of OS9, RAM wasn't prevalent to the levels as it is today, even adjusting for content/application bloat.

And it's funny, because we recently resurrected a machine at a studio I work with occasionally to use some OS9 video software (Imagine). It was so painful trying to get the extensions to work right we just gave up. We couldn't believe we used to deal with ANY OS9 in the past. The only thing I want Apple to do now is get rid of resource forks. Try FTPing an SD2 file and then downloading it again to work on it. (SD2 is an audio format called Sound Designer 2). It doesn't work and is a huge pain in the neck when transferring files to other places that need SD2 files.
 
To people that haven't been editing for years and years on other platforms, iMovie feels intiuitive, like the way video *should* be edited, if such a thing were a natural occurence. The problem has been, especially on 2 hour project, that is just doesn't work. Crashes, has mysterious bugs, too limited funcionality with audio, cc, no pro codecs, no frame rates, etc, etc, etc.

If FCP X fixes all of that, allowing us to use all the power under the hood of the computers with a much broader feature set, I think we've got ourselves an elegant weapon in the cinematic arsenal, perhaps one of the most interesting in years.
 
I think those hoping Apple will "add in all the Pro features" over the next year will be sorely disappointed. It is very clear Apple did not and does not have the Pro Market in mind, because they would have never released this product without working with 3rd party hardware/software/plug-ins, and without some very basic pro features/settings/preferences. Cutting Xserve, no new Final Cut Server, etc. is also further evidence.

When you set out to design a Pro product, even if you aren't "fully baked" on version 1.0, you start with those pro features as the foundation, not an afterthought. They had plenty of time before this release, there were many rumors as far back as 2007 that Apple was working on a completely rewritten version of FCP. Guys, this is not going to change. June 2012 won't bring us FCP7 + FCP X. I absolutely hate to say it but reality is sinking in.
 
Back
Top