Thanks man! Been hanging out for the drag and drop thing to work so that I can tweak the developing of individual RAWS to my liking (...weird about the space in file path quote thing, cool you figured it out though!) Fetch will now become my developing software of choice! Great work. Really appreciate it!

Next version
Is anyone working on an updated version of PV2Fetch? If not, I may try to write some code if I can find time this summer. Here is my wish list: 1) Some sort of feedback/progress meter while the files are being downloaded/converted. 2) Ability to control the directory that the files go into, including separate directories for the raw and jpegs when downloading from the camera. 3) Ability to recognize different cameras and automatically select the download directories based on this. Is there any sort of serial-number that can be easily located? If not, a simple scheme would be to use PV2Tool to upload a file named 'camera.id' to each camera, and the text of this file could be used as the name of a sub-directory for the files to be put into. Thanks, -Jeff

jnorden, I' m not working on an updated version, so you're ready to hack away. Those sound like some great feature ideas - if it works out I'll be glad to accept them into the main codebase and add your name to the credits. It is possible to get the pv2's serial-number over USB. maushammer.com has a list of the pv2 USB commands. You could issue command $5E twice, first with byte 17 set to $0f, and next with byte 17 set to $10, to retrieve the two parts of the serial number. I'm sure none of this means much to you right now, but after you read that linked page and get your hands dirty with the pv2fetch codebase I'm sure it will.

Re: RawVB0_21.zip
I saw around the end of 2005, Marshall and Bill were talking about the VB prog that converted the FF raw files to JPG, I was wondering if anyone still had that and if I could possibly get ahold of a copy? I bought my daughter a Che-Ez! camera for her B-Day and it runs off of the FF drivers, and that Twain conversion takes FOREVER, I spent like 90 min to transfer 150 images. Thanks ahead of time. -Dyke Jones

PV2Fetch (scroll back up through this thread to find link to la-*test*-('") release) came after the old VB program and does a better job.

These cameras have a simple (relatively), lossless compression mechanism for storing the RAW imager data. This leaves a lot of work for the system which is pulling images off the camera - decompress the RAW data, demosaic it to a RGB image, image processing to improve the image and then compress as JPEG. I expect this will be fairly slow for 'most any software. Most other digital cameras have all the processing to JPEG done by the camera's processor. Retrieving images off the camera is just a matter of copying JPEG files from the device. PV2Fetch is the easiest thing to use, I think. Though, I don't know that it'll be faster. Let us know how it compares to the FF drivers!

PV2fetch is definately the best choice short of manipulating the images by hand. As for being able to change directories, as Jnorden asked, my solution is seperate directories for each camera with a copy of pv2fetch in each directory.

I wanted to ask, the software cvs uses might be comparable to the software on those kodak machines where you put in your digital cameras (even the older ones that take raw images) and they process them. as in, the software applies the same routines to the pics the digital cameras take. maybe if we could figure that out, we could apply the same routines on the pv2 images and see if it would give us the same quality as cvs2 ones?

The best bet right now is to use the FF2 drivers, that is if you can find them.