wow!! I'm lost in the doc.
I found that CV_CAP_DSHOW
and CV_CAP_VFW
are available in 2.4.11 C Api too. In 3.0.0, CPP Api provides CAP_DSHOW
and CAP_VFW
(some refs to old CV_CAP_* still here).
- In 2.4.11 the feature works but I can't find any reference around VideoCapture doc. Why ? may be it's unstable feature ? it's just a missing doc ? I'm lost in the doc ?
- In 3.0.0 there is some hint
Now I know that:
VideoCapture cap(0 + CV_CAP_VFW); // opens cam 0 with platform native
VideoCapture cap(0 + CV_CAP_DSHOW); // opens cam 0 with DirectShow (via videoInput)
VideoCapture cap(0 ); // opens cam 0 with with default driver maybe one of above
this works with 2.4.10 too
Just to know...On my computer if I use VideoCapture cap(0 + CV_CAP_DSHOW);
I can set some props via cap.set(CV_CAP_PROP_*
that doesn't have effect when I use VideoCapture cap(0 + CV_CAP_VFW);
One of this is CAP_PROP_SETTINGS that shows the driver's property page but also CV_CAP_PROP_FPS is effective and it has effect on grab loop! this is completely different from what I said in a my recent answer :(
It's never to late to learn something !
"on windows I can use skype to set it once" - you could try the same from opencv by calling
this should take you to the same (persistant) property page as in skype, vlc, or such.
(still ugly, still interactive...)
on my windows C++
cap.set(CAP_PROP_SETTINGS,x);
has no effectsfor x: -10...+10
:(@pklab, again, this calls the driver's property page (if there is one). it all depends on the manufacturer
@berak, good to know that cap.set(CAP_PROP_SETTINGS,1); do this. Anyway, I can get the "Video Capture Filter" property page from other apps but I can't get it from OCV. May be it depends from VFW/DirectShow or other settings like this.
PS: The master doc does't include CAP_PROP_SETTINGS
@pklab - oohh, VFW makes a difference here, too:
it is in the docs