Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
It's funny. 64 bit flash was introduced mainly because IE 9 Beta was introduced yesterday. (Riding the attention IE 9 has been getting.) On computer sites they're talking about performance, benefits, etc. Practical stuff. But in the Apple universe it's all about Apple. The sole reason for 64 bit flash is because of Apple, and Adobe kicking and screaming not to die. 2 different realities, somewhat unaware of each other.
 
Chrome!

Now I just have to wait for Google to implement this in chrome! As far as I know chrome comes with flash built in or something. Anyway, hopefully it won't take that long.
 
Can someone with a reasonably high ish end mac please do a test for me.

You need to have a 1920x1080 screen for this.

Can you go to this page and run the Baby Baboon animation and click the top left option to make it run full screen on your wide-screen monitor and report as to how the CPU usage is when running it?

Due to the different scenes, it tends to fluctuate quite a bit.

On my machine the lowest spike is about 10% to 14% at one point, and up to 45% to 50% for a second at another point.

Normally floating in the mid 20's / mid 30's range most of the time.

I'd be interested to see how this now runs on a nice modern mac.

Thanks :)

The link: http://www.weebls-stuff.com/songs/Baby+Baboon/
 
Video is complicated. Audio is fairly complicated too. But neither is so complicated that it can't be done in HTML5 on big websites (or even small websites with a little bit of extra effort). HTML5 provides a flexible solution to navigate this mess, but as you say, we've got some time to wait before older browsers are sufficiently phased out. Currently the forward-thinking approach involves newer standards for video with Flash fallbacks for older devices. It is workable.

In any case, all the browser makers seem to be onboard with HTML5 (and associated standards and capabilities—all those things people are usually referring to when they say 'HTML5'). Even Microsoft seems to be working a little harder each release to catch up with Internet Explorer.
You're forgetting the simple fact that HTML 5 is not even an official standard yet.
It's a draft standard subject to further changes.
 
You're forgetting the simple fact that HTML 5 is not even an official standard yet.
It's a draft standard subject to further changes.

Are you suggesting that Adobe Flash is an official standard? Or even a draft standard? Or that it is not subject to change?
 
the latest version of the firefox 4 beta supports windows 2000. it's ridiculous to support such an old OS. this is the reason why firefox is so slow

I'm pretty sure Windows 2000 support does not slow Firefox down at all, especially on Mac. It slows testing for regressions down, but platform specific code is not compiled for other platforms. It's called conditional code.

A question for everyone: Is the an ad-blocker for Safari that compares well to ABP on Firefox? That's the main reason (along with Firebug) that Firefox is still my main browser. I don't necessarily like that I'm blocking ads (from a philosophical perspective) but Jeesh, the internet is a tacky and garish place when ads are enabled. I'd rather pay for content.
 
No, I think it's those Mums who spam Facebook with endless Farmville crap. They know just how much more gold their friends could harvest, if only they had 64-bits on their Flash. That's like, nearly twice as many as 32.

Nope...those Farmville Mums now use iPhones and iPads since Zynga has relased iOS versions. Hey, they get a push notification, when they can harvest. :cool:

At least that was, what the last WWDC keynote was about :rolleyes:
 
Can someone with a reasonably high ish end mac please do a test for me.

You need to have a 1920x1080 screen for this.

Can you go to this page and run the Baby Baboon animation and click the top left option to make it run full screen on your wide-screen monitor and report as to how the CPU usage is when running it?

Due to the different scenes, it tends to fluctuate quite a bit.

On my machine the lowest spike is about 10% to 14% at one point, and up to 45% to 50% for a second at another point.

Normally floating in the mid 20's / mid 30's range most of the time.

I'd be interested to see how this now runs on a nice modern mac.

Thanks :)

The link: http://www.weebls-stuff.com/songs/Baby+Baboon/

I tried it on that resolution, since my laptop is connected to a high resolution monitor, but I did it on Windows. Depending on what part of the animation was playing, it played anywhere from 17%, to 40%. But for the most part it was playing with 20 - 25% CPU usage.
 
I tried it on that resolution, since my laptop is connected to a high resolution monitor, but I did it on Windows. Depending on what part of the animation was playing, it played anywhere from 17%, to 40%. But for the most part it was playing with 20 - 25% CPU usage.

Thanks. So you are getting pretty much the same numbers as me. :)

Hope to get some people with 24" iMacs put up their numbers.

Also (if any 27" iMac users are listening) I'd love to know the CPU usage you get from full screen given that you have even more pixels to push around.

Hope some others have a spare couple of minutes to try this little test :)
 
the latest version of the firefox 4 beta supports windows 2000. it's ridiculous to support such an old OS. this is the reason why firefox is so slow

Wow, you're basing your opinion on the fact that it supports Windows 2000? I wonder what your opinions about everything else in life. Forget any speed tests, I'm going to base my opinion on what older OS is supports.

So far firefox beta 4 for Windows (Not sure if there's a mac version) is the best browser I've ever used. And I was down on firefox, actually switched to Chrome the day before I decided to try the beta. The only reason why I downloaded the Beta was because I wasn't going to use FireFox as my main browser anymore. I base my opinion on actually trying it.
 
Can someone with a reasonably high ish end mac please do a test for me.

You need to have a 1920x1080 screen for this.

Can you go to this page and run the Baby Baboon animation and click the top left option to make it run full screen on your wide-screen monitor and report as to how the CPU usage is when running it?

Due to the different scenes, it tends to fluctuate quite a bit.

On my machine the lowest spike is about 10% to 14% at one point, and up to 45% to 50% for a second at another point.

Normally floating in the mid 20's / mid 30's range most of the time.

I'd be interested to see how this now runs on a nice modern mac.

Thanks :)

The link: http://www.weebls-stuff.com/songs/Baby+Baboon/

My Core i7 @ 2560x1440 fullscreen hit 197% than quickly dropped to 41% and went between 35% and 45%.
 
Thanks. So you are getting pretty much the same numbers as me. :)

Hope to get some people with 24" iMacs put up their numbers.

Also (if any 27" iMac users are listening) I'd love to know the CPU usage you get from full screen given that you have even more pixels to push around.

Hope some others have a spare couple of minutes to try this little test :)
Yup, pretty much the same. What are the specs of your machine?

I should mention that I was using dual screen, to play the animation on my 24 inch monitor, and the screen on the laptop to check out the CPU usage. I don't think that made much of a difference though.
 
I don't know why people are so negative about Flash, I haven't had any problems with it so far... I have seen more buggy HTML sites and crash Java applets than Flash applets. So down with HTML! HTML sucks.
Yeah. The web would be better without HTML. :rolleyes:

You're forgetting the simple fact that HTML 5 is not even an official standard yet.
It's a draft standard subject to further changes.
No, I'm not. HTML5 (no space) is, as you say, not a complete standard. It is certainly the next standard, though. XHTML 2 is dead in the water—its corpse abandoned and left for the fishes. Elements of HTML5 as so thoroughly established at this point that they can be readily used (and are being used). Others that are only appropriate for certain demographics are also so completely established that they can be used as well. It is the nature of standards such as this that years and years and years will pass before it is 100% complete and final, but it is in use now, and those fundamental tools which are already being used aren't going to be broken in such a way that what works now will be rendered broken.
 
A question for everyone: Is the an ad-blocker for Safari that compares well to ABP on Firefox? That's the main reason (along with Firebug) that Firefox is still my main browser. I don't necessarily like that I'm blocking ads (from a philosophical perspective) but Jeesh, the internet is a tacky and garish place when ads are enabled. I'd rather pay for content.

I used to use GlimmerBlocker but it messes up click-through links from cashback websites, so I'm currently using Safari Adblock from http://safariadblock.com/ which seems to work perfectly. It uses the same lists as Firefox's AdblockPlus.
 
I found the plugin now will exit itself after flash embed web page is close on safari. Not idle there and stealing CPU power any more.
 
Video is complicated. Audio is fairly complicated too. But neither is so complicated that it can't be done in HTML5 on big websites (or even small websites with a little bit of extra effort). HTML5 provides a flexible solution to navigate this mess, but as you say, we've got some time to wait before older browsers are sufficiently phased out. Currently the forward-thinking approach involves newer standards for video with Flash fallbacks for older devices. It is workable.

Flash and HTML5 are two very different things for content providers. Don't take it from me, take it from Youtube.

Flash and the HTML5 <video> tag

There's been a lot of discussion lately about whether or not the HTML5 <video> tag is going to replace Flash Player for video distribution on the web. We’ve been excited about the HTML5 effort and <video> tag for quite a while now, and most YouTube videos can now be played via our HTML5 player. This work has shown us that, while the <video> tag is a big step forward for open standards, the Adobe Flash Platform will continue to play a critical role in video distribution.


It's important to understand what a site like YouTube needs from the browser in order to provide a good experience for viewers as well as content creators. We need to do more than just point the browser at a video file like the image tag does - there’s a lot more to it than just retrieving and displaying a video. The <video> tag certainly addresses the basic requirements and is making good progress on meeting others, but the <video> tag does not currently meet all the needs of a site like YouTube:


Standard Video Format
First and foremost, we need all browsers to support a standard video format. Users upload 24 hours of video every minute to YouTube, so it's important to minimize the number of video formats we support. Especially when you consider that for each format, we also provide a variety of sizes (360p, 480p, 720p, 1080p). We have been encoding YouTube videos with the H.264 codec since early 2007, which we use for both Flash Player and mobile devices like the iPhone and Android phones. This let us quickly and easily launch HTML5 playback for most videos on browsers that support H.264, such as Chrome and Safari.


Concerns about patents and licensing have prevented some browsers from supporting H.264; this in turn has prevented the HTML5 spec from requiring support for a standard format. We believe the web needs an open video format option. One that not only helps address the licensing concerns, but is also optimized for the unique attributes of serving video on the web. To that end, we’re excited about the new WebM project. Google is open sourcing and contributing the VP8 codec to the WebM effort. Google, Mozilla, and Opera have all committed to support WebM, and we have already started making YouTube videos available in the WebM format. Adobe has also committed to support VP8, the video codec for WebM, in an upcoming Flash Player release.


Robust video streaming
Closely related to the need for a standard format is the need for an effective and reliable means of delivering the video to the browser. Simply pointing the browser at a URL is not good enough, as that doesn't allow users to easily get to the part of the video they want. As we’ve been expanding into serving full-length movies and live events, it also becomes important to have fine control over buffering and dynamic quality control. Flash Player addresses these needs by letting applications manage the downloading and playback of video via Actionscript in conjunction with either HTTP or the RTMP video streaming protocol. The HTML5 standard itself does not address video streaming protocols, but a number of vendors and organizations are working to improve the experience of delivering video over HTTP. We are beginning to contribute to these efforts and hope to see a single standard emerge.


Content Protection
YouTube doesn't own the videos that you watch - they're owned by their respective creators, who control how those videos are distributed through YouTube. For YouTube Rentals, video owners require us to use secure streaming technology, such as the Flash Platform's RTMPE protocol, to ensure their videos are not redistributed. Without content protection, we would not be able to offer videos like this.


Encapsulation + Embedding
Flash Player's ability to combine application code and resources into a secure, efficient package has been instrumental in allowing YouTube videos to be embedded in other web sites. Web site owners need to ensure that embedded content is not able to access private user information on the containing page, and we need to ensure that our video player logic travels with the video (for features like captions, annotations, and advertising). While HTML5 adds sandboxing and message-passing functionality, Flash is the only mechanism most web sites allow for embedded content from other sites.


Fullscreen Video
HD video begs to be watched in full screen, but that has not historically been possible with pure HTML. While most browsers have a fullscreen mode, they do not allow javascript to initiate it, nor do they allow a small part of the page (such as a video player) to fill the screen. Flash Player provides robust, secure controls for enabling hardware-accelerated fullscreen displays. While WebKit has recently taken some steps forward on fullscreen support, it's not yet sufficient for video usage (particularly the ability to continue displaying content on top of the video).


Camera and Microphone access
Video is not just a one-way medium. Every day, thousands of users record videos directly to YouTube from within their browser using webcams, which would not be possible without Flash technology. Camera access is also needed for features like video chat and live broadcasting - extremely important on mobile phones which practically all have a built-in camera. Flash Player has provided rich camera and microphone access for several years now, while HTML5 is just getting started.




We’re very happy to see such active and enthusiastic discussion about evolving web standards - YouTube is dependent on browser enhancement in order for us to improve the video experience for our users. While HTML5’s video support enables us to bring most of the content and features of YouTube to computers and other devices that don’t support Flash Player, it does not yet meet all of our needs. Today, Adobe Flash provides the best platform for YouTube’s video distribution requirements, which is why our primary video player is built with it.

AFT. This is why HTML5 is a much better solution. Why should the world have to wait on Adobe for all things multimedia on the WWW? And they haven't got the Reader plugin 64 bit for Mac OS X yet either.

lol.
If anything, Steves open letter on flash kicked Adobe in the butt.

They can deny how flash sucks on the mac all they want, and then release major updates/upgrades to flahs, but it will still suck
lolx2
 
Nice to see Flash updated, partly because it'll make my Macs run more efficiently and partly because it really ticks off all of the Flash-hating-Apple-Fanboys who think that iOS devices are actually real computers.
 
I've using this all yesterday and today. The last flash version crashed my browser everytime a flash element on a page loaded.

This one makes everything good again.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.