Chris Kenny
Forum Replies Created
-
[Andrew Richards] “Yes, but their stock price hasn’t been stagnant for a decade like MSFT. If you bought Apple ten years ago, you’re doing pretty well now. I don’t follow finance that closely, so maybe I missed it, but I haven’t heard of Wall Street complaining Apple has too diversified a product portfolio.”
Wall Street, if anything, worries about the opposite — that Apple has too few products, and therefore is overly susceptible to a single important product having an off quarter.
—
Digital Workflow/Colorist, Nice Dissolve.You should follow me on Twitter here. Or read our blog.
-
[Herb Sevush] “I’m not playing word games I’m simply using words precisely. Adobe did a total 64 bit re-write on Premiere Pro and it was most definitely NOT “an entirely new ap.” When Avid does it’s re-write I will bet your bottom dollar that it will not be “an entirely new app.” “
No. People keep saying this. I’ve addressed this several times. Moving to 64-bit does not require rewriting an app. It requires taking your existing codebase (probably mostly cross-platform C++ for Premiere and Media Composer), and making it “64-bit clean”, which mostly consists of making sure it doesn’t make 32-bit dependent assumptions about handling memory, and doesn’t call libraries that aren’t 32-bit clean.
Adobe did not rewrite Premiere to make it 64-bit. They did rewrite Premiere back in 2003, and it was fairly messy.
The reason Apple had to actually rewrite FCP was not (just) to move it to 64-bit, but to move it away from QuickTime and Carbon, which it was heavily dependent on.
[Herb Sevush] “How? They’ve EOL’d all support for FCP7.”
They’ve stopped selling new copies. This is not the same thing as EOLing “all support”, or disbanding the maintenance team. Do you have a source that claims they’ve done the latter?
—
Digital Workflow/Colorist, Nice Dissolve.You should follow me on Twitter here. Or read our blog.
-
[Gary Huff] “I have been a Windows guy for all my life and just purchased my first MacBook Pro. I really like it, but if Apple decides their future is iOS only, then I have to decide whether I can work with an editor that relies on a touch interface and make an informed decision, instead of being stuck with expensive hardware that is no longer supported by the company.”
As of today, as far as we know, Microsoft, with Windows 8, has more ambitious touch plans on the desktop than Apple. Now, this may very well be solely because they tend to talk about things three years in advance, whereas with Apple you get maybe six months warning. But, again, as of right now, there is absolutely no public indication that Apple is going to move to touch-only systems.
In fact… that would be incompatible with the hover-based scrubbing that’s a major new feature of FCP X. (Well, unless they move to touch systems that can detect hovering, but that would still be kind of awkward, I think.)
—
Digital Workflow/Colorist, Nice Dissolve.You should follow me on Twitter here. Or read our blog.
-
[Dave LaRonde] “You mean you’ve never had a system drive go south on you for no reason? Boy, are you lucky! I hope your luck holds.”
I’m pretty sure Apple has not actually sent goons around to collect everyone’s installer discs. If you’re worried about those going bad, image them.
[Dave LaRonde] “Take off those rose-colored glasses. About three weeks ago, Apple kicked approximately two million of its customers right in the nether regions, and no amount of rationalizing is going to change it.
“This is, again, vast overstatement. People are projecting their own requirements onto two million other individuals. The truth is, most of the features missing from the first release of FCP X are probably not used by 80% of FCP users. Certainly this is true of things like EDL and OMF export.
—
Digital Workflow/Colorist, Nice Dissolve.You should follow me on Twitter here. Or read our blog.
-
[Christian Kinnard] “After playing around on a test project for 2 weeks what stands out to me is a lack of preciseness. When I’m moving through dailies, I want to move quickly. As far as I’m concerned, all the bells and whistles of background rendering, 64bit, etc are coming to every system. But if it lacks a precision, I want nothing to do with it. I started on M100, learned FCP and Avid at about the same time, also jumped on to Premiere for a little. The argument that I’m just not used to it yet, it’s that revolutionary, is asinine.”
People keep making statements like this without providing specifics. How is FCP X imprecise? Yes, dragging ranges is not the most precise way to mark in and out points. But scrubbing is a really fast way to find something in a pile of footage, and J/K/L and I/O still work when you need precision. There are quite a few commands for trimming in the timeline with similar accuracy, including some FCP 7 lacked.
I really not trying to be a jerk here, but having used the app, I have no literally idea what you’re referring to with this criticism.
—
Digital Workflow/Colorist, Nice Dissolve.You should follow me on Twitter here. Or read our blog.
-
[David Roth Weiss] “That’s your spin entirely Chris, and you’re coming off sounding like a moderator or arbiter of sorts, which you are not.”
Could you please explain what information Apple released via Pogue, that was cited in this forum, has not been borne out, other than the Red workflow information, which was identified as being incorrect at the time?
—
Digital Workflow/Colorist, Nice Dissolve.You should follow me on Twitter here. Or read our blog.
-
[Dave LaRonde] “Apple could have continued FCP 7 sales and it could have kept FCP 7 support on the web site, while steadily filling FCP X’s vast gaps in utility… now that’s a transition period!”
I agree that Apple should have done this, but, again, I believe people are seriously overstating the real-world consequences of Apple having chosen not to. Particularly if Apple restores the ability for volume license customers to add seats; it’s large institutional customers were were most impacted by this. Smaller more flexible shops can always go to eBay.
—
Digital Workflow/Colorist, Nice Dissolve.You should follow me on Twitter here. Or read our blog.
-
[Herb Sevush] “No, it turns out they were totally correct. Apple didn’t re-write FCP, they created, as you have rightly been calling it, an entirely new ap and stuck FCP’s name on it.”
You’re simply playing word games here. A rewrite is “an entirely new app”.
[Herb Sevush] “Of course, as even you have agreed on previous posts, this was totally within Apple’s control. If they wanted to create an Ap that was upgradeable they would have. This is proof of their re-targeting. They knew this was important to their facilities base but they didn’t care enough to incorporate it into their new design.”
They could have created an app that was more compatible… by declining to implement what they believed was an extremely compelling new approach to handling sequences. This is not evidence of Apple ‘retargeting’, it’s evidence of Apple being willing to take a short-term hit to have what they believe is a more compelling product in the long run.
This is not especially unheard of for Apple. For instance, there’s OS X’s Quartz graphics engine, which was, frankly, fairly sluggish on the hardware OS X shipped on for the first couple of years. But Apple was willing to put up with that tradeoff, to have a more capable, future-proof graphics engine.
[Herb Sevush] “Then why did they EOL FCP7? How does that make it easier to continue working along side FCPX. This is the part you really REFUSE to look at. “
There’s information out of last night’s London briefing to the effect that there were legal reasons behind this. My guess is FCS3 requires third-party licensing that Apple doesn’t want to continue paying.
[Herb Sevush] “I’ve seen elsewhere your repeating the nonsense about running FCP7 on Lion. There has never been a single operating system upgrade from Apple that didn’t result in multiple bugs and editing problems over time; they all had to be addressed by a dot point upgrade, but now with Lion everything is going to be perfect right off the bat? “
Huh? No. I haven’t said that at all. I simply think that, having promised that FCP 7 will work on Lion, Apple will fix any such issues, and that it’s essentially FUD-mongering to claim otherwise. Having made this representation in the FAQ, Apple could now be sued for failing to deliver on it.
—
Digital Workflow/Colorist, Nice Dissolve.You should follow me on Twitter here. Or read our blog.
-
[Brian Langeman] “You originally said in your reply that other outlets reported the same information as David Pogue. I can’t recall other outlets relaying information about collaboration with Red, as Pogue did. Then you dismiss Pogue’s info about it, assuming a miscommunication.”
Yes, part of the reason I dismissed Pogue’s comments on collaboration with Red was that other outlets weren’t reporting the same thing. I’m not entirely sure what your point is here.
—
Digital Workflow/Colorist, Nice Dissolve.You should follow me on Twitter here. Or read our blog.
-
[Steven Gonzales] “If a feature means a long form piece, yeah someone will do it.
A feature means originating on film (still predominant) and finishing sound elsewhere, and conforming a DI or cutting a negative, is some future unknown time.
Film Logic worked with FCP1 because it took an EDL, and FCP gave an EDL. Sound worked because tracks were assignable and could be exported to ProTools.
Sure, this could happen some day. I just wouldn’t plan on it for at least a year.”
Again (I’m going to keep repeating this until people quit making statements that don’t take it into account), XML export is coming in “a few weeks”. Someone will figure out how to get sequences into Resolve, etc. via that route (processing FCP X XML into FCP 7 XML or EDL files) fairly quickly once that’s available. I’ll do it myself, if nobody else does is quickly enough for my liking.
Tagging audio clips to assign them to tracks on export is coming “this summer”.
This is right out of Apple’s FAQ. I really don’t understand why people keep throwing around time frames like “a year or two”. Multicam might take a year. These workflow features won’t.
—
Digital Workflow/Colorist, Nice Dissolve.You should follow me on Twitter here. Or read our blog.