Version 1.2.0.7 incorrectly handles temperature

[zigazou]

Hi !

Since I’ve upgraded AfterShop Pro to 1.2.0.7, I cannot set white balance using the temperature and tint sliders.

I can only use the predefined settings (sun, cloud etc.) in order to correct white balance. Whenever I try to manually modify the temperature or the tint, colors are completely out of control !

Strangely, the tint sliders says 150 for each predefined setting.

If I try to open images treated with a previous version of AfterShop Pro for which I manually changed the white balance, the image first looks ok (because it may be from the cache) but soon it turns wrong (as you can see on the attachment).

I have a Sony A55V camera.

Code: Select all

Application vers.: 1.2.0.7
Product Name: AfterShot Pro Registered
Built on:     ven. juin 28 2013
Platform:     Linux
Language:     fr
App Path:     /opt/AfterShotPro/bin/AfterShotPro
System Home:  ../supportfiles
User Home:    /home/fred/.AfterShotPro
Prefs Home:   /home/fred/.config/Corel/AfterShot Pro.conf
Processors:   4
CPU Threads:  4
I/O Threads:  1
B. In-flight: 2
RAM:          7986 MB
SIMD Version: SSE2
Build Mode:   Release
Issue:        Ubuntu 12.04.2 LTS \n \l
Kernel:       Linux version 3.2.0-49-generic (buildd@komainu) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #75-Ubuntu SMP Tue Jun 18 17:39:32 UTC 2013


====================  Plugins  =====================
      Name: 
Identifier: 
   Version: 1.0.0
      Path: 


      Name: asGPS
Identifier: de.schrell.asGPS
   Version: 1.4.1
      Path: <User Home>/Plugins/asGPS.afplugin


      Name: SContrast
Identifier: com.roland65.SContrast
   Version: 0.5.0
      Path: <User Home>/Plugins/SContrast.afplugin


      Name: Wavelet Denoise
Identifier: sph.waveletdenoise
   Version: 0.31.0
      Path: <User Home>/Plugins/Wavelet Denoise.afplugin


      Name: Wavelet Sharpen3
Identifier: sph.waveletsharpen
   Version: 1.34.0
      Path: <User Home>/Plugins/Wavelet Sharpen3.afplugin


      Name: zPerspector
Identifier: tin.tin.zPerspector
   Version: 2.0.1
      Path: <User Home>/Plugins/zPerspector.afplugin


      Name: Black and White
Identifier: com.corel.BlackAndWhite
   Version: 1.0.0
      Path: <System Home>/plugins/Black and White.afplugin


      Name: Equalizer
Identifier: com.corel.equalizer
   Version: 1.0.5
      Path: <System Home>/plugins/Equalizer.afplugin


      Name: Nostalgia
Identifier: com.SMP.Nostalgia
   Version: 1.0.8
      Path: <System Home>/plugins/Nostalgia.afplugin


====================================================

[awm03]

I'm having this problem too. (Windows 7)

[Dutchmm]

I am seeing something like this on my linux system
HOWEVER, when I slide the temperature slider right to the right, I eventually come out at sensible results - only about 2000 higher than you would expect.
Filed a report with the monkey but there is a 404 on the upload link, so I couldn't submit my files as evidence.
Just in case this is a camera specific error, I shoot Sony A55 and in RAW

[awm03]

I have a Sony a77 & shoot raw. My old Sony a330 raw pictures don't seem to have this problem.

[dsigman]

I'm having a similar problem with a Sony A57. The temperature change as I move the slider. If I then click "As Shot" the original image returns but shows a very different temperature of over 9000k. I don't have the problem with a Sony A350.

[Tesselator]

Same here on a MacPro. The displayed temperature values do not correlate properly with Adobe or PhaseOne product image displays. And using the ASP sliders do not always produce the expected result.

Something is wonky here.

[votez]

same story with my sony a850 and sony nex-5n. Sony a700 doesn't have such a problem. Only possible to use predefined temperature (or 'as shot'). 'Click white' and 'Custom Kelvin' messes the picture

[ferdinand-paris]

Same here on a MacPro. The displayed temperature values do not correlate properly with Adobe or PhaseOne product image displays. And using the ASP sliders do not always produce the expected result. Something is wonky here.

This is a long-standing issue, which affects many cameras, if not all. Taken together with your other posts, now you are starting to understand why:

There's probably a bunch of noisy dissatisfied users as a result of the ironing process but it's not useful to overly mind the spoiled.

We are dissatisfied for much the same reason as you - a program with much potential is dying of neglect. Bugs are not fixed, esp long-standing ones. IQ is falling behind. No signs of progress, other than a few camera updates and a questionnaire. Little communication. Welcome to the club.

[Tesselator]

Same here on a MacPro. The displayed temperature values do not correlate properly with Adobe or PhaseOne product image displays. And using the ASP sliders do not always produce the expected result. Something is wonky here.

This is a long-standing issue, which affects many cameras, if not all. Taken together with your other posts, now you are starting to understand why:

There's probably a bunch of noisy dissatisfied users as a result of the ironing process but it's not useful to overly mind the spoiled.

We are dissatisfied for much the same reason as you - a program with much potential is dying of neglect. Bugs are not fixed, esp long-standing ones. IQ is falling behind. No signs of progress, other than a few camera updates and a questionnaire. Little communication. Welcome to the club.

Yeah, I get you. I was talking about something a little bit different tho. Sometimes when a development gets into trouble users start venting and saying how terrible everything is. Usually about at that point every thread becomes a twelve course meal fit for troll royalty. I've already seen that this is the case with ASP as it is now. The problem is that the troll kings and queens have just about zero idea what's actually happening at the company and with the status of the development efforts. And because such threads don't automatically delete themselves as things change for the better, it's not only pointless to rag on the company and app but actually destructive. All to say that the noise from the noisy ones I was referring to is almost never constructive.

Beyond posting an explanation thread of the bug in question and reporting it to the Monkey, people who do like that are not only wasting their time but also causing damage - whether they know it or not.

[Voiceofexperience]

Sometimes when a development gets into trouble users start venting and saying how terrible everything is.

ASP hasn't "got" into trouble as if this has all just happened. These same issues have been a thorn in the sides of long-term users since very early Bibble days, and remain unaddressed to this day.

It's more than slightly tiresome to read someone who hasn't had any meaningful experience of the product talk down to users who have had their legitimate expectations ignored for years, and their concerns dismissed in favour of trivial updates that do not address these core issues in any meaningful way.

The problem is that the troll kings and queens have just about zero idea what's actually happening at the company and with the status of the development efforts.

No, the problem is that users who make interminable excuses for the unacceptable state of the product serve to justify developers' inaction on the issues that effect it. The problem is that individuals who are too easily pleased or have too-low expectations, become the justification for the mess.

And because such threads don't automatically delete themselves as things change for the better

When (more to the point, if) things change for the better, you might have a point. We're about eight years in now, and we're still waiting, so I think we can legitimately dismiss your concerns on that score.

it's not only pointless to rag on the company and app but actually destructive.

It is never, ever "destructive" to have high standards and to expect the providers of a commercial product to do what is necessary to achieve those standards.

[ferdinand-paris]

And because such threads don't automatically delete themselves as things change for the better, it's not only pointless to rag on the company and app but actually destructive. All to say that the noise from the noisy ones I was referring to is almost never constructive.

It's true that there have been some noisy ones here, but the worst one got himself banned.

We can deal with overall impressions if and when things do improve for the better. My concern is that there are still people stumbling across the product and buying it, blissfully unaware of how moribund it is at the moment. Experienced users have a duty of care to ensure that new and potential users have an accurate understanding of the history and the current status of the product. This can be done in a balanced way, and for the most part I think it has been.

[Voiceofexperience]

It's true that there have been some noisy ones here, but the worst one got himself banned.

Even though he was right all along...

[BrianCee]

but banned users can be re-incarnated with a different user name and e-mail apparently

can't they Keith

[Tesselator]

And because such threads don't automatically delete themselves as things change for the better, it's not only pointless to rag on the company and app but actually destructive. All to say that the noise from the noisy ones I was referring to is almost never constructive.

It's true that there have been some noisy ones here, but the worst one got himself banned.

We can deal with overall impressions if and when things do improve for the better. My concern is that there are still people stumbling across the product and buying it, blissfully unaware of how moribund it is at the moment. Experienced users have a duty of care to ensure that new and potential users have an accurate understanding of the history and the current status of the product. This can be done in a balanced way, and for the most part I think it has been.

Kewl, Yeah, I don't really know the state of all things user-forum and I made no claims either way. I tried to use language like if, could, might, and so forth. From what I read of Mr. Voiceofexperience we are actually saying the same things - exactly - but I think he wants stated in a particular way. If it's been balanced for the most part as you say that's a good thing. Skimming older threads here left the impression that several folks had just defaulted to complaint & ridicule mode.

Anyway, back on topic, Version 1.2.0.7 incorrectly handles temperature and I think one of my latest threads is related to this issue. http://forum.corel.com/EN/viewtopic.php ... 82#p275865

[JeroenMentens]

Same problem here but only for my Sony Nex-5N.
The problem isn't there for my Canon cameras.