[sane-devel] VEHO film scanner test application started

[Aidan Karley]

That'll be cool. I'll keep subbed to the list and keep my eyes (well, mail filters, probably) peeled for news.
I'm going to be spending much of the next 6 weeks to two months working abroad, and will have to be travelling within baggage weight allowances, so I won't be on the same continent as the scanner in any case.

Did the code numbers in the windoze driver .INI files match up with what your device has ; any idea how many variations of this there are?

-- 
Aidan Karley,
Aberdeen,
Scotland


--- On Fri, 8/7/11, Glenn Howald <glenn.howald at gmail.com> wrote:

> From: Glenn Howald <glenn.howald at gmail.com>
> Subject: Re: [sane-devel] VEHO film scanner test application started
> To: "Aidan Karley" <aidan_karley at yahoo.co.uk>
> Cc: sane-devel at lists.alioth.debian.org
> Date: Friday, 8 July, 2011, 6:56
> I am still working on this. I have a
> test application which seems to 
> correctly scan my slides. I have been on vacation and
> catching up, but I 
> will be back working on this (and perhaps have a little
> more progress to 
> report) sometime in the next week or so.
> 
> My ultimate goal is to integrate it with the rest of the
> SANE family of 
> devices and then use xsane or something to scan my backlog
> of negatives.
> 
> Your help with testing will be greatly appreciated once I
> have something 
> which works (even a little).
> 
> On 7/3/2011 2:13 PM, Aidan Karley wrote:
> > Glenn Howald glenn.howald at gmail.com wrote
> >> I am starting work on testing my transparency
> scanner (with a desire to get it to
> >> work as a scanner or camera under Linux) because
> it is no longer supported under
> >> Windoze 7.
> > Installed Ubuntu on my new Windoze 7 laptop on it's
> first boot after I brought it. Still not missing Windoze at
> home.
> >
> >> lsusb returns:
> >> ID 05a9:1550 OmniVision Technologies, Inc. VEHO
> Filmscanner
> > Same for mine.
> > "Bus 002 Device 004: ID 05a9:1550 OmniVision
> Technologies, Inc. VEHO Filmscanner"
> >
> >> So far I am reverse engineering the commands from
> USB dumps on my Windows XP
> >> machine.
> > That would be the one that died, causing me to buy the
> Win7 laptop and a Linux magazine? Or was it a Win2k machine?
> I've forgotten already.
> >
> >> This is simply a notice that I am starting some
> development of SANE support
> >> for this scanner.
> > If there's anything I can do to assist in the way of
> testing ...
> >
> I will keep you informed of my progress and when I need
> some testing help.
> >> Anyone have suggestions for a back-end to use as a
> model for this type of
> >> USB support?
> > [Blind stag]
> > It seems there was a flush of different models like
> this in the UK a couple of years ago, and I got one that was
> remaindered. The software had a really horrible interface,
> and crashed /ad nauseam/, but I recall that it had
> calibrations options and several available resolutions.
> >
> > Oh, searching the box, I find manuals and a CD too. Of
> Windoze drivers. But the Setup.ini file for the 32-bit
> version tells me
> > "Product=OVT Scanner X86
> >
> > PackageName=OVT Scanner X86.msi
> >
> > ...
> > ProductCode={6B566EFE-DC1D-471F-93DD-84832663F140}
> >
> > ...
> > PackageCode={24CDC6DC-2AA8-45D1-ACA8-E73050E39762}"
> >
> > Is that any use for determining if we're talking about
> the same or similar devices?
> >
> > Ah : "1650= (This will also install the .NET
> Framework.)"
> > That may well have been why I was running into
> problems. Nothing .NETty worked on that machine.
> >
> > Elsewhere I have .SET files that tell me things like
> >
> "7660APLGam="CameraSetting\SupportCamera\7660APL\DeviceProperties\VideoProcAmp\Gamma"
> >
> >
> 7660APLCol="CameraSetting\SupportCamera\7660APL\DeviceProperties\VideoProcAmp\ColorEnable"
> >
> >
> 7660APLWb="CameraSetting\SupportCamera\7660APL\DeviceProperties\VideoProcAmp\WhiteBalance""
> > Which makes me think that these are settings that need
> to be set on the camera (by your software?) Any use?
> >
> > Strangely, the ".SET" comments also seem to include
> settings for treating it as a video camera. Puzzled?
> >
> >
> > As you can see, I only have the vaguest idea of how
> these things are meant to work. But if you need information
> or a test-bed to try things on ... call.
> >
>  From my reverse engineering, this scanner does behave
> quite a bit like 
> a video camera. Once the setup commands are sent to the USB
> device, the 
> scanner repeats sending the image (sort of like the frames
> of a video).
>