Microsoft VX 6000
Calin
http://groups.google.com/group/microdia/browse_thread/thread/a09aee095c7bf7e4/1da42e25d478ef82
and make my webcam work! I know it`s experimental this webcam 045e:
00f4 (Experimental Support Available : 6242 624e 624f 6270 627b 62bb
145f:013d & 045e:00f4 ). I am using skype and i was wondering, how can
i switch my webcam to mirror image?
Cheers!
Comer352l
there are three module parameters for horizontal and vertical image
flip: hflip, vflip and flip_detect
They can be set to 0 or 1 when loading the driver:
insmod microdia.ko vflip=1 hflip=1 flip_detect=0 (example)
Please tell us if flip_detect works for this cam !
Frank
Calin schrieb:
Calin
insmod microdia.ko vflip=0 hflip=1 flip_detect=0
I`m not sure what flip_detect is but is work, i mean it`s not giving
me an error or something! Thanks! If you need anything else, to test
the camera just ask :)
Cheers!
On Jun 7, 7:31 pm, Comer352l <comer3...@web.de> wrote:
> Hi Calin,
>
> there are three module parameters for horizontal and vertical image
> flip: hflip, vflip and flip_detect
> They can be set to 0 or 1 when loading the driver:
>
> insmod microdia.ko vflip=1 hflip=1 flip_detect=0 (example)
>
> Please tell us if flip_detect works for this cam !
>
> Frank
>
> Calin schrieb:
>
> > Hi everyone! I have read this post
Comer352l
flip_detect is for rotatable cameras. With this parameter enabled, the
driver tries to flip the image automaticly depending on the cameras
position. I don't know if your cam supports this...
Another question: if I remember right, there are 3 other Microsoft cams
that are supposed to used Sonix-bridges as well. Could you please watch
out for a *.inf-file of the windows driver (if you have access to
Windows system ;-) ) ?
Frank
Calin schrieb:
Calin
insmod microdia.ko vflip=0 hflip=1 flip_detect=0
insmod microdia.ko vflip=0 hflip=1 flip_detect=1
i am seeing me upside-down. I am using Windows XP n virtual
machine...and i have installed the camera and works perfect :) and i
found in C:\Program Files\Microsoft LifeCam\Driver32 the NX6000,
VX1000, VX3000, and my webcam VX6000. Every model has two .inf
files...i will upload this 8 files! ;)
Cheers!
Comer352l
> Hi Frank! If i use:
>
> insmod microdia.ko vflip=0 hflip=1 flip_detect=0
>
> i am seeing normal and if i use flip_detect=1
>
> insmod microdia.ko vflip=0 hflip=1 flip_detect=1
>
> i am seeing me upside-down.
happens when turn the cam around/rotate it ?
Btw, you don't have to use these parameters if the desired value is 0...
> I am using Windows XP n virtual
> machine...and i have installed the camera and works perfect :) and i
> found in C:\Program Files\Microsoft LifeCam\Driver32 the NX6000,
> VX1000, VX3000, and my webcam VX6000. Every model has two .inf
> files...i will upload this 8 files! ;)
>
> Cheers!
>
of 201, so it should be the same as 0c45:628f (not 624f).
However, we will add support for several VID:PIDs of "clone"-devices
soon. Please be patient...
Oh, and could you create a USB-log from the init-/start-/stop-sequence
under Windows ?
Frank
Calin
insmod microdia.ko flip_detect=1
and i am seeing me upside-down. If i rotate the camera 180 degree i am
seeing me normal (mirror image). I have discovered something...when i
touch the camera or move it`s start to flicker. Tell me please, how to
create the usb log?
Calin
Calin
(git-clone http://repo.or.cz/r/microdia.git) and modify the file
> so it should be the same as 0c45:628f (not 624f).
i compiled with make and:
make -C /lib/modules/2.6.22.17-0.1-default/build SUBDIRS=/home/calin/
Microdia Testing/microdia modules
make[1]: Entering directory `/usr/src/linux-2.6.22.17-0.1-obj/i386/
default'
make -C ../../../linux-2.6.22.17-0.1 O=../linux-2.6.22.17-0.1-obj/i386/
default Testing/microdia
make[3]: *** No rule to make target `Testing/microdia'. Stop.
make[2]: *** [Testing/microdia] Error 2
make[1]: *** [Testing/microdia] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.22.17-0.1-obj/i386/
default'
make: *** [driver] Error 2
Have you have any ideea why?
Cheers!
Calin
http://groups.google.com/group/microdia/web/usb-sniffing-on-windows
and i will upload the init,start and stop sequence. Hope this helps!
Cheers!
Comer352l
PID 628f will not work, please use 624f instead.
Frank
Calin schrieb:
Comer352l
We need a log from the FIRST start-stream after connecting the camera to
the USB-port.
After stopping the stream, you should wait some seconds before you stop
the logging.
Frank
Calin schrieb:
Calin
microdia: Microdia USB2.0 webcam driver startup
microdia: Microdia USB2.0 Webcam - Product ID 628F.
microdia: This device is not supported yet. Please contact
microdia@googlegroups if you want add support for this device
usbcore: registered new interface driver usb_microdia_driver
microdia: v0.0.0 : Microdia USB Video Camera
i will use 624f. Btw if i stay until it`s closing the stream the log
file will be very big. I was trying to stay until the stream close and
the log was 160MB :)
(in 2 sec)
Cheers!
JoJo jojo
> i will use 624f. Btw if i stay until it`s closing the stream the log
> file will be very big. I was trying to stay until the stream close and
> the log was 160MB :)
> (in 2 sec)
>
> Cheers!
Don't worry about logsize, concentrate on making us a clean sniff.
if it gets too big, you can
ZIP it to get the size down,
if that fails, you can use the PERL parser script to cut the log file
down further
do a complete sniff, zip the log thus obtained, then tell us the size.
-JoJo
Calin
http://files.zenum.net/microdia/sniffusb_logs/045e/00f4/045E_00F4_24-Jun-2008_init_start_stop_sequences.7z
Btw i have use AMcap and i have enable the microphone too.
Calin.
Calin
VX6000m.inf Btw this is the new driver Lifecam 2.0 ;) updated from
microsoft. Jojo said something about the .reg file too but i didn`t
find it.
Calin.
Comer352l
soon as I find some time, but I can already say, that there are some
interesting differences...
Frank
Calin
a virtual one with win XP.
Calin.
Bilbo75
Hi guys, I've upped a new log on files.zenum.net.
I did a mistake,the folder is 054e instead of 045e.Sorry I'm a dumb :(
The path is: http://files.zenum.net/microdia/sniffusb_logs/054e/00f4/045e_00f4_3_jul_08_init_start_sequences.zip
-Andrea
JSadowski
I've tried to get VX-6000 Webcam working using 624f procedures but
results were not very good - terrible noise on video signal, high
contrast and reversed colors, and sometimes when picture contained
many pixels 0xFFFFFF (white colour) the video started to flicker.
Temporary solution (till the SN9C202 chip will be supported):
1. reverse byte order in procedure microdia_raw2bgr24 (microdia-
decoder.c) to swap red and blue components :)
2. remove procedure call "dev_microdia_camera_set_exposure(dev);" in
"dev_microdia_camera_settings" (microdia-dev.c) to remove flickering
and decrease gain (exposure) factor. It's strange, because after this
operation, program "camstream" allows to change gain/exposure by
changing "gamma" control, I'm not sure why. But now setting the
"gamma" in "camstream" to about 1/5 of maximum value gives almost
perfect, clear picture :) Of course only up to 640x480 resolution.
Best wishes,
Jarek
Vasily Khoruzhick
Did you tried to change exposure value?
Brian Johnson
post it looks like you are using camstream which is v4l1 only and
therefor should not work at all with the latest version of our code.
Instead test using mplayer using the following.
# mplayer tv:// -tv driver=v4l2:width=640:height=480:outfmt=bgr24:fps=30
also the bgr24 should not really have its bytes swapped since it is
after all supposed to be ordered blue, green, and red. if you were
using camstream thats probably because its requesting the RGB24 format
under v4l1 which is really supposed to return BGR24 despite its name.
And finally like vasily said try adjusting the exposure value for your
cam to see if you can get a better picture this can be done under
sysfs. however i find it easier and perfer using the v4l2 controls to
adjust these values. you can down v4l2ucp from
http://v4l2ucp.sourceforge.net/. This is a control panel that makes
avaiable allow v4l2 image controls such as gamma and exposure. Just
compile it and then run v4l2ucp </path/to/video/device> then adjust
the settings using the sliders. You can also be running mplayer at the
same time so you can see when things look better for you
Jarosław Sadowski
2008/7/17 Brian Johnson <bri...@gmail.com>:
>
> First I'd make sure you are using the latest code from git. from your
> post it looks like you are using camstream which is v4l1 only [...]
You are (almost) right - I used camstream and v4l1 driver version
because without any modification this gave me better image quality
than mplayer with any settings, no matter if I used v4l1 or v4l2
driver version. 624F init procedure did not change since "last v4l1
release" so even using latest version from git repository I got the
same poor picture quality in mplayer, including flickering.
> also the bgr24 should not really have its bytes swapped since it is
> after all supposed to be ordered blue, green, and red. if you were
> using camstream thats probably because its requesting the RGB24 format
> under v4l1 which is really supposed to return BGR24 despite its name.
Colors are reversed also in jpeg's saved using program "motion"...
> And finally like vasily said try adjusting the exposure value for your
> cam to see if you can get a better picture this can be done under
> sysfs. [...]
Changing exposure value didn't change image quality at all. It looks
like gamma and/or (depends on the program I use) whitebalance (?)
value affects exposure parameter, but all the time exposure is too
high so pictures are too contrast and noisy.
Regards,
Jarek