chrstnherr18 / ehci

Automatically exported from code.google.com/p/ehci
0 stars 0 forks source link

capturing only one frame in 3dboxview program and then the executable stops responding #34

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Using Eclipse in Windows Vista with OpenCV 2.0 since the codes didn't run in 
OpenCV 2.4.3 (which is the latest version)
2. Gave all the relevant links to ehci files,and project gets built. Solved the 
detection problem using issue no. 21 where acgour..@gmail.com pointed out that 
debug value needed to be 1. 
3. Specified values in the config.ini file too

What is the expected output? What do you see instead?
The expected output of the program as per Daniel is that using the face 
detection the perspective of the cubes should change. The problem is that when 
I run the executable file,it detects the head in one frame, the cubes are 
displayed in the background and then the executable stops responding. To check 
how many frames are being captured, wrote a printf line("frame grabbed") after:
frame = cvQueryFrame( capture );
and in the command line,"frame grabbed" appears only twice.
In all likelihood,the frame capturing gets stuck after the first frame.
Hence I would like to know how to establish a continuous detection through the 
frames,since I can see my face being detected before the executable stops 
responding. The code for the program is pretty huge and I couldn't figure out 
the problem. Any help would be beneficial. Its an exciting project.

What version of the product are you using? On what operating system?
Eclipse Helios for Windows Vista with OpenCV 2.0 and MinGW 4.6!  

Please provide any additional information below.

Original issue reported on code.google.com by shivamgu...@gmail.com on 3 Mar 2013 at 2:23

GoogleCodeExporter commented 8 years ago
Hi, shivamgupta2509,

thanks for the feedback. Can you find the specific line where the program stops 
responding? An easy way to check that is filling your program with lots of 
printf's, just to be sure where it has stopped working. Another way, more 
professional, would be using a debugger (maybe gdb, or eclipse's built in ones).

Thank you

Original comment by danielba...@gmail.com on 4 Mar 2013 at 5:52