I assume this is due to wonky profiles anyway.
I downloaded some 7D CR2 files and a few initially read in with a weird magenta cast. Once loaded selecting either "Apply Initial Setting" or "Apply Default Settings" cleared it right up (for me). So I'm not sure what's going on there. Apparently it's confused by the 7D's EXIF on initial import or read - but in a way which gets straightened out when the values are reapplied.
I got the files from http://www.imaging-resource.com/PRODS/E7D/E7DTHMB.HTM since I don't have a 7D of my own. I was testing this because a number of professional photographers on another site stated it was a constant and reoccurring problem for them with ASP and also back when it was BP - so a very old bug I would assume.
It would sure make me not want to use the software if it were happening to me.
1.2.0.7 - Magenta Cast From Some Canon Camera Profiles
-
Tesselator
- Posts: 18
- Joined: Tue Sep 10, 2013 5:33 pm
- System_Drive: N/A
- 32bit or 64bit: 64 Bit
- processor: Dual x5355 Xeon
- ram: 32GB
- Video Card: GTX570
- Hard_Drive_Capacity: 24TB
- Monitor/Display Make & Model: 3-monitors
- Location: Japan
- Contact:
1.2.0.7 - Magenta Cast From Some Canon Camera Profiles
Check Out Some Of My Photos: https://www.facebook.com/robert.edison3/photos
-
Tesselator
- Posts: 18
- Joined: Tue Sep 10, 2013 5:33 pm
- System_Drive: N/A
- 32bit or 64bit: 64 Bit
- processor: Dual x5355 Xeon
- ram: 32GB
- Video Card: GTX570
- Hard_Drive_Capacity: 24TB
- Monitor/Display Make & Model: 3-monitors
- Location: Japan
- Contact:
Re: 1.2.0.7 - Magenta Cast From Some Canon Camera Profiles
I think I may have figured out what is going on with this. Either that or I discovered a new bug. 
When you double-click (or slide) on any color balance setting anywhere to change or reset its value it changes the White Balance preset from "As Shot" to "Custom Kelvin" - even if the slider value was already on it's default (as loaded) position.
So let's say you load an image and immediately move the Tint or Temp (as so many of us normally might do) but the changes are not satisfactory for whatever reasons. You double-click on it to reset the value to what you think is the loaded state and navigate to the next (nearly identical) image to see if that's easier to get right. You get the second one right (let's say), process it, and quit ASP. When you load ASP the next time and cursor over or to that first image you gave up on and reset - it's still assigned to "Custom Kelvin". This would be fine if "Custom Kelvin" didn't have different ideas about the magenta channel than whatever "As Shot" produces given identical values for Tint and Temp.
To demonstrate this here's a gif anim of ASP with an image loaded were no other values are being changed. Only the mouse is rolling over the two profiles: "As Shot" and "Custom Kelvin". Nothing else is being modified and all displayed numerical values remain the same throughout the GUI. You might notice that the histogram is also changing here. :p

If "Custom Kelvin" in ASP is supposed to act like "Custom" in ACR where any changes set the white balance profile name to "Custom" which I assume it is, then "Custom Kelvin" given the same numerical values, should display identically to "As Shot" - yet here it adds a ton of magenta. Bug.
Tho probably nothing to do with camera profiles? 
When you double-click (or slide) on any color balance setting anywhere to change or reset its value it changes the White Balance preset from "As Shot" to "Custom Kelvin" - even if the slider value was already on it's default (as loaded) position.
So let's say you load an image and immediately move the Tint or Temp (as so many of us normally might do) but the changes are not satisfactory for whatever reasons. You double-click on it to reset the value to what you think is the loaded state and navigate to the next (nearly identical) image to see if that's easier to get right. You get the second one right (let's say), process it, and quit ASP. When you load ASP the next time and cursor over or to that first image you gave up on and reset - it's still assigned to "Custom Kelvin". This would be fine if "Custom Kelvin" didn't have different ideas about the magenta channel than whatever "As Shot" produces given identical values for Tint and Temp.
To demonstrate this here's a gif anim of ASP with an image loaded were no other values are being changed. Only the mouse is rolling over the two profiles: "As Shot" and "Custom Kelvin". Nothing else is being modified and all displayed numerical values remain the same throughout the GUI. You might notice that the histogram is also changing here. :p

If "Custom Kelvin" in ASP is supposed to act like "Custom" in ACR where any changes set the white balance profile name to "Custom" which I assume it is, then "Custom Kelvin" given the same numerical values, should display identically to "As Shot" - yet here it adds a ton of magenta. Bug.
Check Out Some Of My Photos: https://www.facebook.com/robert.edison3/photos
