Howdy. Somebody, albeit back in March, made a claim that the ATi drivers for the new 2011 MBPs aren't hardware-accelerated for H.264 video.
Is that true? (Nobody responded to that person, which is a shame as - by now - a development surely would have taken place?)
http://forums.macworld.com/index.php?/topic/135441-review-macbook-pros-early-2011/page__st__14
(that poster is ignorant in that, while Flash is a mess, it's not HTML5 but H.264 that is the relevant CODEC and the video drivers, if they aren't by now, definitely need to be.)
Is that true? (Nobody responded to that person, which is a shame as - by now - a development surely would have taken place?)
http://forums.macworld.com/index.php?/topic/135441-review-macbook-pros-early-2011/page__st__14
And DVD is old and outdated. Even Powerbook G4 1.25Ghz could easily play DVD without any hardware acceleration. MacWorld should replace DVD with a movie encoded at BluRay quality, that means 1080p, codec H.264 at 30Mbps. With hardware acceleration battery life would be good.
I tested some clips and I was shocked that graphics drivers for my new 17" MacBook Pro do not support H.264 hardware offload. HD h.264 video decode is done on CPU even when I play clips in Quicktime X. Notebook gets got quickly while playing 1080p clip, fans are up in a minute.
Has MacWorld already inquired Apple when we can expect HW acceleration on the new line? Neither Intel HD neither ATI drivers seem to support H.264 hw acceleration.
That is a major omission these days when internet is full of videos. And people will then complain that Flash drains battery... and that solution is HTML5. Well not if drivers do not support GPU offload.
It is also a mistake MacWorld should not afford. MacWorld should clearly point out the deficiency. Hardware accelerated video is these days a MUST.
It is ironic that on my girlfriend's MacBook air same clip consumes just few % of CPU. Even greater difference in CPU usage is seen when Flash 10.2 is used.
(that poster is ignorant in that, while Flash is a mess, it's not HTML5 but H.264 that is the relevant CODEC and the video drivers, if they aren't by now, definitely need to be.)