Install New Update 1.1.0.30 or Not???

[jpmccormac]

1. What am I gaining by installing the new update to ver. 1.1.0.30? Some say it runs slower than the current version.
Corel says these enhancements have been added, but the new version doesn't support my camera's RAW files (Canon G15):
- Improved Sharpening algorithm
- Selective Color filter speed improvement
- New RAW default settings: RAW noise enabled
- Workspace changes for JPEG display
-Corel PaintShop Pro X5 auto-detect

2, If I update is there any way to go back to the earlier version if I'm not happy? I have a backup of the ASP folders.

[afx]

1. What am I gaining by installing the new update to ver. 1.1.0.30? Some say it runs slower than the current version.

Depends. Try yourself.

2, If I update is there any way to go back to the earlier version if I'm not happy? I have a backup of the ASP folders.

As long as you have the old installer it is easy to go back.

cheers
afx

[Zarastro]

I won't update for the moment, since this version has been prone to get stuck while processing raw files even with OpenCL disabled - something that never happened in 1.1.0.10. And I really didn't feel any improvement on the images processed from my A700 camera RAW files.

[lundbech]

I won't update for the moment, since this version has been prone to get stuck while processing raw files even with OpenCL disabled - something that never happened in 1.1.0.10. And I really didn't feel any improvement on the images processed from my A700 camera RAW files.

Are you talking about 1.1.0.10 or 1.0.1.10?

[Zarastro]

I won't update for the moment, since this version has been prone to get stuck while processing raw files even with OpenCL disabled - something that never happened in 1.1.0.10. And I really didn't feel any improvement on the images processed from my A700 camera RAW files.

Are you talking about 1.1.0.10 or 1.0.1.10?

Oops, sorry! 1.0.1.10.

[dFlyer]

I have the A700 and A100. I've been using 1.1.0.30 since the beta without a problem.

[wildhoney]

Yesterday I've updated my AfterShot Pro to 1.1.0.30 and performed some simple speed tests. Camera model is Nikon D700. I converted six RAW files (14-bit) into 16-bit TIFFs with Noise Ninja enabled. The results are as follows:

- OpenCL disabled: 3.25 sec/image
- OpenCL "minimum": 2.83 sec/image
- OpenCL "low": 2.97 sec/image

It seems to me that all works as expected since I have a relatively fast CPU and cheap low-end GPU (see my hardware list). And what's more, new version certainly produces considerably better picture (more smooth and with less artifacts). So my verdict is "all right". The only sad thing is that the new version still doesn't support Nikon D600. My friend is going to buy a D600 soon and is looking for a good and not too expensive RAW processing software. Now I think he will prefer Adobe Lightroom...

P. S. I run AfterShot Pro in Windows 8 Pro x64 (not Linux).

[hannes_hab]

not very elegant but a workaround for the Nikon D600:
to work with NIKON D600 pictures

on Linux install exiftool if not installed yet
open the folder with the D600 pictures in a terminal window

exiftool -model="NIKON D7000" *.NEF

on Windows install exiftool if not installed yet
install ExifToolGui
http://u88.n24.queensu.ca/~bogdan/

select the D600 Nefs change camera model to d7000

now the files are recognized

[pekkal]

D800 RAWs with zPerspector: (full size) output batches with zPerspector take either very long or never finish. Reverting back to the previous (1.0.1.0.10?) version seems fix this issue.

Regards,
pekkal

[rossopaolo1949]

Sorry, but where can I find this update???? I don't find it on the support site, so I can't install it.
Can you help me ?

[BrianCee]

rossopaolo1949

Please read this topic :-

http://forum.corel.com/EN/viewtopic.php?f=90&t=48791

[Zarastro]

D800 RAWs with zPerspector: (full size) output batches with zPerspector take either very long or never finish. Reverting back to the previous (1.0.1.0.10?) version seems fix this issue.

Regards,
pekkal

I've tried to reproduce this behaviour with my A700, and in batches which contain zPerspector activated in some pictures, the lockups DO occur, but not necessarily on the pictures where it's been activated. (This has happened once to me during a series of 10 batch tests.) Also, pressing the batch stop button makes no difference: CPU continues to be fully utilized and the only way to get processing back is shutting ASP down and restarting it again (which can be done gracefully from the UI).

Sometimes, when I activate OpenCL at the minimum setting, the batch gets stuck for some time but normally continues after some waiting, and the batch processing ends with the note that there was 1 error out of 40 images. However, the message does not point which file caused the error to occur, neither the nature of the error.

Other thing I've noticed is that some pictures are processed out of order; in this batch, it started from the last selected image for the batch and then came processing from the first to the penultimate image. Sometimes this image is processed at the middle of the queue, and so on. I don't know if this has something to be with the plugins which are activated for each image.

As with you, going back to previous version fixes the issue. So upgrading to the latest version is still a no-no to me.

[dFlyer]

D800 RAWs with zPerspector: (full size) output batches with zPerspector take either very long or never finish. Reverting back to the previous (1.0.1.0.10?) version seems fix this issue.

Regards,
pekkal

I've tried to reproduce this behaviour with my A700, and in batches which contain zPerspector activated in some pictures, the lockups DO occur, but not necessarily on the pictures where it's been activated. (This has happened once to me during a series of 10 batch tests.) Also, pressing the batch stop button makes no difference: CPU continues to be fully utilized and the only way to get processing back is shutting ASP down and restarting it again (which can be done gracefully from the UI).

Sometimes, when I activate OpenCL at the minimum setting, the batch gets stuck for some time but normally continues after some waiting, and the batch processing ends with the note that there was 1 error out of 40 images. However, the message does not point which file caused the error to occur, neither the nature of the error.

Other thing I've noticed is that some pictures are processed out of order; in this batch, it started from the last selected image for the batch and then came processing from the first to the penultimate image. Sometimes this image is processed at the middle of the queue, and so on. I don't know if this has something to be with the plugins which are activated for each image.

As with you, going back to previous version fixes the issue. So upgrading to the latest version is still a no-no to me.

Have you tried this with openGL turned off. I have the A700 and A100 and have not have any problems with batch processing. It maybe related to OpenGL.

[Zarastro]

D800 RAWs with zPerspector: (full size) output batches with zPerspector take either very long or never finish. Reverting back to the previous (1.0.1.0.10?) version seems fix this issue.

Regards,
pekkal

I've tried to reproduce this behaviour with my A700, and in batches which contain zPerspector activated in some pictures, the lockups DO occur, but not necessarily on the pictures where it's been activated. (This has happened once to me during a series of 10 batch tests.) Also, pressing the batch stop button makes no difference: CPU continues to be fully utilized and the only way to get processing back is shutting ASP down and restarting it again (which can be done gracefully from the UI).

Sometimes, when I activate OpenCL at the minimum setting, the batch gets stuck for some time but normally continues after some waiting, and the batch processing ends with the note that there was 1 error out of 40 images. However, the message does not point which file caused the error to occur, neither the nature of the error.

Other thing I've noticed is that some pictures are processed out of order; in this batch, it started from the last selected image for the batch and then came processing from the first to the penultimate image. Sometimes this image is processed at the middle of the queue, and so on. I don't know if this has something to be with the plugins which are activated for each image.

As with you, going back to previous version fixes the issue. So upgrading to the latest version is still a no-no to me.

Have you tried this with openGL turned off. I have the A700 and A100 and have not have any problems with batch processing. It maybe related to OpenGL.

Actually turning on OpenCL improves things a bit - as I've said, in this case the lockups are rarer, but sometimes they still do occur.