Forum Replies Created
- AuthorPosts
- August 10, 2009 at 8:18 am in reply to: ICAP_XRESOLUTION and ICAP_YRESOLUTION and memory problem #24981
Kodak made a scanner, the i30 (well, they made a lot of scanners but I like the i30). At that time the drivers that Kodak used for their i-series contained an additional mode, simulation mode. If you search Google you can find the driver – typically with the words ‘Scanner Validation Tool’ in the name. Then if you search this forum for the word ‘simulation’ you should find a thread where I tell you how to enable it, if you can’t find either then post back and I’ll go get links again.
.
August 10, 2009 at 7:52 am in reply to: ICAP_XRESOLUTION and ICAP_YRESOLUTION and memory problem #24979yup, thats pretty much all of it – if you’re already checking the units, bitdepth and pixeltype then you’re doing as much right as you can. you may benifit from testing development on a more stable driver – I use the Kodak i30 in simulation mode and highly recommend it
.
August 10, 2009 at 6:03 am in reply to: ICAP_XRESOLUTION and ICAP_YRESOLUTION and memory problem #24977I think you have a device where the Ui and Api don’t match. In those cases I usually trust the Ui over the values reported to the api as it has seemed in the past that when in doubt trust the Ui over the Api. I also don’t think the device’s driver is doing any check on your available memory and hiding values, I’d bet that the Ui was tested better than their api and they ‘forgot’ to remove the higher values.
Are you following the capability guide for capability ordering when you set the caps?.
August 6, 2009 at 3:45 pm in reply to: ICAP_XRESOLUTION and ICAP_YRESOLUTION and memory problem #24975like you I like the SupportedCaps capability and enjoy using Get to determine what the appropriate values are, seems kinda natural to use the capabilities as they are documented and as they are used in sample code.
that said, if you see different values returned from a driver than are displayed on the driver’s Ui there is a good chance you are either doing something wrong, have a close to worthless driver on your hands or both.
what are you using for units and how is the tranfer set? try switching to file mode for the transfer to check the memory issue. if you have not taken a look at Dosadi’s twirl & twister utilities with that datasource.
.
dosadi.com has a videods that seems support many generic webcams that may work for you
.
no problem you use GetFirst, GetNext until you find the device you want to open. if you’re comfortable reading vb.net code i have some over on codeplex.com/opentwain that does just this.
no, they made that bit up.
.
..maybe if you could be a little more specific
.
does that device support multi-streaming? In my somewhat limited experience, I’ve only run across kodak devices that supported that.
.
there have been post here before about that vendor not exposing their capabilities and instead using CustomDsData hacks. If it were me I would start with Dosadi’s ‘twirl’ and check the output of the report, you can post it here if you have trouble with it. Twirl will let you know if the Capabilities are reported are supported and how many general problems there are with the driver.
.
there is a commandline sample in the 2.0 downloads.
.
no, netMasters code seems to be the basis for pretty much all .net code that I’ve seen. If you having trouble with his code, read through the comments on his article – most problems have addressed in there even though his sample code doesn’t include the fixes. You can also search here, there have been several threads about his code. Then you could ask here if there were twain specific problems remaining.
.
‘should’ is a funny word. All driver drivers are not created equal.
Yes, your generic twain code ‘should’ work on your canon/epson/hp but that is rarely the case once you start to do anything more than send enableDs..
That’s what I see on every device. I wouldn’t say anything was wrong here. I typically don’t expect anything more than a dib from native or memory transfers, and haven’t seen any file transfers go to multi-image tiff.
But it’s easy to code around, image manipulation code snippets/articles/samples/libraries are easy to come by and pretty much every single one of them less complex than getting twain drivers to play nice.
.
what twain library are you using?
there is no conditioncode ‘get’..
- AuthorPosts