White Balance All Messed Up

[GoremanX]

But was the white balance for my camera buggy in the previous version? Or is it now buggy in this newer version? What'll happen in upcoming versions? Should I expect things to break regularly?

This is my livelihood... I depend on this software to keep my business running. I've got 3 shows that I'm scheduled to display at, and all of my best recent work is broken because of this bug. Some of it is unrecoverable because of the number of layers which were interacting with each other. Meanwhile, I've already processed a bunch of recent stuff, so going back to the previous version isn't an option.

Corel is marketing this as a Lightroom alternative... so far, not so much.

[sauron]

But was the white balance for my camera buggy in the previous version? Or is it now buggy in this newer version? What'll happen in upcoming versions? Should I expect things to break regularly?

If it used to work, and now fails, that's a regression, however you cut it. Even if you were to assume that the old version was buggy, you've now got a compatibility issue as a result, which is itself a problem that needs fixing.

This is my livelihood... I depend on this software to keep my business running. I've got 3 shows that I'm scheduled to display at, and all of my best recent work is broken because of this bug. Some of it is unrecoverable because of the number of layers which were interacting with each other. Meanwhile, I've already processed a bunch of recent stuff, so going back to the previous version isn't an option.

Ugh. That's awkward - I'd expect the to fix the regression with the next version, but that's more than likely to leave you with a bunch of processed files that will have incorrect colour balance after the fix. In an ideal world, there'd be a way to migrate those so that the rendering differences between versions are compensated for, but that's likely to be hard to implement, and I wouldn't count on it .

Corel is marketing this as a Lightroom alternative... so far, not so much.

Bibble has always had a small team who have struggled to keep up. It's early days in the Corel stable, and I've got hopes that things will keep improving - there's no LR at all on Linux today. FWIW, you've got my sympathy - you're in a frustrating situation until they fix it, doubly so if you're doing this professionally, rather than as a hobbyist. You could try installing two versions in parallel - with a bit of filesystem level fiddling that can be done.

[KeithR]

Put it in perspective - it's one camera, and one image format.

But it's not: it's one camera and format for the OP, but on this same thread people have confirmed similar issues with the Canon 40D, 7D (both of which I have had problems with too), 5D Mk II and 1D.

[GoremanX]

But it's not: it's one camera and format for the OP, but on this same thread people have confirmed similar issues with the Canon 40D, 7D (both of which I have had problems with too), 5D Mk II and 1D.

All of which are professional level cameras that people often use to make a living.

[Ralf]

I've seen much the same thing with my Nikon D7000. Switching from any of the preset white balance settings to Custom Kelvin (with the same temp/tint setting) produces a substantial green cast. I need to shift tint 15 to 20 points toward magenta to remove the cast.

[simico]

I've noticed that my raw files from my K-5 get a green cast in ASP. Photos shot in AWB or Sunny mode on my cam get very different wb values in ASP than in any other raw developer app, for example instead of 5600K the wb value is 5831 and tint is 123 in ASP. I think the fact the tint is almost all the way right in magenta range itself suggests something is clearly wrong in ASP's wb management.

Then the good old bug of changing wb from "as shot" to anything else immediately results in ridiculous colors... I mean I reported this years ago for Bibble 5 and it's still not fixed in second release of ASP?

I'm really getting fed up with all these long standing ridiculous bugs and half-finished features in ASP.

[GoremanX]

Join the party...

I use Linux on my desktop, which is why I bought Bibble/ASP to begin with. But I recently bought a Windows laptop just so I could run Lightroom and escape ASP's horrible WB handling with K-5 files. Pretending that ASP is a professional tool in a photographer's workflow is ludicrous. No professional photographer should have to put up with this kind of defect for this long. Especially since whatever fix eventually gets implemented will probably end up breaking ALL K-5 pictures that have been processed with prior versions of ASP.

[simico]

I use Linux on my desktop, which is why I bought Bibble/ASP to begin with.

Same here. Though LR runs fine on my pc (either in Wine or in VM). I'm going to take another look at RT and DT as well. Corel won't ever see a cent from me for sure.

[sauron]

DarkTable is starting to look very competent. I'm sticking with ASP for now, but if the move to Corel fails to address the issues around neglect of longstanding bugs, communication, and generally better treatment of the users, it'll be very tempting to shift. It can't yet match ASP for speed, but with ever faster CPUs that's less of an issue than it used to be. I still hope ASP lives up to it's promise, though. It could be really great....