avs + google chrome
ok it's a weird title but i couldn't come up with better and it's not really a trouble just interesting. so when i leave google chrome running while avsing on xp the max framerate increases from 64 fps to 512 fps or something similar and the framerate limiter works normally (so if it set to 30 fps it'll limit to 30 fps not 21) but as i close chrome everything drops back to normal behavior. what could be the reason of it? or it's yet another magic what never will be uncovered? (it's just for xp, on vista or win7 avs could operate on "insanely high" framerates)
i had this happening with photoshop(!) and other people with other programs.
i suspect some really deep magic at work here, like the memory/cpu flow of one program affecting and facilitating AVS's flow. this is just an uneducated guess though.
but it's fun 🙂 although it only seemed to lift the limit for the max fps and it wouldn't speed up very slow presets.
could it be this behaviour shows whenever you use a software that can use multiple cores/cpus? does the framerate really increase or just the counter?
of course presets won't be faster and as i could check just the fps counter gets crazy (so still max 64 fps in reality) but the framerate limiter still operates better while chrome (and as gc said or many other programs) is/are running. but that's an ape and long time ago a black hole ate Goebish😁.
AVS uses the CPU to do all it's work, as opposed to Milkdrop which off loads the rendering to the GPU.
So yes, AVS eats your CPU for breakfast (Or at least one core of it) and then wants more!
If you're planning on using any CPU expensive applications then it's best to not have AVS running at the same time, unless you enjoy waiting.