tag:blogger.com,1999:blog-6843566830671277353.post681742591499022547..comments2023-12-11T22:56:18.291-08:00Comments on Codedependent: Time's UpChet Haasehttp://www.blogger.com/profile/03250991041464602854noreply@blogger.comBlogger5125tag:blogger.com,1999:blog-6843566830671277353.post-87919562913018830432008-06-07T09:33:00.000-07:002008-06-07T09:33:00.000-07:00@matt> It seems that FF3 do not limit the framerat...@matt> It seems that FF3 do not limit the framerate as FF2 does on windows. I've done some benchmarks and give the results here : http://www.tekool.net/blog/2008/05/27/overriding-flash-player-60fps-limit-in-firefox-up-to-950fps-as-silverlight-2-in-bubblemark/Unknownhttps://www.blogger.com/profile/03933605127884762731noreply@blogger.comtag:blogger.com,1999:blog-6843566830671277353.post-81724457629204735402008-06-03T10:37:00.000-07:002008-06-03T10:37:00.000-07:00i'm viewed this in firefox 3 rc1 on XP and saw num...i'm viewed this in firefox 3 rc1 on XP and saw numbers like you saw in the stand alone player. maybe it's more of an IE thing?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6843566830671277353.post-58669745995000614592008-04-15T07:22:00.000-07:002008-04-15T07:22:00.000-07:00Cédric,Thanks for the information and links. Note,...Cédric,<BR/><BR/>Thanks for the information and links. Note, however, that I was only talking about the average frame rate. I haven't gotten around to measuring the variability of the inter-frame rate. That's a fairly separate (albeit related and important) timing issue.Chet Haasehttps://www.blogger.com/profile/03250991041464602854noreply@blogger.comtag:blogger.com,1999:blog-6843566830671277353.post-12711040339701474902008-04-14T23:50:00.000-07:002008-04-14T23:50:00.000-07:00Hi, Thanks for sharing that. Just a word to say th...Hi, <BR/><BR/>Thanks for sharing that. Just a word to say that the problem of the Flash Player's framerate lost in a browser is rather old now, I remember several post from Andre Michelle (http://blog.andre-michelle.com/2005/tight-fps-solution/ for example, which will have three years old soon) about that point, and see many approach to keep the framerate stable (using transparent flash, infinite loop, etc...). <BR/><BR/>Instead trying to keep the player framerate at a constant speed, which is IMHO a bad idea when we see how ustable is the flash player behavior (the same animation running on windows in a browser at 40fps, run with difficulty at 20fps in the standalone player on my linux).<BR/><BR/>That why I wrote Kairos one year ago, a small framework which avoid the use of any hack to make the player framerate stable by the use of discrete computation for all animated elements (movie clips, tweens, etc...) based on the recorded time between each "frames". If I can suggest you to take a look at it :<BR/><A HREF="http://code.google.com/p/kairos3/" REL="nofollow">http://code.google.com/p/kairos3/</A>Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6843566830671277353.post-671076151512946502008-04-14T15:46:00.000-07:002008-04-14T15:46:00.000-07:00Yup, this is true, but it's a hard meme to raise a...Yup, this is true, but it's a hard meme to raise above the noise. Mac Projectors usually do much better than Mac browsers on identical content. But "slow on Mac" has gotten more traction than "test on the desktop".<BR/><BR/>Differences in hosting resources shouldn't affect a benchmark much, but benchmarks vary so much, that it might.... ;-)<BR/><BR/>Another tough meme has been that one you raise about optimal screen rate... even though Disney animated 12-up, and film is at 24fps, the ability to request high framerates (and increase processor load) has been the common fixation.<BR/><BR/>Thanks for putting hard evidence behind it all, though.... ;-)<BR/><BR/>jd/adobeAnonymousnoreply@blogger.com