Simple test. Get out your second hand. Right now, push your F5 (volume up) button. Now wait. How many seconds before you get the "bwap" sound and the little speaker icon shows up on the screen? And post your machine.
iBook G4 1 ghz OS 10.4. It took 4 seconds.
Comments
It would depend on how many/what programs are running in the background...
it would depend on a lot of stuff. i'm not researching a thesis here.
Yeah, it is weird. Once it starts changing then it's snappy (TM) but it seems to have to "start up." It's kind of like Dashboard. ? The menu bar doesn't do it I believe. By the way, Progmac, I'll be posting my time when I get home tonight.
That's because it does have to start up. All of this is handled by the BezelUIServer process. It is launched on-demand. To see for yourself, just start Activity Monitor, enter "Bezel" into the search field, then quickly change your volume or display brightness repeatedly for few seconds.
The images it uses reside in /System/Library/LoginPlugins/BezelServices.loginPlugin/Contents/Resources/BezelUI. If you go up two levels in the directory hierarchy, you will also find the sound used when changing the volume.
EDIT: Just put it to sleep and woke up and tried it and it was maybe a second....
It's my understanding that as a powersaving thing, Apple have made it so that the audio kernel extensions are unloaded after a period of no use. Perhaps the 4 second lag on the iBook has to do with this. Keep audio playing when doing this test.
No, audio playing or not has nothin to do with this, the problem is as [alloc init] said, in caching. Those audio components aren't kept in permanent memory, but instead they are swapped out of memory after a while when they are not needed. When needed they need to get swapped back. Loading videos or other memory intensive tasks lengthen the load time even more. For people with lots of memory it would be nice if apple enabled keeping these components in permanent memory. Same goes with dashboard widgets.
For people with lots of memory it would be nice if apple enabled keeping these components in permanent memory. Same goes with dashboard widgets.
Yeah, I know. It's absolute hell to wait 2.5 seconds for the current temperature to pop up.
Yeah, I know. It's absolute hell to wait 2.5 seconds for the current temperature to pop up.
It's a lot longer than 2.5 seconds for dashboard to pop up on my machine, especially with a ton of widgets. More like thirty to a minute. Defeats the whole point of Dashboard.
No, audio playing or not has nothin to do with this, the problem is as [alloc init] said, in caching. Those audio components aren't kept in permanent memory, but instead they are swapped out of memory after a while when they are not needed. When needed they need to get swapped back. Loading videos or other memory intensive tasks lengthen the load time even more. For people with lots of memory it would be nice if apple enabled keeping these components in permanent memory. Same goes with dashboard widgets.
There is something with audio playing, too at least on my PB although it is probably unrelated. When something is played, even a system sound, there is a slight pop as if the audio is turning on. This happens even if the volume is all the way down.
There is something with audio playing, too at least on my PB although it is probably unrelated. When something is played, even a system sound, there is a slight pop as if the audio is turning on. This happens even if the volume is all the way down.
funny, i just noticed that same thing on my ibook. kind of a distant low-frequency pop and then the real pop comes up with the screen graphic.
funny, i just noticed that same thing on my ibook. kind of a distant low-frequency pop and then the real pop comes up with the screen graphic.
Correction: I meant, "even if the volume is muted." Play any sound and you'll hear it. You also hear it at startup which is something I've noticed on Dell's too. However, it seems once it's on on a Dell it stays on, but Apple powers down the sound circuit or something. Maybe it's just on laptops?
It's a lot longer than 2.5 seconds for dashboard to pop up on my machine, especially with a ton of widgets. More like thirty to a minute. Defeats the whole point of Dashboard.
Then methinks you have too many widgets.
Then methinks you have too many widgets.
psshhh! What are you, some kind of widget nazi?