blob tracker "forgets" the previous frame

[GoogleCodeExporter]

The blob tracker forgets the previous frame of blobs which causes it to 
lose track of current blobs and create new ones instead. This is because 
it fails to generate valid permutations because of a too low _numchecks_.

It should be possible to somehow predict the least value of _numchecks_ 
which causes at least one valid permutation to exist.

Original issue reported on code.google.com by sebastia...@gmail.com on 21 Jul 2007 at 3:29

[GoogleCodeExporter]

This should already be fixed. Numcheck has to be at least 2. The first is to 
check 
the nearest blob and the second is to see if this is a 'new' blob. 

Original comment by dwalli...@gmail.com on 21 Jul 2007 at 3:33

• Changed state: Fixed

[GoogleCodeExporter]

Original comment by sebastia...@gmail.com on 2 Nov 2007 at 11:41

• Changed state: Accepted

[GoogleCodeExporter]

The problem remains. I attach a video which proves it.

The problem arises because permute2(.) doesn't manage to generate any valid 
permutations out of the "numcheck" closest previous frame blobs for each 
current 
frame blob.

Original comment by sebastia...@gmail.com on 2 Nov 2007 at 11:44

Attachments:

• tracking-failure2.mp4

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

...and this is because at least two of the current blobs will always have the 
same 
numcheck closest blob in each permutation.

Original comment by sebastia...@gmail.com on 2 Nov 2007 at 11:45

[GoogleCodeExporter]

Works with at least 20 fingers simultaneously now. 'numcheck' can be further 
tuned 
to track better, however it doesn't belong in this issue. Well done!

Original comment by sebastia...@gmail.com on 3 Nov 2007 at 5:25

• Changed state: Verified