Filter Speed Meter

Hi


I wrote a little program

It gives a filter a Speed Rating based on the number and type of components within the filter.

I thought it may be useful to check how fast a filter may work.

This program can also create a log file which is saved in the same location as the filter with the name "(filtername).txt". This text file lists the filter components and shows how they connect to each other. It is not a complete flowchart as it stops at multiple input components such as blends and other components with multiple inputs. It may help to debug a filter

Have a play with it and let me know if I can make any improvements.

How to Use
Download the attached Zip file "SpeedMeter.zip" to a location of your choice
Unzip SpeedMeter.exe
Double click SpeedMeter.exe to run it
File > Open and locate the filter to test
The Filter Speed will be Displayed

Use File > Save Log to create the debug file. The file will be called "(filtername).txt". and will be saved at the Test filter location. NB it will automatically overwrite any existing txt file of the same name.

You may find it easier to drop this program into
C:\Documents and Settings\YourName\Application Data\Filter Forge\My Filters
And create a desktop shortcut. That way the program will always open in the correct folder by default

(Coming soon)
'Filter Updater' to update all the old components to the latest versions.


Ken

Hey Ken Long time No see or type..

So what would be a cutoff point of good speed and bad speed..Kind of a nifty utility.
Did some filters, I took Rocky Formations and Rotate Zoom.
Rocky Formations 165
Rotate Zoom 73
Quite a difference there..

This could be great in the filter library to indicate rendering speed on a filter page

We could write some code to write filters from scratch. A random component connected to another etc, we could invent thousands of filters per hour. The problem is that we would also have to write some code to check if the results were good or not. I think this would be way too difficult.

Ken,

This sounds pretty cool — like Fluxtah said, sounds like it's a worthwhile feature request to show a filter's relative speed within FF itself. I could see it being useful if I'm pressed for a deadline and going through my collection.