I'm not sure why this is considered a problem. For one thing, your processor can run flat out and it won't overheat. Secondly, try the iTunes default visualiser - it uses even more CPU. Finally, if you're using the visualiser, presumably you are not all that concerned with doing anything else with your computer - you just want to listen to some music and watch some pretty display, so what's the problem? I don't really understand this comment - I mean, why would you expect it NOT to take a fair bit of CPU to render up to 3,000 separate rectangles every few milliseconds?
Existing users, log in. New users, create a free account. Lost password?
Not so excellent... - Graham Cox
I'm not sure why this is considered a problem. For one thing, your processor can run flat out and it won't overheat. Secondly, try the iTunes default visualiser - it uses even more CPU. Finally, if you're using the visualiser, presumably you are not all that concerned with doing anything else with your computer - you just want to listen to some music and watch some pretty display, so what's the problem? I don't really understand this comment - I mean, why would you expect it NOT to take a fair bit of CPU to render up to 3,000 separate rectangles every few milliseconds?Reply to This
Monday, May 10 2004 @ 05:49 AM PDT