News:

MASM32 SDK Description, downloads and other helpful links
MASM32.com New Forum Link
masmforum WebSite

cvExtractSURF

Started by Farabi, July 10, 2011, 04:59:15 AM

Previous topic - Next topic

Farabi

Anyone know how many bytes it used the stack as parameters?

fOpenCVcvExtractSURF proc uses esi edi image:dword,_mask:dword,keypoints:dword,descriptors:dword,storage:dword,params:CvSURFParams ,useProvidedKeyPts:dword
   
   push useProvidedKeyPts
   push params.nOctaveLayers
   push params.nOctaves
   push dword ptr params.hessianThreshold[4]
   push dword ptr params.hessianThreshold[0]
   push params.extended
   push storage
   push descriptors
   push keypoints
   push _mask
   push image
   call cvExtractSURF
   add esp,11*4
   
   ret
fOpenCVcvExtractSURF endp

I used it that way, but it seems did not work, if it is not because I feed a wrong picture depth bit, it is because I feed a wrong parameters.
Those who had universe knowledges can control the world by a micro processor.
http://www.wix.com/farabio/firstpage

"Etos siperi elegi"

donkey

Reading the docs, I don't see an entry for useProvidedKeyPts. Also keypoints and descriptors are defined as **keypoints and **descriptors, both are double pointers (pointers to pointers). From what I can gather from the declaration the function uses 40 bytes and you have it at 44.

http://opencv.willowgarage.com/documentation/feature_detection.html#extractsurf
"Ahhh, what an awful dream. Ones and zeroes everywhere...[shudder] and I thought I saw a two." -- Bender
"It was just a dream, Bender. There's no such thing as two". -- Fry
-- Futurama

Donkey's Stable