Andrew Richards
Forum Replies Created
-
This patent along with Alex Gollner’s observations are almost enough to buoy my hopes of actually seeing a client/server collaborative FCPX feature set.
Almost. It’s hard not to expect to be disappointed anymore.
Alex posted his thoughts on the patent as well.
Best,
Andy -
[Oliver Peters] “Of course, I’m not a lawyer, but this is certainly not a patent for a specific piece of software.”
It wouldn’t be a proper software patent if it weren’t tragically broad and overreaching.
Best,
Andy -
[Michael Gissing] “Patenting collaborative workflows? Sounds like the antithesis of collaboration to patent it. A sure way to make third parties shun you I would have thought. “
Did you read it? It isn’t a patent on collaborative workflows. It is a patent for an NLE-like computer program that can have multiple instances of the UI acting upon a single project at the same time. It has nothing to do with the amorphous concept of interchanging work between multiple tools as is done with XML, OMF, EDL, etc.
[Michael Gissing] “More Apple control freak stuff more likely”
Yes. Software patents as a concept are bogus. Apple aggressively exploits them for better or worse. I say they stifle innovation in their current implementation.
Best,
Andy -
I’d pick G-tech from that list every time.
Best,
Andy -
[Mike Halper] “Restoring 4.0.1 and then upgrading to 4.0.4 via App Store work fine also. I gave that a shot earlier and it worked. So there appears to potentially be an issue with new installs of Compressor.”
My hypothesis (assuming you are on Lion): On Lion, App Store updates come as deltas, not full binary replacements, so there could be a corrupt resource in the full 4.0.4 payload on the App Store that isn’t downloaded when updating from 4.0.1. You should file a feedback.
Best,
Andy -
[Mike Halper] “Then check off Render and the CPU usage skyrockets and the whole computer becomes nearly unusable. I try to click on Options for Render and Compressor hangs. I have to force quit Compressor to do anything on the computer at all.”
Why are you enabling Render in the cluster settings? That is for Qmaster rendering of stuff like Maya or Shake, it isn’t used by FCP to Compressor itself at all.
Best,
Andy -
As others on here have and will tell you, a 15″ MBP with its discrete GPU will perform significantly better for FCPX and other GPU-optimized apps. That said, you specifically asked about the 13″ MBP vs the 13″ Air. I’d go with the Air mostly for its higher-resolution screen (which also reflects a bit less glare). The 13″ MBP has a claustrophobic 1280×800 screen while the Air has the same 1440×900 resolution as the base legacy 15″ MBP. The 256GB SSD in the Air is also $100 less expensive than the optional 265GB SSD in the 13″ MBP.
The only reason I’d go for the MBP is if you plan to predominantly use it with a second display and/or if you are a tinkerer and are interested in swapping out the ODD for a second HDD or SSD. You can also swap in 3rd party RAM up to 16GB in the MBP, while the Air has its RAM soldered onto the motherboard and is maxxed at 8GB.
Get the Air, especially if you are going to be getting an iMac for most of your editing work.
Best,
Andy -
Not on the 13″.
Best,
Andy -
I thought Lion required 64-bit kernel? Is that new in ML?
Best,
Andy -
Not to mention that the drivers for the GTX570 are only available for Lion, which can’t run on that 2006 Mac Pro.
Again I say, shame on Apple for not doing an E5 Mac Pro!
Best,
Andy