Frage von Eckart Pluennecke:
Hello
I've run out while Langer probiert, my video camera NV-GS 180 as a webcam
under Suse 10.3 to run. The camera is in USB port in the
Webcam mode. After connecting the camera and installing the module
uvcvideo does it almost synonymous, but only almost.
The only program that shows me a picture, is luvcview. By
Call of luvcview-d / dev / video-I 12 do I get a picture with about 12 fps
to see and luvcview reports:
luvcview 0.2.4
SDL information:
Video driver: x11
A window manager is available
Device information:
Device path: / dev / video
Stream settings:
Frame format: MJPG
Frame size: 320x240 (size 640x480 requested is not supported by device)
Frame rate: 25 / 2 fps (requested frame rate 12 fps is not supported by
device)
Where does that also.
But as in Kopete comes only a black picture. vlc reports "[00000322] v4l
demuxer error: can not get channel infos (The argument is valid ¼ Hungarian). "xawtv
¤ talks is something multilingual, but for me unverstà r ¤ TALLY FRIENDLY:
This is xawtv-3.95, running on Linux/i686 (2.6.22.18-0.2-bigsmp)
xinerama 0: 1680x1050 0 0
/ dev/video0 [v4l2]: no overlay support
v4l-conf had some trouble, trying to continue anyway
ioctl: VIDIOC_G_STD (std% 0xb7fb65dfbfaf8a60
[PAL_D, PAL_D1, PAL_N, PAL_60,?, SECAM_B, SECAM_D, SECAM_G, SECAM_H, SECAM_K1? ATSC_8_VSB, ATSC_16_VSB
(null) (null) (null) (null) (null) (null) (null) (null) (null) (null)
(null) (null) (null) (null) (null) (null) (null) (null) (null) (null)
(null) (null) (null) (null) (null) (null) (null) (null) (null) (null)]):
The argument is valid Hungarian ¼
ioctl: VIDIOC_S_STD (std% 0x0 []): The argument is valid Hungarian ¼
no way to get: 384x288 32 bit TrueColor (LE: BGR)
And now I stand on the hose and said do not know where
further search. Could it be that it s.der GÃ ¶ sse of 320x240, or the
somewhat peculiar 25 / 2 fps? Or that the whole matter as MJPG?
¼ rde I would glad if someone could tell kà ¶ how I the video image,
which is obviously in the PC arrives in kopete or vlc or similar ¤ Ã
get.
Thank you in advance and Grà ¼ sse from the Emmental
Ecki
Antwort von Dirk Thierbach:
Eckart Plünnecke
wrote:
> I've run out while Langer probiert, my video camera NV-GS 180 as a webcam
> Under Suse 10.3 to run. The camera is in USB port in the
> Webcam mode. After connecting the camera and installing the module
> Uvcvideo works almost synonymous, but only almost.
> The only program that shows me a picture, is luvcview.
[...]
> But for example in Kopete comes only a black picture. vlc reports "[00000322] v4l
> Demuxer error: can not get channel infos (The argument is invalid). "Xawtv
> Is a little talkative, but to me incomprehensible:
> Ioctl: VIDIOC_G_STD (std% 0xb7fb65dfbfaf8a60
[...]
> The argument is invalid
> And now I stand on the hose and said do not know where
> Continue looking. Could it be that it s.der the size of 320x240, or the
> Somewhat peculiar 25 / 2 fps? Or that the whole matter as MJPG?
> I would be glad if someone could tell me how I use the video image,
> Which is obviously in the PC arrives in kopete or vlc or something similar
> Get.
I can not tell you, but I can tell you roughly what
goes wrong: The application programs (vlc, etc.) communicate with the
Drivers (= kernel module) about so-called "ioctl" s. The Drivers, the
Because you've loaded, but support at least one ioctl, namely
"VIDIOC_G_STD" (asked as to whether the picture in PAL / NTSC / SECAM, etc. arrives)
not. Then get the most apparently Programs a
Hiccups and no longer know quite what to do.
I have no Suse, and synonymous know "uvcvideo", but the name
seems "luvcview" so closely related to be used and therefore
possibly only the iotcl's, the driver understands synonymous.
If not someone else who knows better, a little smarter
change, would I'll find out what Drivers (= what
Kernel-module) there really is active (or my test with you
"Module" above the kernel module?). The source code tells you
synonymous then why VIDIOC_G_STD not supported (if you do not C
can read, does it perhaps synonymous in a friendly e-mail s.die
Authors of the module, which are synonymous in the source code in it.) Detailed
Read any documentation provided with the kernel module is to
harms not synonymous.
From the situation of her is "the driver has its own
ioctl interface, and supports v4l/v4l2 not at all "to" times
just a half-dozen lines of C source code in the insert, then
running's "everything in it. Should we stop to see.
- Dirk
Antwort von Eckart Pluennecke:
Dirk Thierbach wrote:
> Eckart Plünnecke wrote:
>> I've run out while Langer probiert, my video camera NV-GS 180 as
>> Webcam on Suse 10.3 to run. The Camera is in
>> USB port in webcam mode. After connecting the camera and Installation
>> Uvcvideo module works almost synonymous, but only almost.
>
>> The only program that shows me a picture, is luvcview.
> [...]
>> But in Kopete for example, only a black picture. vlc reports "[00000322]
>> V4l demuxer error: can not get channel infos (The argument is valid ¼ Hungarian) ".
>> Xawtv is multilingual ¤ talks, but for me unverstà r ¤ TALLY FRIENDLY:
>
>> Ioctl: VIDIOC_G_STD (std% 0xb7fb65dfbfaf8a60
> [...]
>> The argument is valid Hungarian ¼
>
>> And now I stand on the hose and said do not know where
>> Continue looking. Could it be that it s.der GÃ ¶ sse of 320x240, or
>> The somewhat peculiar 25 / 2 fps? Or that the whole than MJPG
>> Arrives?
>
>> I would ¼ rde glad if someone could tell kà ¶, as I
>> Video image, which is obviously in the PC arrives in kopete or vlc or
>> Ã ¤ Similar receive.
>
> I can not tell you, but I can tell you roughly what
> Goes wrong: The application programs (vlc, etc.) communicate with the
> Drivers (= kernel module) about so-called "ioctl" s. The Drivers, the
> Because you've loaded, but support at least one ioctl, namely
> "VIDIOC_G_STD" (asked as to whether the picture in PAL / NTSC / SECAM, etc. arrives)
> Not. Then get the most apparently Programs a
> Hiccups and no longer know quite what to do.
Interesting, I am not come
>
> I have no Suse, and synonymous know "uvcvideo", but the name
> Seems "luvcview" so closely related to be used and therefore
> Possibly the only iotcl's, the driver understands synonymous.
>
> Unless someone else who knows better, a little smarter
> Change, would I'll find out what Drivers (= what
> Kernel module) that really is active (or my test with you
> "Module" above the kernel module?). The source code tells you
Yes, "uvcvideo" is the kernel module and dates of
http://linux-uvc.berlios.de (at Packman's an rpm reading). That
Kernel module is loaded and is synonymous with v4l used:
Eckart @ linux: ~> lsmod | grep UVC
uvcvideo 686160
compat_ioctl32 176641 uvcvideo
videodev 427522 uvcvideo, saa7146_vv
v4l2_common328963 uvcvideo, saa7146_vv, videodev
v4l1_compat286763 uvcvideo, saa7146_vv, videodev
usbcore 1368127
snd_usb_audio, snd_usb_lib, uvcvideo, usb_storage, uhci_hcd, ehci_hcd
luvcview dates of
http://www.quickcamteam.net/software/linux/v4l2-software/luvcview/
and announces the call of luvcview-L (to be valid
Video formats queried), the following:
luvcview 0.2.4
SDL information:
Video driver: x11
A window manager is available
Device information:
Device path: / dev/video0
/ dev/video0 does not support read i / o
(Pixel format = 'MJPG', description = 'MJPEG')
(Discrete: width = 320, height = 240)
Time interval between frame: (min (2 / 25) .. max (2 / 25) /
stepsize (1 / 10000000)),
Why there is "/ dev/video0 does not support read i / o" is not synonymous to me
entirely clear. Perhaps it's because the other terminals Programs
If I luvcview à ¼ brige the parameter fà ¼ r your framerate (-i 12) do not
, then goodbye synonymous and the program reports only:
Unable to set frame rate: Input / output error
V4l2 init failed! exit fatal
Apparently the program recognizes not automagically Framrate of the devices.
> Synonymous then why VIDIOC_G_STD not supported (if you do not C
> Read it, does it perhaps synonymous in a friendly e-mail s.die
> Authors of the module, which are synonymous in the source code in it.) Detailed
> Read any documentation provided with the kernel module is to
> Harms not synonymous.
In the mailing of the Drivers project gabs last year schonmal a
Question because of the same camera, but unfortunately no definite Kla ¤ rung.
But an inquiry into the mailing list can not hurt.
Antwort von Dirk Thierbach:
Eckart Plünnecke wrote:
> Yes, "uvcvideo" is the kernel module and dates of
> http://linux-uvc.berlios.de (at Packman's an rpm reading).
Ok. Quick Search in the v4l2 standard definition:
http://www.linuxtv.org/downloads/video4linux/API/V4L2_API/spec-single/v4l2.html
: To query and select the standard used by the current video input or
: Output applications call the VIDIOC_G_STD and VIDIOC_S_STD ioctl,
: Respectively. The received standard can be sensed with the
: VIDIOC_QUERYSTD ioctl. Note of all these parameters is a pointer IOCTLs
: V4l2_std_id to a type (a standard set), not s.index into the standard
: Enumeration [7]. Drivers must implement all standard video when IOCTLs
: Has the device one or more video inputs or outputs.
:
Special rules apply to USB cameras where the notion of video
: Standards makes little sense. More generally any capture device,
: Output devices accordingly, which is
:
- Incapable of capturing fields or frames s.the nominal rate of the
: Video standard, or
: - Where timestamps refer to the instant the field or frame which
: Received by the driver, not the capture time, or
:
: - Where sequence numbers refer to the frames received by the driver,
: Not the captured frames.
:
: Here the driver shall set the std field of struct v4l2_input and
: Struct v4l2_output to zero, the VIDIOC_G_STD, VIDIOC_S_STD,
: VIDIOC_QUERYSTD and IOCTLs VIDIOC_ENUMSTD shall return the EINVAL
: Errorcode [8].
The Teiber code does more or less, but forgets to make the
Fields to zero:
http://svn.berlios.de/svnroot/repos/linux-uvc/linux-uvc/trunk/uvc_v4l2.c
/ * Analog video standards make no sense for digital cameras. * /
VIDIOC_ENUMSTD case:
VIDIOC_QUERYSTD case:
VIDIOC_G_STD case:
VIDIOC_S_STD case:
VIDIOC_OVERLAY case:
VIDIOC_ENUMAUDIO case:
VIDIOC_ENUMAUDOUT case:
VIDIOC_ENUMOUTPUT case:
uvc_trace (UVC_TRACE_IOCTL, "Unsupported ioctl 0x x \ n", cmd);
return-EINVAL;
That explains the error in xawtv:
: Ioctl: VIDIOC_G_STD (std% 0xb7fb65dfbfaf8a60
: [PAL_D, PAL_D1, PAL_N, PAL_60,?, SECAM_B, SECAM_D, SECAM_G, SECAM_H, SECAM_K1,
:? ATSC_8_VS, B, ATSC_16_VSB
: (Null) (null) (null) (null) (null) (null) (null) (null) (null) (null)
: (Null) (null) (null) (null) (null) (null) (null) (null) (null) (null)
: (Null) (null) (null) (null) (null) (null) (null) (null) (null) (null)]):
: The argument is invalid
: Ioctl: VIDIOC_S_STD (std% 0x0 []): The argument is invalid
"The argument is invalid" is probably EINVAL, and is apparently
not as the exception for USB cameras detected. Perhaps, therefore,
std because 0xb7fb65dfbfaf8a60% non-zero. Possible remedies also:
1) Change Drivers, so that the fields he really set to zero.
2) The application programs to inspect whether the exemption for USB cameras
properly processed.
For the latter one should first look at the latest versions provide.
According to wiki works at least one older version of Kopete not:
http://openfacts.berlios.de/index-en.phtml?title%Linux UVC
Recent versions of Kopete and then xawtv seems to work.
If it still hangs, contact the developer, and
Problem with the above details describe. Or better: a spendier
Friend who can program in your home to a beer, and let
it quickly write the patch and try it directly.
Can still of course be that only the first stumbling block is
and it still hangs s.anderen things.
- Dirk
