cvRetrieveFrame captures every second frame when used with FFMPEG DLL (Bug #1992)
Description
When adding the FFMPEG dll to the executable folder cvRetrieveFrame captures every second frame. When deleting the .dll file from the executable folder then it works ok.
(version 8466)
Associated revisions
Merge pull request #1992 from ElenaGvozdeva:ocl_medianFilter
History
Updated by Ioannis Katramados almost 13 years ago
Test video attached (XVID). The same problem exists with uncompressed video captured with OpenCV.
- File 120528_182651_Logitech_QuickCam_Pro_5000_0_XVID.avi added
Updated by Ioannis Katramados almost 13 years ago
The bug may be in cvGrabFrame. Every time it's called the frame pointer advanced to the next position.
Updated by Andrey Kamaev almost 13 years ago
- Target version deleted (
2.4.1)
Updated by Vadim Pisarevsky almost 13 years ago
cvRetrieveFrame() is supposed to get the last captured frame without advancing position; cvGrabFrame() advances position in the video stream. cvQueryFrame() advances position and returns the current frame (i.e. it calls cvGrabFrame() followed by cvRetrieveFrame()). How do you use those functions?
Updated by Ioannis Katramados almost 13 years ago
Thanks Vadim. I use cvGrabFrame to see if there is a valid frame and then cvRetrieveFrame to retrieve it. When reading an AVI file without the FFMPEG dll it works fine. However, when the FFMPEG dll is present then cvGrabFrame advances two positions each time.
Updated by Andrey Kamaev over 12 years ago
- Category changed from highgui-images to highgui-video
Updated by Vadim Pisarevsky over 12 years ago
- Target version deleted ()
- Assignee deleted (
Alexander Reshetnikov)
Updated by Kirill Kornyakov over 12 years ago
- Target version set to Next Hackathon
Updated by Vadim Pisarevsky about 12 years ago
- Affected version set to 2.4.1
- Target version deleted (
Next Hackathon)
Updated by Vadim Pisarevsky about 12 years ago
- Assignee set to Vadim Pisarevsky
Updated by Vadim Pisarevsky about 12 years ago
the bug can not be reproduced with 2.4 branch. Looks like it has been solved. Please, try it out with the latest 2.4.3 or 2.4 snapshot
- Status changed from Open to Done
Updated by Kirill Kornyakov about 12 years ago
- Target version set to 2.4.4