HOME | DD

CatSquared In reply to VictoryCrow [2008-03-07 22:12:04 +0000 UTC]

yeah, no problem. and thanks

👍: 0 ⏩: 0

dummyddd In reply to pak-9 [2005-06-18 15:13:00 +0000 UTC]

You get a rock solid 64 fps? Is it the highest AVS ever goes with you? Does AVS tend to fix its framerate at 2^n values?

If so I think I've had a similar problem, and it's not related with the presets, but instead with your hardware.
Try running windows messenger (not msn messenger) or try playing a movie with winamp while running AVS, and check if it alters the framerate (especially for simple presets).

I don't know exactly what problem windows messenger fixes, but apparantly some systems needs to constantly play movies in order to have normal framerates.

By the way what graphics card do you have?

👍: 0 ⏩: 1

pak-9 In reply to dummyddd [2005-06-18 18:18:21 +0000 UTC]

Ummm... your sort of all over the place there dummyddd, I think you are referring to the fact that sometimes AVS locks the framerate at 64 and sometimes it reports it as much higher. I have no idea what causes this but its nothing to be concerned about, since 64 fps or above is too fast for your eyes to notice the difference in refresh (plus the refresh rate of your monitor is probably only 60-80hz). If you are worried about frame chopping turn on 'wait for retrace', however this WILL slow down your framerate, because it will wait for monitor refreshes before frame swapping.

I have no idea why playing movie clips would make a difference, if anything it would just slow AVS down because its sucking up resources and a bit of CPU time.

The make of my graphics card is irrelevant because AVS isn't hardware accelerated.

Sorry if I've just told you stuff you already know, but I cant quite put my finger on what your problem is.

👍: 0 ⏩: 2

pak-9 In reply to pak-9 [2005-06-23 02:17:52 +0000 UTC]

I do know what you mean, however it has been my (fairly extensive) experience that the frame rate NOT being capped at 64 is the exception rather than the rule. I too have noticed that when it isnt capped in this fashion the frame rates tend to be generally better.

I would be cautious with your assertions though, just because AVS reports your FPS to be something does not necessarily mean that it is accurate; on the other hand the FPS AVS states usually seems pretty accurate.

To be honest it doesnt particularily concern me, my PC is pretty porky so the difference in speed isnt noticable. If your particularily keen on following this bug up just grab the AVS source and delve into the code [link]

👍: 0 ⏩: 0

dummyddd In reply to pak-9 [2005-06-22 20:16:18 +0000 UTC]

Ehm, I gues my reply was pretyy bad formulated, so I'll take another go at it.
AVS is not meant to cap the frame rate at 64 fps.
If you didn't get an fps boost by disableing that effect you mentioned in your reply, it must be because of your system being odd, and not that cat^2's system is odd.

The reason as to why I made the reply in the first place, is because I've had the same problem as you (with having the framerate being capped). It may not be a serious problem when the framerate is just capped at 64, but if you try out some other more complex presets you should notice that the framerate is usually fixed to n^2 values (but because of AVS's way of detecting framerate, you'll just see the framerate going up and down between 32 and 64).
That can be a problem as AVS will generally have a worsened performance, and the tendancy to fix the framerate gives you a worse idea of how your preset will appear on other systems.

If you try and run a movie clip with winamp, or start up windows messenger while running AVS, you should notice that the framerate will no longer be fixed. I do not know why running a movie-clip affects the framerate of AVS so drasticly, but the fact that the framerate is kind-of fixed, may be because of your graphics card.
The graphical calculations in AVS aren't hardware accelerated (by the graphics card anyway), but the refreshing of the AVS window is, and the problem lies within updateing the AVS window.

👍: 0 ⏩: 0