Ubuntu 8:10 and Microdia 0c45:612e

[gboxadmin]

Hello all. I have a 0c45:612e Microdia PC Camera (SN9C110) device
that did not work on Ubuntu 8.04 (it would not mount on /dev/video0).
However now with 8.10 it will connect with no errors, except for a
few. I have installed the application 'cheese' and it shows what is
on the camera, however it is always black and white. It gives an
error of 'image cannot be captured' in camorama, and shows green noise
with Skype (which is the main reason for doing all of this). Now, I
have looked through the pages and what not about what to do, and it
seems to me that the device I have isn't even supported by Microdia
themselves. (Circa http://groups.google.com/group/microdia/web/project-status?hl=en&pli=1).
Regardless, I have been searching on this site (http://www.
64bitjungle.com/tech/microdia-webcam-0c54-experimental-drivers-
installation-and-testing-part-1/) even though I have a 32 bit OS and
processor, and have run those a few times prior to this event and
still nothing seems to work. Can someone shed some light on the
dreaded 612e driver and where they are available? Below I am pasting
the 0c45_612e_device_descriptors.txt as per the last site that I
linked. Any and all help will be appreciated, and thanks in advance!


Bus 002 Device 002: ID 0c45:612e Microdia PC Camera (SN9C110)
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x0c45 Microdia
idProduct 0x612e PC Camera (SN9C110)
bcdDevice 1.01
iManufacturer 0
iProduct 1 USB camera
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 279
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0000 1x 0 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 100
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 1
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0080 1x 128 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 100
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 2
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0100 1x 256 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 100
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 3
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0180 1x 384 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 100
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 4
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 100
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 5
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x02a8 1x 680 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 100
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 6
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0320 1x 800 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 100
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 7
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0384 1x 900 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 100
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 8
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x03ff 1x 1023 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 100
Device Status: 0x0000
(Bus Powered)

[GWater]

OK,
let's clear this up:

MICRODIA Ltd. is a company which lends their USB-identifier(0c45) to
other companies like Sonix (Sonix are the guys who build the bridge chip
and USB-controller of your webcam). We (microdia googlegroup) have no
connection to MICRODIA Ltd. or Sonix.

Ubuntu 8.10 ships kernel 2.6.27 which supports a lot of webcams because
of the inclusion of GSPCAv2. A part of the GSPCAv2 inclusion process was
a removal of all image decoders in the driver. This is why Skype doesn't
show a correct image.

Camorama does not work because it uses the old V4L1 standard. All recent
webcam drivers only support V4L2.

Both problems can be solved using libv4l. Please search your Ubuntu 8.10
system for libv4l and read the README.

GWater

> --~--~---------~--~----~------------~-------~--~----~
> Lets make microdia webcams plug'n play, (currently plug'n pray)
> To post to this group, send email to micr...@googlegroups.com
> Visit us online https://groups.google.com/group/microdia
> -~----------~----~----~----~------~----~------~--~---
>

[Matt Payerle]

Ok, thanks for the information.  I have done a locate libv4l and it came up with a bunch of places, but no readme nor man pages found.  Googling has not returned any results either.  I did however apt-get install libv4l-* to capture any updates, but once I did that, as soon as I tested my webcam in skype it simply forced a close.. Obviously I missed something and would appreciate any more help you are willing to give!  Thanks again.

[Brian Johnson]

If you have the pacakge installed from the ubuntu repository. The two
files you are interested in are v4l2convert.so and v4l1compat.so. If
you need v4l1 compatability you will use that file if not you
will use the v4l2convert.so. Just make sure your environment has a
LD_PRELOAD variable set to the
full path of one of those two libraries. I belive ubuntu will install
them under /usr/lib/libv4l/

So for example if you want to run camorama you should be able to do
enter the following command
# LD_PRELOAD=/usr/lib/libv4l/v4l1compat.so camorama
This should launch camorama with the proper environment variable set.
If you always want it to get set you should be able to export that
variable from your .bashrc file as well

[Matt Payerle]

Awesome!  Thanks that totally works.  There is still one issue.  It shows the picture only in black and white, and very very dark.  I have to directly shine a light on my face to get it to appear, and even still it is dark.  Also, how do I edit my .bashrc to make this work every time?  Thanks again, this is a great step!

[GWater]

You need to add this line to your ~/.bashrc:

export LD_PRELOAD=/usr/lib/v4l1compat.so

Note: I don't think it's a good idea because every app you run will want
to link up with v4l1compat.so - even if the respective app doesn't need
it or isn't a video-app at all.

GWater

Matt Payerle schrieb:

> <http://groups.google.com/group/microdia/web/project-status?hl=en&pli=1>).

> >>> Regardless, I have been searching on this site (http://www.
> >>> 64bitjungle.com/tech/microdia-webcam-0c54-experimental-drivers-

> <http://64bitjungle.com/tech/microdia-webcam-0c54-experimental-drivers->

[GWater]

I am sorry - here's the correct line:

export LD_PRELOAD=/usr/lib/libv4l/v4l1compat.so

GWater

GWater schrieb:

[Matt Payerle]

Good call.  I actually thought about that.  What I will probably do is just drop that line into the preferences of any of the icons that I would like to run and that way it runs when I click the icon rather than load terminal every time I need to run something with or without camera use.  Still working on the color issue..

[Matt Payerle]

Still having issues with contrast and color (changing the contrast and color does nothing in the program that I am trying to run) Any help is appreciated.  Thanks again!

[GWater]

Please post a few screenshots.

GWater

Matt Payerle schrieb:

> <mailto:bri...@gmail.com <mailto:bri...@gmail.com>>>

> wrote:
>
>
> If you have the pacakge installed from the ubuntu
> repository. The two
> files you are interested in are v4l2convert.so and
> v4l1compat.so. If
> you need v4l1 compatability you will use that file if
> not you
> will use the v4l2convert.so. Just make sure your
> environment has a
> LD_PRELOAD variable set to the
> full path of one of those two libraries. I belive
> ubuntu will install
> them under /usr/lib/libv4l/
>
> So for example if you want to run camorama you should
> be able to do
> enter the following command
> # LD_PRELOAD=/usr/lib/libv4l/v4l1compat.so camorama
> This should launch camorama with the proper
> environment variable set.
> If you always want it to get set you should be able
> to export that
> variable from your .bashrc file as well
>
>
> On Wed, Nov 5, 2008 at 12:18 AM, Matt Payerle
> <gbox...@gmail.com <mailto:gbox...@gmail.com>

> <mailto:gbox...@gmail.com

> <mailto:gbox...@gmail.com>>> wrote:
> > Ok, thanks for the information. I have done a
> locate libv4l and
> it came up
> > with a bunch of places, but no readme nor man
> pages found.
> Googling has not
> > returned any results either. I did however
> apt-get install
> libv4l-* to
> > capture any updates, but once I did that, as soon
> as I tested my
> webcam in
> > skype it simply forced a close.. Obviously I
> missed something and
> would
> > appreciate any more help you are willing to give!
> Thanks again.
> >
> > On Tue, Nov 4, 2008 at 10:45 AM, GWater
> <grew...@googlemail.com <mailto:grew...@googlemail.com>

> <mailto:grew...@googlemail.com

[Matt Payerle]

OK, so here are a few shots in cheese that I took.  You can see me in the middle one only because there is a light shinning directly on me.  The others were of very minimal light.  As you can see, it is terrible contrast.  Trying to change the brightness or contrast in any of the programs unfortunately fails to work.  Any suggestions?  Thanks.

[GWater]

Well,
brightness doesn't usually help - black parts will only become brighter
but no additional image data is created.

If 612e supports it try to set a higher Exposure. If cheese doesn't
offer this option use v4l2ucp while you run cheese.

GWater

Matt Payerle schrieb:

> OK, so here are a few shots in cheese that I took. You can see me in
> the middle one only because there is a light shinning directly on me.
> The others were of very minimal light. As you can see, it is terrible
> contrast. Trying to change the brightness or contrast in any of the
> programs unfortunately fails to work. Any suggestions? Thanks.
>
> On Fri, Nov 7, 2008 at 12:01 PM, GWater <grew...@googlemail.com
> <mailto:grew...@googlemail.com>> wrote:
>
> Please post a few screenshots.
>
> GWater
>
> Matt Payerle schrieb:
>
> Still having issues with contrast and color (changing the
> contrast and color does nothing in the program that I am trying
> to run) Any help is appreciated. Thanks again!
>
> On Wed, Nov 5, 2008 at 10:10 PM, Matt Payerle
> <gbox...@gmail.com <mailto:gbox...@gmail.com>

> <mailto:gbox...@gmail.com <mailto:gbox...@gmail.com>>> wrote:
>
> Good call. I actually thought about that. What I will
> probably do
> is just drop that line into the preferences of any of the
> icons that
> I would like to run and that way it runs when I click the icon
> rather than load terminal every time I need to run something
> with or
> without camera use. Still working on the color issue..
>
>
> On Wed, Nov 5, 2008 at 3:54 PM, GWater
> <grew...@googlemail.com <mailto:grew...@googlemail.com>

> --~--~---------~--~----~------------~-------~--~----~
> Lets make microdia webcams plug'n play, (currently plug'n pray)
> To post to this group, send email to micr...@googlegroups.com
> Visit us online https://groups.google.com/group/microdia
> -~----------~----~----~----~------~----~------~--~---
>
>

> ------------------------------------------------------------------------
>

[Matt Payerle]

Ok I will take a look into that.  So run  LD_PRELOAD=/usr/lib/libv4l/v4l2ucp cheese just to double check before I get home and start working on it.  or is it more based off of LD_PRELOAD=/usr/lib/libv4l/v4l1ucp.so cheese?
Thanks. 

...

[Message clipped]  

[GWater]

We have a big misunderstanding here:

V4L2ucp is a simple app which uses the V4L2 interface to adjust camera
properties. (A small window with a lot of buttons.)

What you are trying to do is preload libv4l which is entirely different
from v4l2ucp.

Please take a look in the (microdia) README file - there is a link to
v4l2ucp in there. Also check if your distro has it available in a repo.

If not, you have to download, compile and install it.

GWater

Matt Payerle schrieb:

> Ok I will take a look into that. So run
> LD_PRELOAD=/usr/lib/libv4l/v4l2ucp cheese just to double check before I
> get home and start working on it. or is it more based off of
> LD_PRELOAD=/usr/lib/libv4l/v4l1ucp.so cheese?
> Thanks.
>
> On Mon, Nov 10, 2008 at 3:41 AM, GWater <grew...@googlemail.com
> <mailto:grew...@googlemail.com>> wrote:
>
> Well,
> brightness doesn't usually help - black parts will only become
> brighter but no additional image data is created.
>
> If 612e supports it try to set a higher Exposure. If cheese doesn't
> offer this option use v4l2ucp while you run cheese.
>
> GWater
>
>
>
> Matt Payerle schrieb:
>
> OK, so here are a few shots in cheese that I took. You can see
> me in the middle one only because there is a light shinning
> directly on me. The others were of very minimal light. As you
> can see, it is terrible contrast. Trying to change the
> brightness or contrast in any of the programs unfortunately
> fails to work. Any suggestions? Thanks.
>
> On Fri, Nov 7, 2008 at 12:01 PM, GWater <grew...@googlemail.com

> <mailto:grew...@googlemail.com> <mailto:grew...@googlemail.com
> <mailto:grew...@googlemail.com>>> wrote:
>
> Please post a few screenshots.
>
> GWater
>
> Matt Payerle schrieb:
>
> Still having issues with contrast and color (changing the
> contrast and color does nothing in the program that I am
> trying
> to run) Any help is appreciated. Thanks again!
>
> On Wed, Nov 5, 2008 at 10:10 PM, Matt Payerle
> <gbox...@gmail.com <mailto:gbox...@gmail.com>
> <mailto:gbox...@gmail.com <mailto:gbox...@gmail.com>>

> <mailto:gbox...@gmail.com <mailto:gbox...@gmail.com>
> <mailto:gbox...@gmail.com <mailto:gbox...@gmail.com>>>> wrote:
>
> Good call. I actually thought about that. What I will
> probably do
> is just drop that line into the preferences of any of the
> icons that
> I would like to run and that way it runs when I click
> the icon
> rather than load terminal every time I need to run
> something
> with or
> without camera use. Still working on the color issue..
>
>
> On Wed, Nov 5, 2008 at 3:54 PM, GWater
> <grew...@googlemail.com <mailto:grew...@googlemail.com>
> <mailto:grew...@googlemail.com <mailto:grew...@googlemail.com>>

> <mailto:bri...@gmail.com <mailto:bri...@gmail.com>>>>>

[Matt Payerle]

Ok, Thanks for that info, and thanks for helping me through all of this.  I'm not sure why I'm not grasping this like I do other things.  Either way, I went to http://v4l2ucp.sourceforge.net/ and downloaded the file there and I am trying to complie (sudo ./configure) and I am getting "configure: error: cannot find QT" Qt is located in /usr/lib/qt4 so I also tried (sudo ./configure --with-qt-libs=/usr/lib/qt4) - no such luck.  is there a .deb file or something I am missing that I need to get this going?  Thanks.

...

[Message clipped]  

[GWater]

You might need the development files. I don't know the exact name - try
"qt4-dev".

GWater

Matt Payerle schrieb:

> <mailto:grew...@googlemail.com> <mailto:grew...@googlemail.com
> <mailto:grew...@googlemail.com>>> wrote:
>
> Well,
> brightness doesn't usually help - black parts will only become
> brighter but no additional image data is created.
>
> If 612e supports it try to set a higher Exposure. If cheese
> doesn't
> offer this option use v4l2ucp while you run cheese.
>
> GWater
>
>
>
> Matt Payerle schrieb:
>
> OK, so here are a few shots in cheese that I took. You
> can see
> me in the middle one only because there is a light shinning
> directly on me. The others were of very minimal light.
> As you
> can see, it is terrible contrast. Trying to change the
> brightness or contrast in any of the programs unfortunately
> fails to work. Any suggestions? Thanks.
>
> On Fri, Nov 7, 2008 at 12:01 PM, GWater
> <grew...@googlemail.com <mailto:grew...@googlemail.com>
> <mailto:grew...@googlemail.com
> <mailto:grew...@googlemail.com>>

> <mailto:grew...@googlemail.com <mailto:grew...@googlemail.com>
> <mailto:grew...@googlemail.com
> <mailto:grew...@googlemail.com>>>> wrote:
>
> Please post a few screenshots.
>
> GWater
>
> Matt Payerle schrieb:
>
> Still having issues with contrast and color
> (changing the
> contrast and color does nothing in the program
> that I am
> trying
> to run) Any help is appreciated. Thanks again!
>
> On Wed, Nov 5, 2008 at 10:10 PM, Matt Payerle
> <gbox...@gmail.com <mailto:gbox...@gmail.com>
> <mailto:gbox...@gmail.com <mailto:gbox...@gmail.com>>
> <mailto:gbox...@gmail.com <mailto:gbox...@gmail.com>
> <mailto:gbox...@gmail.com <mailto:gbox...@gmail.com>>>

[Matt Payerle]

Ok, I checked and it is qt4-dev-tools and it is the most updated on my machine. 

...

[Message clipped]  

[GWater]

What about "libqt4-dev"?

GWater

Matt Payerle schrieb:

> Ok, I checked and it is qt4-dev-tools and it is the most updated on my
> machine.
>
> On Mon, Nov 10, 2008 at 3:55 PM, GWater <grew...@googlemail.com
> <mailto:grew...@googlemail.com>> wrote:
>
> You might need the development files. I don't know the exact name -
> try "qt4-dev".
>
> GWater
>
> Matt Payerle schrieb:
>
> Ok, Thanks for that info, and thanks for helping me through all
> of this. I'm not sure why I'm not grasping this like I do other
> things. Either way, I went to http://v4l2ucp.sourceforge.net/
> and downloaded the file there and I am trying to complie (sudo
> ./configure) and I am getting "configure: error: cannot find QT"
> Qt is located in /usr/lib/qt4 so I also tried (sudo ./configure
> --with-qt-libs=/usr/lib/qt4) - no such luck. is there a .deb
> file or something I am missing that I need to get this going?
> Thanks.
>
>
>
> On Mon, Nov 10, 2008 at 11:45 AM, GWater
> <grew...@googlemail.com <mailto:grew...@googlemail.com>

> <mailto:bri...@gmail.com <mailto:bri...@gmail.com>>>>>>>

[GWater]

You know what - skip the compiling and download it here:

http://www.debian-multimedia.org/dists/stable/main/binary-i386/package/v4l2ucp.php

GWater

Matt Payerle schrieb:

> Ok, I checked and it is qt4-dev-tools and it is the most updated on my
> machine.
>
> On Mon, Nov 10, 2008 at 3:55 PM, GWater <grew...@googlemail.com
> <mailto:grew...@googlemail.com>> wrote:
>
> You might need the development files. I don't know the exact name -
> try "qt4-dev".
>
> GWater
>
> Matt Payerle schrieb:
>
> Ok, Thanks for that info, and thanks for helping me through all
> of this. I'm not sure why I'm not grasping this like I do other
> things. Either way, I went to http://v4l2ucp.sourceforge.net/
> and downloaded the file there and I am trying to complie (sudo
> ./configure) and I am getting "configure: error: cannot find QT"
> Qt is located in /usr/lib/qt4 so I also tried (sudo ./configure
> --with-qt-libs=/usr/lib/qt4) - no such luck. is there a .deb
> file or something I am missing that I need to get this going?
> Thanks.
>
>
>
> On Mon, Nov 10, 2008 at 11:45 AM, GWater
> <grew...@googlemail.com <mailto:grew...@googlemail.com>

[Matt Payerle]

Already the newest version installed...

...

[Message clipped]  

[Matt]

Ok, thanks for sticking with this so long! That .deb was exactly what I
was looking for before. Either way, I am posting a new screenshot.
There is a little more light in the room, but nothing shinning right on
my face (notice the v4l2ucp program running as well) Color is still
out, not sure what is going on there. Either way, making good progress.

[GWater]

OK - just to make sure - you set exposure to the highest possible value?

GWater

Matt schrieb:

> --~--~---------~--~----~------------~-------~--~----~
> Lets make microdia webcams plug'n play, (currently plug'n pray)
> To post to this group, send email to micr...@googlegroups.com
> Visit us online https://groups.google.com/group/microdia
> -~----------~----~----~----~------~----~------~--~---
>
>
>

> ------------------------------------------------------------------------
>

[Matt]

Yes. It stopped at that mark.

GWater

> ------------------------------------------------------------------------
>

[GWater]

Then I'm out of ideas sorry.

GWater

Matt schrieb:

[Matt]

Ok, well thanks for sticking with this project so long. Where were you
getting some of your information by the way? And if you happen to think
of something that would give it color, that would be much appreciated.
Thanks again. Have a good one.

[GWater]

Hey come on,
I basically had one tought:
The image is dark though there is light shining right onto his face.
Must be too low exposure.

The rest was just my way of trying to fix this single issue. Good luck.

GWater

Matt schrieb:

[Matt]

No really. I haven't talked to many people that would stick on a
project like this. I wasn't being sarcastic! Sorry if I came across
that way. Thanks for all of the help with everything else, you did a
good job thinking of that last program to brighten things up and change
the exposure. I'm sure there will be a fix soon enough or something I
can stumble upon. I mean, back in 8.04 the thing didn't even mount
on /dev/video0, now it at least shows up! Thanks again.

[Johan]

I got my image less dark by changing the "Gain" in v4l2ucp.

Changing "Exposure" doesn't seem to do anything (neither in v4l2ucp,
nor in guimicrodia).


Greetings,

Johan

[Matt Payerle]

That sounds like good information, however when I run v4l2ucp, I do not have a "Gain" option.  Is there another program that you can recommend? 

[GWater]

Matt Payerle schrieb:

> --~--~---------~--~----~------------~-------~--~----~
> Lets make microdia webcams plug'n play, (currently plug'n pray)
> To post to this group, send email to micr...@googlegroups.com
> Visit us online https://groups.google.com/group/microdia
> -~----------~----~----~----~------~----~------~--~---
>

Please update your driver - gain just came in a few weeks ago.

GWater

[Matt Payerle]

Does anyone happen to have that .deb or know where I can update it?  Does this also add color?  Thanks.

On Fri, Jan 2, 2009 at 4:46 AM, GWater <grew...@googlemail.com> wrote:

Matt Payerle schrieb:

That sounds like good information, however when I run v4l2ucp, I do not have a "Gain" option.  Is there another program that you can recommend?

On Tue, Dec 30, 2008 at 3:22 PM, Johan <johan.r...@gmail.com <mailto:johan.r...@gmail.com>> wrote:


   I got my image less dark by changing the "Gain" in v4l2ucp.

   Changing "Exposure" doesn't seem to do anything (neither in v4l2ucp,
   nor in guimicrodia).


   Greetings,

   Johan

[GWater]

Matt Payerle schrieb:

> Does anyone happen to have that .deb or know where I can update it?
> Does this also add color? Thanks.
>
> On Fri, Jan 2, 2009 at 4:46 AM, GWater <grew...@googlemail.com
> <mailto:grew...@googlemail.com>> wrote:
>
> Matt Payerle schrieb:
>
> That sounds like good information, however when I run v4l2ucp, I
> do not have a "Gain" option. Is there another program that you
> can recommend?
> On Tue, Dec 30, 2008 at 3:22 PM, Johan
> <johan.r...@gmail.com <mailto:johan.r...@gmail.com>

> <mailto:johan.r...@gmail.com

> <mailto:johan.r...@gmail.com>>> wrote:
>
>
> I got my image less dark by changing the "Gain" in v4l2ucp.
>
> Changing "Exposure" doesn't seem to do anything (neither in
> v4l2ucp,
> nor in guimicrodia).
>
>
> Greetings,
>
> Johan
>
>
>
>
>
>
> Please update your driver - gain just came in a few weeks ago.
>
> GWater
>
>
>

> --~--~---------~--~----~------------~-------~--~----~
> Lets make microdia webcams plug'n play, (currently plug'n pray)
> To post to this group, send email to micr...@googlegroups.com
> Visit us online https://groups.google.com/group/microdia
> -~----------~----~----~----~------~----~------~--~---
>

If we're talking about the microdia driver for 0c45:62xx devices:
- There is a howto in the pages section of this googlegroup.

For other drivers - ask their maintainers.

GWater

[Johan]

I don't know of any packages, but it's easy to compile from source, as
described here:

<https://groups.google.com/group/microdia/web/testing-microdia-driver-
draft>


Must say, I just did a fresh 'git clone' and now the gain option in
v4l2ucp stopped working.

It says:

Unable to set Gain
Invalid argument

[Brian Johnson]

This is because gain is currently only implemented for the SOI968
sensor. If you have any other sensor gain does not work

[Johan]

I do have the SOI968 sensor.

It's a Trust WB-5400.


Like I said previously:

> I got my image less dark by changing the "Gain" in v4l2ucp.
>
> Changing "Exposure" doesn't seem to do anything (neither in
> v4l2ucp, nor in guimicrodia).
>

But, as of today:

> Must say, I just did a fresh 'git clone' and now the gain option in
> v4l2ucp stopped working.
>
> It says:
>
> Unable to set Gain
> Invalid argument
>

So I would assume the latest patches caused some unwanted behavior.


Greetings,

Johan

[Brian Johnson]

Oh alright yes apparently when i rewrote the the sensor setup routines
i forgot to add gain support to SOI968. Should fixed in the repository
now.

[Johan]

> Oh alright yes apparently when i rewrote the the sensor setup routines
> i forgot to add gain support to SOI968. Should fixed in the repository
> now.
>

It works here.


Thanks,

Johan

[Matt Payerle]

Ok, I went to that site and I recompiled and what not, but I still do not see Gain on the v4l2ucp program.  Very good information though, thanks!