JobManager Output problems!

[kevinkar]

Hi,

Don't know how to describe this adequately, but I will give it a try. I have been scanning several hundred negatives manually since receiving my copy of SilverFast just a few weeks ago. It's going well, but I wanted to speed things up a bit so I have begun to try the JobManager to see if it really helps.

So far, it seems to be marginally quicker though the time saved is relatively small per individual film strip. I guess it will add up and save me plenty of time in the long run though.

The only problem is that the output from a JobManager job is somehow different from that of a standard (almost completly default) scan and this difference has been causing problems in my editing software.

I am using a Nikon LS-2000, SilverFast 5.5.2.r20 (TWAIN or Photoshop plugin though I use TWAIN more often) and my grapics applicatios are ACDSee 4.0.1.0598 and Photoshop 5.0.2.

Output from a default regular scan can be manipulated in ACDSee without problem and can be called up into Photoshop without warning, but any output from a JobManager job can not be edited and saved in ACDSee (I get an error that the plugin encountered an unrecoverable error and the save operation aborts) and in Photoshop, when calling up a JobManager output file, I get a warning box that states "The embedded profile does not match the current RGB setup. Specify desired input conversion:" and am then asked to convert from "Nikon Adobe RGB 4.0.0.3000" to another color space.

When I checked the SilverFast settings for a default manual scan versus a JobManager scan, they are pretty much the same though some items are not selectable depending on which scan is being used. Generally, they both have Nikon RGB as the embedded profile yet Photoshop complains only about the output from a JobManager session but not a standard manual scan!

Once called up into Photoshop, I can save the file (these are all TIFF output) which then has no problem being called up in Photoshop again or being further edited in ACDSee so it's clear that the tif out of a JobManager is different than everything else.

So what's going on here? Why are two separate graphics programs having problems with the output from a JobManager scan? What do I need to do to solve this problem?

Sorry for being so long winded and thank you for the help.

Kevin

[kevinkar]

I want to also point out that the faulty output happens using standard "Batch Mode" as well.

The resultant scans can not be rotated in ACDSee 4.0. I have a workaround which involves saving as a Windows bitmap and the resaving as a tif file but that's not a proper solution.

Something is going on with the output from SilverFast in batch or JobManager modes.

Anyone?

[LSI_Support]

Dear Kevinkar,
did you try the Option button in SilverFast? It brings up the SilverFast preset window, where - in the CMS tab - you can unselect the box "embed ICC profile". What happens, if you scan without profiles embedded?

[kevinkar]

Yes, I did uncheck the "embed ICC profile" box and the results were the same. I should also mention that this checkbox is checked when I perform single "default" scans yet the output is ok.

Is there a location where I can upload a sample that works in one case but not in another? Perhaps you have some software tools that can check the internal format of the tiff file and see what the differences are between the two outputs?

Kevin

[LSI_Support]

A single scan directly into ACDSee with the "embed profile" box checked renders a satisfying scan, is this correct?


BUT, when you perform a Scan-to-file out of SF JobManager and you open this image into ACDsee, the image does NOT look satisfying, is this correct?

[kevinkar]

On 2002-07-12 14:31, LSI_support_Kohler wrote:
A single scan directly into ACDSee with the "embed profile" box checked renders a satisfying scan, is this correct?

BUT, when you perform a Scan-to-file out of SF JobManager and you open this image into ACDsee, the image does NOT look satisfying, is this correct?

Technically, this is not correct. The scan itself LOOKS fine. So satisfaction of the resultant scan is not in question. The problem is that the results from batch or job manager are not able to be MANIPULATED and seem to have an issue being opened in Photoshop. This is the problem.

I am using ACDSee 4.0.1.0598 which has as it's editor, Photo Canvas Lite (an ACDSee product) 1.1.

When I scan, I scan vertically the way it is suggested so that means almost every scan has to then be rotated 90 degrees, but when I attempt to rotate an output from batch mode or job manager, ACDSee/PhotoCanvas generates an error and the image is not rotated.

I don't see this an an ACDSee issue though since a single scan from SilverFast produces an image that can be rotated, saved, manipulated at will but when the same image is output from job manager or batch, no go.

Hope this helps clarify the situation.

Kevin

[kevinkar]

Hello? Anyone have any suggestions? I really want to e-mail or FTP a couple examples to you so you can check the output yourselves to see what might be wrong with the images.

Just wondering if you have done any investigation in the differences between standard output and batch/job manager output. I know they should be the same but in my case, they are definitely different.

Thanks,

Kevin

[kevinkar]

I still have not gotten batch mode output to work properly. Anyone here want to offer a suggestion?

I still think it would be advantageous to send you a copy of a scan from batch mode and the same scan from a regular non-batch scan and see if there are any internal differences between the outputs.

Anyone?

[LSI_Flyvbjerg]

Ok, please send your files to "eric.flyvbjerg@silverfast.com". I will analize the files and report back.

Eric.