ACDSee Pro 3

Back to Topic OverviewPost New Reply

Crash and/or mishandling of large TIFF files

(3 posts)

Tags:

  • focusfirm
    Member

    I have been running into errors with larger TIFF files (over 250MB). Specifically, 16-bit TIFF files whose dimensions and resolution take the file size over 250MB. Some larger files handle OK, but most either display as black or crash ACDSee Pro 3.0 release version. These same files display fine in Photoshop CS4, Canon Professional software, and QImage printing software. ACDSee Pro is the only software having issues with them so far. I am not trying to even edit these files - just view, zoom and pan. When first opening some of them, I saw messages about the file being corrupted according to a plug-in. It did not say which plug-in was the problem. The Manage and View windows say the file is an unknown format. However, if I load the file back into CS4 and resize it smaller and save, it will work fine in ACDSee Pro. Has anyone else seen this? I have XP Pro SP2 and 4GB RAM. It makes it impossible to use Pro to view files I am preparing for or have already sent to the lab.

    Posted On October 17, 2009 - 07:31 PM (1 month ago) (Permalink to this post)

  • richardchesher
    Member

    This is listed as a known bug on the ACDSee Pro 3 Release Notes. Since so many professionals use large tiff files it is a major flaw that hopefully will be fixed ASAP.

    Yes, I have the same problem with large Tiff files. Some work, some don't even when they are the same exact image saved with Photoshop CS3. I can't figure out what the problem is. When they do work you can edit them BUT, as with any really large file (over 100MB) you need to make ONE change and save the file, get out of the editor, then reopen the file to make a second edit. Otherwise ACDSee will crash. This was a problem in Pro 2 and is still a problem in Pro 3. I've tried the Windows fix to allow full use of 4GB of RAM but ACDSee Pro3 still crashes with big files.

    Richardhc

    Posted On October 18, 2009 - 05:25 AM (1 month ago) (Permalink to this post)

  • Jorgd
    Member

    Would be nice to have this fixed in Pro 2, for those people who do not intent on upgrading to Pro 3.

    Posted On October 18, 2009 - 05:58 AM (1 month ago) (Permalink to this post)

Subscribe to this topic via RSS

Reply

You must log in to post.