core image compatibility - Page 2

**fryke** · #9 November 6th, 2004, 01:25 PM

I'd say so, too. Could be that the build you had was specifically flawed in the graphics department for the specific card(s) you tried it on, could be that the development on those drivers only took off afterwards... But I quite definitely think that Apple would rather end compatibility for 'those' machines completely than to only half-heartedly support them in the future. After their experience with all those G3s etc. that gave them quite some headaches (lawsuits) in the past... So I guess: It'll be fine by final release at the latest...

Krevinek · #10 November 6th, 2004, 02:08 PM

Well, as I have been saying (see my first post in this thread), is that I fully expect Apple to restore the speed of Video to 10.3 levels by the time of the release. I was also explaining the reasoning behind the glitches is because of the CoreVideo/CoreImage rewrite. It isn't like tacking on something on top of Quartz, it is rewriting parts of Quartz itself. That takes time.

Another reason why they cannot drop support is that to drop support for machines without CoreImage/CoreVideo supported cards is shooting themselves in the foot worse than the 'half-hearted' support issue. More likely, this is all the lessons learned from Final Cut and the like, and adding in extra accelerations when available. Especially considering the only problem with the Lombard/Wallstreet was the lack of 3D support in OS X. Sure the card was underpowered, but I know it would have been possible for OpenGL support.