(Mostly Digital) Aftershot Pro 3 Stuck on Exporting

[Ariston]

I have edited a large format photo and am trying to export it. I limited the size to just under 50 megapixels. Still, Aftershot keeps freezing up when I try to export the edited image. Has anyone else dealt with this?

It works with 35mm scans just fine. How small do I need to make the file in order for it to work okay? I want to do a fairly large print, so I'd prefer not to lose all the detail.

I do not have the latest and greatest pc, but it is an i5 3.2ghz processor, with a decent video card and 12 gigs of RAM. I've never had issues before... maybe Aftershot sent out a bad update?...

 

[Kino]

You may need to increase the cache memory available to your PC if you are running a 32 bit version of Windows.

Assuming you are using Windows 10: https://www.x-plane.com/kb/increasing-virtual-memory-on-windows/

Otherwise, search for "increase cache size Windows whatever" for your system.

 

[MattKing]

Aftershot Pro 3 runs only in 64 bit.
What format of file are you exporting?

 

[Ian Grant]

Aftershot Pro 3 runs only in 64 bit.
What format of file are you exporting?

64-bit distributions require 32-bit compatibility libraries (ia32-libs), that's according to Corel. But it's a faster processor than my laptop and PC and is 64 bit, I ahve no issues with the program.

Ian

 

[Ariston]

I am definitely on a 64 bit computer. I think it was jpeg, but am not in front of the computer right now. Whatever format it was, I used the same for a smaller file and it worked fine. Maybe it was a bad Windows update. I will give more info shortly.

 

[Kino]

Problems I have run into in the past with graphics programs:

• Too many recursive directories/folders; try writing to the root directory.
• Windows cache too small; enlarge Windows cache.
• Another program has messy housekeeping; close everything, reboot and only open the program you need to make the render.
• Drive/SSD too fragmented; defrag drive.
• External drive unable to keep up; render to internal drive.

 

[Ariston]

Problems I have run into in the past with graphics programs:

• Too many recursive directories/folders; try writing to the root directory.
• Windows cache too small; enlarge Windows cache.
• Another program has messy housekeeping; close everything, reboot and only open the program you need to make the render.
• Drive/SSD too fragmented; defrag drive.
• External drive unable to keep up; render to internal drive.

Man, I can't figure it out. I keep my computer pretty tidy, and keep a close watch on what I do and don't allow to be added to the startup sequence. I checked the cache setting from your earlier post and made some changes, and still no luck.

I edited another large format file and it worked fine. I thought that maybe it was because I added layers, but that worked for other files, too. What's weird is that I stitched together the two parts of the one I'm editing (from scratch) again, and re-edited it (essentially a new file), and it still wouldn't work. There is something I am doing in editing that it doesn't want to export. Very frustrating!

 

[MattKing]

I think it was jpeg, but am not in front of the computer right now.

A 50 megapixel jpeg is a pretty big jpeg!

 

[Kino]

Try it at a lower resolution.

Is the source file corrupt?

 

[Ariston]

A 50 megapixel jpeg is a pretty big jpeg!

I tried tiff, too. The other (90Mp) large format photo I tried worked fine. And fast.

Try it at a lower resolution.

Is the source file corrupt?

I thought maybe. That's why I started again from scratch, but it still didn't work. I edited the same way, so that's the only thing I can think that was the same between the two.

I'll try a lower resolution, but higher res files are working fine.

Thanks for the help. Keep it coming.

 

[Ariston]

I tried it at 20% quality, and still no go. Is it possible that the original scans were corrupted, but work fine everywhere and stitch together fine, and then don't work in Aftershot. I may have to go back and re-scan.

I have now edited this image twice, and editing is my least favorite thing to do.

I hate computers.

 

[Ariston]

Try it at a lower resolution.

Is the source file corrupt?

I edited each of the two scans (that I stitched together) individually, and they both exported fine, so they are not corrupt. I don't know what else to do, so I am un-doing one edit at a time to see if a particular edit is giving it fits.

... Actually, as I was typing this I tried to export without the "Zframe" plugin, and it exported. Something is wrong with that plugin. Thank you to everyone for your suggestions!

 

[Kino]

Try re-installing that plugin. The libraries or links to the libraries it uses can be corrupted by updates to other programs...