Andrew Richards
Forum Replies Created
-
[Gav Bott] “This is where the fear kicks in for me – annual OS changes that effect thrid party aps, but that they can’t realistically charge for – as it’s only “making it actually work”.
This is a weakness in the model of building the foundation ap, creating the space for the 3rd parties to make it sing – how do they survive and keep your vital aps up to date unless they can get an income stream in?”
I think the disruptiveness of major OS revs is being overstated. How often do you have your apps break when you update OS X? Unless they are older apps that depend on deprecated APIs, they almost always continue to work. Can it happen? Sure, but it isn’t like we have transitions to 64-bit or a new CPU architecture ahead of us now. That is all over with.
Best,
Andy -
[Michael Garber] “So how long until we see FCPX using Airplay to an AppleTV instead of using an AJA, BM or Matrox alternative?”
I think you’ll see that as a monitoring option with the first FCPX update after Mountain Lion comes out. It won’t be a replacement for AJA, BMD, or Matrox I/O, but it would be pretty slick for client screenings. Carry a little AppleTV along with your MacBook and have a wireless HD screening system. I wouldn’t be surprised to see an updated AppleTV this year with an A5 chip and 1080p support either.
Best,
Andy -
It might be a bit more work for third parties to stay current, but the alternative is what happened with Windows XP where hardly anything changed for almost a decade. My observation is Apple has turned a corner with their Core frameworks where they have shed much of their legacy tech and can move forward additively rather than desruptively. So much of the guts in Lion is brand new or still very young code compared to stuff like QuickTime which dates back decades. That is not to say there won’t be version dependency issues, but the bad old days of brittle dependencies on stuff like QuickTime are behind us. They still have legacy left to shake off (HFS+ is as old as the Mac itself!), andI’m just glad to see a commitment to the desktop that matches the effort they are putting into iOS.
Best,
Andy -
[Jeremy Garchow] “How about a user that might like the direction it’s going in? :)”
You’ll have to wait like everyone else. Including the users of almost every other product out there. OSes need to reveal their futures since they are platforms, but apps and machines only hurt their vendors when they are teased to openly. With a few notable exceptions, it is pretty uncommon for the general public to get exposed to product development ahead of when the vendor wants to reveal it. This is true for many more industries than tech. There are a lot of things that can happen when you let the cat out of the bag early, and most of them are bad.
Best,
Andy -
Zeroning is strictly a security measure. It doesn’t improve the function of the drive or change how new data is re-written after a re-format. In the case of SSDs, zeroing is actually going to shorten the life of the drive since NAND storage is by its nature destructive when it writes blocks.
Best,
Andy -
[Jeremy Garchow] “An FCPX development roadmap would be so nice.”
Methinks OSes are the only previews the world gets. For previews of FCPX, become a leading hardware partner or plugin developer. I wouldn’t be shocked to see more feature previews for FCPX like we had for 10.0.1 and 10.0.3, but I would be a lot less surprised not to see them ever again.
There are a lot of hints about what could become features of FCPX in the preview of Mountain Lion. AirPlay mirroring (which many of us saw coming anyway) and iCloud document storage (which seems impractical, but who knows) spring to mind.
Best,
Andy -
-
-
[Steve Connor] “Now let’s have a briefing and a roadmap for FCPX!”
I’m sure Larry Jordan is still on the guest list for previews, if they are giving any.
A significant thing here to me is a new pattern for Apple and its product announcements. No longer will we learn about OS X or FCP or the Mac from blockbuster press events, but from these more grass-roots types of things.
Another significant thing here is the renewed vigor in the OS X development path. It is reasonable to think Apple got caught a little off guard with the rapid success of iOS and it took them a few years to fill out their engineering to support that whole massive column of their business so that it wasn’t cannibalizing OS X. Leopard, Snow Leopard, and Lion all had to wait a bit longer than previous OS X releases to see the light of day, and it was due to engineering focus on iOS. If Apple is committing to an annual rev on OS X, even if they are more evolutionary revs, this is a stake in the ground that augurs well.
Best,
Andy -
[Michael Sanders] “I just wonder if anyone else has been caught out by it and why Apple did it in the first place.”
There needs to be a default location that can be depended on for any given Mac. Legacy FCP defaults all the scratch disks to the user’s Documents folder. Moving that default to the Movies folder is a logical step for an app that works with video.
Best,
AndyEDIT: I agree though there ought to be a setting to point the render files to optimized storage.