White Balance All Messed Up

[GoremanX]

I've got hundreds upon hundreds of photos that I've worked on using AfterShot 1.0.0. Ever since I upgraded to AfterShot 1.0.1, the white balance on those pictures has gone down the toilet. They've all gone horribly cyan. Here's an example.

This is how the picture used to look after I was done editing it (old JPG that I generated a few months ago):


And here's how it looks now after I updated AfterShot:


In addition, there's a serious problem with the way white balance is affected when I make the slightest edit. This is how the picture looks when I select "As Shot" for the white balance (temp: 6082 / tint: 125):


If I change the temp by a single digit, the whole picture changes dramatically (this is temp: 6083 / tint: 125):


And if I change it back to the original values manually (6082/125), it still looks completely wrong, and it looks nothing like when I select "As Shot", even though the values are supposedly identical:


Near as I can tell, the white balance functionality in AfterShot is completely broken, and it's gotten way worse since version 1.0.1 because now all my existing pictures are broken too. I'm using AfterShot for Linux on openSUSE 12.1 and for Windows on Windows 7 (same result in both). The raw files are DNGs from a Pentax K-5.

[John123]

It could be due to the file format you use. DNG is an Adobe file format. To my understanding ASP doesn't handle DNG files well. Is there a way to use the camera's own RAW format?

Beautiful image BTW.

[GoremanX]

I've been using DNGs from the camera for the last 3 years, and Bibble never had any problems with them before. Besides, this doesn't seem like a file format issue. However I'll try out the PEF format to see if it behaves the same.

Thanks for the comment on my picture. It's one of my more successful photographs from this winter's shooting.

[afx]

It is a camera specific bug....
Please send to the Monkey.

cheers
afx

[df]

The WB is horrible for me too. Somewhat fixable for my Canon 40D, not even worth monkeying with on the 1D.

[GoremanX]

It is a camera specific bug....
Please send to the Monkey.

I'm sorry, what is "the Monkey"? And how do I file bug reports?

[afx]

It is a camera specific bug....
Please send to the Monkey.

I'm sorry, what is "the Monkey"? And how do I file bug reports?

See signature...

cheers
afx

[GoremanX]

Thanks.

And someone will get back to me to confirm that the bug exists and is being worked on? Or is this more like a mail-in rebate kind of thing?

[Jeff Stephens]

Could you share that file, or another that exhibits this issue, with us? If so, upload here.

Cheers, Jeff

[GoremanX]

I already posted a link to a relevant DNG file (and accompanying XMP file) that is affected by this issue in the bug report that I submitted through Survey Monkey. The uploader you link to does not work for me.

[spoilerhead]

monkied that some time ago for 7d files, too (to a lesser extent)

[GoremanX]

For the record, this issue does not occur with files generated by my Pentax K-x (also DNGs), only my Pentax K-5.

[AsterixEtObelix]

It is a camera specific bug....

I am not so sure I already reported some month ago a similar pb with a canon camera :
http://forum.corel.com/EN/viewtopic.php ... 38#p242138

If I set to white balance to SUNNY, it gaves me this value
Temp: 4519
tint 20

and this picture:
IMG_0738_ASP.jpg

then I move the sliders, so it switch the white balance to "personal" and I set it to the same values as before (so Temp: 4519 / tint 20 ) it gave me this results:
IMG_0738_v2_ASP.jpg

[GoremanX]

And someone will get back to me to confirm that the bug exists and is being worked on? Or is this more like a mail-in rebate kind of thing?

...so like a mail-in rebate then... cross my fingers and hope for the best.

I love having my workflow and all my previous work ruined. It's so... professional.

[sauron]

And someone will get back to me to confirm that the bug exists and is being worked on? Or is this more like a mail-in rebate kind of thing?

...so like a mail-in rebate then... cross my fingers and hope for the best.

I love having my workflow and all my previous work ruined. It's so... professional.

It's a bug - and Jeff (who's the ASP product manager at Corel) did respond to you. So I'd regard that as confirmation that it's being looked at. Put it in perspective - it's one camera, and one image format. I know that sucks hugely when you're the one it affects, but they'll fix it. I had raw files taken with my ancient Canon S40 P&S that had a very similar problem with an old version of Bibble, and it got sorted.