-
gruber constructs a carefully apple supportive line of bollocks
-
[Scott Sheriff] “Since you’re this hours designated apple apologist, maybe you could explain what those that want or need FCS3 are supposed to do?”
I do think Apple probably should have continued selling FCS3 for a year or whatever to help ease the transition. But realistically, it’s probably not going to be very hard for anyone who wants a copy to get one. As I pointed out in a previous post, for instance, FCP X actually is suitable for a respectable fraction of Apple’s user base even now, and because it’s not sold as an ‘upgrade’, users who migrate to it are free to sell off their copies of FCS3.
—
Digital Workflow/Colorist, Nice Dissolve.You should follow me on Twitter here. Or read our blog.
-
[Chris Kenny] “I’m not sure I understand what the problem is with leaving (some of) their users where they were two days ago while continuing to add features to FCP X that will eventually allow those users to move over.”
I don’t even know where to begin to answer that.
Like I have said before, your defense is admirable, there *may* be something to this program some day for the 54% market share, but please stop. They yanked off the shelf where their users were 2 days ago on top of this very limited release.
There is far more going on here then just a lack of features and that’s fine you won’t address that, but this is a complete paradigm shift on Apple’s part when that new paradigm cannot even replace what came before it while at the same time yanking 7 out of our hands without warning…
Yes, we can still use 7…if we have a copy or are lucky to find one that doesn’t cost 3000$ on ebay by next week…
It stinks. It’s not overly dramatic…this is a pretty big deal to some of us…
-
No Ben, I’ll stay really annoyed thanks. Enjoy your rad fast software and the best of luck to you.
http://www.ogallchoir.net
promo producer/editor.grading/motion graphics -
[Jamie Franklin] “Like I have said before, your defense is admirable, there *may* be something to this program some day for the 54% market share, but please stop. They yanked off the shelf where their users were 2 days ago on top of this very limited release. “
FCP X isn’t missing that many features (i.e. I think it will be viable for most people sooner than “some day”), and while I agree Apple should have left FCS3 on sale, the way people are acting you’d think Apple had yanked it off their hard drives.
In point of fact, it’s not all that uncommon for more conservative customers like facilities to hold off for 12 or 18 months even on incremental upgrades… and Apple has always, as far as I know, pulled old versions when new ones went on sale. So if those customers managed to remain FCS2 shops for 18 months after FCS3 was the only thing on Apple’s shelves, I don’t see why they won’t be able to do the same with FCS3 and FCP X.
—
Digital Workflow/Colorist, Nice Dissolve.You should follow me on Twitter here. Or read our blog.
-
[Chris Kenny] “Has your previous software stopped working? No. Were really you going to move all of your projects to a newly rewritten NLE the first day it shipped regardless of what (remotely realistic) feature set it offered? Probably not.
“When they went from FCP6 to FCP7, all my projects still opened, as well they should have. Are you kidding me? Had they spent the last two years added these new features to FCP8, my projects would have opened just fine. Now i can’t even share a project, nor export a EDL, nor do any of dozen obvious work flow features I have come to rely on.
Jim Carey
Director of Video, Radical Entertainment
linkedin: https://ca.linkedin.com/in/jcarey256
mobygames: https://www.mobygames.com/developer/sheet/view/developerId,17212/ -
[Chris Kenny] ” So if those customers managed to remain FCS2 shops for 18 months after FCS3 was the only thing on Apple’s shelves, I don’t see why they won’t be able to do the same with FCS3 and FCP X.”
You have me scratching my head here. FCS3 was a pretty soft “update”…this is not. And I think the way this was delivered gives everyone enough reason to doubt it’s future. Drama justified. That aside, we have been clamoring for Final Cut to keep pace with other platforms and not reinvent the wheel while we wait for it to be viable for a true post workflow. “Some day”…
I just feel the pushback is warranted. The pushback to the pushback seems fairly shallow and assumes things none of us know on Apples behalf who are quite, understandably at this point, silent…
-
[Jamie Franklin] “You have me scratching my head here. FCS3 was a pretty soft “update””
Yes, but files weren’t backwards compatible. Which means that facilities that chose to stay on FCS2 — which quite a few did — had to be able to get copies of it despite it not being available direct from Apple anymore. If getting discontinued versions wasn’t a serious problem then, why would it be now?
[Jamie Franklin] “I just feel the pushback is warranted. The pushback to the pushback seems fairly shallow and assumes things none of us know on Apples behalf “
As I’ve noted, there’s evidence of at least some level of implementation of some of the missing features lurking in the FCP X binaries. Apple pretty much told Philip Hodgetts flat out that they’re working on the ‘ecosystem’ thing, which means XML or some other interface mechanism for third-party tools. And the idea that Apple is never going to support video I/O is kind of silly. I mean, what’d they bother with Thunderbolt for, if they’re not going to use it for things like this? My guess with video I/O is that it requires framework features that aren’t quite there yet (remember, FCP X isn’t written on top of QuickTime). I’d say there’s about a 60% chance they are there in Lion.
—
Digital Workflow/Colorist, Nice Dissolve.You should follow me on Twitter here. Or read our blog.
-
[Chris Kenny] “Yes, but files weren’t backwards compatible. Which means that facilities that chose to stay on FCS2 — which quite a few did — had to be able to get copies of it despite it not being available direct from Apple anymore. If getting discontinued versions wasn’t a serious problem then, why would it be now?”
It was where I worked then. That wasted a lot of man hours for such a dodgy thing *forcing* us to upgrade and shelving projects until we got our systems running…I’m not saying my experience was everyone’s so I can only speak for myself on that…bygones
-
“As I pointed out in a previous post, for instance, FCP X actually is suitable for a respectable fraction of Apple’s user base even now, and because it’s not sold as an ‘upgrade’, users who migrate to it are free to sell off their copies of FCS3.”
…Unless you want to ever open up your old FCP7 or earlier projects. Seeing as there is no capability to open older FCP projects… most editors are likely to hold onto their Studio 3 copies. Even if we move to Premiere or Avid those Studio 3 licenses will let us access our old projects natively, and export XMLs and such as needed.
*Sony PMW-F3 (Preordered!)
*Final Cut Studio 3 -
[james carey] “Had they spent the last two years added these new features to FCP8”
Technically impossible. A rewrite was necessary. Apple bit the bullet and did one. It will take some time for the new app to match the old app’s feature set.
—
Digital Workflow/Colorist, Nice Dissolve.You should follow me on Twitter here. Or read our blog.
Reply to this Discussion! Login or Sign Up