ACR 6 color artifacting not present in ACR 5

Has anyone yet noticed or reported the blotchy color artifacting in 6 (ACR 6.0.0.205) that was not there in 5?
I have noticed it in clear blue skies (see link below). When doing a conversion of a scenic file using the ACR interface, the skies show to be smooth and almost free from artifacting. But when I open up the actual JPG 12 file that was output, it shows large, magenta tinted, blotchy areas. The problem even exists when I set the color noise reduction to 100.
The texture of the clear blue skies is finer and more uniform in ACR6 (2010), there is less color bleed at sharp edges and transition, and overall resolution and definition is slightly better. ACR5 yields skies of a courser lumpier texture, and sometimes has areas where the blue bleeds into adjacent areas of a different color. But ACR 5 does not suffer from the magenta blotching that almost looks like faint magenta clouds.
When I try outputting to 16-bit TIFF (instead of qual 12 JPG), the sky in looks much more like the ACR 5 JPG output -- courser texture but no magenta blotches. When I save the 16-bit TIFF as a JPG12, (in Photoshop CS5), I see faint large blotchy areas of magenta artifacting in the JPG that are not present in the TIFF.
I have posted 3 files here: http://stevesucsy.com/ACR/
They are all in ProPhoto color space.
DPP-5424.jpg   converted in Canon's DPP     nice smooth sky, very few artifacts
ACR6-2003_NoBlotch-5424.jpg     using the 2003 process in ACR6 shows less clearly defined color noise that is spread more uniformly than the 2010 version
ACR6-2010_MagentaBlotch_5424-1.jpg    using the 2010 process shows faint magenta patches or blotches.
I just thought of something else. Here I tried setting ACR6 (2010) to the Adobe RGB color space (instead of ProPhoto). All the other settings are identical to the file above (with the magenta blotching). But this Adobe RGB file that was output by ACR6 (2010) has no obvious magenta blotching.
ACR6-2010-aRGB_NoBlotch-5424.jpg
Any comments/observations?
I hope Adobe will fix this problem, as I far prefer working in and keeping all my general purpose output in ProPhoto color space.

Thanks for your reply Doran.
The problem happened using ACR 6.0, ProPhoto, 16 bit. But it was "solved" (or improved) by using AdobeRGB in 16 bit.
And the problem did not happen using ProPhoto in 16 bit when using ACR 5.6.
I don't really want a "work-around".
I would like to be able to:
1) Have the interface accurately represent what I will get in the final file.
2) Be able to work in ProPhoto 16bit and get output that does not have banding and blotching.
Dave

Similar Messages

D700 Camera Profile Artifacts (still present in ACR 5.5?)

Just installed ACR 5.5 RC and it looks like the color problems with the "Camera" profiles (for the Nikon D700 and D3) are still present. Namely, green/magenta color casts in what should be neutral areas, and weird posterization effects in shadow areas. Then again, I'm not sure if installing a new version of ACR update camera color profiles.
I posted a thread about this on Dpreview a while ago; or just do a Google search for "D700 color" and it's one of the top results.
Here's a Flickr photoset with some crops showing the issue. The artifacts with the shadows are kind of hard to see in those small crops though (it's better to look at the original image).
To Adobe: can we get any sort of an idea when this is going to fixed?

What you're seeing - the color shifts anyway - are as a result of the "hue twists" in the new generation Adobe profiles. What it amounts to is that the new profiles change the hue of a pixel based on its intensity. So, what were in the original image two pixels with the same "color", but different intensities end up as different colors. This has been discussed quite intensively in context of the 5DII, which also shows these issues, both on this forum (http://forums.adobe.com/thread/311802?start=0&tstart=0) and on dpreview (http://forums.dpreview.com/forums/read.asp?forum=1032&message=32482073)
If you want to know more about the technicalities, I've written about hue twists here: http://chromasoft.blogspot.com/2009/02/adobe-hue-twist.html
You might say that well designed "hue twisted" profile would keep neutrals neutral, and that's true, but there's a complication - what neutral is varies with white balance, which makes it a judgement call as to how much "twist" you can tolerate close to a hue that might conceivably end up as a neutral. Probably what adobe will need to do to solve this issue (if they decide it impacts enough people to be worth addressing) is to tweak the profile to maintain "untwisted" across a wider range of near neutral colors.
Short Adobe fixing the profiles, you have three possible solutions;
a) Use the earlier profiles which didn't have the twist
b) use a profile generated by Adobe's DNG profile editor (which never have twists)
c) If you want to try and preserve some of the profiles's look, you can also try untwisting the profiles with dcpTool (disclaimer - I wrote dcpTool): http://dcptool.sourceforge.net/ However, be aware that dcpTool can only preserve some part of the look, not all of it.
Sandy

ACR 5.2 camera profiles and Nikon D700 color artifacts

Using LR 2.2 or Photoshop CS4, conversions of D700 NEFs often result in peculiar color 'artifacts' (posterization?) in certain images, when using the new camera specific profiles like Camera Standard (or particularly Camera Landscape). Typically, the Adobe Standard or ACR 5.2 profile don't exhibit this behavior, at least not with significant changes to saturation and contrast.
An example of this can be seen at http://farm4.static.flickr.com/3400/3179948383_cfda478eb8.jpg (LR 2.2, Camera Standard profile). Question is whether these sorts of results are expected? I'm otherwise quite happy with the new profiles. Thanks,
Mike

Mike,
1. You may be happy if the problem goes away with the lossless compression, but it would be a nice service to the D3/D700 owners' community to
b prove
this. There are many photogs convinced, that the lossy compression does not cause visible loss (Nikon created a myth about this issue already with the D70).
If you can create pairs of shots demonstrating the effect and would not mind my using your images, I would spread this on other forums as well, as I did with the D300.
2. Re WB:
i normally
you can accept the WB interpretations of different raw processors, but not if the issue is just the WB. The fact, that the displayed color temperatures are close, does not mean much: the color temperature is not absolute. I don't go so far as to say, that it
i should
be different between CNX and ACR, but you can not rely on the number.
Even the snow is clearly reddish in the ACR created JPEG. You may complain about ACR's WB conversion, but that is a separate issue. In order to compare the colors, first the greys have to be made grey in both conversions.

ACR 7.1 RC Issue Not Fixed in ACR 7.1

The issue I identified in ACR 7.1RC is not fixed in the production release of ACR 7.1. Maybe I did not explain this in enough detail, it's very easy to miss.
1. Select a RAW file that was previously adjusted using PV2010. When you open the file with ACR 7.1 it will open with PV2010 since the xmp file was saved with that process version.
2. Click on the "!" next to the image and it changes to PV2012 with suggested slider settings. Adjust one of the sliders in the Basic Panel - this is very important becasue if you don't adjust a slider the issue does not show up.
3. With the Basic Panel still selected, click on the three dashes to the right of the Basic Panel to get the pop down menu and select "Image Settings". The image changes back to PV2010 with settings that are saved in the XMP file. Now click on the three dashed again to get the pop down menu and "Custom Settings" is checked, but the image is displaying PV2010, not PV2012 like it should if "Custom Settings" is checked. You just lost your PV2012 settings. ACR 7.0 does not have this issue.
4. If in #3 above you select another panel before you click "Image Setting" the first time you can switch between PV2010 and PV2012 by clicking "Image Settings" for PV2010 and "Custom Settings" for PV2012. After you do this first in a panel other than the Basic Panel for the first time you can then do it in the Basic Panel without the problem occuring.
I discovered this while converting images that were adjusted using PV2010 to PV2012 and like to compare the two Process Versions. I did not have any problems with ACR 7.0, but when I installed ACR 7.1RC the issue occured. I was hoping it would be resolved in the Production Release of ACR 7.1, but it's still there.
I am using Photoshop CS6 on a Windows 7 Professional 64 bit computer, don't know if this same issue exists in Lightroom.

None of the issues reported on this forum have been fixed in Camera Raw 7.1, near as I can see.
The Camera Raw 7.1 software was built on May 15, but Adobe appears to ignore beta feedback unless it's a real show-stopper. I can only imagine the definition of "show-stopper" must include users' systems actually catching fire or something.
Camera Raw 7.1 puts columnar color artifacts like this into images, for example:
Compare the above to the same conversion done with Camera Raw 7.0:
Plus Adobe has removed several color-fringing reduction features without providing suitable substitutes.
I recommend eveyone avoid upgrading to this release.
-Noel

CS6/ACR 7.x not recognizing Canon 5d Mark 3 files previously edited in same version. Help?

Why are my previously edited canon 5d mark 3 raw xmp files no longer recognized and all sliders set to zero? I can see the xmp files associated with the raw file in their folder. The files were originally edited in CS6/ACR 7.x -in July 2012 - and recently re-opened in the same CS6/ACR 7.x.
The canon 5d mark 2 files from the same time/event are showing up fine. I have updated everything, but both before and after the update, same issue with the Mark 3 files.
On a side note:
We have found that opening mark 2 files (that were originally edited in CS4 / ACR 5.7) in CS 6 / ACR 7.x and making any changes such as color coding causes all previous xmp information being zero'd out in the mark 2 xmp file. Not sure if this is a symptom of the same problem? Except the difference here is the Mark 3 files have never been touched outside of version CS6/ACR7.x - however the folder which holds both mark 2 & mark 3 files from the same event has been opened in the CS4 / ACR 5.7 window but without touching the files. By opening the folder in CS4 I can see that the Mark 3 files aren't reading and then know this event was originally edited in CS6/ACR 7.x
Specifics:
PS CS6 13.0.4 x64
Mac OSX 10.6.8
Canon 5d Mark 3 Raw files
This is the first time in these circumsances that this issue has presented itself.
Any insight would be much appreciated
Thank you!

First check to make sure your view mode in ACR is set to Image Settings, not Camera Raw Defaults. This is accessible as the top item or three in the menu that comes up when you click the little threelines-arrow icon at the right of the tabs title bar, for example to the right of the word Basic.
Otherwise, did you switch your Camera Raw settings location to be the central database instead of XMP files and/or are you on a different computer that might have a different metadata storage location?
Open up one of the XMP files in a text editor, perhaps one that hasn’t had a picture opened for it, recently, yet, and see if you see any non-zero settings. Also take note of the last file creation time. This will help determine if the XMP files, themselves, have been written with ACR defaults or if they are just being ignored.
Also, check the date and timestamps of a CR2 and XMP file that hasn’t been opened, recently, and see if the XMP date/time is before the CR2 date/time. There has been a bug, not sure in LR or PS, where if the XMP file date is BEFORE the raw-file date, then the XMP is ignored so maybe that could be happening. If it is a LR bug, then have the files been edited in LR, which might have ignored the XMP files and the rewritten things with the LR default settings?
If no explanation can be found on your side, can you zip up a raw and its corresponding XMP, preferably one that’s not been looked at, recently, then put them online somewhere like http://www.dropbox.com/ and reply with the public download link, so others can take a look?
What version of Camera Raw are you using? ACXR 7.4 just came out this week.

ACR color difference with PS CS4

I tried a search and can't find a thread about what I'm seeing, so I'm posting in the hopes that others may be seeing the same thing.
I have PS CS4 and ACR 5.3 (latest patches) on a Windows XP Pro computer. I use Adobe RGB as my working space and profile my dual monitors with an Eye One Display2. I recently started experimenting with using ACR to edit tif files, but I noticed that while the image is loaded in the ACR window it looks quite different color wise than the Bridge thumbnail or within CS4 (after opening it as a smart object). The look in ACR is similar to what the same image looks like in CS4 with the ColorMatch profile assigned to the image (i.e. quite a bit brighter and lacking saturation).
Here's the weird things:
When I first open the tif image, it looks correct as long as the exclaimation mark is present on the preview window. Once the file is fully processed and that icon disappears the image color makes the dramatic change. If I then make no changes and simply open the image in CS4, then it's back to the original "correct" colors.
If I zoom in the ACR preview to 50% or higher, then the color difference is negligible if not entirely gone, but I can't edit an 8000x5000 without seeing the entire image.
Here's what I have tried:
Turned off all OpenGL features
Verified my monitor profile was being recognized by CS4
Ensured my color settings didn't get changed (preserve profiles is on, as well as ask on mismatch)
Tested them with an image that was a known mismatch and it asked what I should do as expected
I tried PS CS3 and ACR 4.x with the same result
Stripped out XMP metadata with Exiftool to see if that may have been an issue - it wasn't
I'm hoping someone else has an idea what is causing this or if it's a known issue. Any ideas or confirmation on what I'm seeing would be appreciated.
Craig

cssadobe wrote:
It doesn't matter which space is set, the display of the image is always the same in ACR.
Holy cow! If that's the case in your setup, you have a HUGE problem, Craig.
You should definitely see a big difference in the ACR preview when you set your ACR worflow options to ProPhoto RGB compared to either Adobe RGB or sRGB. If you don't, either your monitor is not accurately calibrated and profiled, or it's a lousy narrow-gamut monitor, or your color management is broken.
EDIT: It could be that the scan was not really made in ProPhoto RGB but was converted by the lab to that profile, in which case then, yes, you would see no difference because the true, original color space was and remains narrower and smaller than the lowest common denominator, which could well be anything, including Color Match or sRGB (and we all know what the s stands for in sRGB!).
cssadobe wrote:
Since PS CS4 created the tiff, the preview and the actual image data should be identical in my opinion. Would you agree with that? I don't know why PS would create a preview that was not identical in display characteristics to the actual image.
No, I would not agree with that. No reasonable person can expect a low-resolution, JPEG-like preview embedded in the TIFF to look identical to the TIFF. Information has to be discarded to generate the preview. But that's beyond the scope of ACR.
What I would expect is that ACR would render a better display from the original data in the TIFF than what the mediocre embedded preview can generate.
cssadobe wrote:
If I zoom in on the image in ACR to at least 50%, then the difference seems to disappear.
Well, duh! You only see the real image when you view it at 100%. The farther you get from 100%, the more information is either being discarded (at anything less than 100%) or made up, invented at greater than 100%. 50% is still not as good as 100%, but it's definitely better than the miserably low 8.7% view you were using when you made that last screen shot.
Seeing that you have severe problems with your display, as suggested by the first paragraph in this post, there seems to be no point in discussing in detail any of the discrepancies you mention, most especially at any other view that is not actual pixels (100%).
I'll have to read the thread again when I have the time to see if you have said when you calibrated your monitor last and how, what your color settings are, what monitors you're running, etc.
I validate the calibration on my monitors practically on a daily basis with a hardware calibrator puck.
But, ultimately, viewing a large scan at a dismal 8.7% you can't make any of the judgments you are trying to make.

ACR color mode defaults

raw captures do not use the camera settings. It records them in the EXIF data.
ACR uses the EXIF data when opening a raw capture. This is painfully obvious when it comes to white balance if it has not been set properly at capture time. Not a problem, that can be modified the EXIF WB is the starting point.
The questions concerns the color mode:
If set at sRGB at the time of capture, does ACR uses the camera EXIF setting (sRGB) as it does for the white balance?
If so, should not color mode be a choice BEFORE opening the raw capture in ACR?
The 'no question asked', EXIF color mode data opening is troubling as sRGB cuts the gamut quite a bit. All edits are made in the sRGB mode. Setting the 'open as 16 bit RGB' only opens a 16 bit sRGB image as if it was a 16 bit RGB, meaning there is no color in the suddenly re-opened gamut space since the original color data has been killed when opening the file.
Last question:
What am I missing here?
Message was edited by: Jacques V, 'wording'

The answer is bad....
This is the transcript. It confirms what I suspected.
Thank you for contacting Adobe.
A representative will be with you shortly.
You are now chatting with Abhishek Joshi.
Abhishek Joshi: Hello. Welcome to Adobe Technical Support.
Jacques V: This is a two pronged question that concerns ACR and raw. Background A raw capture does not use the camera settings but records them, including white balance and color mode. ACR uses that recorded data to import the raw image as illustrated by the 'default' that reflects the original color balance. Questions: Does ACR uses the color mode recorded as camera setting when importing the image? If so, is there a way to override that import setting in ACR? My concern is that if ACR defaults to the camera settings the potential color gamut is ignored and one of the advantage of the raw format is severely limited by ACR as the raw format allows for a color mode change.
Abhishek Joshi: I will check it first
Abhishek Joshi: I am checking on this please provide me 2 minutes
Jacques V: Ok
Abhishek Joshi: Thankyou
Abhishek Joshi: Thank you for your time and patience
Abhishek Joshi: ACR information is derived from your RAW picture
Abhishek Joshi: If you do ACR default it will take the picture to the original state
Jacques V: Meaning it will use sRGB?
Jacques V: (as it was the camera setting, even if not used when recording the raw caprture)
Abhishek Joshi: You clicked the picture in sRGB ?
Abhishek Joshi: What ever the profile you chose in camera while capturing the picture
Jacques V: Ok then. In this case we eidt the raw file in sRGB and the export to PS CC is whatever is set in the option link in ACR. Am I correct?
Abhishek Joshi: Correct
Jacques V: Thank you. Not good news but a good information to have.
Jacques V: Good bye.
Abhishek Joshi: Your welcome
Abhishek Joshi: BBye

New camera profile not "appearing" in ACR, but does in Lightroom

I recently created a camera profile for a Nikon D200, using an X-Rite Colorchecker chart photo and the Chart feature in the DNG Editor. I exported the camera profile. When I go to the Calibration tab in ACR 5.5, the new profile does not appear in the drop down list with the other camera profiles. However, when I go to the Develop module in Lightroom 2.5, the new profile does appear in the drop down list there.
I am running Windows 7. Snooping around my root drive I find that if I look within the Users\User Name\AppData\Roaming\Adobe\CameraRaw\CameraProfiles directory (referenced in the Fraser and Schewe CS4 Camera Raw book as the Vista location for the profiles) I can find no camera profiles and when I place the new profile there it still does not appear in ACR. When I look in ProgramData\Adobe\CameraRaw\CameraProfiles\Camera\Nikon D200 directory I can see the regular set of camera profiles for the camera, as well as the one I created, but as I previously stated, the newly created profile does not appear in the ACR list.
A side note - I did some experimentation with camera profile names. I added "XX" to the end of the Nikon Vivid profile name (not the extension), and then that profile no longer appears in the ACR list of profiles. I removed the extra letters and then the profile reappears in the ACR list of profiles. Seemed odd behavior to me. I also noticed that the profile I created with DNG Editor is noticeably smaller than the others provided by Adobe (28K compared to 110k).
Hope someone has a suggestion for me.

Your reminder about both Photoshop (main) and Bridge needing to be shut down for changes to take effect reminded me that I had Bridge set to "auto-start at log-in". So I checked and it was still running (shown with the other hidden icons). When I "shut it down" from the UI I had thought it was fully terminated. So I completely shut Bridge down, restarted, and the new profile now appears.
Thanks for the reminder/pointer in the right direction.

Converted raw (or .dng) will not open in ACR?

OK, now that I've gotten sort-of over the hurdle of synching all the pieces associated with a smart object, I've hit the NEXT hurdle (SOs appear to be the usual double-edged sword - kinda handy in a way but rife with pitfalls and hurdles)...
I open a .NEF in Bridge, go into ACR and open the file as a Smart Object in Photoshop. Double-click the layer icon and I'm back in ACR, just like all the demos and seminars I've watched. But, take the SAME .NEF in Bridge and open it as a standard image in Photoshop, then CONVERT it to a smart object, double-click the layer icon and all I get is a .psd and NOT jump into ACR. It does exactly the same thing with a .dng file And from Lightroom OR ACR...
I found an entry from a discussion (not in here, I couldn't find anything about this in here) about CS3 (yes 3), where a user had this problem and was told it's because the original image was opened as a rasterized image, NOT as a Smart Object from ACR... Which isn't making sense to me 'cause who cares what it was way back when, it's NOW a Smart Object and should be treated like one no matter HOW it got there...
Is there some preference or setting or something I need to change in Photoshop so this will work as expected is is there really some restriction about exactly HOW the Smart Object got created? And if so, is there some paragraph is big, bold letters in the documentation that makes it really clear to the uninformed that you MUST open it as a Smart Object or it won't work?
And yes, I KNOW that in ACR I can set it so it defaults to opening as a Smart Object, but like many other PS users I normally use Lightroom and I haven't seen any such default. Which means it's REALLY easy to forget to go down to the Open as Smart Object and instead just hit Open in Photoshop...

Listen, buddy, no one has any obligation to answer your questions here in this user to user forum. Lose the attitude.
I'll repeat the answer anyway, as you apparently are unable to read replies carefully.
davepinminn wrote:
…CAN I take an image that was opened in Photoshop as a "standard" image, then converted to a smart object and edit it in ACR? If yes, HOW?
No, ABSOLUTELY NOT ! You cannot. Period. That's what I said in post #2 of this thread.
ACR will only open and edit Smart Objects that contain raw data. Any image opened in Photoshop —not as a Smart Öbject—is already cooked and contains no raw data any more. Additionally, ACR can edit JPEGs and TIFFs if you set your preferences accordingly, but with much less latitude and functionality than a raw file.
What's more, the cooked Smart Object 's now in the cooked PSB format (a variation of PSD that can handle much larger files than PSD can) so there's no way on Earth ACR can open it.
davepinminn wrote:
I've gotta remember that people in here will pummel the semantics to death and miss the question…
…and we forum regulars have to remember that some folks come here just to argue, looking for a fight.
Please read this FAQ for advice on how to ask your questions correctly for quicker and better answers:
http://forums.adobe.com/thread/419981?tstart=0
Excerpt:
• Do not be abusive or aggressive in your tone
An aggressive or abusive sounding post will often evoke an aggressive or abusive and unhelpful reply
Remember, you are requesting Help from other users, just like you, who are giving their time free of charge. No one is under any obligation to answer your question.

I had to reinstall CS4 and now raw images taken with my Canon 7D will not open in ACR.

Bridge tries to open in Photoshop. I downloaded the camera raw plug in for the 7d

Windows 7 64 bit
Date: Thu, 13 Sep 2012 12:13:15 -0600
From: [email protected]
To: [email protected]
Subject: I had to reinstall CS4 and now raw images taken with my Canon 7D will not open in ACR.
    Re: I had to reinstall CS4 and now raw images taken with my Canon 7D will not open in ACR.
    created by station_two in Adobe Camera Raw - View the full discussion
Are you on Macintosh or Windows? I can provide a screen shot of the appropriate Mac install location: http://forums.adobe.com/servlet/JiveServlet/downloadImage/2-4696566-231627/450-213/Path-to -ACR-5.2-for-CS4.jpg
     Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: http://forums.adobe.com/message/4696566#4696566
     To unsubscribe from this thread, please visit the message page at http://forums.adobe.com/message/4696566#4696566. In the Actions box on the right, click the Stop Email Notifications link.
     Start a new discussion in Adobe Camera Raw by email or at Adobe Forums
For more information about maintaining your forum email notifications please go to http://forums.adobe.com/message/2936746#2936746.

Phase One files shot with C1 4 will not open with ACR

Hi, files shot with Capture One 4 will not open with ACR nor DNG. Extension is set to .TIF but only the small preview opens. If I shoot with Capture One 3.7 - no problem. Any ideas ?
Thanks,
Gunter

Hi Gunter.
You would need to upload the file to your own web server or to a file sharing site like Yousendit.com and then post a link to the file here in the Forum.
John

"send to Color" not present

I just installed Final Cut 6. The "send to Color" is not an option from the send to section from the clip. Does anyone know why it is not present or how to fix the problem? Thank you!!

If you haven't found any bugs in it yet, you will. I just finished a two-day training session, and we all experienced instability on some level. Even the instructor had things happen that weren't supposed to. Color promises to be one of, if not the most important piece of the FCP Suite. But it's no more stable than Motion 1 was. In fact, it might even be less so. Give it time. It will come of age.
Why so many Apple users are so defensive is more of a riddle. Why the automatic "knee-capping" of anyone who uses the word "bug" or "glitch" in this forum continues to be one of life's eternal mysteries.
All software has bugs and glitches. I've never seen a perfect program. If you use an application long enough, sooner or later, something will happen that isn't supposed to.

Intalled os x yosemite and my greys are displaying brown and Im receiving this error message -Checking 80 profiles... /Library/Application Support/Adobe/Color/Profiles/RedBlueYelllow.icc    Tag 'pseq': Required tag is not present. /Library/Applicati

Intalled os x yosemite and my greys are displaying brown and Im receiving this error message
Tag 'pseq': Required tag is not present on 4 of my color profiles
Thank you

EtreCheck version: 2.0.6 (91)
Report generated October 23, 2014 at 6:17:40 PM EDT
Hardware Information: ℹ️
    MacBook Pro (17-inch, Mid 2009) (Verified)
    MacBook Pro - model: MacBookPro5,2
    1 2.8 GHz Intel Core 2 Duo CPU: 2-core
    4 GB RAM Upgradeable
        BANK 0/DIMM0
            2 GB DDR3 1067 MHz ok
        BANK 1/DIMM0
            2 GB DDR3 1067 MHz ok
    Bluetooth: Old - Handoff/Airdrop2 not supported
    Wireless: en1: 802.11 a/b/g/n
Video Information: ℹ️
    NVIDIA GeForce 9400M - VRAM: 256 MB
    NVIDIA GeForce 9600M GT - VRAM: 512 MB
        Color LCD 1920 x 1200
System Software: ℹ️
    OS X 10.10 (14A389) - Uptime: one day 3:29:31
Disk Information: ℹ️
    FUJITSU MJA2500BH FFS G1 disk0 : (500.11 GB)
    S.M.A.R.T. Status: Verified
        EFI (disk0s1) <not mounted> : 210 MB
        Macintosh HD (disk0s2) / [Startup]: 499.25 GB (245.60 GB free)
        Recovery HD (disk0s3) <not mounted> [Recovery]: 650 MB
    HL-DT-ST DVDRW GS21N
USB Information: ℹ️
    Apple Inc. Built-in iSight
    Apple Inc. BRCM2046 Hub
        Apple Inc. Bluetooth USB Host Controller
    Apple, Inc. Apple Internal Keyboard / Trackpad
    Apple Computer, Inc. IR Receiver
Gatekeeper: ℹ️
    Mac App Store and identified developers
Kernel Extensions: ℹ️
        /Library/Extensions
    [loaded]    com.sophos.kext.sav (9.2.50 - SDK 10.8) Support
    [loaded]    com.sophos.nke.swi (9.2.50 - SDK 10.8) Support
        /System/Library/Extensions
    [not loaded]    com.Seagate.driver.PowSecDriver (4.4.10) Support
    [not loaded]    com.rim.driver.BlackBerryUSBDriverInt (0.0.39) Support
    [not loaded]    com.rim.driver.BlackBerryUSBDriverVSP (0.0.39) Support
    [not loaded]    com.wacom.kext.wacomtablet (6.3.9 - SDK 10.9) Support
    [not loaded]    com.wdc.driver.1394HP (1.0.9) Support
    [not loaded]    com.wdc.driver.USBHP (1.0.11) Support
Startup Items: ℹ️
    HP IO: Path: /Library/StartupItems/HP IO
    Startup items are obsolete and will not work in future versions of OS X
Launch Agents: ℹ️
    [not loaded]    com.adobe.AAM.Updater-1.0.plist Support
    [running]    com.adobe.AdobeCreativeCloud.plist Support
    [running]    com.amazon.sendtokindle.launcher.plist Support
    [loaded]    com.hp.help.tocgenerator.plist Support
    [running]    com.intego.commonservices.statusitem.plist Support
    [running]    com.intego.netupdate.agent.plist Support
    [loaded]    com.intego.personalbackup.agent.plist Support
    [loaded]    com.intego.task.manager.notifier.plist Support
   [invalid?]    com.intego.VirusBarrierX6.alert.plist Support
[invalid?]    com.rim.BBLaunchAgent.plist Support
    [running]    com.sophos.uiserver.plist Support
    [running]    com.wacom.wacomtablet.plist Support
    [invalid?]    Kersh-Wellness.Activity-Monitor-Dock.plist Support
Launch Daemons: ℹ️
    [loaded]    com.adobe.fpsaud.plist Support
    [running]    com.intego.commonservices.daemon.plist Support
    [loaded]    com.intego.commonservices.icalserver.plist Support
    [loaded]    com.intego.commonservices.metrics.kschecker.plist Support
    [running]    com.intego.netupdate.daemon.plist Support
    [running]    com.intego.personalantispam.daemon.plist Support
    [running]    com.intego.PersonalBackup.daemon.plist Support
    [running]    com.intego.task.manager.daemon.plist Support
   [invalid?]    com.intego.VirusBarrierX6.daemon.plist Support
   [invalid?]    com.intego.VirusBarrierX6.scanner.daemon.plist Support
    [loaded]    com.microsoft.office.licensing.helper.plist Support
   [invalid?]    com.rim.BBDaemon.plist Support
    [running]    com.sophos.common.servicemanager.plist Support
    [invalid?]    com.wdc.WDSmartWareServer.plist Support
User Launch Agents: ℹ️
    [loaded]    com.adobe.AAM.Updater-1.0.plist Support
    [loaded]    com.adobe.ARM.[...].plist Support
    [loaded]    com.adobe.ARM.[...].plist Support
    [loaded]    com.adobe.ARM.[...].plist Support
    [invalid?]    com.citrixonline.GoToMeeting.G2MUpdate.plist Support
   [invalid?]    com.google.GoogleContactSyncAgent.plist Support
    [loaded]    com.google.keystone.agent.plist Support
    [running]    com.microsoft.LaunchAgent.SyncServicesAgent.plist Support
    [running]    com.spotify.webhelper.plist Support
User Login Items: ℹ️
    iTunesHelper    UNKNOWN (missing value)
    Antispam Engine    ApplicationHidden (/Library/Application Support/Intego/Personal Antispam/Antispam Engine.app)
    EvernoteHelper    UNKNOWN (missing value)
    Android File Transfer Agent    Application (/Users/[redacted]/Library/Application Support/Google/Android File Transfer/Android File Transfer Agent.app)
    iAntiVirus    UNKNOWNHidden (missing value)
    SpeechSynthesisServer    Application (/System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks /SpeechSynthesis.framework/Versions/A/SpeechSynthesisServer.app)
    Google Drive    UNKNOWN (missing value)
    EvernoteHelper    Application (/Applications/Evernote.app/Contents/Library/LoginItems/EvernoteHelper.app)
    StatusMenu    Application (/Incompatible Software/StatusMenu.app)
    HPEventHandler    UNKNOWN (missing value)
Internet Plug-ins: ℹ️
    WacomNetscape: Version: (null) Support
    Default Browser: Version: 600 - SDK 10.10
    Flip4Mac WMV Plugin: Version: 2.3.8.1 Support
    OfficeLiveBrowserPlugin: Version: 12.2.6 Support
    WacomTabletPlugin: Version: WacomTabletPlugin 2.1.0.6 - SDK 10.9 Support
    AdobeAAMDetect: Version: AdobeAAMDetect 2.0.0.0 - SDK 10.7 Support
    FlashPlayer-10.6: Version: 15.0.0.189 - SDK 10.6 Support
    AdobePDFViewerNPAPI: Version: 11.0.06 - SDK 10.6 Support
    Silverlight: Version: 5.0.61118.0 - SDK 10.6 Support
    Flash Player: Version: 15.0.0.189 - SDK 10.6 Support
    QuickTime Plugin: Version: 7.7.3
    iPhotoPhotocast: Version: 7.0
    SharePointBrowserPlugin: Version: 14.2.0 - SDK 10.6 Support
    DirectorShockwave: Version: 11.6.0r626 Support
User Internet Plug-ins: ℹ️
    CitrixOnlineWebDeploymentPlugin: Version: 1.0.105 Support
    Picasa: Version: 1.0 - SDK 10.4 Support
3rd Party Preference Panes: ℹ️
    Flash Player Support
    Flip4Mac WMV Support
    NetUpdate Support
    WacomTablet Support
Time Machine: ℹ️
    Time Machine not configured!
Top Processes by CPU: ℹ️
        12%    firefox
        10%    WindowServer
         4%    plugin-container
         0%    hidd
         0%    AppleSpell
Top Processes by Memory: ℹ️
    743 MB    firefox
    451 MB    plugin-container
    94 MB    Finder
    90 MB    mds_stores
    77 MB    WindowServer
Virtual Memory Information: ℹ️
    64 MB    Free RAM
    1.22 GB    Active RAM
    1.16 GB    Inactive RAM
    733 MB    Wired RAM
    9.37 GB    Page-ins
    119 MB    Page-outs
MacBook Pro, OS X Yosemite (10.10)

Turning off "Chroma Blur" introducing color artifacts? (Aperture 1.5)

I seeing what appears to be color artifacts being introduced when turning OFF chroma blur. I have two images posted here that you can use to see what I'm talking about. They're both crops of the same image with and without chroma blur (looks specifically in the text written on the side of the plane - you might have to zoom in to see the "magenta" colors bleeding between the letters on the version without chroma blur). If I view the original raw file in "Preview" the image is clean and looks like the one with Chroma Blur turned on. Is this a known issue?
Images: http://johnterrell.smugmug.com/gallery/1968434/1/100160466
(The keywords below the image will tell you the one with and without chroma blur)
Thoughts?

I seeing what appears to be color artifacts being
introduced when turning OFF chroma blur. > blur).... If I view the original > raw file in "Preview"
the image is clean and looks like the one with Chroma
Blur turned on. Is this a known issue?
Certain features you are only going to see when the image is viewed within Aperture at 100%. This is similar to ACR, DPP and Lightroom.
You need to view the image at 100% to see the effect of noise reduction. So, it's not an issue, it's just the way the program works.
Chroma Blur eliminates or lessens chroma noise so it makes sense that turning it off would lead to noise and artifacts in images.

Does ACR 7 delete D800 profiles from ACR 6.7?

I have a Macbook Pro and a Mac Pro, both of which are running, OS X 10.7.3, Photoshop CS5, and ACR 6.7rc1. On the Macbook Pro, the folders for D800 and D800E profiles are present, and the canned profiles for those cameras appear in the Camera Profiles menu of ACR 6.7. But these folders and profiles are missing on the Mac Pro. I can load D800 raw files into PS CS5 on that machine, but ACR 6.7 only shows "Matrix" in the Camera Profiles menu.
Maybe the installation of ACR 6.7rc1 went awry on the Mac Pro. There's another possibility. I installed the beta versions of Lightroom 4 and Photoshop CS6 on the Mac Pro. They are running side by side with CS5 and appear to function OK. CS6 comes with ACR 7. Perhaps there is a conflict between ACR 6.7 and ACR 7.
I know that ACR 7 does not yet support D800(E). Is it possible that the CS6 installer removed the D800(E) profiles that had been installed by ACR 6.7?
Can ACR 6.7 and ACR 7 run on the same machine?
Is it safe for me to copy those missing profiles from Macbook Pro to the Mac Pro?

I sent the JPG to a service for a print on canvas. They reported that the image was not the proper size and shape when they opened it in Photoshop. Unfortunately I have not been able to get them to tell me what pixel size it was, just rough inches (!?!?!). So I started trying things in Photoshop and came up with this strange behavior that might explain the problem at the service.

ACR 6 color artifacting not present in ACR 5

Similar Messages

Maybe you are looking for