Are you sure about that?
I have the same model as you, and I definitely see an improvement.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Adobe Enables Mac Hardware-Accelerated Decoding in Updated Flash Player 10.1
- Thread starter MacRumors
- Start date
- Sort by reaction score
Are you sure about that?
I have the same model as you, and I definitely see an improvement.
i think the macbook aluminum unibody late 08 should be on the list. the macbook was renamend in 2009 as a macbook pro.
it has a 9400m GPU. the list excludes it anyway.
it has a 9400m GPU. the list excludes it anyway.
That's basically what an OS is. Provide facilities for software to interact with hardware. So to answer your question : Duh. Of course they should.
funny thing is that there are still people in the Mac community who STILL believe that Jobs' hatred of flash has anything to do with the technical limitations and not because flash is the single biggest threat to the App store.
fools...
fools...
This is about time. But now Adobe is also making older hardware 'obsolete.'
Another one that doesn't read before commenting and has no knowledge of the situation.
It's easy people : Adobe used what Apple provided 4 months ago. Adobe didn't make hardware obsolete, they didn't support a limited subset of hardware, they just used what they could.
Ask Apple to support your hardware under the new API. They are the ones who can enable this. BTW, this new API also requires 10.6.3, so folks on Leopard don't get this either.
I've never seen the white cube. I thought I was running the Gala preview version of Adobe's Flash player plug-in. Maybe not. Do we know if the October 2008 aluminium MacBooks with the 9400m chipsets are in, too? (The cake is a lie, by the way.)Yeah this is basically just a more stable version of Gala, nothing more. I kinda miss that white box though, it was like a Companion Cube. (hopefully someone gets that one
i have installed the update and i'm surfing with the newest safari on a brand new i7 mbp, harware acceleration enabled. BUT scrolling is very laggy, as soon as a side contains any flash component, it hurts my eyes. this didnt happen, while on flash 10.0.blabla versions. is this happening just for me or what? it really sucks.
I'm using this new version, but I see no difference on CPU usage playing from the web (FF or Safari), but if I play a .flv file from my hard drive the CPU goes to 90-100% where it use to be 70%ish.
Lovely.
Lovely.
I've been playing tons of flash games since Macromedia released the first Linux plug-in, about oh... 10 years ago. They played satisfactory on my P2-333 mhz.
You people have really weird computers if you can't manage to play flash games.
I agree, but in the end, it's the Mac community that loses because of Job's greed.
They get a more limited internet experience on their machines and they are forced to buy only from the Apple app store.
I've been playing tons of flash games since Macromedia released the first Linux plug-in, about oh... 10 years ago. They played satisfactory on my P2-333 mhz.
You people have really weird computers if you can't manage to play flash games.
Or flash has gotten successfully crapper at every release.
..and the genius of Jobs (if he has any) is that he makes the customers think this is a good thing.!!!!
madness....
I'm a not fool. The majority of flash games are INCREDIBLY limited in comparison to some of the amazing 3D games we've got on the App Store, albeit there are some great flash games, but most of them can't compete with the App Store apps; they would be more of an addition to the apps you get, rather than any competition.
Or it hasn't, and most Flash complaints that are about video decoding have turned to a massive "Flash sucks" complaint with no rhyme or reason.
Or it hasn't, and most Flash complaints that are about video decoding have turned to a massive "Flash sucks" complaint with no rhyme or reason.
No it has, on top of Flash being used for increasingly complex things it was never originally designed for.
Yes!
And be unhappy with legacy Vista problems like inconsistent wireless access, numerous UI inconsistencies and other problems left over from the Vista debacle.
There's another option - install Windows 7 and be happpy - with more money left in your pocket.
And be unhappy with legacy Vista problems like inconsistent wireless access, numerous UI inconsistencies and other problems left over from the Vista debacle.
This API isn't actually allowing the 3rd party developer to talk directly to the hardware and program it to do arbitrary things. The OS is still the only thing allowed to do that.
Rather, this API allows the feeding in of frames of H.264-compressed video as function arguments, and it provides frames of raw, uncompressed video as callback return values.
The application software doesn't need to know anything about the unique low-level characteristics of the underlying video cards, and it doesn't "talk to" the video cards directly.
This is a good start.
Apple has a few "next steps" they should take:
1) Expand the API to transparently work with a wider variety of video cards. If they do this, then Adobe Flash should automatically gain access to these new cards without the need to modify their software at all.
2) Follow Microsoft's lead with the DXVA framework, and expand this API to work with any hardware-accelerated codec which has been installed in the video subsystem and automatically fall back to the OS's built-in software codecs if no hardware path exists for any particular codec.
Basically, they could approach both of these objectives in two ways.
1) They could expand this API.
2) They could fold this API into QTKit as a lower-level point of entry and exit to that system, offering all the benefits of QTKit's codec flexibility without the lock-in of having to go with QuickTime's container all the way from file I/O through to on-screen delivery.