282 replies to this topic

[Ascend4nt]

With Windows 2000 it worked well, as long as gdiplus.dll was added (another dependency of your DLL). Windows XP seemed to work fine, though the FastFind_Demo program crashed with an exception in fastfind.dll. I'm not sure why that failed, it should have worked fine on XP. Could just chalk it up to a Virtual Machine fluke though. It'd be best to test it on a true Windows XP install to make sure.

[1loxe2006]

hello everybody !
please help me,about 10 days ago I still useable but now i not use my script, when I run my script I get a message box saying "Can't start, try again".
followed by the "Failed to load FastFind.dll, application probably won't properly work." message box from FastFind.au3

[FastFrench]

@Ascend4nt : Thank you for your report. As I use GDI+, the gdiplus.dll dependency is obvious.

@1loxe2006 : the last version should fix that problem.

Also note that CeramicWeasel has started to write a documentation on FastFind. It will be a nice addition to help people in using FastFind.

Edited by FastFrench, 04 November 2011 - 01:31 PM.

[fisofo]

I've been searching a while for this, thought I'd just ask here: has anyone created something like this in AutoIt? Before I dig into trying to create it, I thought this might be a good place to ask:

http://stackoverflow.com/questions/1855884/determine-font-color-based-on-background-color

[Deamons]

Hello FastFrench,

I juste need some information about FastFind.dll, because I developed an application in C# and I recently found your dll, but after including the dll with DllImport, I tried the FFGetPixel function for example, but it always return "-1"

Sample :

        [DllImport(@"....\FastFind.dll")]
        static extern int FFGetPixel(int X, int Y, int NoSnapShot);

        private void timer1_Tick(object sender, EventArgs e)
        {
            int pixel = FFGetPixel(Cursor.Position.X, Cursor.Position.Y, 0);
            this.Text = pixel.ToString();
        }

Do I have to do something with SnapShot function ?

[frank10]

Very good UDF/dll. Very fast.

How do you make a webcam motion detection?
Let's say I have a 640x480 webcam pic and I want to detect if someone opens a door in a vertical position of 100x350 at 70px from the left of window.
I thougth using FFLocalizeChanges, but it compares the entire snapshot and the webcam introduces fuzzy pixels every frame because of noise, so snapshots are always different...

Could you post a code example?

[FastFrench]

Hello FastFrench,

I juste need some information about FastFind.dll, because I developed an application in C# and I recently found your dll, but after including the dll with DllImport, I tried the FFGetPixel function for example, but it always return "-1"

Sample :

        [DllImport(@"....FastFind.dll")]
        static extern int FFGetPixel(int X, int Y, int NoSnapShot);

        private void timer1_Tick(object sender, EventArgs e)
        {
            int pixel = FFGetPixel(Cursor.Position.X, Cursor.Position.Y, 0);
            this.Text = pixel.ToString();
        }

Do I have to do something with SnapShot function ?

Yes. When you use the AutoIt wrapper, SnapShots are done implicitely as needed. If you use FastFind.dll in some other language like C#, then you have to explicitely make a SnapShot first to use it.

You may check the autoit wrapper (FastFind.au3) to see how to do that.

The log file should give you precious hints on the problem.

Edited by FastFrench, 05 January 2012 - 10:46 AM.

[FastFrench]

Very good UDF/dll. Very fast.

How do you make a webcam motion detection?
Let's say I have a 640x480 webcam pic and I want to detect if someone opens a door in a vertical position of 100x350 at 70px from the left of window.
I thougth using FFLocalizeChanges, but it compares the entire snapshot and the webcam introduces fuzzy pixels every frame because of noise, so snapshots are always different...

Could you post a code example?

If you want to localize changes in a restricted region, you should better do SnapShots of only that restricted region (rectangle).

But you're right : LocalizeChanges do not handle ShadeVariations, so it has no noise tolerancy.

There are probably many ways to do that. The starting point would be compare a pic with the door opened and another with the door closed. If you have a significative area with a relatively homogeneous color when opened and closed, then
ColorCount should do the job. You need to experiment to find the optimal ShadeVariation value.

Hope this will help,
FF

Edited by FastFrench, 05 January 2012 - 10:58 AM.

[frank10]

I post some pics as an example.
Cam1 is with all doors closed, Cam1_Zones has doorA, doorB and doorC that's not visible.
Cam2 is with DoorB open, Cam3 is with DoorB half-closed, Cam4 is with DoorA open.

I don't think it's possible with ColourCount, because one can check the colourCount of B when closed and it's brown with some shadevariations, but if someone opens it (you can fire this with ColourCount) and leaves B open like Cam2 you can't use the previous ColourCode brown code, because there is no more brown... So you could not detect anymore if someone crosses. And what about someone dressed with similar colour?

I hope to detect if someone enters A and crosses B, or enters from B and crosses C and so on.

I think the best mode should be to compare two adjacent screenshots taken every about 700ms and looking at how many contiguos pixels changed: so if they are a lot contiguos px changed, there was motion in that reported area A, B or C.
This way the webcam noise should not interfere because they are sparse pixels over all the screenshot.
I don't know if this is possible with your udf, up to now.
If it's not possible, I think you could add this feature: it should be a value one for all motion detection uses.

Or maybe another approach could be to flatten the most differences in the colours, making a flat cartoon uniform pic, so eliminating noise, and then compare these screenshots with FFLocalizeChanges.
Like Emboss or Cartoonize.
http://cartoonized.net/tutorial-turning-photograph-into-cartoon-part1.php
But I don't know how to automate this in autoit.

Attached Thumbnails

• 
• 
• 
• 
• 
• 
• 

Edited by frank10, 05 January 2012 - 03:41 PM.

[FastFrench]

I post some pics as an example.
Cam1 is with all doors closed, Cam1_Zones has doorA, doorB and doorC that's not visible.
Cam2 is with DoorB open, Cam3 is with DoorB half-closed, Cam4 is with DoorA open.

I don't think it's possible with ColourCount, because one can check the colourCount of B when closed and it's brown with some shadevariations, but if someone opens it (you can fire this with ColourCount) and leaves B open like Cam2 you can't use the previous ColourCode brown code, because there is no more brown... So you could not detect anymore if someone crosses. And what about someone dressed with similar colour?

I hope to detect if someone enters A and crosses B, or enters from B and crosses C and so on.

I think the best mode should be to compare two adjacent screenshots taken every about 700ms and looking at how many contiguos pixels changed: so if they are a lot contiguos px changed, there was motion in that reported area A, B or C.
This way the webcam noise should not interfere because they are sparse pixels over all the screenshot.
I don't know if this is possible with your udf, up to now.
If it's not possible, I think you could add this feature: it should be a value one for all motion detection uses.

Or maybe another approach could be to flatten the most differences in the colours, making a flat cartoon uniform pic, so eliminating noise, and then compare these screenshots with FFLocalizeChanges.
Like Emboss or Cartoonize.
http://cartoonized.net/tutorial-turning-photograph-into-cartoon-part1.php
But I don't know how to automate this in autoit.

I see. Probably the best option would be to have a sort of FFLocalizeChanges with an additional "ShadeVariation" (or noise tolerancy) parameter. May be a good candidat for the next version of FastFind.

For all people that failed to dowload FFshowPixels, could you please try again now ? An admin told me that the link is available now.

Thanks,

FF

[FastFrench]

Could someone please confirm if ShowPixel can be downloaded (link on 1st post) ?

[frank10]

Yes I downloaded ShowPixel_1.7 (I don't find 1.8)

In your C func, how do you compare the pixel variations?
Do you trasform the pixel region in array and then compare them as strings?

[Aktonius]

Just want to say that you are beyond awesome FastFrench, thanks for the amazing work!

[JohnOne]

frank10, If I were you I'd put coloured stickers on the doors, and focus the script attentions on those areas.

Perhaps noise might cause some pixels to loo lose credibility but I doubt all of them in that area would.

[frank10]

@JohnOne
I could do this if the doors were always closed after each entry.
But when one enters, he can leave the door open, so I could know the door isn't closed but I can't detect anymore if someone crosses again.

EDIT:
Maybe you mean to put these stickers on the doorposts. Yes in that case it could work.
But it's a bit unaestetich...

Edited by frank10, 12 January 2012 - 11:40 PM.

[JohnOne]

Maybe, but even if you focus on a number of pixels anywhere in a particular spot
of a fixed area and only acknowledge the break in continuity if all of them change.

[CeramicWeasel]

How about using KeepChanges to blank out everything that hasn't changed, then follow up with BestSpot with a large shade variation that includes everything except black pixels.

With BestSpot, specify something like a 10x10 area with a minimum of 30 matching pixels. This will hopefully be enough to ignore noise and give you a location for the change.

Not perfect, but may work.

You could drastically reduce noise by cartoonizing the snapshot, but you'll never completely eliminate noise with that technique. To do this you could loop through every pixel in the snapshot and "round" it's color to the nearest n'th shade (GetPixel -> Round -> SetPixel), but I don't know how fast that will be.

Edited by CeramicWeasel, 16 January 2012 - 08:24 AM.

[frank10]

Interesting CeramicWeasel, I will try the BestSpot method when I have time. The only problem could be the different color of pixels, but shadeVariation should do the trick.

I thought also to get some orizontal areas in the crossing points and trasform the pixels in Array, then using some string compare method to find how many pixels changed. May work well and also be fast.

[CeramicWeasel]

Actually, NearestSpot should work too, and will be slightly faster since BestSpot will do 2 full searches before it even considers the ShadeVariation parameter.

[FastFrench]

I fear that on a reasonably noisy 24 bits per pixel picture recording, most - if not all - pixels will change from one picture to another. Even if the change is usually not perceptible, the color will usually not be exactly the same.

I think of a new function that would simply do a "AND" filter on each pixel of a snapShot. It would be very easy to implement and very fast too.
The usage would be :
Filter(SnapShotNb, FilterValue).

For instance, to ignore the 6 low weight bits out of 8 for each color component, the FilterValue would be 0x00C0C0C0. This would make a decent noise filter (this way, you would actually transform your 24 bits per pixel picture into a 64 colors - or 6 bits per pixel - picture).
Another usage would be to split each color channel (Red, Green and Blue) :
the Red SnapShot would come with Filter(SnapShotNb, 0x00FF0000)
the Green one SnapShot would come with Filter(SnapShotNb, 0x0000FF00)
and the blue one with Filter(SnapShotNb, 0x000000FF)


Any use ?