FPS adjustment for each preset

Looking at some older presets, you might experience some perfomance problems: Older presets are often too fast for modern CPUs. Then you might adjust the fps within the avs options, but that has to be done for each single preset. So my idea is to create the possibility of saving fps limit information in the presets itself. Thus, your presets will look the same way on different computers.

Let me just jump in before Tugg...

You can do this yourself in code, by using gettime(), so that movements are frame rate independant. It doesnt apply to 'moving particles' and other crappy codeless AVS elements...but you shouldn't be using them anyway 😉

Oh PAK-9, you totally jumped the gun on this one, see if im right (which i am of course) he isn't looking a solution for making presets, instead he wants to view the old presets he already has with a little lesser framerate and also wants to save those fps settings for them.

There has been much discussion about a framerate limiter APE, but so far no one has done that yet.

So sorry, there isn't any other solution to this right now than to stick with the performance slider.

Rectification: The slider doesn't have to be set per preset, it should stay as you have set it.
(Stored on HDD when Winamp closes if I'm right... not sure about that)

here it is

I just compiled such an ape, I think it is really usefull for "oldschool" presets that run too fast with nowadays CPUs.

Get it at: http://goebish.free.fr/vfx

Very nice job!

I like it.

You should post that ape somewhere more public.

As it is a final version feel free to spread it where you want (websites, packs ...)

@goebish: Great thing! Thank you very much 😁

Another idea: I think, it would be very useful to have the Limiter in "Main", right under "clear every frame", with an enabling option, so that people don't have to download the APE.

May not be possible ... I say "May" coz' I know someone made an APE capable of resizing AVS editor window without having to add the APE to each preset so it also "may" be possible ... I promise I'll have a look 🙂