On Tue, 28 Jun 2011, IOhannes m zmoelnig wrote:
the v4l2convert trick mentioned above, is a workaround to make applications not using libv4l to still be able to benefit from libv4l's color conversion routines. but really, the application (e.g. GF or Gem) should use libv4l natively. as far as i know, both do so, if they can find libv4l (+headers!) during configure/compile time. it seems however, that your version of Gem has found libv4l while it was built, whereas GF has not. if you compiled GF yourself, try installing libv4l-dev and then re-configure & re-compile GF.
Even when you compile GF with libv4l1 support, it doesn't use it by default. The default is still plain v4l1. I think that it's because some old cameras' v4l1 extensions don't work in libv4l1 at all, but I don't recall for sure.
libv4l1 is going to be the default in the next release of GF.
| Mathieu Bouchard ---- tél: +1.514.383.3801 ---- Villeray, Montréal, QC