Well, here's hoping that the new version of FCP doesn't rely on it. Who knows, it could even be pushed out further. iPhone...:angry03:
http://www.macrumors.com/2007/04/12/...opard-release/
Here's REALLY hoping that REDCINE doesn't rely on it!
|
|
Well, here's hoping that the new version of FCP doesn't rely on it. Who knows, it could even be pushed out further. iPhone...:angry03:
http://www.macrumors.com/2007/04/12/...opard-release/
Here's REALLY hoping that REDCINE doesn't rely on it!
Too bad. Maybe the FCP will be delayed...
Wow. Well, better get it done right slowly rather than done fast poorly.
I don't really mind... I'm still using Panther 10.3...
I predict the FCP 6 box will deflate like a leaky balloon during Sunday's announcement.![]()
Odds are the new Final Cut everyone has been expecting wasn't going to ship until fall anyway, so this probably doesn't make any difference as far as that goes.
The hell with the iphone! Ya I want it, but I'd rather get Leopard. All of a sudden OSX revolves around the iphone. Thats bull! Well, it was coming and it's only gonna get worse for the Pros. Consumer products are becoming apart of Apple now.
Given that Apple's consumer devices are probably going to be a big part of the future of media distribution, we should probably cut them a little slack. Heh. I'd be careful not to read too much into this with respect to Apple's long-term focus. This sounds like it was an unexpected last minute push on the iPhone; no permanent reallocation of resources should be necessary, since long-term Apple can simply hire more people -- if the iPhone is a success they're certainly have the growth to justify it.
Also, as Mike said over on HD for Indies, the iPhone might not have quite as much to do with this delay as Apple indicates; it might just be a convenient excuse. Operating systems are big and complicated; these things happen.
Anyway, the only really big thing in Leopard for the video market was ZFS. I can live without it for a few extra months if I have to. Tiger is already a great platform for video. The FCP announcements next week will have far more direct impact on most of us, and I'm expecting some pretty interesting stuff. (Though, as I note above, probably not shipping immediately.)
Thoughts:
1.) Either FCS 6 wasn't going to ship till then anyway (and little birdies keep jumping up and saying that isn't the case, but I Don't Know), or
2.) FCS 6 isn't going to require it. They wouldn't strangle themselves with that kind of a dependency I'd think - FORCE everyone to upgrade to Leopard? They'd need a MASSIVE increase in productivity/capabilities to justify that leap - like, everything I was hoping for.
Chris - thanks for the shootout, and one tweak to your ZFS comment - perhaps Leopard was where CoreImage and CoreVideo were going to REALLY take off and work?
If it is correct - like I read somewhere - that they're doing some major re-programming of QT, I'd rather wait for that to get right before they release Leopard.
I'm pretty happy with the state of things, both hardware and software (as stated - I could easily use the current octo-mac as it is)
QT is the big PITA at the moment (gammashift et al)
Get quicktime right, and then throw in all the GPU acceleration if that's what's needed.
... hm...
As I type I get the feeling these are connected subjects -;)
My guess about FCP
FCP 6 will be here pretty soon. They want all our upgrade cash again by now.
FC-extreme will have to wait for leopard.
There's nothing stopping them from making FCP resolution-independant (like Shake) or allowing background rendering in Tiger, and if they add these two features (where 2 is the most important for me, as I'll probably offline in DVCPRO-HD or AVC-Intra anyway - if not cineform) I'll pull my card very happily with a big smile on my face, with or without Leopard or Red in the office.
Gunleik
This is mostly just an application support issue, isn't it? I'm not aware of specific technical problems that have prevented adoption in Tiger.
Anyway, in-house Apple developers don't really have to wait for OS releases for this sort of thing. Motion had something along the lines of Core Image internally before Tiger made similar functionality available via an API to third parties. Implementing this sort of thing within Apple apps and then later extracting some of it into APIs for third-parties seems to be a common pattern at Apple.
| « Previous Thread | Next Thread » |