Camera RAW pixel artifact issue

This is something that has been bothering me for a while and I don't understand how other people don't see it.. Mainly due to the fact that you need to be zoomed in about 300% or more on an image to see it. I have only seen Lightroom 3 rendered jpeg files without this problem. I am talking about the absurdly weird artifacts in the pixel makeup when zoomed in on a edited image rendered by Adobe Camera raw 5.6 and lower. It looks like worms have been moving around under all the pixels. It is not a clean and definate pixel noise ratio that you would get from rendering images from their native software for example ViewNX, Capture NX nor Canon's DPP.

1. Do you see the worms in LR/ACR too, in this magnification, or only in the JPEG version?
2. Do you see them in a TIFF as well?
3. If they are not there in TIFF: create a JPEG from the TIFF. I guess LR too has a "preview" option, showing the effect of conversion in the image in the currently displayed magnification. Change the "quality" setting and watch for the effect (you have to wait a bit to see the effect of the change). If I do this in CS3, the worms are there up to quality 8, most of them vanish with 9 and it is clean from 10.
If the worms are visible already during the raw processing, i.e. in LR/ACR, then it is a different issue, probably camera dependent.
Gabor

Similar Messages

  • Installer, application manager and camera raw plug in issues

    Hi - I need help.
    I'm running on Windows 7. I have just upgraded Photoshop to CS5.5 from CS4 (on my laptop not a creative cloud version). I have since uninstalled Photoshop CS4. I was trying to install the camera raw plug in 6.7.1 but it would not install and I got a message saying that the application manager was damaged and to download it again. I have downloaded the application manager file but cannot install it. I am getting the "installer failed to initilize" message. I've read through the forums on this and cannot find a solution.
    I have extracted the file so I am not trying to open a zip file. I have downloaded a second time to a different location and tried installing again while logged into creative cloud but got the same message. I saw the comment about deleting the Adobe/OOBE folder and trying again but was wary about doing this as I don't know what this folder is. Can someone tell me what this is and why I would delete it?
    I don't think I had this issue before I uninstalled CS4. I think I had already downloaded a camera raw plug in for that version. So I am wondering if deleting CS4 caused the issue.
    I then downloaded CS6 cloud version thinking that perhaps I would get application manager installed correctly within that. I have now been able to install the camera raw plug in and this is now working in CS5.5 but strangely still cannot run the setup.exe for the application manager (So perhaps it is just a problem with Installer?).
    Can someone tell me if application manager is just relevant for cloud based products or is it required for desktop versions as well? Could creative cloud be interferring with my desktop version? Where can I find the application manager files? If I uninstall CS6 will I have the same problem with application manager not working in future? I do not really want to use a cloud based version (CS6) and don't want to keep unnecessary programs on my laptop.I signed up to Creative Cloud when both desktop and cloud versions were supported and may not continue when my subscription expires.
    To fix this problem without CS6 do I need to reinstall CS5.5? (To do this I will have to reinstall CS4 as it was an upgrade version). Would just reinstalling CS4 fix the problem? Can I just reinstall the application manager part of either of these or is there a simpler solution?
    Thanks in advance as I am not super tecchie and am running out of ideas.

    Hi
    I have Creative Suite 5.5 Master Collection but have only installed Photoshop and Bridge ( this includes files associated with that install). Since installing that I have also installed Photoshop 6 (with Bridge etc).
    The issue I had in Photoshop 5.5 was I was unable to read files from Canon EOS 5D Mark 2. I was trying to install the camera raw plug in 6.7.1 to fix this. I got a message saying that the application manager was damaged and to download it again. I downloaded the application manager file (adobe application manager 8) but couldn't install it. I got an "installer failed to initilize" message.
    So I downloaded CS6 to see if that would fix the application manager issue. I have now been able to install the camera raw plug 6.7.1  and this is now working in CS5.5. So the initial problem is fixed for now but what I want to know is -
    - Is the Application Manager associated with the version or does it stand alone as a separate file?
    - If I now uninstall Photoshop 6 will the Application Manager uninstall also, or will it continue to work in 5.5?
    - What is the best way to uninstall version 6 - should I do this through Application Manager not Windows Control Panel? I cannot see where to do this.
    The Adobe site says to start AAM by :
    Choose Help > Updates in a Creative Suite 5 product.
    Double-click PDApp.exe in the following locations:  Windows 64 bit: \Program Files (x86)\Common Files\Adobe\OOBE\PDApp\core\
    If I chose Help in Photoshop 5.5 - the update option is greyed out and not available.
    If I follow the second option I get the Creative Cloud Application Manager (version 9) offering me updates for version Photoshop 6 only.
    How can I find out if I have a working Application manager for 5.5?
    What is the best way to uninstall version 6?
    You are right I have found folders / files which need to be cleaned up from CS4 eg: plug ins and a lot of empty folders. What is the best way to clean up these - can I just delete them in Windows Explorer?
    Sorry this is long - I am learning as I go
    Carmel

  • Camera Raw Color Temperature Issue

    Help me verify color temperature issue please.
    I shoot with Canon EOS 5D.
    I sat white balance mode to K - Manual Kelvin temperature - and set value to 6000K.
    So my raw files should have this setting - color temperature 6000K.
    Canon ZoomBrowser EX shows me the value - 6000K
    Nevertheless I see different reading in Adobe Camera RAW converter (as shot)?
    Photoshop CS2 Camera Raw CT=5600K Tint=+3 (! as Shot !)
    Why?

    Ramon seemed to have the answer in hand, then G Sch above chimed in with some random comment about coordinate systems. Weirdly, Ramon then agreed with G Sch's nonsense and thanked him for it. Suddenly the thread has suffered an ineluctable defenestration.
    Is:
    - camera maker's control for XXXX Kelvin wrong?
    - Adobe's control for XXXX Kelvin wrong?
    - the use of the designator "K" in these contexts wrong, as it implies physics reference for the measure while the camera and ACR just do their own thing?
    By the logic used in this thread, 1/250sec shutter doesn't have anything to do with a time standard, nor does F4 mean an aperture, it's just a coordinate in a locally defined system, la la la. So why bother to even code it in EXIF? What's the point of providing a control in terms of K if K isn't normalized?
    The question was answered at Ramon's first post: ACR doesn't read the 5D white bal metadata. The camera K setting is used for in-camera processing and by Canon utilities. But note that the raw data are white bal agnostic but white bal results are subject to a camera profile which may differ between OEM and ACR, and at which point there is room for discrepancy for interpretation of color. Which one is right? I can't say. It's important to realize the results for a given K setting may differ between OEM and ACR because of this. Contrary to what G Sch writes above, the same K setting ought to give the same results if a "Kelvin" setting is to have real meaning, but the seems to be impracticable if the developers don't agree on the characterization of the gear.

  • Camera Raw custom settings issue on 4.5?

    I updated to CR 4.5 on my new Mac 17 inch powerbook, and now the custom settings choice uder the basic pull down menu no longer seems to do anything. It used to update from the previous change I had done in the open camera raw window. Now I would need to close the window, reopen and use the previous conversion under the basic pull down menu. It has slowed my workflow dramatically. I can't find anything in preferences. Anybody have any ideas? J.

    > A new image will show up initially with camera raw defaults as its setting. making a change will alter to custom settings.
    Yes ... ok so far ...
    > If you move to custom settings in the basic drop down menu nothing happens.
    ... again, ok so far ...
    > Previously, this would alter the file to the last image settings you had changed.
    I don't remember CR ever doing this. Why would CR "assume" anything (other than the defaults) for a new image selected?
    > Which will force me to use another program, as the workflow is too slow.
    I don't understand how CR's intended method for "assuming" settings from another image (ie , synchronization), is any slower than what you're describing. In fact, if the images were many your method would be slower.
    I won't deny what you're seeing as apparent behaviour of CR on your computer, but I fail to understand how what you describe is better than CR's intended behaviour(?) I suppose choosing 'custom' could assume something, and the last edit is as good as any - but even so, doing this one-at-a-time for subsequent images has got to be slower than synchronizing.
    my CA$0.02 :)

  • DNG / Camera RAW 8.3 issue

    Have CS6.  Just downloaded Camera Raw update from here:
    http://www.adobe.com/support/downloads/detail.jsp?ftpID=5694
    because my CS6E Help > Updates is grayed out & I can't do it from there...
    Update lists Sony RX10 RAWs as being recognized.
    Download was reported as successful & file was correct size at 154MB.
    DNG program opens as separate window from CS6E.
    But it sees a folder of RX10 RAWs as empty
    with message that RAWs are not recognized.
    Any advice on resolving appreciated!
    Thanks!

    > In the dng converter just point to the folder with the images, not open the folder with the images.
    Thanks!  That worked!
    Was able to convert SonyRAWs to DNG-RAWs.
    Am using Windows 7.
    Had CS2 on same laptop & couldn't open CS6 Bridge.
    (some kind of conflict reported by others as to CS2-CS6)
    So tried deleting CS2 & CS6 & reinstalling CS6.
    But now am able to update to Camera RAW 8.3 from 7.0.
    Still can't open CS6 Bridge, too.
    Where do I find AdobeApplicMgr & how to check for updates?
    Thanks in advance.

  • Camer Raw Plug-in Issue

    When sending a photo from LR5 to CS5 I get a message saying this version of LR may required the photoshop camera raw plug-in version 8.2 for full compatibility.  I don't know what to do?

    Photoshop CS5 uses ACR 6.x. You need Photoshop CS6 or later to have Camera Raw rendering compatibility, or render the image as Tiff when doing an Edit In > Photoshop CS5.

  • Digital camera raw 3.2 issue with Canon 1000d

    Hi all,
    When I install the digital camera raw 3.2 update, Aperture 3 (3.0.3) gives me the indication to reprocess all master files. After that my images become darker and the colours like red, orange and skin tones become very saturated and strange compared with the previous version.
    To solve this problem I revert to the previous version of digital camera raw and everything is ok now.
    Follow the tip in the link above. http://discussions.apple.com/thread.jspa?messageID=11148487&#11148487
    My English isn’t very good, however my experience could save some troubles and time to other users.

    You need to reprocess them in Aperture. Ap3 has a better more advanced raw processor/converter than ap2 It is far superior and the first thing i noticed on ap3. Try on an image you thought was at it's best and could not be improved. I will be surprised if you can not make it better in ap3.
    My suggestion is to process them one at a time, before you want to make some image adjustments.
    Allan

  • D800 camera raw and cs5 issue

    i have a nikon d800. i have cs5. ps5 wont open RAW files. i have tried plugins, upgrades etc but just cant get any joy. i have 64bit windows home premium. no luck. any help?

    You need to update your Camera Raw plugin to 6.7 inorder to work with the Nikon d800 , check the link below:-
    http://blogs.adobe.com/lightroomjournal/2012/05/adobe-camera-raw-6-7-and-dng-convertor-6-7 -now-available-on-adobe-com.html

  • Adobe Camera Raw 8.6 issue with Nikon D810 files

    Just installed ACR 8.6 with D810 support.
    A huge amount of moire is introduced when selecting the following profiles: camera standard, camera landscape, camera vivid, and camera monochrome.
    All other profiles (adobe standard, camera neutral, camera flat, and camera portrait) seem ok.
    The problem exists in Photoshop (via ACR) and in Lightroom 5.6. Please note that Nikon Capture NX-D doesn't have this issue.
    Example: Check the upper portion of the following image:

    I have experienced the same, although having never owned a camera without the olpf, I did not realize that what I was seeing was moire -- I was calling it "color banding" as if shooting with a low bit rate or very small color gamut.
    I think the same issue is referred to in the following post: http://www.dslrbodies.com/accessories/software-for-nikon-dslrs/software-news/acr-86-and-li ghtroom-56.html but he is vague as to just what the "issue" is.
    I noticed this issue not only with acr, but on the back of the lcd of the 810 itself.  Wondering if I was doing something wrong in terms of settings or if it was a bad copy of the d810, I contacted nikon support. They were not helpful and told me to return the unit for repair.   I saw this to a great degree on the lcd, to a small degree even in the raw images processed via Capture NX-D and to some extent via acr 8.6 as you say, when using he following profiles: camera standard, camera landscape, camera vivid, and camera monochrome.  Since I was not able to convince myself tat it was not an issue with the camera itself, I returned the d810, so I was not stuck with a problematic unit or having to wait for a repair.  Now of course I just have to wait for a replacement unit!!
    Again, I am curious as to the extent others are seeing this problem.  I am seeing nothing but superlatives posted by others.  I am hoping that this is some raw processing issue and a bad lcd screen on my original d810, but it seems too big of a coincidence.  If it is a matter of Adobe racing to keep up with the new profiles ok, but if this is the extent that I am going to see moire on a camera of this price then it is not worth the upgrade.
    What are others experiencing?

  • Lightroom 3.6 Camera Raw 6.6 - Issues with NEF files

    Hello all,
    I'm sure I'm not the only person with this problem, I'm a Nikon user and when I view NEF files in Lightroom 3, before the images loads completely it looks like it did on my camera but when the loading phase is done the picture darkens and it changes, sometimes darkens, sometimes changes tones.. What is happening here and is there any way around this with NEF files?  I love Lightroom but if I can't work with NEF the way they look on my camera then I'm going to have to make the switch over to Capture NX 2 and I really don't want to....  In addition I have no problems with JPEG files so I know the issue is isolated to NEF files.  I'm also on a Mac with 10.6.7 if that makes any difference.. not sure it does though.
    Please help!!

    This is not just a characteristic of NEF files.  Adobe software and other third party software does not read the in camera settings, instead it applies default settings.  The initial image you see is probably the stored image that was processed by the camera, but it is replaced by the image rendered using the defaults from Lightroom.  The default camera profile is Adobe Standard, which does not match what you get from the camera.  Adobe has generated Camera matching profiles for Nikon and Canon cameras and a few others.  Go to Camera Calibration and select the same profile you have selected in the camera - it will have a name like Camera Standard, Camera Neutral, etc.  If you have other parameters set to nominal in the camera, this will be a close match to the JPG from the camera.  You can set a new default for Lightroom that will use the setting you select and it will use this when any new NEF files are first opened.  If you want the NEF file to open identical to the JPG from the camera then Nikon software is the only option.  If you were using a Canon, then Canon software would be the only option. 

  • BMD Cinema Camera RAW Files Import Issues

    While the playback performance seems strong--there is a marked visual difference in the image than when opening these files in AE or PS--strong green push and muted colors--
    Do I have an incorrect setting somewhere?

    Yes, here too untouched BMDs seem te have a green cast. Althoug muted colors, to me mean not having the right (or any) LUT applied; just a part of working with RAW; you have full control, just have to create a first light/primary.
    (Haven't tested against AE yet.)

  • Hot / dead pixel elimination in later versions of Camera RAW

    Hi!
    I was wondering if we could get some under the hood info on how Camera RAW handles hot / dead pixels. The standard answer 'Camera RAW eliminates these automatically' does not apply I'm afraid. I've seen more and more of these stuck pixels in my final output over the last few CR versions. Now, it could be my camera showing its age, but I'd like to know more about how Camera RAW maps stuck pixels.
    I've just re-developed a set of some stage performance from last year, Canon 5D Mark II, high ISO and pushed, yes, but thats my whole niche. There's stuck pixels in all of them in the same spots. So I wondered how camera raw handles the whole mapping / processing of hot pixels. The set of images are here, and there's access to full size images also: http://www.flickr.com/photos/mvejerslev/sets/72157627732199199/ (I did clone out the stuck pixels on just a few of them though). It's a mix of processing version 2010 and 2012. Did not make a difference to the stuck pixels.
    Mathias

    Well, the issue with higher ISO images is: what's a hot pixel vs. what's a result of salt & pepper noise–those are different artifacts...
    When you start ramping up the ISO (and use PV 2010 or 2012 without luminance noise reduction) the likelyhood of random bright (more or less) pixels (or subgroups of pixels) goes up.
    The hot pixel fix is still in LR/ACR...but it becomes a battle between what's a hot pixel vs what's a result of camera noise...and ACR/LR tend to be very conservative when it comes to mapping out a hot pixel (or dead or constantly a certain color pixel).
    ACR/LR can really only estimate what constitutes a hot pixel because there's no way of recording the XY position of a single pixel and telling it how to handle the mapping. It's an auto thing and as such it's subject to sometimes not working perfectly...
    To really determine the issue, one (or Eric) would need an actual raw file–not something that's already been processed and resample. The more examples of ACR/LR not doing an optimal result the better the likelyhood somebody will look at doing something about it.

  • Possible GPU Issues With Camera Raw 6.6

    Over the past day on my Windows 7 x64 workstation I've done some updates.  Specifically:
    The Adobe updater brought in Camera Raw 6.6, replacing 6.5.
    I updated the to the ATI Catalyst 11.12 display driver version from previous version 11.11.
    I allowed Windows Update to apply the dozen or so changes that were pending.
    I was just doing some OpenGL testing with Photoshop CS5 12.0.4 x64 and I noticed that under some conditions I saw Photoshop drop out of OpenGL acceleration.  Specifically, when I opened a Canon 5D Mark II image through Camera Raw I saw subsequent operations stop using OpenGL acceleration even though the checkmark remained in the [  ] Enable OpenGL Drawing box in Edit - Preferences - Performance.
    What I did to determine whether OpenGL acceleration was enabled was this:  Select the Zoom Tool, then click and hold the left mouse button on the image.  When OpenGL is enabled, I see a smooth increase in zoom.  When it goes disabled, I see only a jump in zoom level after letting up the mouse button.  Also, the [  ] Scrubby Zoom box gets grayed out.  As I mentioned, even in this condition, a check of Edit - Preferences - Performance still shows OpenGL enabled.
    Just as a control, I saved the converted file as a PSD, and every time I opened THAT file (with a fresh copy of PS CS5 running) and did the same operations I could not reproduce the failure.  The difference being I did not run Camera Raw.
    Since I wasn't specifically looking for issues with Camera Raw, I am not sure that the problem occurred every time I did run Camera Raw.  I do know that when I open images from my own camera (40D; I do not own a 5D Mark II) that the problem doesn't seem to occur.  Notably I always open my image from Camera Raw to the largest possible pixel size - 6144 x 4096, as I did with the 5D Mark II image, so it's not an obvious size difference that's leading to the issue.  Given other comments of late, I'm wondering if it could be a specific issue with conversions of files from 5D Mark II.
    Nor am I sure whether any of the above updates caused it - it might done this before; I don't regularly convert 5D Mark II images.  I DO think I would have noticed Photoshop reverting to GDI operation before, since I just noticed it pretty easily, but I'm not completely sure of that either.  I do use OpenGL-specific features (such as right-click brush sizing) pretty often.
    I'm trying now to find a set of steps with which to reliably reproduce the problem now, and will advise.
    -Noel

    Figures.  Now I can't reproduce the problem at all, even after an hour of testing.  It probably had nothing to do with Camera Raw.
    I wonder if there are latent GPU status indicators and config values stored by Photoshop based on its specific environment that might not be right for the first run (or first few runs) after a display driver update.  Hm....
    -Noel

  • Camera Raw 7.1 Columnar Color Artifacts

    Adobe:  For some reason you wouldn't listen when these problems were reported during beta and you went ahead and released the new version, so I'm not sure I should even bother, but here goes:
    Camera Raw 7.1 introduces columnar artifacts in the red color channel (that I've seen), apparently as a result of the operation of the new half-baked defringing features.  I've seen this in a number of images.
    Here's a raw Canon EOS-40D file and associated XMP with which you can reproduce the problem. Look at the red channel in the blue water of the pool.
    http://Noel.ProDigitalSoftware.com/ForumPosts/IMG_5037.zip
    Now convert the same file with version 7.0 (or 7.1 with the Defringe sliders set to 0) and compare the result.
    Trouble is, without being able to use the Defringe (Purple/Green) features at all, and considering the Defringe:  All Edges feature has been removed, edge artifacts from the debayering process get to be unacceptable.
    Let me spell out for you what you need to do, in case it isn't obvious:
    1.  You need to bring back the Defringe:  Off / Highlight Edges / All Edges feature that you had in 7.0 and earlier.
    2.  You need to fix this new slider-based defringe facility so that it doesn't do such nasty things to the image. I'd advise you to listen to Vit Novak's input on what else to do to it.
    With BOTH of these things done, between the two one could actually hope to get an improved result over the conversions from 7.0.  Fixing the second alone won't cut it.
    -Noel

    Back off?  I should heed your expert advice on avoiding confrontation, Jeff?    I have to assume by your unwavering support of Adobe on this issue that you are looking forward to having stylish artifacts like these in your own images.  I guess this will define your new style for 2012.  LOL
    All the slack that's going to be cut on this has already been cut.
    Hey, I could have just quietly dropped back to 7.0 and just have my own images be superior to those made by those using 7.1, but no - I chose to try to help Adobe by pointing out a problem to them here.
    When I reported this problem during the beta, I was clearly ignored.  When I reported it again after the release, I was argued-with.
    I don't need to be argued-with nor reasoned-with - Adobe needs to listen to people who know what they're talking about.  People not blindly praising the emperor's new clothes.
    I don't need nor expect appreciation, but I had thought I might have earned enough respect around here that Adobe's first response wouldn't be "choose different settings, stupid".
    An output image quality problem should be a release show-stopper. Experts like me and Vit telling Adobe that their latest color fringing reduction changes aren't working well enough should be considered seriously. Instead, it's just business as usual: Release whatever's in the pipeline.
    Adobe's dropping quality standards are something I find myself wanting less and less to be associated with each passing day.
    Just typing this message took me longer than it should have, because of this bogus forum software.
    There's a difference between leadership and "too big to fail" thinking.
    This is my last post in this thread.  Thanks for your participation.
    -Noel

  • Photoshop Camera Raw 7.4 Update  is not installing because of Error Code U43M1D207. What needs to be done to resolve this error code issue?

    Photoshop Camera Raw 7.4 update is not installing because of error code U43M1D207.  What needs to be done to resolve this issue?

    If you need to post again, please keept the following in mind:
    BOILERPLATE TEXT:
    Note that because this is boilerplate text, not all points may apply to any given, specific poster.
    If you give complete and detailed information about your setup and the issue at hand,
    such as your platform (Mac or Win),
    exact versions of your OS, of Photoshop (not just "CS6", but something like CS6v.13.0.6) and of Bridge,
    your settings in Photoshop > Preference > Performance
    the type of file you were working on,
    machine specs, such as total installed RAM, scratch file HDs, total available HD space, video card specs, including total VRAM installed,
    what troubleshooting steps you have taken so far,
    what error message(s) you receive,
    if having issues opening raw files also the exact camera make and model that generated them,
    if you're having printing issues, indicate the exact make and model of your printer, paper size, image dimensions in pixels (so many pixels wide by so many pixels high). if going through a RIP, specify that too.
    etc.,
    someone may be able to help you (not necessarily this poster).
    a screen shot of your settings or of the image could be very helpful too.
    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
    Thanks!

Maybe you are looking for