Interesting new bug while using HDR

[nurgle]

Hi, Have been scanning some glass negs in Silverfast A1 6.6.r2 (Intel iMac, 4gig ram 320 gig HD, OS 10.5.4, Epson V700 )

Have been using the Grey HDR and all area Transparency (the Negs are 8.5"x6.5")

(I have a Epson 7600 24" large format printer, and also 9500 44" large format printer), so I want big sharp files.

using 2400 Dpi I get an image, but change the dpi to 3600 (optical for the scanner) and the file that results then is totally blank...

Now why does it do that.???. changing the resolution should not change the difference between getting an image file and not... does it have memory problems, and I have tone of memory, Ram & HD.!!

I always keep 100 gig hd space free. (I also have 4- 500 gig external drives also. did I mention BIG files..)

as great as silverfast can be when it want to be good, it can also be dam frustrating at times... (and those are always at the time when you dont want it to be... clearly their stress sensing routine is working well....
Nurgle.

[LSI_Ketelhohn]

Dear Nurgle,

you can test your Mac with the Macintosh OSX disc which came with your Mac. there is a hardware testing suite on it.
If you do not have an hardware problem please contact us by our support assistant because I need some logfiles for further troubleshooting.


kind regards,
Arne Ketelhohn
- LSI support -

[nurgle]

Hi,
disk tests perfectly. (TechTools Pro, Disk Warier, etc. No permission problems either.!) there is no hardware problems here.
(Adobe Bridge crashes if I click on a Gif, is about my only problem, well apart from this one)
I want to send some files to a company with a 64" printer to cover a wall of a display..
Nurgle

[nurgle]

Hi, just an update. have tried several resolution settings.

it seems that anything above a 600Mb files is a non event... so it seems it has a memory problem/bug. (I have a 4gig ram, and tons of disk space to spare)

Strange as earlier Silverasft versions, (with my epson 2450) I have been making 1.5 gig files... (bloody slow though)

Nurgle

[LSI_Ketelhohn]

SilverFast has a limitation of 2Gig per operation and 30000lines per frameside.
This limit does not apply to the final image but to the internal operations.
There are several reasons why a 600mb file might hit this limit.
the lines per side limitation applies to the actual scan area. If a frame is turned the enclosing rectangular is the actual limit.
e.g.: a frame is turned exactly 45° the actual scanning area would than be across the diagonal and not the frame side. So a 10x10 frame turned 45° would result in a scanning area of 14x14.

Another Source of a larger internal filesize is that SilverFast always works with hardwareresolutions.
e.g.: you choose a hardware resolution of 1200dpi and a scaling of 110% this results in a 1320dpi image. But the scanner can not scan at this resolution and automatically scanns at 2400dpi if that is the next higher hardware resolution. This results in a much larger internal filesize.

Also the internal resolution is always 48bit so the internal image size is much larger than a 24bit output file.

If you comine these effects the internal filesize can be much larger than the output file.

The reson for this limitation is that the internal operations use several instances of the image (original. colorcorrected, MultiExposure Scan, iSRD channel, final image) all of these have to be in the Memory at the same time, So a 2Gig image may in fact take up several times its size in internal memory.

This is no problem with modern Systems but older workstations would have a memory overflow if we removed this limit.
So this limit will not be removed in the SilverFast 6.6 Series, but will fall in the next major release.

[nurgle]

Hi,
thanks for the explanation. That is the sort of reply that really does help (especialy when it cant find similar explanations elsewhere), as when you know what happens AND WHY, you can do things about it.
Regards
Nurgle