Hello

I didn't read luvcview output, sorry hehe.
Of course, Ian is right :D


Good bye
Palmax


2010/4/10  <[email protected]>:
> Send Linux-uvc-devel mailing list submissions to
>        [email protected]
>
> To subscribe or unsubscribe via the World Wide Web, visit
>        https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
> or, via email, send a message with subject or body 'help' to
>        [email protected]
>
> You can reach the person managing the list at
>        [email protected]
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Linux-uvc-devel digest..."
>
>
> Today's Topics:
>
>   1. Re: 16MP or 1.3MP? (Paulo Assis)
>   2. Re: Linux-uvc-devel Digest, Vol 46, Issue 9 (Palmax Maverick)
>   3. Re: 16MP or 1.3MP? (Ian Latter)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 9 Apr 2010 12:15:25 +0100
> From: Paulo Assis <[email protected]>
> To: Ian Latter <[email protected]>
> Cc: [email protected]
> Subject: Re: [Linux-uvc-devel] 16MP or 1.3MP?
> Message-ID:
>        <[email protected]>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hi,
> >From your lsusb output the camera max resolution is 640x480 (even for
> still image)
> If you can get an higher resolution in windows, I guess it's probably
> trough some sort of interpolation technique.
> I doubt however that the quality is any good.
> It can also be that the camera uses some sort of "extra" proprietary
> protocol, but if it does, it doesn't seem to reported .
>
> Best Regards,
> Paulo
>
> 2010/4/9 Ian Latter <[email protected]>:
>> Hello,
>>
>>
>> ?Its a been a long time since I was last working with UVC,
>> but I found a camera that I couldn't resist, and you're in the
>> mainline kernel now .. and I'd like to do some aerial photos
>> from my embedded platform ..
>>
>> ?You have a 093a:2700 device listed on your site as
>> working (and my testing confirms this);
>>
>> ? ?http://linux-uvc.berlios.de/
>> ? ?093a:2700
>> ? ? ? ?- iSonic W002
>> ? ? ? ?- A4Tech PK-635K
>> ? ? ? ?- Digital Innovations 1.3MP Webcam
>> ? ? ? ?--> Pixart Imaging
>>
>> ?Confirmed in Fedora 12 (kernel 2.6.31 - dmesg output);
>> ? ?usb 1-1: new high speed USB device using ehci_hcd
>> ? ?and address 27
>> ? ?usb 1-1: New USB device found, idVendor=093a,
>> ? ?idProduct=2700
>> ? ?usb 1-1: New USB device strings: Mfr=16, Product=96,
>> ? ?SerialNumber=0
>> ? ?usb 1-1: Product: USB2.0_Camera
>> ? ?usb 1-1: Manufacturer: PixArt Imaging Inc.
>> ? ?usb 1-1: configuration #1 chosen from 1 choice
>> ? ?Linux video capture interface: v2.00
>> ? ?uvcvideo: Found UVC 1.00 device USB2.0_Camera
>> ? ?(093a:2700)
>> ? ?input: USB2.0_Camera as /devices/pci0000:00/0000:
>> ? ?00:02.1/usb1/1-1/1-1:1.0/input/input6
>> ? ?usbcore: registered new interface driver uvcvideo
>> ? ?USB Video Class driver (v0.1.0)
>> ? ?ALSA sound/usb/usbaudio.c:1300: current rate
>> ? ?6292992 is different from the runtime rate 16000
>> ? ?ALSA sound/usb/usbaudio.c:1300: current rate 34560
>> ? ?is different from the runtime rate 48000
>> ? ?usbcore: registered new interface driver snd-usb-audio
>> ? ?ALSA sound/usb/usbaudio.c:1300: current rate 33024
>> ? ?is different from the runtime rate 48000
>> ? ?ALSA sound/usb/usbaudio.c:1300: current rate 33280
>> ? ?is different from the runtime rate 48000
>>
>>
>> ?luvcview output looks okay (save that massive fraction);
>> ? ?# ./luvcview -L
>> ? ?luvcview version 0.2.1
>> ? ?Video driver: x11
>> ? ?A window manager is available
>> ? ?video /dev/video0
>> ? ?/dev/video0 does not support read i/o
>> ? ?{ pixelformat = 'YUYV', description = 'YUV 4:2:2 (YUYV)' }
>> ? ?{ discrete: width = 640, height = 480 }
>> ? ? ? ?Time interval between frame: 1/30, 1/20, 1/15, 1/10,
>> ? ? ? ?1/5, 1/1,
>> ? ?{ discrete: width = 320, height = 240 }
>> ? ? ? ?Time interval between frame: 1/30, 1/20, 1/15, 1/10,
>> ? ? ? ?1589/15625, 1/1,
>> ? ?{ discrete: width = 160, height = 120 }
>> ? ? ? ?Time interval between frame: 1/30, 1/20, 1/15, 1/10,
>> ? ? ? ?1589/15625, 1/1,
>> ? ?{ discrete: width = 176, height = 144 }
>> ? ? ? ?Time interval between frame: 1/30, 1/20, 1/15, 1/10,
>> ? ? ? ?1589/15625, 1/1,
>> ? ?{ discrete: width = 352, height = 288 }
>> ? ? ? ?Time interval between frame: 1/30, 1/20, 1/15, 1/10,
>> ? ? ? ?1589/15625, 1/1,
>>
>>
>> And I can see my ugly mug at 640x480 via the native
>> "Cheese Webcam Booth" app - no magic required. ?Nice.
>>
>>
>> The issue that I have is that this camera is sold as a 16
>> (well, 16.0) mega-pixel camera;
>>
>> ? ?Speed 16.0Mega Pixel USB2.0 Webcam S4850v
>> ? ?https://www.pcdiy.com.au/product_info.php?products_id=9757
>>
>> ? ?TECHNICAL SPECIFICATION
>> ? ? ?- Speed 16.0Mega Pixel USB2.0 Webcam
>> ? ? ?- Effective Static Pixels 16 Mega Pixel
>> ? ? ?- Maximum Resolution : 4608 x 3456
>> ? ? ?- Output Format: YUY2
>> ? ? ?- Max Frame Rate: 30fps
>> ? ? ?- USB 2.0 compatible
>> ? ? ?- White balance: Auto
>> ? ? ?- Auto Exposure ( AE ): Auto
>>
>>
>> ?While I understand that I would get 16MP in a photo,
>> I don't see the option to take a photo greater than
>> 640x480 (the 1.3MP that is reported on the linux-uvc
>> compatibility chart).
>>
>> ?Any thoughts on how to poke this device to get the
>> higher resolutions? ?Or is it possible that they're going
>> outside of UVC (to something proprietary) to get those
>> resolutions? ?Or are they doing something bodgy in
>> the win32 software by collating 16 to 32 frames of 1.3MP
>> shots to "assemble" a 16MP image?
>>
>> ?I'm confident that my reseller is above board - the
>> specifications on that site match those on the back of
>> the product's packaging. ?I obviously can't speak for
>> the whole-saler or upstream there-after ..
>>
>> ?lsusb -v output is attached and is consistent with
>> luvcview output.
>>
>> ?The device does not have an external power option.
>>
>>
>> Thanks for your help,
>>
>>
>>
>>
>>
>> --
>> Ian Latter
>> Late night coder ..
>> http://midnightcode.org/
>>
>> _______________________________________________
>> Linux-uvc-devel mailing list
>> [email protected]
>> https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
>>
>>
>
>
> ------------------------------
>
> Message: 2
> Date: Fri, 9 Apr 2010 13:25:12 +0200
> From: Palmax Maverick <[email protected]>
> To: [email protected]
> Subject: Re: [Linux-uvc-devel] Linux-uvc-devel Digest, Vol 46, Issue 9
> Message-ID:
>        <[email protected]>
> Content-Type: text/plain; charset=UTF-8
>
> Hello there,
>
> I want to speak about "Maximum Resolution : 4608 x 3456". I think that
> it could get this huge resolution only as a Still Image.
> You should remember that still image capture is not include in
> linux-uvc (you may read it in http://linux-uvc.berlios.de/#status ).
> But I'm studying Still Image for getting this feature to linux-uvc.
>
> 32$ is a too good price for a cool webcam... I don't know this manufacture.
>
> If you buy it, you would send us its lsusb description for
> understanding this device.
>
>
> Good bye
> Palmax
>
> 2010/4/9  <[email protected]>:
>> Send Linux-uvc-devel mailing list submissions to
>> ? ? ? [email protected]
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>> ? ? ? ?https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
>> or, via email, send a message with subject or body 'help' to
>> ? ? ? [email protected]
>>
>> You can reach the person managing the list at
>> ? ? ? [email protected]
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of Linux-uvc-devel digest..."
>>
>>
>> Today's Topics:
>>
>> ? 1. 16MP or 1.3MP? (Ian Latter)
>>
>>
>> ----------------------------------------------------------------------
>>
>> Message: 1
>> Date: Fri, 09 Apr 2010 20:40:41 +1000
>> From: "Ian Latter" <[email protected]>
>> To: [email protected]
>> Subject: [Linux-uvc-devel] 16MP or 1.3MP?
>> Message-ID: <[email protected]>
>> Content-Type: text/plain; charset="us-ascii"
>>
>> Hello,
>>
>>
>> ?Its a been a long time since I was last working with UVC,
>> but I found a camera that I couldn't resist, and you're in the
>> mainline kernel now .. and I'd like to do some aerial photos
>> from my embedded platform ..
>>
>> ?You have a 093a:2700 device listed on your site as
>> working (and my testing confirms this);
>>
>> ? ?http://linux-uvc.berlios.de/
>> ? ?093a:2700
>> ? ? ? ?- iSonic W002
>> ? ? ? ?- A4Tech PK-635K
>> ? ? ? ?- Digital Innovations 1.3MP Webcam
>> ? ? ? ?--> Pixart Imaging
>>
>> ?Confirmed in Fedora 12 (kernel 2.6.31 - dmesg output);
>> ? ?usb 1-1: new high speed USB device using ehci_hcd
>> ? ?and address 27
>> ? ?usb 1-1: New USB device found, idVendor=093a,
>> ? ?idProduct=2700
>> ? ?usb 1-1: New USB device strings: Mfr=16, Product=96,
>> ? ?SerialNumber=0
>> ? ?usb 1-1: Product: USB2.0_Camera
>> ? ?usb 1-1: Manufacturer: PixArt Imaging Inc.
>> ? ?usb 1-1: configuration #1 chosen from 1 choice
>> ? ?Linux video capture interface: v2.00
>> ? ?uvcvideo: Found UVC 1.00 device USB2.0_Camera
>> ? ?(093a:2700)
>> ? ?input: USB2.0_Camera as /devices/pci0000:00/0000:
>> ? ?00:02.1/usb1/1-1/1-1:1.0/input/input6
>> ? ?usbcore: registered new interface driver uvcvideo
>> ? ?USB Video Class driver (v0.1.0)
>> ? ?ALSA sound/usb/usbaudio.c:1300: current rate
>> ? ?6292992 is different from the runtime rate 16000
>> ? ?ALSA sound/usb/usbaudio.c:1300: current rate 34560
>> ? ?is different from the runtime rate 48000
>> ? ?usbcore: registered new interface driver snd-usb-audio
>> ? ?ALSA sound/usb/usbaudio.c:1300: current rate 33024
>> ? ?is different from the runtime rate 48000
>> ? ?ALSA sound/usb/usbaudio.c:1300: current rate 33280
>> ? ?is different from the runtime rate 48000
>>
>>
>> ?luvcview output looks okay (save that massive fraction);
>> ? ?# ./luvcview -L
>> ? ?luvcview version 0.2.1
>> ? ?Video driver: x11
>> ? ?A window manager is available
>> ? ?video /dev/video0
>> ? ?/dev/video0 does not support read i/o
>> ? ?{ pixelformat = 'YUYV', description = 'YUV 4:2:2 (YUYV)' }
>> ? ?{ discrete: width = 640, height = 480 }
>> ? ? ? ?Time interval between frame: 1/30, 1/20, 1/15, 1/10,
>> ? ? ? ?1/5, 1/1,
>> ? ?{ discrete: width = 320, height = 240 }
>> ? ? ? ?Time interval between frame: 1/30, 1/20, 1/15, 1/10,
>> ? ? ? ?1589/15625, 1/1,
>> ? ?{ discrete: width = 160, height = 120 }
>> ? ? ? ?Time interval between frame: 1/30, 1/20, 1/15, 1/10,
>> ? ? ? ?1589/15625, 1/1,
>> ? ?{ discrete: width = 176, height = 144 }
>> ? ? ? ?Time interval between frame: 1/30, 1/20, 1/15, 1/10,
>> ? ? ? ?1589/15625, 1/1,
>> ? ?{ discrete: width = 352, height = 288 }
>> ? ? ? ?Time interval between frame: 1/30, 1/20, 1/15, 1/10,
>> ? ? ? ?1589/15625, 1/1,
>>
>>
>> And I can see my ugly mug at 640x480 via the native
>> "Cheese Webcam Booth" app - no magic required. ?Nice.
>>
>>
>> The issue that I have is that this camera is sold as a 16
>> (well, 16.0) mega-pixel camera;
>>
>> ? ?Speed 16.0Mega Pixel USB2.0 Webcam S4850v
>> ? ?https://www.pcdiy.com.au/product_info.php?products_id=9757
>>
>> ? ?TECHNICAL SPECIFICATION
>> ? ? ?- Speed 16.0Mega Pixel USB2.0 Webcam
>> ? ? ?- Effective Static Pixels 16 Mega Pixel
>> ? ? ?- Maximum Resolution : 4608 x 3456
>> ? ? ?- Output Format: YUY2
>> ? ? ?- Max Frame Rate: 30fps
>> ? ? ?- USB 2.0 compatible
>> ? ? ?- White balance: Auto
>> ? ? ?- Auto Exposure ( AE ): Auto
>>
>>
>> ?While I understand that I would get 16MP in a photo,
>> I don't see the option to take a photo greater than
>> 640x480 (the 1.3MP that is reported on the linux-uvc
>> compatibility chart).
>>
>> ?Any thoughts on how to poke this device to get the
>> higher resolutions? ?Or is it possible that they're going
>> outside of UVC (to something proprietary) to get those
>> resolutions? ?Or are they doing something bodgy in
>> the win32 software by collating 16 to 32 frames of 1.3MP
>> shots to "assemble" a 16MP image?
>>
>> ?I'm confident that my reseller is above board - the
>> specifications on that site match those on the back of
>> the product's packaging. ?I obviously can't speak for
>> the whole-saler or upstream there-after ..
>>
>> ?lsusb -v output is attached and is consistent with
>> luvcview output.
>>
>> ?The device does not have an external power option.
>>
>>
>> Thanks for your help,
>>
>>
>>
>>
>>
>> --
>> Ian Latter
>> Late night coder ..
>> http://midnightcode.org/
>> -------------- next part --------------
>> An embedded and charset-unspecified text was scrubbed...
>> Name: lsusb.txt
>> URL: 
>> <https://lists.berlios.de/pipermail/linux-uvc-devel/attachments/20100409/af1c174c/attachment.txt>
>>
>> ------------------------------
>>
>> _______________________________________________
>> Linux-uvc-devel mailing list
>> [email protected]
>> https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
>>
>>
>> End of Linux-uvc-devel Digest, Vol 46, Issue 9
>> **********************************************
>>
>
>
> ------------------------------
>
> Message: 3
> Date: Sat, 10 Apr 2010 13:14:57 +1000
> From: "Ian Latter" <[email protected]>
> To: "Paulo Assis" <[email protected]>
> Cc: [email protected]
> Subject: Re: [Linux-uvc-devel] 16MP or 1.3MP?
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset="us-ascii"
>
> Hello Paulo,
>
>
>  Out of the 15-or-so computers that I own none of them
> run Windows, so I can't actually test it in Windows here.
> I'll send it round to a mates place and see what he makes
> of it - and I'll try and get a "high res" sample up on a web
> server somewhere.
>
>  This morning I did a quick search for specifications, and
> which-ever sensor chip is inside it, it can't be good;
>
> http://www.pixart.com.tw/productsditel.asp?ToPage=1&productclassify_id=8
>
>  The max spec there is for a 640x480 sensor - so it
> must be Win32 application magic - which, I agree, must
> make an output image that is as fuzzy as foobar ...
>
>
> Thanks,
>
> ----- Original Message -----
>>From: "Paulo Assis" <[email protected]>
>>To: "Ian Latter" <[email protected]>
>>Subject:  Re: [Linux-uvc-devel] 16MP or 1.3MP?
>>Date: Fri, 09 Apr 2010 12:15:25 +0100
>>
>> Hi,
>> From your lsusb output the camera max resolution is
> 640x480 (even for
>> still image)
>> If you can get an higher resolution in windows, I guess
> it's probably
>> trough some sort of interpolation technique.
>> I doubt however that the quality is any good.
>> It can also be that the camera uses some sort of "extra"
> proprietary
>> protocol, but if it does, it doesn't seem to reported .
>>
>> Best Regards,
>> Paulo
>>
>> 2010/4/9 Ian Latter <[email protected]>:
>> > Hello,
>> >
>> >
>> > �Its a been a long time since I was last working with UVC,
>> > but I found a camera that I couldn't resist, and you're
> in the
>> > mainline kernel now .. and I'd like to do some aerial photos
>> > from my embedded platform ..
>> >
>> > �You have a 093a:2700 device listed on your site as
>> > working (and my testing confirms this);
>> >
>> > � �http://linux-uvc.berlios.de/
>> > � �093a:2700
>> > � � � �- iSonic W002
>> > � � � �- A4Tech PK-635K
>> > � � � �- Digital Innovations 1.3MP Webcam
>> > � � � �--> Pixart Imaging
>> >
>> > �Confirmed in Fedora 12 (kernel 2.6.31 - dmesg output);
>> > � �usb 1-1: new high speed USB device using ehci_hcd
>> > � �and address 27
>> > � �usb 1-1: New USB device found, idVendor=093a,
>> > � �idProduct=2700
>> > � �usb 1-1: New USB device strings: Mfr=16, Product=96,
>> > � �SerialNumber=0
>> > � �usb 1-1: Product: USB2.0_Camera
>> > � �usb 1-1: Manufacturer: PixArt Imaging Inc.
>> > � �usb 1-1: configuration #1 chosen from 1 choice
>> > � �Linux video capture interface: v2.00
>> > � �uvcvideo: Found UVC 1.00 device USB2.0_Camera
>> > � �(093a:2700)
>> > � �input: USB2.0_Camera as /devices/pci0000:00/0000:
>> > � �00:02.1/usb1/1-1/1-1:1.0/input/input6
>> > � �usbcore: registered new interface driver uvcvideo
>> > � �USB Video Class driver (v0.1.0)
>> > � �ALSA sound/usb/usbaudio.c:1300: current rate
>> > � �6292992 is different from the runtime rate 16000
>> > � �ALSA sound/usb/usbaudio.c:1300: current rate 34560
>> > � �is different from the runtime rate 48000
>> > � �usbcore: registered new interface driver snd-usb-audio
>> > � �ALSA sound/usb/usbaudio.c:1300: current rate 33024
>> > � �is different from the runtime rate 48000
>> > � �ALSA sound/usb/usbaudio.c:1300: current rate 33280
>> > � �is different from the runtime rate 48000
>> >
>> >
>> > �luvcview output looks okay (save that massive fraction);
>> > � �# ./luvcview -L
>> > � �luvcview version 0.2.1
>> > � �Video driver: x11
>> > � �A window manager is available
>> > � �video /dev/video0
>> > � �/dev/video0 does not support read i/o
>> > � �{ pixelformat = 'YUYV', description = 'YUV 4:2:2
> (YUYV)' }
>> > � �{ discrete: width = 640, height = 480 }
>> > � � � �Time interval between frame: 1/30, 1/20, 1/15, 1/10,
>> > � � � �1/5, 1/1,
>> > � �{ discrete: width = 320, height = 240 }
>> > � � � �Time interval between frame: 1/30, 1/20, 1/15, 1/10,
>> > � � � �1589/15625, 1/1,
>> > � �{ discrete: width = 160, height = 120 }
>> > � � � �Time interval between frame: 1/30, 1/20, 1/15, 1/10,
>> > � � � �1589/15625, 1/1,
>> > � �{ discrete: width = 176, height = 144 }
>> > � � � �Time interval between frame: 1/30, 1/20, 1/15, 1/10,
>> > � � � �1589/15625, 1/1,
>> > � �{ discrete: width = 352, height = 288 }
>> > � � � �Time interval between frame: 1/30, 1/20, 1/15, 1/10,
>> > � � � �1589/15625, 1/1,
>> >
>> >
>> > And I can see my ugly mug at 640x480 via the native
>> > "Cheese Webcam Booth" app - no magic required. �Nice.
>> >
>> >
>> > The issue that I have is that this camera is sold as a 16
>> > (well, 16.0) mega-pixel camera;
>> >
>> > � �Speed 16.0Mega Pixel USB2.0 Webcam S4850v
>> > �
> �https://www.pcdiy.com.au/product_info.php?products_id=9757
>> >
>> > � �TECHNICAL SPECIFICATION
>> > � � �- Speed 16.0Mega Pixel USB2.0 Webcam
>> > � � �- Effective Static Pixels 16 Mega Pixel
>> > � � �- Maximum Resolution : 4608 x 3456
>> > � � �- Output Format: YUY2
>> > � � �- Max Frame Rate: 30fps
>> > � � �- USB 2.0 compatible
>> > � � �- White balance: Auto
>> > � � �- Auto Exposure ( AE ): Auto
>> >
>> >
>> > �While I understand that I would get 16MP in a photo,
>> > I don't see the option to take a photo greater than
>> > 640x480 (the 1.3MP that is reported on the linux-uvc
>> > compatibility chart).
>> >
>> > �Any thoughts on how to poke this device to get the
>> > higher resolutions? �Or is it possible that they're going
>> > outside of UVC (to something proprietary) to get those
>> > resolutions? �Or are they doing something bodgy in
>> > the win32 software by collating 16 to 32 frames of 1.3MP
>> > shots to "assemble" a 16MP image?
>> >
>> > �I'm confident that my reseller is above board - the
>> > specifications on that site match those on the back of
>> > the product's packaging. �I obviously can't speak for
>> > the whole-saler or upstream there-after ..
>> >
>> > �lsusb -v output is attached and is consistent with
>> > luvcview output.
>> >
>> > �The device does not have an external power option.
>> >
>> >
>> > Thanks for your help,
>> >
>> >
>> >
>> >
>> >
>> > --
>> > Ian Latter
>> > Late night coder ..
>> > http://midnightcode.org/
>> >
>> > _______________________________________________
>> > Linux-uvc-devel mailing list
>> > [email protected]
>> > https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
>> >
>> >
>>
>
>
> --
> Ian Latter
> Late night coder ..
> http://midnightcode.org/
>
>
> ------------------------------
>
> _______________________________________________
> Linux-uvc-devel mailing list
> [email protected]
> https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
>
>
> End of Linux-uvc-devel Digest, Vol 46, Issue 10
> ***********************************************
>
_______________________________________________
Linux-uvc-devel mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel

Reply via email to