AfterShot Pro 2.0

[satart]

Waited for Sony A6000 support.
Version 2.0 do not support this popolar camera.

Well, i have to switch to Lightroom

[ferdinand-paris]

My understanding is that the x-trans cameras are not just another camera, they're a major new development. Even the old Bibble Labs staff once said that they'd never do it.

It is really hard to do X-Trans right, Adobe still sucks at it according to the pixel peepers....
...
The further on in the pipeline Bayer is assumed, the harder it gets.

I think the problems with LR and X, while real, can be overstated. And often are. There's more to an image than mere pixels.

My understanding is that demosaicing is the first thing in the pipe. That's where the difference is. The general assumption is that the Adobe problems are in demosaicing. I read a recent analysis that rather the problem lies in LR sharpening, but I'm not sure how that can be.

[Hobgoblin]

All plugins seem to work (problem with zFrame - color - nothing happens - pick color works) except GradFilter Pro (ubuntu)
Did someone notice this too?

Yes you are right.
It does not work here either, that alone would deter me from upgrading.
Some odd things with zFrame as you say, Pick colour works and I get a coloured frame, But the calibration tool does not seem to work.

[Dutchmm]

Hannes_Hab said:

All plugins seem to work ... except GradFilter Pro (ubuntu)

Yes. My log says:

Code: Select all

25.597: Successfully registered  LabTools  filter
25.598: Registering AfterShot plugin...  "GradFilter"
25.598: Failed to load the GradFilter filter
25.598: Registering AfterShot plugin...  "asGPS"

And this would be a reason I can't get enthusiastic about ASP2.

[lathspell]

Ok, as an Oly E-30 user I can perfectly skip this new version.

The maze artifacts are still there, so I assume ASP will never get a decent demosaicing algorithm for old(er) Olys. Removing the NN functionality breaks most of my older workarounds. And retouching formerly processed pictures with the new denoising tool even removes the old NN settings for an image, so after going back to ASP 1.2 the NN settings are completely gone (thanks to afx for the hint so I did only try that with some non-important pictures).

The GUI is the same not-really multi-monitor supporter. Actually IMO it has gone worse due to the new, darker flat color scheme and bold fonts which don't help structuring tools at all. (ETA: Even the misdesigned horizontal file browser scrollbar is still in there. Gosh!)

Speed has never been a problem with ASP so the 64-bit thing is a nice to have, but not urgently needed and currently useless with older plug-ins.

Nothing new at all about lens correction. APS 2 needs much longer to display thumbnails of a chosen folder.

HDR and Local Contrast - hm. I'll give it a try during the trial period, but I dont think I'd use them that heavily.

Sorry, to me that's only ASP 1.5, not 2 and therefore not worth the € 50 upgrade price.

[Hobgoblin]

Well, I've done mine for 64-bit and tintin has done his. I don't know when they'll be made available. Some of kbarni's now come packaged with ASP and the others are in progress. Not sure about the other developers.

This is great! The one I shall really miss, if it isn't re-done for 64-bit, is the Graduated ND filter. In fact, it will hold me on the 32-bit version (as long as that runs) until it it is re-done or replaced. I would be happy to pay for another copy, if that helped Roger Barnes to make the right decision!

Have you got the 32bit Graduated ND filter filter working in ASP2?
It doesn't work for me on Linux Mint 16 with a 32bit install of ASP2.

Like you I would have no objections to paying Roger Barnes for his work.


R.

[GlenBarrington]

[...] Do you see the E-M5 or the E-M10? (The E-M10 is probably the most popular camera Olympus has produced in a while and I believe the E-M5 has been out around a year now, maybe longer. [...]

ASP has had support for Oly's E-M5 long before LightRoom did.
Those were the times ... ;-/

Yeah, I missed the M5, the first time around and I jumped the gun on THAT, my apologies to you all. However, I believe my point is still valid.

It's a pretty lame mix of camera support that I see. I understand that X-Trans is a tough nut to crack, ACDSee, for instance still doesn't offer ANY X-trans support (and one of the reasons I bought an M10), and Lightroom's support is still less than perfect. But X-trans is X-trans, and OMD orf files are also pretty much the same.

If you have enough confidence to release support for one camera in a series, how much more difficult can it be to release support for a second or third in that series? You've got the hard stuff already figured out!

What really set me off was that if PSP X6 Camera Raw Lab supports E-M10 very well. X6 gets a bum rap as a raw developer - I've even written about it, look up my personal blog on Google Blogspot. Why isn't it available in ASP? Are the two products SO different that what is learned for one can't be applied to the other? If so, THAT should be Corel's #1 goal, integrating PSP, ASP, and the Corel Draw Suite to make an Editing/Imaging SYSTEM.

That kind of thinking propelled Adobe into the Catbird seat by reducing support costs overall and increasing sales.

My frustration is that there are 2 Corel personalities, one is the serious imaging/graphics company, and the other is this company that tries to sweep up any loose change lying about on the table. And we never know from one minute to the next which personality we are dealing with. That will slow ASP sales more than the price or Adobe's dominance in graphics.

[explo]

Has anyone tried direct image quality comparisons against the previous ASP yet? I'm personally mostly curious about the highlight recovery, amount of detail and whether there's any posterisation or excessive colour shifts in the shadows (excluding the results of really heavy shadow lifting, then of course the output will eventually become garbage).

[Dutchmm]

I am in the process of doing a systematic test on noise reduction. I am a little stuck because I don't have a NN license. What I could do is publish a RAW and the improvements I have been able to make using version 2. Anyone who wants to help can PM me.

[sbattaio]

Well, I believe that does it for me regarding ASP 2. Still only one Fuji camera is supported (X100). The latest Lightroom 5 update not only supports all of my cameras (including Fuji), it also added support for Fuji film emulation color profiles: Astia, Velvia, monochrome with filters, etc. Not that I love Adobe, but right now it is the best tool for my needs. Sorry, Corel.

[albernier]

highlights recovery: progress = 0

[havok]

Calling this a 2.0 release is stupid.

Unless they have completely re-written the underlying framework to support more rapid development and addition / change of features and cameras, this should be v1.5 not 2.0.

The nomenclature at this point is pure marketing so the general public believes that the product is not dead.

Lipstick on a pig.

[Dutchmm]

Hobgoblin wrote

Have you got the 32bit Graduated ND filter filter working in ASP2?
It doesn't work for me on Linux Mint 16 with a 32bit install of ASP2.

Like you I would have no objections to paying Roger Barnes for his work.


R.

No, it isn't working for me. I am on an earlier (I think) version of Mint in 32 bits. The log entries I showed are from that machine. I haven't tried on my more up to date 64-bit box, but I amn't going to bother ATM.

[spoilerhead]

The .rpm file is just terrible broken in all ways possible:

The Package name is "AfterShotPro", so co isntall with asp1 is not possible,

even worse:
Version : 0.0
Release : 0.0

so this registers as version 0.0 in the rpm database
also, corels build server seems to have a broken clock:
Build Date : Fri 28 Jun 2013 07:16:02 AM CEST



TL;DR: rpm kaputt


edit:

www.aftershotpro.com/en/ seems to link to the correct files, www.aftershotpro.com/de links to ASP1 builds

for the /en version:
Package name is still:
Name : AfterShotPro

Release : 0.0
should probably be 0.133 (from the filename)

same goes for the x64 version.

[spoilerhead]

Parallel install of the ASP2 on rpm machines can be fixed with:

Code: Select all

rpmrebuild --change-spec-preamble='sed -e "s#^Name:.*#Name: AfterShotPro2#"' --change-spec-provides='sed -e "s#AfterShotPro#AfterShotPro2#"' --notest-install -p AfterShotPro2_2.0.0.133.i386.rpm

phew :S

fixed output file is then placed in ~/rpmbuild/RPMS/i386/

(worksforme)