This message did sometimes appear during scanning, mostly when other programs on the computer are used during scanning. When multisampling was used, these crashes were more frequent than without.
After the most recent update 6.4.3r9, multisampling got almost impossible due to the frequent crashes (always during image processing), so I have downgraded to the previous version which seems to solve the problem for now.
Any suggestions ?
Memory: 1 GByte
CPU: AMD 2,2 GHz
Scanner DigitDia 4000
System: Win XP SP 2
Eckart M?rkel
SF Launcher hat ein Problem ... und muss beendet werden
Moderator: LSI_Ketelhohn
- RAG
- SilverFast Master

- Posts: 761
- Joined: Wed Jan 12, 2005 7:59 am
- Location: Sonoma County, California
EMaerkel,
I read a posting from "degrub" about reducing the amount of memory allocated to Photoshop (this helped another user). Scanning, especially with de-screening, can use considerable system resources.
If you are using a program other than Photoshop you should probably submit a support request to LaserSoft.
I read a posting from "degrub" about reducing the amount of memory allocated to Photoshop (this helped another user). Scanning, especially with de-screening, can use considerable system resources.
If you are using a program other than Photoshop you should probably submit a support request to LaserSoft.
Member in good standing - NAPP
A picture is worth a thousand words!
A picture is worth a thousand words!
Hello RAG,
Thanks for your reply. As I had already memory problems in the past, I now have the task manager running to monitor the available memory. Problems do also happen if there is no obvious memory lack.
Eckart M?rkel
RAG wrote:I read a posting from "degrub" about reducing the amount of memory allocated to Photoshop (this helped another user). Scanning, especially with de-screening, can use considerable system resources.
Thanks for your reply. As I had already memory problems in the past, I now have the task manager running to monitor the available memory. Problems do also happen if there is no obvious memory lack.
Eckart M?rkel
I can confirm this problem after upgrading from 6.4.3r8 to 6.4.3r9. I also had this problem when Photoshop wasn't even running and Silverfast was running standalone, I ussual use it standalone.
I think the allignment problem is solved but a software bug was introduced.
I already made a support ticket for this problem together with colour differences between the preview and the final output.
I think the allignment problem is solved but a software bug was introduced.
I already made a support ticket for this problem together with colour differences between the preview and the final output.
-
tobbbie
- SilverFast Beginner
- Posts: 22
- Joined: Thu Jan 05, 2006 3:48 pm
- Location: Bietigheim-Bissingen/Germany
I also had a problem with the r9 release.
If you watch the manual iSRD settings, the steps it can take for the correction
strength were reduced from 255 to 20 and the automatic was incredibly slow
also delivering unacceptable results (e.g. a width of 5 pixels).
Stepping back to r8 everything is as normal.
bye
tobbbie

If you watch the manual iSRD settings, the steps it can take for the correction
strength were reduced from 255 to 20 and the automatic was incredibly slow
also delivering unacceptable results (e.g. a width of 5 pixels).
Stepping back to r8 everything is as normal.
bye
tobbbie
DigitDia 4000 / FW1.04 using SilverFast AI (latest version)
Searching for:
- IT8 verification strategy
- decode of EXIF maker notes for SilverFast AI JPEG write
Searching for:
- IT8 verification strategy
- decode of EXIF maker notes for SilverFast AI JPEG write
Return to “All other problems”
Who is online
Users browsing this forum: No registered users and 1 guest
