| 
      
      
      From: SinaVIP <da...@vi...> - 2006-11-14 12:50:11
       | 
| Dear Sir
 
   
    I wanna use LibUSB access USB camera and grab the video data. But
usb_set_configuration function alwayes said "CRC Error" ,Why? 
Does LibUSB not support USB Camera device ? 
 
 
Thanks
Danny
-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.409 / Virus Database: 268.14.5/533 - Release Date: 2006-11-13
 
 | 
| 
      
      
      From: Bertrik S. <be...@si...> - 2006-11-14 17:39:59
       | 
| -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 SinaVIP wrote: > Dear Sir > > > I wanna use LibUSB access USB camera and grab the video data. But > usb_set_configuration function alwayes said "CRC Error" ,Why? > Does LibUSB not support USB Camera device ? As far as I know, libusb cannot do isochronous transfers yet (which are used by a lot of webcams). What kind of protocol does your camera use? Apparently, some of the newer (and expensive) ones use the USB video class standard. CRC error does not make sense to me in response to a usb_set_configuration call. What argument do you use? It is in line with the device descriptor? Kind regards, Bertrik -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFWf9GETD6mlrWxPURAqdFAKC6pZ7RPj18HbK+GK+DAopDcw2h2wCfagdo AAN4fY+ta1uaiEKIxub248Y= =u8EV -----END PGP SIGNATURE----- | 
| 
      
      
      From: SinaVIP <da...@vi...> - 2006-11-15 02:46:51
       | 
| Hi My camera use isochronous transfer protocol.=20 usb_set_debug(4); usb_init(); usb_find_busses(); =09 -----=D3=CA=BC=FE=D4=AD=BC=FE----- =B7=A2=BC=FE=C8=CB: lib...@li... [mailto:lib...@li...] =B4=FA=B1=ED = Bertrik Sikken =B7=A2=CB=CD=CA=B1=BC=E4: 2006=C4=EA11=D4=C215=C8=D5 1:39 =CA=D5=BC=FE=C8=CB: lib...@li... =D6=F7=CC=E2: Re: [Libusb-win32-devel] Does LibUSB not support USB = Camera device ? -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 SinaVIP wrote: > Dear Sir > =20 > =20 > I wanna use LibUSB access USB camera and grab the video data. But=20 > usb_set_configuration function alwayes said "CRC Error" ,Why? > Does LibUSB not support USB Camera device ? As far as I know, libusb cannot do isochronous transfers yet (which are = used by a lot of webcams). What kind of protocol does your camera use? Apparently, some of the newer (and expensive) ones use the USB video = class standard. CRC error does not make sense to me in response to a = usb_set_configuration call. What argument do you use? It is in line with the device descriptor? Kind regards, Bertrik -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFWf9GETD6mlrWxPURAqdFAKC6pZ7RPj18HbK+GK+DAopDcw2h2wCfagdo AAN4fY+ta1uaiEKIxub248Y=3D =3Du8EV -----END PGP SIGNATURE----- -------------------------------------------------------------------------= SF.net email is sponsored by: A Better Job is Waiting for You - Find it = Now. Check out Slashdot's new job board. Browse through tons of technical = jobs posted by companies looking to hire people just like you. http://jobs.slashdot.org/ _______________________________________________ Libusb-win32-devel mailing list Lib...@li... https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.409 / Virus Database: 268.14.5/534 - Release Date: = 2006-11-14 =20 --=20 No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.409 / Virus Database: 268.14.5/534 - Release Date: = 2006-11-14 =20 | 
| 
      
      
      From: SinaVIP <da...@vi...> - 2006-11-15 02:52:04
       | 
|  Hi
   My camera use  isochronous transfer protocol.=20
DLL version:	0.1.12.0
Driver version:	0.1.12.0
bus/device  idVendor/idProduct
bus-0/\\.\libusb0-0001--0x0ac8-0x301b     0AC8/301B
- Manufacturer : Vimicro Corp.
- Product      : PC Camera
  wTotalLength:         193
  bNumInterfaces:       1
  bConfigurationValue:  1
  iConfiguration:       0
  bmAttributes:         a0h
  MaxPower:             80
    bInterfaceNumber:   0
    bAlternateSetting:  0
    bNumEndpoints:      2
    bInterfaceClass:    255
    bInterfaceSubClass: 255
    bInterfaceProtocol: 255
    iInterface:         0
      bEndpointAddress: 81h
      bmAttributes:     01h
      wMaxPacketSize:   0
      bInterval:        1
      bRefresh:         0
      bSynchAddress:    0
      bEndpointAddress: 82h
      bmAttributes:     03h
      wMaxPacketSize:   8
      bInterval:        10
      bRefresh:         0
      bSynchAddress:    0
    bInterfaceNumber:   0
    bAlternateSetting:  1
    bNumEndpoints:      2
    bInterfaceClass:    255
    bInterfaceSubClass: 255
    bInterfaceProtocol: 255
    iInterface:         0
      bEndpointAddress: 81h
      bmAttributes:     01h
      wMaxPacketSize:   128
      bInterval:        1
      bRefresh:         0
      bSynchAddress:    0
      bEndpointAddress: 82h
      bmAttributes:     03h
      wMaxPacketSize:   8
      bInterval:        10
      bRefresh:         0
      bSynchAddress:    0
    bInterfaceNumber:   0
    bAlternateSetting:  2
    bNumEndpoints:      2
    bInterfaceClass:    255
    bInterfaceSubClass: 255
    bInterfaceProtocol: 255
    iInterface:         0
      bEndpointAddress: 81h
      bmAttributes:     01h
      wMaxPacketSize:   192
      bInterval:        1
      bRefresh:         0
      bSynchAddress:    0
      bEndpointAddress: 82h
      bmAttributes:     03h
      wMaxPacketSize:   8
      bInterval:        10
      bRefresh:         0
      bSynchAddress:    0
    bInterfaceNumber:   0
    bAlternateSetting:  3
    bNumEndpoints:      2
    bInterfaceClass:    255
    bInterfaceSubClass: 255
    bInterfaceProtocol: 255
    iInterface:         0
      bEndpointAddress: 81h
      bmAttributes:     01h
      wMaxPacketSize:   256
      bInterval:        1
      bRefresh:         0
      bSynchAddress:    0
      bEndpointAddress: 82h
      bmAttributes:     03h
      wMaxPacketSize:   8
      bInterval:        10
      bRefresh:         0
      bSynchAddress:    0
    bInterfaceNumber:   0
    bAlternateSetting:  4
    bNumEndpoints:      2
    bInterfaceClass:    255
    bInterfaceSubClass: 255
    bInterfaceProtocol: 255
    iInterface:         0
      bEndpointAddress: 81h
      bmAttributes:     01h
      wMaxPacketSize:   384
      bInterval:        1
      bRefresh:         0
      bSynchAddress:    0
      bEndpointAddress: 82h
      bmAttributes:     03h
      wMaxPacketSize:   8
      bInterval:        10
      bRefresh:         0
      bSynchAddress:    0
    bInterfaceNumber:   0
    bAlternateSetting:  5
    bNumEndpoints:      2
    bInterfaceClass:    255
    bInterfaceSubClass: 255
    bInterfaceProtocol: 255
    iInterface:         0
      bEndpointAddress: 81h
      bmAttributes:     01h
      wMaxPacketSize:   512
      bInterval:        1
      bRefresh:         0
      bSynchAddress:    0
      bEndpointAddress: 82h
      bmAttributes:     03h
      wMaxPacketSize:   8
      bInterval:        10
      bRefresh:         0
      bSynchAddress:    0
    bInterfaceNumber:   0
    bAlternateSetting:  6
    bNumEndpoints:      2
    bInterfaceClass:    255
    bInterfaceSubClass: 255
    bInterfaceProtocol: 255
    iInterface:         0
      bEndpointAddress: 81h
      bmAttributes:     01h
      wMaxPacketSize:   768
      bInterval:        1
      bRefresh:         0
      bSynchAddress:    0
      bEndpointAddress: 82h
      bmAttributes:     03h
      wMaxPacketSize:   8
      bInterval:        10
      bRefresh:         0
      bSynchAddress:    0
    bInterfaceNumber:   0
    bAlternateSetting:  7
    bNumEndpoints:      2
    bInterfaceClass:    255
    bInterfaceSubClass: 255
    bInterfaceProtocol: 255
    iInterface:         0
      bEndpointAddress: 81h
      bmAttributes:     01h
      wMaxPacketSize:   896
      bInterval:        1
      bRefresh:         0
      bSynchAddress:    0
      bEndpointAddress: 82h
      bmAttributes:     03h
      wMaxPacketSize:   8
      bInterval:        10
      bRefresh:         0
      bSynchAddress:    0
=20
-----=D3=CA=BC=FE=D4=AD=BC=FE-----
=B7=A2=BC=FE=C8=CB: lib...@li...
[mailto:lib...@li...] =B4=FA=B1=ED =
Bertrik
Sikken
=B7=A2=CB=CD=CA=B1=BC=E4: 2006=C4=EA11=D4=C215=C8=D5 1:39
=CA=D5=BC=FE=C8=CB: lib...@li...
=D6=F7=CC=E2: Re: [Libusb-win32-devel] Does LibUSB not support USB =
Camera device ?
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
SinaVIP wrote:
> Dear Sir
> =20
>  =20
>     I wanna use LibUSB access USB camera and grab the video data. But=20
> usb_set_configuration function alwayes said "CRC Error" ,Why?
> Does LibUSB not support USB Camera device ?
As far as I know, libusb cannot do isochronous transfers yet (which are =
used
by a lot of webcams). What kind of protocol does your camera use?
Apparently, some of the newer (and expensive) ones use the USB video =
class
standard.
CRC error does not make sense to me in response to a =
usb_set_configuration
call. What argument do you use?
It is in line with the device descriptor?
Kind regards,
Bertrik
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFFWf9GETD6mlrWxPURAqdFAKC6pZ7RPj18HbK+GK+DAopDcw2h2wCfagdo
AAN4fY+ta1uaiEKIxub248Y=3D
=3Du8EV
-----END PGP SIGNATURE-----
-------------------------------------------------------------------------=
SF.net email is sponsored by: A Better Job is Waiting for You - Find it =
Now.
Check out Slashdot's new job board. Browse through tons of technical =
jobs
posted by companies looking to hire people just like you.
http://jobs.slashdot.org/
_______________________________________________
Libusb-win32-devel mailing list
Lib...@li...
https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.409 / Virus Database: 268.14.5/534 - Release Date: =
2006-11-14
=20
--=20
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.409 / Virus Database: 268.14.5/534 - Release Date: =
2006-11-14
=20
 | 
| 
      
      
      From: Bertrik S. <be...@si...> - 2006-11-15 23:01:48
       | 
| -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 SinaVIP wrote: > Hi > > My camera use isochronous transfer protocol. In that case, I think it will be hard to get it to work. You can try googling if perhaps some linux hacker has figured out the webcam protocol. Kind regards, Bertrik -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFW5xLETD6mlrWxPURAkjpAKC5clgoKEWE8CmDCeB31BLmbM1vRwCeL5OQ BXUb1394gl85v/iKprR0gMY= =+1Es -----END PGP SIGNATURE----- |