libvidcap-devel — Development discussion for libvidcap

Re: [libvidcap-devel] Bid to port the Quicktime SG to QTKit

[Alejandro I. <ai...@ya...>]

On Fri, Mar 2, 2012 at 5:53 PM, Alejandro Imass <ai...@ya...> wrote:
> Hello folks,
>
> We'd like to see if we can finance the addition of 64 Bit Quicktime
> and looking for an experienced commiter (Peter, Bill) that has the
> Quicktime knowledge, or anyone that feels up to the task. The work
> will be done directly on the project on a BSD or Lesser GPL 2.x
> license, or similar allowing commercial linkage.

FYI the bid is also open at vworker if anyone would like to take that route.

Thanks,

-- 
Alejandro Imass

[libvidcap-devel] Bid to port the Quicktime SG to QTKit

[Alejandro I. <ai...@ya...>]

Hello folks,

We'd like to see if we can finance the addition of 64 Bit Quicktime
and looking for an experienced commiter (Peter, Bill) that has the
Quicktime knowledge, or anyone that feels up to the task. The work
will be done directly on the project on a BSD or Lesser GPL 2.x
license, or similar allowing commercial linkage.

>From what we've researched the QuickTime framework does not and will
not work in 64 bits. So applications have to switch to the QTCapture
classes instead of the sequence grabber.

It should be a quick and easy job for any of the authors here and we
think it will benefit everyone. Maybe just adding sapi_qtkit and the
QTKit counterparts.

Please share your ideas on the list but quotes off-list only.

Thanks,

-- 
Alejandro Imass

[libvidcap-devel] Creating Virtual webcam that broadcast desktop

[Tzahi B. <tz...@hb...>]

Hi,
I was wondering if the libvidcap can create a virtual web cam and capture the desktop?
What other video capture devices except webcam can it capture?


Thanks and regards,
Tzahi

[libvidcap-devel] libvidcap on MAC OS X (Snow Leopard)

[Ellen R. <ell...@gm...>]

Hi,

I'm encountering an error when compiling the libvidcap on MAC OS X
64bit. Please help.
Here is the error:

IC -o quicktime/.libs/libvidcap_la-sg_manager.o
In file included from quicktime/sg_manager.h:31,
                 from quicktime/sg_manager.c:27:
quicktime/sg_source.h:42: error: expected specifier-qualifier-list
before 'SeqGrabComponent'
quicktime/sg_source.h:76: error: expected declaration specifiers or
'...' before 'SGDataUPP'
quicktime/sg_manager.c: In function 'sg_manager_update':
quicktime/sg_manager.c:46: error: 'SGDeviceList' undeclared (first use
in this function)
quicktime/sg_manager.c:46: error: (Each undeclared identifier is
reported only once
quicktime/sg_manager.c:46: error: for each function it appears in.)
quicktime/sg_manager.c:46: error: expected ';' before 'device_list'
quicktime/sg_manager.c:47: error: 'SGDeviceListPtr' undeclared (first
use in this function)
quicktime/sg_manager.c:47: error: expected ';' before 'dlr'
quicktime/sg_manager.c:73: warning: implicit declaration of function
'SGGetChannelDeviceList'
quicktime/sg_manager.c:73: error: 'struct sg_source' has no member
named 'channel'
quicktime/sg_manager.c:74: error: 'sgDeviceListIncludeInputs'
undeclared (first use in this function)
quicktime/sg_manager.c:75: error: 'device_list' undeclared (first use
in this function)
quicktime/sg_manager.c:82: error: 'dlr' undeclared (first use in this function)
quicktime/sg_manager.c:103: error: 'SGDeviceInputListPtr' undeclared
(first use in this function)
quicktime/sg_manager.c:103: error: expected ';' before 'ilr'
quicktime/sg_manager.c:109: error: 'ilr' undeclared (first use in this function)
quicktime/sg_manager.c:128: warning: implicit declaration of function
'SGDisposeDeviceList'
quicktime/sg_manager.c:128: error: 'struct sg_source' has no member
named 'grabber'
make[2]: *** [quicktime/libvidcap_la-sg_manager.lo] Error 1
make[1]: *** [all-recursive] Error 1

Thanks!
Ellen

[libvidcap-devel] Video4Linux2 support

[Roman H. <hi...@id...>]

Hi,

recently I bought a Microsoft Webcam that was not supported by the V4L1 backend of the libvidcap library, because the driver was missing some features in the V4L1 compatibility layer.
Therefore I am working since 2 Weeks at a V4L2 backend. 

Basically it's working, but there are still lot's of missing features and lot's of unnecessary debug messages in the code.

I have tested it with two Webcams so far. The Microsoft Webcam is working, but the Quickcam Messanger at my work has a Bayer BGRG output that is not yet supported by the conversion code
(I found code in here though, but haven't checked the license yet. URL: http://home.mag.cx/messenger/ ).

Now I saw, that after a small break, there is some activity in the SVN tree again. I hope that you guys didn't already have some V4L2 code at home that is pending for a commit. 
If not, I want to discuss in what kind of way you would accept a V4L2 Backend patch to include in your library.

In the moment. I split the v4l_sapi into two separate parts, one that handles V4L1 and the other that handles V4L2. If the v4l_sapi detects that the device to open can handle the V4L2 API, the newer interface is chosen;  Otherwise the old code is used.

Would you accpet that kind of design, or would you like to have two complete seperate sapi interfaces for the two V4L APIs? 

Greetings from a freezing Cologne,

Roman

Re: [libvidcap-devel] (no subject)

[Peter G. <jpg...@gm...>]

2009/8/12 Екатерина Челинцева <rem...@ma...>:
> Hello!
>
> i have several questions.
>
> 1. I need to set up camera settings manually, for example focus, exposure etc. Does libvidcap provide interface for this?

No, libvidcap does not have this ability. Someone would have to implement it.

> 2. Is it possible to choose the capture frame size? i have seen vidcap_format_bind function, that has vidcap_fmt_info parameter, can i use it for setting the resolution?

Yes, you can set the resolution in the manner you are suggesting. The
particular resolutions available will depend on the particular camera.

>
> thx

Pete

[libvidcap-devel] (no subject)

[Екатерина Ч. <rem...@ma...>]

Hello!

i have several questions.

1. I need to set up camera settings manually, for example focus, exposure etc. Does libvidcap provide interface for this?
2. Is it possible to choose the capture frame size? i have seen vidcap_format_bind function, that has vidcap_fmt_info parameter, can i use it for setting the resolution?

thx

Re: [libvidcap-devel] Newbie questions

[Bill C. <bc...@ya...>]

> Hello,

Hey there.


> 
> I have been looking at the code for release 0.2.1 and there are some
> things I don't quite understand yet:
> 
> - Is it possible to capture the desktop instead of a webcam?

No. Libvidcap is for webcams and other capture devices.

> 
> - How do I specify what video codec I want to use? Which one are
> supported? (I'd like to use a lossless codec)

libvidcap provides un-encoded video (i.e. rgb, i420)

> - How do I tell libvidcap what region I want to capture? (for
> instance, my has resolution 800x600 but I only want to capture the
> 400x300 region in the center)

Not applicable

> 
> Thanks and sorry if these are basic questions.

np


      

[libvidcap-devel] Newbie questions

[Pau G. i Q. <pgq...@el...>]

Hello,

I have been looking at the code for release 0.2.1 and there are some
things I don't quite understand yet:

- Is it possible to capture the desktop instead of a webcam?

- How do I specify what video codec I want to use? Which one are
supported? (I'd like to use a lossless codec)

- How do I tell libvidcap what region I want to capture? (for
instance, my has resolution 800x600 but I only want to capture the
400x300 region in the center)

Thanks and sorry if these are basic questions.

-- 
Pau Garcia i Quiles
http://www.elpauer.org
(Due to my workload, I may need 10 days to answer)

Re: [libvidcap-devel] MacOSX: Getting rid of those deprecated warnings

[Peter G. <jpg...@gm...>]

On Thu, Nov 13, 2008 at 1:28 PM, Roman Himmes
<rom...@po...> wrote:
> Hi,
>
> a few Months ago I was developing my own  platform independed webcam
> library, before I found this library.
> At least the Mac version was very similiar to your version  because
> both take the sequenceGrabber and extract the video
>  picture by picture form the GWorld with the deprecated functions
> GetGWorldPixMap and Un-/LockPixels.
>
> This is the way the QuickTime Sample Hack TV Carbon Example (http://developer.apple.com/samplecode/HackTVCarbon/index.html
> ) or
> BrideOfMungGrab Example (http://developer.apple.com/samplecode/BrideOfMungGrab/index.html
> )
> has done it as well.
>
> Now  as I understood the GWorld concept has been replaced by the new
> CoreImage system, but I don't find any functions to simply get the
> same functionality with CoreImage than the GetGWorldPixMap and Un-/
> LockPixels functions.
>
> Now my question:
>
> Is there somebody working on this? Or should I investigate further?

I am not doing any libvidcap development at the moment.

> I am not happy with the performance of the current version, since it
> takes more cpu load than the Windows Version. Perhaps the Locking and
> Unlocking of the GWorld is too expensive and there is a better way.

What Apple would like everyone to do is upgrade to 10.5 and use their
new Cocoa-based QtKit Capture framework to do video capture. That
framework obviates all of the Carbon-based sequence grabber and video
digitizer code used in libvidcap. Two problems:

1) Nobody has done the work to add QtKit capture as a source api for libvidcap
2) Only OS X 10.5 or later users will be able to take advantage of
this sapi. It should be possible to have both exist in libvidcap and
determine at runtime which to use though.

Pete

[libvidcap-devel] MacOSX: Getting rid of those deprecated warnings

[Roman H. <rom...@po...>]

Hi,

a few Months ago I was developing my own  platform independed webcam  
library, before I found this library.
At least the Mac version was very similiar to your version  because  
both take the sequenceGrabber and extract the video
  picture by picture form the GWorld with the deprecated functions  
GetGWorldPixMap and Un-/LockPixels.

This is the way the QuickTime Sample Hack TV Carbon Example (http://developer.apple.com/samplecode/HackTVCarbon/index.html 
) or
BrideOfMungGrab Example (http://developer.apple.com/samplecode/BrideOfMungGrab/index.html 
)
has done it as well.

Now  as I understood the GWorld concept has been replaced by the new  
CoreImage system, but I don't find any functions to simply get the  
same functionality with CoreImage than the GetGWorldPixMap and Un-/ 
LockPixels functions.

Now my question:

Is there somebody working on this? Or should I investigate further?

I am not happy with the performance of the current version, since it  
takes more cpu load than the Windows Version. Perhaps the Locking and  
Unlocking of the GWorld is too expensive and there is a better way.


Roman Himmes

Re: [libvidcap-devel] Documentation

[Peter G. <jpg...@gm...>]

On Wed, Oct 15, 2008 at 8:51 PM, Craig Ritzdorf <cri...@gm...> wrote:
>
> Is there any documentation (API etc) on libvidcap or should I just be
> looking through the header files?

Header files. And questions here.

Pete

[libvidcap-devel] Documentation

[Craig R. <cri...@gm...>]

Hey all,

Is there any documentation (API etc) on libvidcap or should I just be  
looking through the header files?

Thanks,

Craig

Re: [libvidcap-devel] Mac OS X, builtin iSight, output-log from simplegrab.c

[Peter G. <jpg...@gm...>]

Hi Jacob,

On Thu, Aug 21, 2008 at 11:30 PM, Jacob Smith <jar...@gm...> wrote:
> I just wanted to make sure if the attached output is "okay" before I begin
> digging into the code too much more. My main concern comes from the end of
> the log; it says:
>
> vidcap: warning: failed to acquire default source
> vidcap: error: failed to acquire default
> simplegrab: error: failed to acquire default src 2
>
> Does this mean a failure in simplegrab? the quicktime layer? or is it the
> "expected" output? It appears that simplegrab.c is trying to grab two input
> video sources. I am not sure this is possible with the built-in iSight...
> perhaps this is the appropriate output?

This is normal -- simplegrab does a number of test scenarios and the
one that is failing is the "double default test". This test tries to
acquire a default source twice. Since you only have one video device
attached to your system, it makes sense that the second attempt to
acquire a source would fail.

You can choose which tests simplegrab runs. Try "simplegrab -h" to see
its options.

> thank you,
>
> -Jacob Smith.
>
> p.s. Your library is going to be a *life-saver* for me. Thank you very much.

You are welcome. I appreciate the positive feedback. Good luck!

Pete

Re: [libvidcap-devel] libvidcap, qedit.h

[Peter G. <jpg...@gm...>]

On Thu, Aug 21, 2008 at 10:56 AM, David Alm <dav...@gm...> wrote:
> Greetings,
>
> I just downloaded libvidcap, and I'm new to DS.
>
> In my Aug 2007 DS SDK folder, there is no qedit.h.  Apparently
> (googling), this is an older DX header.

Microsoft effectively broke being able to build video capture
applications by removing this from the DX SDK. This was a braid-dead
move on their part.

> Any advice on how to proceed to get this to build?

The workaround is to use an older DX SDK. I use June 2007 successfully.

Hope this helps.

Pete

Re: [libvidcap-devel] Convert I420 to RGB24

[Jean C. M. <jc_...@ho...>]

I'm writing a portable/multiclient/multicamera streaming webcam server that send jpeg frames.I have to compress each frame from RGB to jpeg because my jpeg library takes RGB24 (3 bytes per pixel with no padding) on the input.I've modify your lib to retrieve each frames on rgb24 or jpeg format (if the webcam is able to give me a native mjpeg stream.
In this case, I haven't to compress the received frames).I will give you all my modifications when I've finish (according the GPL licence).
I'm using the [yuy2|i420]_to_rgb32 convert functions to write my own xxx_to_rgb24 ones but I can't make it for the i420 :/
 
I'v made the following function but it doesn't work :
 
int vidcap_i420_to_rgb24(int width, int height, const char * src, char * dest){ const unsigned char * y_even; const unsigned char * y_odd; const unsigned char * u; const unsigned char * v; unsigned char *dst_even; unsigned char *dst_odd; int i, j;
 if ( !tables_initialized )  init_yuv2rgb_tables();
 dst_even = (unsigned char *)dest; dst_odd = dst_even + width;
 y_even = (const unsigned char *)src; y_odd = y_even + width; u = y_even + width * height; v = u + ((width * height) >> 2);
 for ( i = 0; i < height / 2; ++i ) {  for ( j = 0; j < width / 2; ++j )  {   const int rc = yuv2rgb_r[*v];   const int gc = yuv2rgb_g1[*v] + yuv2rgb_g2[*u];   const int bc = yuv2rgb_b[*u];   const int yc0_even = CLIP_OFFSET + yuv2rgb_y[*y_even++];   const int yc1_even = CLIP_OFFSET + yuv2rgb_y[*y_even++];   const int yc0_odd = CLIP_OFFSET + yuv2rgb_y[*y_odd++];   const int yc1_odd = CLIP_OFFSET + yuv2rgb_y[*y_odd++];
   *dst_even++ = (unsigned char)yuv2rgb_clip[(yc0_even) + (rc)];   *dst_even++ = (unsigned char)yuv2rgb_clip[(yc0_even) + (gc)];   *dst_even++ = (unsigned char)yuv2rgb_clip[(yc0_even) + (bc)];
   *dst_even++ = (unsigned char)yuv2rgb_clip[(yc1_even) + (rc)];   *dst_even++ = (unsigned char)yuv2rgb_clip[(yc1_even) + (gc)];   *dst_even++ = (unsigned char)yuv2rgb_clip[(yc1_even) + (bc)];
   *dst_odd++ = (unsigned char)yuv2rgb_clip[(yc0_odd) + (rc)];   *dst_odd++ = (unsigned char)yuv2rgb_clip[(yc0_odd) + (gc)];   *dst_odd++ = (unsigned char)yuv2rgb_clip[(yc0_odd) + (bc)];
   *dst_odd++ = (unsigned char)yuv2rgb_clip[(yc1_odd) + (rc)];   *dst_odd++ = (unsigned char)yuv2rgb_clip[(yc1_odd) + (gc)];   *dst_odd++ = (unsigned char)yuv2rgb_clip[(yc1_odd) + (bc)];      ++u;   ++v;  }
  y_even += width;  y_odd += width;  dst_even += width;  dst_odd += width; }
 return 0;}
_________________________________________________________________
Votre contact a choisi Hotmail, l'e-mail nouvelle génération. Créez un compte. 
http://www.windowslive.fr/hotmail/default.asp

Re: [libvidcap-devel] Convert I420 to RGB24

[Peter G. <jpg...@gm...>]

On Thu, Jul 3, 2008 at 6:32 PM, Jean Charles MAMMANA
<jc_...@ho...> wrote:
> I'm adding the RGB24 to the fourCC list to capture frame to this format.
> So I've created two convert functions : vidcap_yuy2_to_rgb24 that works
> correctly and vidcap_i420_to_rgb24 but I don't try to make this conversion
> :/
> So I would like to know if someone may give me some help to do it.

By rgb24, I assume you mean 3 bytes per pixel with no padding, e.g.
RGBRGBRGB, not RGB_RGB_RGB_?

The algorithms for convetring i420 and yuy2 to rgb32 found in
vidcap_i420_to_rgb32() and vidcap_yuy2_to_rgb32() should be a
sufficient reference. Getting the red, green, and blue color
components converted is the same, the difference is just in how the
bytes are packed.

I am also interested in how being able to convert to RGB24 is helpful.
What application are you looking at?

Thanks,
Pete

[libvidcap-devel] Convert I420 to RGB24

[Jean C. M. <jc_...@ho...>]

Hi,
 
I'm adding the RGB24 to the fourCC list to capture frame to this format.
So I've created two convert functions : vidcap_yuy2_to_rgb24 that works correctly and vidcap_i420_to_rgb24 but I don't try to make this conversion :/
So I would like to know if someone may give me some help to do it.
 
Thanks.
_________________________________________________________________
Retrouvez vos e-mails Hotmail sur votre mobile
http://www.messengersurvotremobile.com/?d=hotmail

Re: [libvidcap-devel] [win32] listing device modes

[Jean C. M. <jc_...@ho...>]

> > I've done some tests on windows XP SP2 and Vista SP1 on two computers with 3> > cameras.> > All cameras gave me the same 44 modes with libvidcap library.> Okay, that makes sense.
 
Is there a reason to get "only" 44 modes each time ?
 
> Another thing that is a little funny about libvidcap is that it has a> "hotlist" of modes that it looks for. So when it reports the modes> available for a device, it only includes device modes that match with> hotlist modes. If I recall, it was implemented this way because it can> be difficult to get exhaustive mode lists from source apis, but it is> easier to validate any particular mode.> > Even if libvidcap does not report that the device supports a> particular format, the application may still successfully bind that> format using vidcap_format_bind(). For example, libvidcap would> probably be able to capture using "Mode 00: 720x480 @ 25 fps (YUY2)".> > It might make sense to add formats to libvidcap's hotlist. Perhaps the> 720x480 resolution would be a good one to look for.
I think this "hotlist" exists to help us to standardise format on differents platforms.
I'll take a look into the code to find a way to retrieve the real supported format (with directshow).
> > An other question : is there a way to get the native camera output mode> > (without conversion ?).> > By exemple : on a camera which is capable to give me an mjpeg image format,> > is it possible to retrieve it ?> > This is not currently a feature of libvidcap. I would consider a patch> for this feature though.
Good. I'll wait.
 
Thanks.
_________________________________________________________________
Retouchez, classez et partagez vos photos gratuitement avec le logiciel Galerie de Photos !
http://www.windowslive.fr/galerie/

Re: [libvidcap-devel] [win32] listing device modes

[Peter G. <jpg...@gm...>]

On Wed, Jun 25, 2008 at 11:08 AM, Jean Charles MAMMANA
<jc_...@ho...> wrote:
> Thanks for your help.
>
>> Are you using simplegrab or vidcapTester? There is no example.cpp.
> I'm using simplegrab.c file.

Okay, good.

>> What platform are you using? Windows? Mac? Linux?
> I've done some tests on windows XP SP2 and Vista SP1 on two computers with 3
> cameras.
> All cameras gave me the same 44 modes with libvidcap library.

Okay, that makes sense.

>> Why do you suspect that the mode output is wrong? What other tools are
>> you using to query the device capabilities?
> I've made some tests with an other webcam library called vidcapture (
> http://www.codevis.com/vidcapture/ )
> This lib give me the correct modes for each camera according to the camera
> datasheet as you can see on my previous message.
>
>
>> One thing to note is that libvidcap is reporting the modes it can
>> achieve using this video device, not all the modes that the video
>> device itself can achieve. For example, libvidcap does not know how to
>> convert motion jpeg into either rgb32, yuy2, or i420.
> I understood. but I my case there are some missing resolutions (over
> 640*480).

Another thing that is a little funny about libvidcap is that it has a
"hotlist" of modes that it looks for. So when it reports the modes
available for a device, it only includes device modes that match with
hotlist modes. If I recall, it was implemented this way because it can
be difficult to get exhaustive mode lists from source apis, but it is
easier to validate any particular mode.

Even if libvidcap does not report that the device supports a
particular format, the application may still successfully bind that
format using vidcap_format_bind(). For example, libvidcap would
probably be able to capture using "Mode 00: 720x480 @ 25 fps (YUY2)".

It might make sense to add formats to libvidcap's hotlist. Perhaps the
720x480 resolution would be a good one to look for.

> An other question : is there a way to get the native camera output mode
> (without conversion ?).
> By exemple : on a camera which is capable to give me an mjpeg image format,
> is it possible to retrieve it ?

This is not currently a feature of libvidcap. I would consider a patch
for this feature though.

Thanks,
Pete

Re: [libvidcap-devel] [win32] listing device modes

[Jean C. M. <jc_...@ho...>]

Thanks for your help.
> Are you using simplegrab or vidcapTester? There is no example.cpp.I'm using simplegrab.c file.
> What platform are you using? Windows? Mac? Linux?I've done some tests on windows XP SP2 and Vista SP1 on two computers with 3 cameras.All cameras gave me the same 44 modes with libvidcap library.
> Why do you suspect that the mode output is wrong? What other tools are> you using to query the device capabilities?I've made some tests with an other webcam library called vidcapture ( http://www.codevis.com/vidcapture/ )This lib give me the correct modes for each camera according to the camera datasheet as you can see on my previous message.
 
> One thing to note is that libvidcap is reporting the modes it can> achieve using this video device, not all the modes that the video> device itself can achieve. For example, libvidcap does not know how to> convert motion jpeg into either rgb32, yuy2, or i420.I understood. but I my case there are some missing resolutions (over 640*480).
An other question : is there a way to get the native camera output mode (without conversion ?).
By exemple : on a camera which is capable to give me an mjpeg image format, is it possible to retrieve it ?
_________________________________________________________________
Avec Hotmail, vos e-mails vous suivent partout ! Mettez Hotmail sur votre mobile !
http://www.messengersurvotremobile.com/?d=hotmail

Re: [libvidcap-devel] [win32] listing device modes

[Peter G. <jpg...@gm...>]

Hi,

On Wed, Jun 25, 2008 at 4:19 AM, Jean Charles MAMMANA
<jc_...@ho...> wrote:
> I'm using the exemple.cpp source code to list all connected cameras and all
> modes for them. The list is the same for all camera and doesn't give the
> right available modes. (It seems the lib always return me the 44 first
> mode.

Are you using simplegrab or vidcapTester? There is no example.cpp.

What platform are you using? Windows? Mac? Linux?

Why do you suspect that the mode output is wrong? What other tools are
you using to query the device capabilities?

One thing to note is that libvidcap is reporting the modes it can
achieve using this video device, not all the modes that the video
device itself can achieve. For example, libvidcap does not know how to
convert motion jpeg into either rgb32, yuy2, or i420.

Pete

> Exemple :
> Device 00: USB Video Device
> Mode 00: 640x480 @ 15 fps (rgb32)
> Mode 01: 320x240 @ 15 fps (rgb32)
> Mode 02: 160x120 @ 15 fps (rgb32)
> Mode 03: 640x480 @ 30 fps (rgb32)
> Mode 04: 320x240 @ 30 fps (rgb32)
> Mode 05: 160x120 @ 30 fps (rgb32)
> Mode 06: 640x480 @ 29 fps (rgb32)
> Mode 07: 320x240 @ 29 fps (rgb32)
> Mode 08: 160x120 @ 29 fps (rgb32)
> Mode 09: 640x480 @ 10 fps (rgb32)
> Mode 10: 320x240 @ 10 fps (rgb32)
> Mode 11: 160x120 @ 10 fps (rgb32)
> Mode 12: 640x480 @ 1 fps (rgb32)
> Mode 13: 320x240 @ 1 fps (rgb32)
> Mode 14: 160x120 @ 1 fps (rgb32)
> Mode 15: 640x480 @ 15 fps (i420)
> Mode 16: 320x240 @ 15 fps (i420)
> Mode 17: 160x120 @ 15 fps (i420)
> Mode 18: 640x480 @ 30 fps (i420)
> Mode 19: 320x240 @ 30 fps (i420)
> Mode 20: 160x120 @ 30 fps (i420)
> Mode 21: 640x480 @ 29 fps (i420)
> Mode 22: 320x240 @ 29 fps (i420)
> Mode 23: 160x120 @ 29 fps (i420)
> Mode 24: 640x480 @ 10 fps (i420)
> Mode 25: 320x240 @ 10 fps (i420)
> Mode 26: 160x120 @ 10 fps (i420)
> Mode 27: 640x480 @ 1 fps (i420)
> Mode 28: 320x240 @ 1 fps (i420)
> Mode 29: 160x120 @ 1 fps (i420)
> Mode 30: 640x480 @ 15 fps (yuy2)
> Mode 31: 320x240 @ 15 fps (yuy2)
> Mode 32: 160x120 @ 15 fps (yuy2)
> Mode 33: 640x480 @ 30 fps (yuy2)
> Mode 34: 320x240 @ 30 fps (yuy2)
> Mode 35: 160x120 @ 30 fps (yuy2)
> Mode 36: 640x480 @ 29 fps (yuy2)
> Mode 37: 320x240 @ 29 fps (yuy2)
> Mode 38: 160x120 @ 29 fps (yuy2)
> Mode 39: 640x480 @ 10 fps (yuy2)
> Mode 40: 320x240 @ 10 fps (yuy2)
> Mode 41: 160x120 @ 10 fps (yuy2)
> Mode 42: 640x480 @ 1 fps (yuy2)
> Mode 43: 320x240 @ 1 fps (yuy2)
> Mode 44: 160x120 @ 1 fps (yuy2)
>
> For this camera I should have only these modes :
> Device 00: USB Video Device
> Mode 00: 720x480 @ 25 fps (YUY2)
> Mode 01: 704x576 @ 25 fps (YUY2)
> Mode 02: 160x120 @ 30 fps (YUY2)
> Mode 03: 176x144 @ 30 fps (YUY2)
> Mode 04: 320x240 @ 30 fps (YUY2)
> Mode 05: 352x288 @ 30 fps (YUY2)
> Mode 06: 640x480 @ 30 fps (YUY2)
> Mode 07: 1280x1024 @ 30 fps (MJPG)
> Mode 08: 1280x960 @ 30 fps (MJPG)
> Mode 09: 1280x720 @ 30 fps (MJPG)
> Mode 10: 1024x768 @ 30 fps (MJPG)
> Mode 11: 1024x576 @ 30 fps (MJPG)
> Mode 12: 800x600 @ 30 fps (MJPG)
> Mode 13: 720x480 @ 30 fps (MJPG)
> Mode 14: 640x480 @ 30 fps (MJPG)
> ________________________________
> Centralisez tous vos comptes mails dans Hotmail ! Créez un compte Hotmail,
> c'est gratuit !
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> libvidcap-devel mailing list
> lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libvidcap-devel
>
>

[libvidcap-devel] [win32] listing device modes

[Jean C. M. <jc_...@ho...>]

I'm using the exemple.cpp source code to list all connected cameras and allmodes for them. The list is the same for all camera and doesn't give theright available modes. (It seems the lib always return me the 44 firstmode.Exemple : Device 00: USB Video DeviceMode 00: 640x480 @ 15 fps (rgb32)Mode 01: 320x240 @ 15 fps (rgb32)Mode 02: 160x120 @ 15 fps (rgb32)Mode 03: 640x480 @ 30 fps (rgb32)Mode 04: 320x240 @ 30 fps (rgb32)Mode 05: 160x120 @ 30 fps (rgb32)Mode 06: 640x480 @ 29 fps (rgb32)Mode 07: 320x240 @ 29 fps (rgb32)Mode 08: 160x120 @ 29 fps (rgb32)Mode 09: 640x480 @ 10 fps (rgb32)Mode 10: 320x240 @ 10 fps (rgb32)Mode 11: 160x120 @ 10 fps (rgb32)Mode 12: 640x480 @ 1 fps (rgb32)Mode 13: 320x240 @ 1 fps (rgb32)Mode 14: 160x120 @ 1 fps (rgb32)Mode 15: 640x480 @ 15 fps (i420)Mode 16: 320x240 @ 15 fps (i420)Mode 17: 160x120 @ 15 fps (i420)Mode 18: 640x480 @ 30 fps (i420)Mode 19: 320x240 @ 30 fps (i420)Mode 20: 160x120 @ 30 fps (i420)Mode 21: 640x480 @ 29 fps (i420)Mode 22: 320x240 @ 29 fps (i420)Mode 23: 160x120 @ 29 fps (i420)Mode 24: 640x480 @ 10 fps (i420)Mode 25: 320x240 @ 10 fps (i420)Mode 26: 160x120 @ 10 fps (i420)Mode 27: 640x480 @ 1 fps (i420)Mode 28: 320x240 @ 1 fps (i420)Mode 29: 160x120 @ 1 fps (i420)Mode 30: 640x480 @ 15 fps (yuy2)Mode 31: 320x240 @ 15 fps (yuy2)Mode 32: 160x120 @ 15 fps (yuy2)Mode 33: 640x480 @ 30 fps (yuy2)Mode 34: 320x240 @ 30 fps (yuy2)Mode 35: 160x120 @ 30 fps (yuy2)Mode 36: 640x480 @ 29 fps (yuy2)Mode 37: 320x240 @ 29 fps (yuy2)Mode 38: 160x120 @ 29 fps (yuy2)Mode 39: 640x480 @ 10 fps (yuy2)Mode 40: 320x240 @ 10 fps (yuy2)Mode 41: 160x120 @ 10 fps (yuy2)Mode 42: 640x480 @ 1 fps (yuy2)Mode 43: 320x240 @ 1 fps (yuy2)Mode 44: 160x120 @ 1 fps (yuy2)For this camera I should have only these modes : Device 00: USB Video DeviceMode 00: 720x480 @ 25 fps (YUY2)Mode 01: 704x576 @ 25 fps (YUY2)Mode 02: 160x120 @ 30 fps (YUY2)Mode 03: 176x144 @ 30 fps (YUY2)Mode 04: 320x240 @ 30 fps (YUY2)Mode 05: 352x288 @ 30 fps (YUY2)Mode 06: 640x480 @ 30 fps (YUY2)Mode 07: 1280x1024 @ 30 fps (MJPG)Mode 08: 1280x960 @ 30 fps (MJPG)Mode 09: 1280x720 @ 30 fps (MJPG)Mode 10: 1024x768 @ 30 fps (MJPG)Mode 11: 1024x576 @ 30 fps (MJPG)Mode 12: 800x600 @ 30 fps (MJPG)Mode 13: 720x480 @ 30 fps (MJPG)Mode 14: 640x480 @ 30 fps (MJPG)
_________________________________________________________________
Retouchez, classez et partagez vos photos gratuitement avec le logiciel Galerie de Photos !
http://www.windowslive.fr/galerie/

Re: [libvidcap-devel] question about v4l2 interface

[Peter G. <jpg...@gm...>]

On Fri, Jun 20, 2008 at 8:53 PM, Rory Petty <ror...@gm...> wrote:
> Peter,
>
> Thanks for the reply. I have a camera that has an empia 2760 chip and
> is supported as a UVC device under linux using the uvcvideo kernel
> module. From what I can tell however, it only shows up as a V4L2
> device. For example, I cannot get it to show up using either
> vidcaptester or simplegrab, as it provides the error can't find device
> /dev/video0. I also tried several other utilities such as xawtv,
> tvtime and camstream and none of them can see the video device.
> However, I can see the video fine without any configuration using
> ekiga or skype. From my reading of various forums, people seem to
> indicate this is because the uvc video project is only implementing a
> v4l2 interface. Any ideas how i can get a v4l2 device to show up in a
> program like vidcaptester using only v4l? I know there is a v4l2 to
> v4l compatibility layer, but my understanding is that it does not
> implement all the mappings and that the code is getting pretty stale.

That makes sense. I suppose one way to go would be to write a v4l2
source api backend for libvidcap. In other words, write sapi_v4l2.c.
Alternatively, it seems like it would be possible to extend the
existing sapi_v4l.c to first attempt to use the v4l2 interfaces and
then fallback to v4l if there are no v4l2 devices available. Offhand,
I'm not sure which approach would be better.

I am not going to have the bandwidth to work on this myself anytime
soon (or even later), but patches are welcome.

Thanks,
Pete

Re: [libvidcap-devel] question about v4l2 interface

[Peter G. <jpg...@gm...>]

Hi Rory,

On Thu, Jun 19, 2008 at 8:13 PM, Rory Petty <ror...@gm...> wrote:
> Is there any plan to develop a v4l2 interface? Most of the cameras I
> have use v4l2 now days.

I haven't looked in-depth at the differences between v4l and v4l2
lately, but as I recall there was not a clear benefit in using the
additional stuff that v4l2 provides over v4l for what libvidcap was
trying to accomplish.  All those v4l2 devices are backwards compatible
with v4l, so using the older v4l API actually allows for somewhat more
device support than using v4l2.

Is this different than your understanding? Are there features in v4l2
that might benefit libvidcap?

Thanks,
Pete