Introducing AfterShot Pro 2.2!

[andreas]

Currently trying to compile asGPS on Mac. With new Qt, for ASP2.2. I get the same error message. Have to look deeper into it. Would be nice to see some info in the missing symbols...

Andreas

[Arnfinn]

Installed the ASP 2.2 64 bit upgrade for Windows 7 and very pleased so far with the responsiveness of the thumbnail previews and the speed of ASP. Everything seems to go lightning fast now, compared to 32 bit 2.1
Should be even better when more plugins becomes available...

[tomk]

Installed Upgrade on Fedora 21 and got the following Errors and ASP won't start:

Fatal: QMetaType::registerType: Binary compatibility break -- Size mismatch for type 'QPaintBufferCacheEntry' [1024]. Previously registered size 16, now registering size 0.
QMetaType::registerType: Binary compatibility break -- Size mismatch for type 'QPaintBufferCacheEntry' [1024]. Previously registered size 16, now registering size 0.
Abgebrochen (Speicherabzug geschrieben)

[spoilerhead]

Are the .rpm files fixed yet? i have no intention of fixing them myself all the time ...

[Alex Brazeau]

Are the .rpm files fixed yet? i have no intention of fixing them myself all the time ...

Hi spoilerhead, I've just left Greg's office and can confirm this is sitting at the top of the backlog.

Installed Upgrade on Fedora 21 and got the following Errors and ASP won't start

Thanks, tomk. The team is looking into this.

[zawel]

Installed Upgrade on Fedora 21 and got the following Errors and ASP won't start:
Fatal: QMetaType::registerType: Binary compatibility break -- Size mismatch for type 'QPaintBufferCacheEntry' [1024]. Previously registered size 16, now registering size 0.
QMetaType::registerType: Binary compatibility break -- Size mismatch for type 'QPaintBufferCacheEntry' [1024]. Previously registered size 16, now registering size 0.
Abgebrochen (Speicherabzug geschrieben)

Have the same problem on OpenSUSE 13.1. It's caused by the outdated plugin, to solve it remove ~/.AfterShot/Plugins and start again.

[avant]

I wanted to thank Greg for this announcement and the dev team to make this happen. Great work - thanks a lot !
I really do like the UI of ASP and the workflow in general as it is quite intuitive for me.
It's good thing to see when reading the release history, that new versions are now released on a more frequent basis in order to be able to provide user feedback. Maybe it would be a good idea to make beta releases available to avoid surprises at the first days after release to stabilize the whole build/new features. Linux users are used to providing feedback and I am sure it would help in your case as well.

Just my feedback after initial installation on Fedora 21: I am using a Sony Alpha 6000 and this camera has been on the list of supported cameras, but it got removed. Same applies to the sister model Alpha 5100. When I browse through the model database in section lens correction, I can neither see Alpha 5100 nor Alpha 6000. Can someone shed some light on why none of those cameras are listed in the database ?

Thanks a lot - avant

EDIT: found now the entry in release notes of version 2.0.2.10 as ILCE 5000, ILCE 6000 - but again I can't find them in the database for selection.

[yves77]

I tried the new ASP 2.2 but:
- To few plugins
- No acces to noise reduction tool (except the raw noise reduction one). Big regression.
- The Pentax K3 is always ignored in the list of Pentax gears for distortion correction (since the Pentax K3 is treated by ASP). So when you want to correct a file, you have to manualy select the brand,then the model (I choose K5 or K30) then the lens.

Conclusions:
I reinstall ASP 2.1
I use DXO

Very sory.

Yves

[baldrick777]

I use DXO
Yves

According to their website, DxO is Win and OSX only, yet your sig indicates you're using Linux. I'm confused. Am I missing something?? Does DxO have a Linux version not published on their website? If so, please post a link.

Cheers.

[Dutchmm]

According to their website, DxO is Win and OSX only, yet your sig indicates you're using Linux. I'm confused. Am I missing something?? Does DxO have a Linux version ..?

I wish!

[John Lance]

Autolevel still does not work, not for the black level or the full saturation.

Version 2.2.0.29 64 bit.

I have NEF files being processed.

This is supposed to be a percentage of pixels with 1.00 in the display being 1 percent of the pixels, or .01 * number of pixels. Someone changed this a long time ago. Percent makes sense here. 10 being .1 and 100 being 1 for the multiplier.

Thanks for the update though. Please work through the bugs and get this thing running smoothly.

[Arnfinn]

Autolevel still does not work, not for the black level or the full saturation.

I have never used that function as it looks butt ugly on most of the images I have tried, and I have been under the impression that it's more of a dynamic function that might give a different result later on if you use other ajustment tools. If I need this kind of behavior I use the Auto Contrast button in the Curves panel as a starter point.

[John Lance]

Autolevel still does not work, not for the black level or the full saturation.

I have never used that function as it looks butt ugly on most of the images I have tried, and I have been under the impression that it's more of a dynamic function that might give a different result later on if you use other ajustment tools. If I need this kind of behavior I use the Auto Contrast button in the Curves panel as a starter point.

I can appreciate this, however I used to start with a baseline of 0 black and 0 full on up to 2 or 3 for black and .1 to .5 for full on for Autolevel which would automatically do the adjustment towards black and full on. This worked fine for many pictures for many years. If it does not work quickly for something, turn it off and pursue results elsewhere in the program.

The point is that Autolevel is there, and it now malfunctions. This is a case for sure of many ways to do the essentially the same thing, and yet it was the end users choice depending on how they think or want to approach a picture, or for what is just quickly perfect for a given situation without resorting to other methods.

For me, I never use Perfectly Clear, but for folks that do use it and get the results they want, the situation would not be fine if it malfunctioned. I would have an argument in favor of the person that wants to use it, even though I personally do not use it. This is more a matter of a program that was beginning to meet requirements, needs, and the thinking of many users, with provided tools geared to the user's needs and thinking, even if there is some overlap.

I have taken to using the histogram exclusively now, but it is much more time consuming for generic photos that a generic setting for Autolevel used to handle quite well.

[yves77]

I use DXO
Yves

According to their website, DxO is Win and OSX only, yet your sig indicates you're using Linux. I'm confused. Am I missing something?? Does DxO have a Linux version not published on their website? If so, please post a link.

Cheers.

I usualy use linux Mageia (and ASP).
But I also also use Win7 (DXO - perfect noise removal and great lens correction- and ASP -speed and ease of use-).

Each world has his advantage.

Yves

[bifffa]

"Lock Position and Zoom" doesn't work properly.

Display 2 identical pictures (eg: JPG and RAW of the same shot) and zoom with the mouse wheel. The selected image zooms from the cursor the other image zooms from the centre.

Application vers.: 2.2.0.29 Linux 32 bit
OS Linux Mint 17 Cinnamon 64 bit
NVIDIA G98 (GEForce 8400 GS Rev 2)


Regards
Martin