When I try to scan in Photo-Paint using the Twain Scanner setting for my Canon Scanner, the application crashes on Scan. The Scan Preview works just fine. The WIA (Windows Image Acquisition) also works fine, but has lousy custom settings. I also updated to the latest Canon scanner driver.
However, if I Twain Scan in CorelDraw, it works just fine. Furthermore, if I use the "Edit Bitmap" function in CorelDraw, it opens Photo-Paint with the scanned image, no problem. I can then save the image from either of the programs.
Now, I can live with this workaround, but it's really frustrating not being able t directly Twain Scan from Photo-Paint. So, if anyone has a solution I would be most grateful. Thanks.
Not sure TWAIN wascsupported in 2018 and windows 64 bit programs.
I'm sorry, but that answer makes absolutely no sense. My TWAIN is working perfectly in CorelDraw 2018, but it's crashing Photopaint 2018. Both applications are included together in Corel Graphics Suite 2018.
For what it's worth, I have always found Twain, and actually also WIA, to be a bit laggy and unreliable.I use WIA on 64-bit Draw/PP 2020 because my scanner doesn't seem to have 64-bit Twain drivers, but I can not say it is working perfectly.When everything is working normally, I can scan from both apps though.
I have the choice of using TWAIN for either Canon drivers or WIA, but both crash Photo Paint. I also have WIA as non-TWAIN and that works okay in Photo Paint. However, WIA is very limited in scanner controls compared to the Canon TWAIN, which is why I prefer it to WIA.
When used in CorelDraw, the TWAIN selection works just fine, no glitches (so far). So for now, that is the route I will have to take.
What I've always done was to use only the scanners software, saving to a working folder for the project and importing into Photo-PAINT for editing. Maybe people think it's less convenient but it always works and provides an archive folder of original scans for the project.
I think the basic problem is that TWAIN is a 32-bit concept so is unreliable on a 64-bit program.
I''ve moved to the same approach as David M.