Simple thing, when using videoReader_GPU, the video data is stored in GPU data memory. If it stops at 80% it means that your assigned GPU data memory is full. Cut your video into parts, feed whole parts to the GPU and then process them. This will do the trick.
Thanks for your help! However I don't now if this is the problem because i tried with smaller videos and the problem was the same. For example, one video has frame size 320 x 240 and 169 frames but videoReader_GPU reads only 150 frames. The other has frame size 400 x 224 and 4289 frames and it reads 3445 frames. Do you have any idea of what is wrong?
Thanks!
I have same problem, and the issue wont change with different size or length of video. IT will throw: Unsupported format or combination of formats (Unsupported video source) in grab, file /home/reza/Templates/opencv-2.4.6.1/modules/gpu/src/video_reader.cpp
I have tried it with many video files
@antz24 simply said, do not use 2.4.9 but go grab the bugfree 2.4.11 version!
@StevenPuttemans I tried the new version but the issue still seems to occur. I was able to trace it down to the HandlePictureDisplay callback function. I added counters to the HandlePictureDecode and HandlePictureDisplay to verify they are both counting the same amount of frames but i found the HandlePictureDisplay stops before the video is done. The HandlePictureDecode callback is counting the correct amount of frames though. Do you know why this could be?
Hmm it seems to point at a corrupt video format ... Could you try to grab the details of the last frame it can visualise and the following frame that doesn't work anymore?
Figured it out! There is a bug in the grab function of the video_reader.cpp file. The code is returning false before the frameQueue_ is empty . The code has to go into the infinite for loop and dequeue the frames, if not there will be frames missing at the end. I had to comment out frameQueue_->isEndOfDecode and create my own return. I can send my source if needed.
in your bug reply you are talking about 2.4.9, first download the latest 2.4 branch on github to see if it has been fixed there please.
Asked: 2013-03-08 07:22:03 -0600
Seen: 1,279 times
Last updated: Nov 12 '13
