Where's The Image?

[rckowal]

I use Vuescan 7.6.65 with an Epson flatbed scanner. Vuescan is set to automatically open scanned images using Photoshop CS as a "Viewer".

When Photoshop opens (prompted by Vuescan) it does not display my scanned image. A "New" dialogue box opens (like the one in "File" menu > "New") but there is no image (only options for selection). Clicking on "OK" opens a new (blank) box in whatever "Background" mode was selected (but no image).

What's wrong here & how do I fix it so my scanned image opens automatically in Photoshop?

Best regards, Dick

 

[mscallisto]

Does Vuescan have a "Help

 

[rckowal]

Yes it does. The applicable paragraph is shown here.

"Viewer: If the "External viewer" option is enabled, the specified program will be started with each cropped image upon completion of a scan. The default value is "default".

On Windows, if the viewer name is "default", the file association for this type of file will be used. You can also put command-line options after the name of the viewer (e.g. "vuepro32 /fillwindow" to display images without a window frame with VuePrint). If the name of the viewer has "%1" after it (e.g. vuepro32 "%1"), the file name will be substituted at that point. If you use the %1 argument on the command line, be sure to put double-quotes around it, or file names that have embedded spaces won't work."

I have Vuescan, as well as Windows folder options setup accordingly but from what I understand; Photoshop (not Vuescan)is what is opening into the blank dialogue box. Before some thing changed (don't know what) Photoshop used to open the scanned image ok with the same Vuescan settings.

 

[mscallisto]

I'm familiar with VuePrint but have never used VueScan.

It does seem however that vuescan is not passing the filename to photoshop.

Is there a file association with the filetype generated by your scanner software and photoshop?

e.g. if your scanner produces a bitmap (.bmp) and you double click a .bmp file, does photoshop open it?

 

[rckowal]

Thanks for the reply Mscallisto, it's appreciated.

Problems all solved now thanks to help of folks on another forum. Just a matter of setting an incorrect file association.

Best regards