Andrew Kimery
Forum Replies Created
-
Apple was still selling monitors?
-
[Darren Roark] “It’s a lot better than when I finally got around to getting a B&W G3 tower and then the G4 came out a month later. “
Yeah, my most irrational fear is probably of buying electronics and then having an better version come out right after my return window ends. lol
-
[Darren Roark] “That pesky intel went to a longer wait time between CPU refreshes. It’s going to be even slower in the next few years.”
Intel hasn’t released a new CPU since 2013, AMD hasn’t released a new GPU since 2012… Man, Apple has the toughest luck finding reliable partners. 😉
-
[Scott Witthaus] “But I do feel it is fine to ask questions about the history of the software and why things were released the way they were. Seems like a fair question to me…of course IMHO….
“I think it’s a fine question too, and my guess is that Apple was feeling the heat from users and didn’t think they could stay radio silent on FCP for another year (or perhaps longer depending on when you think X hit the ‘good enough to launch’ point). The takeover of the NAB Supermeet at the last minute always struck me as a desperation move to try and reassure users that a new FCP was almost here and that was only a few months before the launch. If they felt enough pressure to do that I can’t imagine them keeping it secret for another year as they fleshed out development.
I certainly think if the version of X from 2013 launched in 2011 it would have gone much better, but Apple couldn’t afford to wait until 2013 to get X out the door. Releasing it as a beta might have been another way to temper expectations, but that doesn’t seem like a very Apple thing to do.
-
[Bill Davis] “They kept those blinders firmly on for YEARS and wasted huge amounts of time in negative land. “
Or they just moved on with their life and career and that’s why their lasting impression with X was their first impression from 2011. Not everyone spends an inordinate amount of time following the iterations of various NLEs and subsequently discuss said iterations extensively on the internet (says the person posting at 11:59pm on a Tuesday).
Much to my chagrin, as someone that enjoys talking and learning about the nuts & bolts side of things, I’ve met so many talented and successful editors that are surprisingly technically illiterate that it makes me question why I bother to learn anything beyond the bare minimum when it comes to the tech side of things (it’s not like Fincher is going to pick me over Kirk Baxter just because I started using PPro before he did). Me and my stupid desire for knowledge for the sake of having knowledge….
[Bill Davis] “A big fat head start. “
Does the head start come with cookies or a t-shirt or some sort of bonus I’m not aware of ’cause to best of my knowledge I’ve never been anywhere close to v1.0 of any software or hardware I use yet somehow I’m still gainfully employed.
Oh, wait, no I got one. I got in with Apple Color at version 1. Yes, I know that’s kinda a cheat since Final Touch existed for years before Apple bought it technically it was a v1.0 product from Apple. That… that didn’t do much for me though since as soon as Apple killed Color everyone moved over to Resolve in a heartbeat. I also got in kinda early with Final Cut Server (again I know not a ‘real’ v.1) but that proved even less useful than Color. Man, I’m apparently really bad when it comes to getting in the ground floor of things…
[Bill Davis] “X was plenty good enough on day one to change the trajectory of my whole professional practice.
For the better. As I’ve long argued, if I could see that from the hinterlands of Arizona, anyone, anywhere also could. “
I doubt many people besides you were equipped to judge whether or not X at launch was good enough to change the trajectory of your whole professional practice. X was no where near good enough on day one to change the trajectory of my whole professional practice, but as you say YMMV.
-
[Scott Witthaus] “Once a new version is released, any development of older versions should cease. So, you can introduce X and still sell 7 for a while, but make it clear there will be no further investment in the development of 7 after X is released. And in reality, that’s what happened. “
Where did I say anything about continued development of 7? There’s no reason for that (which is why I never suggested or implied that course of action). Apple didn’t continue developing iMovie HD when they introduced ’08. Avid didn’t keep developing Avid 6 or 7 even though they came ‘bundled’ when you bought a perpetual license for MC 8. Adobe doesn’t continue developing the last 4 (5?) versions of their apps even though they are all available to download if you are CC subscriber.
I’ve always said it was a mistake for Apple to immediately pull 7 when they launched X. Keeping it available for sale until all copies were gone would have been the best option. Making it only available with purchase of X would’ve been the next best option. Pulling it like they did was the worst option.
[Scott Witthaus] “Do tell. I just upgraded my CC and it overwrote the older software versions.”
Weird, I have like 6 different versions of CS/CC installed on my laptop (mainly because there’s no penalty for keeping them installed).
[Scott Witthaus] “This is the problem that Apple had; X was not ready for release when it was released. Had it been, this thread might be irrelevant.”
So when is it ‘done enough’? 2012? 2013? 2014? How many years to you expect FCP 7 users to wait around as Apple develops the next version in complete secrecy? I can only imagine situation if both FCP and the MP laid dormant for years until 2013 rolled around.
-
[Scott Witthaus] “You are missing the point. I am not saying stop selling 7, but why would you give a version of 7 to everyone who buys X?”
Because it’s feature incomplete but you want to nudge people towards it. Apple did the same thing with iMovie ’08 and iMovie HD. HD was mature and feature rich, ’08 was completely redesigned and feature bare. People got pissed so Apple gave away HD to everyone who bought ’08. I think a year or two later they released another version of iMovie that hard largely replaced the missing features in ’08 so they discontinued the offer.
Someone at Apple was afraid that continuing to sell FCP 7 would hinder the adaption rate of X so they chose to stop selling it. Bundling an 7 license w/X would’ve been a better compromise (and one that had worked for Apple in the past).
[Scott Witthaus] “I mean, would Adobe do that now? Avid? “here is our new software, and if you buy it, you get a free version of the old software”. “
Adobe basically does that w/it’s subscription model and when I bought my Avid 8.x perpetual license it also gave me access to Avid 7 and Avid 6.
[Scott Witthaus] “I have all the respect in the world for Randy. I make my salary on his work. But the idea above is simply not good business. The key is to have a product that is ready to replace the old product before release. X was not.”
Ideally yes, but how much longer would that have taken before X matched features with 7. 12 months? 24 months? The FCP Legend natives were already restless thanks to the lame 2009 update so expecting users to wait until 2012 or 2013 would’ve been the greater of two evils, IMO. Releasing X in 2011 was the right call, Apple just dropped the ball on the launch (starting with the last minute take over of the Supermeet).
-
So I saw someone on Twitter say that Adobe said at NAB that this is just a normal point release and the CC 2016 release is coming later this year. Anyone else hear this? It would explain the numbering if true.
-
For the rock ‘n roll fans that are into beating dead horses…
https://www.youtube.com/watch?v=u8X76NRiQLQ
Some contents or functionalities here are not available due to your cookie preferences!This happens because the functionality/content marked as “Google Youtube” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.
-
Yeah, the naming/numbering convention is needlessly confusing. Change the entire suite to CC 2016 and then just do point updates to the invidual apps. For example, in CC 2015 PPro is v.9.2.0 so just make the new one CC 2016 and PPro v9.3.0). That way you can just ask, “Hey, do you have CC 2016 installed”? and it’s very clear what you are talking about.
I can’t see a lot of conversations going like this:
Hey, do you have PPro CC 2015.3 installed?
Yeah, I have CC 2015 installed.
No, not CC 2015. CC 2015.3. The new one.
Oh, you mean CC 2016?
No. CC 2015.3. It came out in 2016, but unlike all the other CC versions the year of release doesn’t match the name of the suite.And the fact that not all the apps have the same number (ex. PS is CC 2015.5, AE is CC 2015.3 and DreamWeaver is just CC 2015) is just nuts. Who came up with this and who are the people that agreed with that person?
Also, having ‘delete other apps’ as the default action is still wrong. Anything that automatically removes stuff from users computers should be opt-in, not opt-out.
[John Davidson] “but don’t torch my workflow with a haphazard update. It’s reckless.”
Weird, Adobe didn’t torch my workflow… Oh, that’s right I didn’t upgrade my work machine on day 1 of a new build while in the middle of a project. 😉
Not pointed at you specifically John, but at what point did upgrading in the middle of a project start becoming the norm? I see it more and more these days but 10yrs ago that was certainly not SOP.