I think the data that goes over the usb connection is mjpeg when using the IS-DV software. That'll compress things a little bit.

So... any news about this is-dv integration ?

I think it would be difficult to get the thing to work properly in windows until somebody finds out a way to permanently unlock the camcorder.

yeah this would be the perfect setup.. But anyway even with the instruction on this thread I can't find a way to make it work.. changed the setup.ini for product=Saturn installed IS-DV modded the 3 oemX.inf with good PID and VID Detect as saturn... ok.. uninstall libusb driver... reboot still detect as saturn... and I can't install any inf of is-dv (witch I think are oem.inf ??) can you give me any foolproof explanation for me ?? Im curently doing some timelapse video with my cheap webcam and I would like to try with the camcorder :D

Unfortunately, you must unlock the camcorder with Ops before you can use other drivers. This makes the IS-DV software somewhat pointless for now, until we can modify the firmware to eliminate the locking mechanism. If you do want to play with this, you will need to connect the camcorder to one USB port, and bind it to libusb. Unlock the camcorder with Ops, then move the camcorder to ANOTHER USB port, and bind it to the ISDV drivers. You will need to do this every time you power cycle the camcorder - and for now, it can't be automated.

Ok I understand that I must use is-dv driver.... But what file are the working driver ?? all the oemX.inf wont install even if I mod them... Im quite experimented with computer and hardware ... but when talking about "writing" driver im completly lost... anyway Ill try to mod the driver with another VID-PID... edit : ok.. VID and PID is ok but oemX.inf = libusb driver ? edit : holy smo..... we always learn thing by planing with inf file... I misused your instruction... when you say mod the VID and PID... you mean the whole line ! (else than the var name) now im getting something ! ill probably post a video soon edit : ok...Ill get it someday... Now i can install as "Dv5900(video)" (or Audio or Still but Im sure Video is the one I need) but then it wont work... and im sure something is wrong as I can open and unlock the cam in ops while Dv5900 driver are installed Ive tryed with 5 capture software and none can "preview" the "graph" is-dv is the worst one ...its gray.. showing nothing even when I choose my webcam as a capture device (witch work on other software) any other tips until I just stop wasting my time ?

IIRC, only DV5700 works (you indicate you have tried DV5900). It would be great to see some more comparisons - The 640x480 using IS-DV seems to be of much better quality than changing USP.BIN to 640x480.

If you do want to play with this, you will need to connect the camcorder to one USB port, and bind it to libusb. Unlock the camcorder with Ops, then move the camcorder to ANOTHER USB port, and bind it to the ISDV drivers. You will need to do this every time you power cycle the camcorder - and for now, it can't be automated. How do you stop the camcorder from power-cycling when you switch usb ports?

i dont know how he does it, but you could hook up the +5 line to a 5v wall-wort transformer (or 5v worth of batteries) and keep the data +/- lines hooked up to the usb port. or use a powerd usbhub to keep the power to the camera but thats just a guess

you shouldn't need to do that. It was sufficient for me to just switch drivers

...shh I make a typing mistake about the 5900 .. its installed as a 5700. .. but still wont work. What I do : Plug the camcorder... install saturn driver....open..unlock.....change saturn to is-dev 5700 (video).....hardware wont power on balbalba..so...reboot.....dv 5700 (video) is ok.... nothing in is-dv or any capture software.. then : plug the cam corder....install saturn.....open unlock...uninstall saturn driver....reboot...detect...install dv 5700 (video)....hardware wont power up.....another reboot....(camcorder still open)......nothing shown anywhere.. ill retry the 2nd..

I achieved success by installing IS-DV drivers on a different XP partition than libusb. I unlock with OPS then reboot leaving camcorder plugged in while I select an XP partition with IS-DV driver (using Windows multiboot boot.ini). I believe ygfperson has had success using another method. andreq - keep trying, we need more comparison shots. You might need to install just libusb filter or just driver to get results. extracted from one of my posts above: You first need to unlock camcorder with Ops, then reboot leaving camcorder plugged in. I usually just reboot to another XP instance, but have also removed libusb device driver leaving just libusb filter - which allows dv5700 driver to work if libusb has not been invoked (requires reboot after unlock also).

you shouldn't reboot. Rebooting will power on and off the camera too

Well now I can't remember all the details, but I am sure a shutdown restart and selecting another partition worked several times for me. I wonder if some motherboards continue to power USB through a reboot. I think we need a how to when using only a single partition (my multipartitioned multiXP machine is uncommon).