Camera Raw monitor compensation

I have this question: what is the rendering intent in Camera Raw 6 monitor compensation? It is fixed or changes with profile version (v2 and v4)?
And: is the monitor compensation in module Develop of Lightroom 3 the same (i. e. same rending intent?) as in Camera Raw 6?
Thank you.
Mauro

I retested with a specific target image for matrix/TRC and, as far as I can see, neither Bridge nor Camera Raw seem to use the monitor profile in any way...
Can it be?
Note that Bridge has no "Use Color management" switch anywhere in preferences. I also reset prefernces (files and registry) to be sure.
May be that Bridge color management stops at embedded color profiles without using the monitor profile?
The same for Camera Raw?
By the way I test another well know DAM software... it uses Perceptive intent but at last it sees monitor profiles.
A very strange matter indeed...
Massimo

Similar Messages

  • Camera Raw window appears in wrong monitor

    About a week ago, the camera raw window started appearing in the secondary monitor of my pair and I cannot stop it from starting there. It appears with the title bar up off the top of the screen and I can just barely grab the top corner of it from the edge of the primary monitor and drag it out where I can move it.
    Prior to this, if I opened a raw file directly into CS3, it would start in the primary where CS3 is placed or if I right clicked a raw file in Bridge and chose open in CR, then it would open in the secondary monitor where Bridge is located. Now I don't get the choice. This was happening before the latest updates which all appear okay. System is a PC by the way.
    I would appreciate any assistance.
    Col

    Okay, here's a lesson for us all. I had accidentally hit the F key (Full screen mode toggle) whilst in there and it fills the screen with no hope of getting to the edges. Once back in normal mode all is well again!!!!! Embarassed
    Thanks for the help
    Col

  • Hello, I have a Mac computer with NVIDIA 750M dedicated graphics card and monitor EIZO but the problem was there when I was working with Windows and Acer monitor. When I open a file from Camera Raw in PS this is smaller than the screen so I double-click w

    Hello, I have a Mac computer with NVIDIA 750M dedicated graphics card and monitor EIZO but the problem was there when I was working with Windows and Acer monitor. When I open a file from Camera Raw in PS this is smaller than the screen so I double-click with the tool "hand" to fit on the screen, but the picture loses sharpness and becomes blurry. If you magnify the image even only slightly with the tool "zoom" the picture comes back clear. In Camera Raw instead is always sharp. I solve the problem by turning off the graphics card in PS but often use plugin that need the graphics card otherwise the processing time is much longer. I ask for help.
    Thanks.

    Hello, I have a Mac computer with NVIDIA 750M dedicated graphics card and monitor EIZO but the problem was there when I was working with Windows and Acer monitor. When I open a file from Camera Raw in PS this is smaller than the screen so I double-click with the tool "hand" to fit on the screen, but the picture loses sharpness and becomes blurry. If you magnify the image even only slightly with the tool "zoom" the picture comes back clear. In Camera Raw instead is always sharp. I solve the problem by turning off the graphics card in PS but often use plugin that need the graphics card otherwise the processing time is much longer. I ask for help.
    Thanks.

  • Camera raw on a 4K Monitor (CC 2014.1)

    I've downloaded the trial of Photoshop CC today with a view to taking out a subscription having bought a 4K Monitor (using with Windows 8) - my problem is that while Photoshop CC itself has the very helpful scale UI to 200% option in experimental features, this doesn't carry over to Camera Raw.
    Is there any way of making Camera RAW usable / readable on a 4K monitor?

    You may also want to post in the Camera Raw.  The Camera Raw team is relatively active there—except when they're superbusy pushing out a new release.
    Here's the link:
    Adobe Camera Raw

  • After using Canon Digital Photo Professional Adobe Camera Raw cannot identify my Monitor again.

    Wenn eine RAW Bildbearbeitung mit Canon Digital Photo Professional stattgefunden hat, erkennt Camera Raw die Auflösung meines Bildschirms nicht mehr und produziert die Fehlermeldung, das die Auflösung des Bildschirmes zu niedrig wäre. Diese Fehlermeldung kommt dann auch bei bisher nicht aufgerufene und somit nicht bearbeitete .raw. Die gleichen Bilder als .jpeg werden in der richtigen Bildschirmauflösung angezeigt.
    Installiere ich Photoshop Elements 13 neu ist alles OK, bis zu dem Zeitpunkt wo ich Canon Digital Photo Professional das erste Mal wieder benutze. Nach der 1. Nutzung erkennt Camera Raw die Auflösung nicht mehr.
    Der Fehler ist seit dem letzten Update von Ramera Raw vorhanden und auch mit dem letzten Bugfix von Camera Raw nicht verschwunden.
    Hat jemand eine Lösung?

    Wenn eine RAW Bildbearbeitung mit Canon Digital Photo Professional stattgefunden hat, erkennt Camera Raw die Auflösung meines Bildschirms nicht mehr und produziert die Fehlermeldung, das die Auflösung des Bildschirmes zu niedrig wäre. Diese Fehlermeldung kommt dann auch bei bisher nicht aufgerufene und somit nicht bearbeitete .raw. Die gleichen Bilder als .jpeg werden in der richtigen Bildschirmauflösung angezeigt.
    Installiere ich Photoshop Elements 13 neu ist alles OK, bis zu dem Zeitpunkt wo ich Canon Digital Photo Professional das erste Mal wieder benutze. Nach der 1. Nutzung erkennt Camera Raw die Auflösung nicht mehr.
    Der Fehler ist seit dem letzten Update von Ramera Raw vorhanden und auch mit dem letzten Bugfix von Camera Raw nicht verschwunden.
    Hat jemand eine Lösung?

  • Raw photos opened in Camera Raw look much, much different

    Hello Adobe Community,
    I'm hoping you can help me solve my exceptionally frustrating problem that I'm currently having.
    I shoot with a Canon 5d mark III, and do my preliminary narrowing down in Photo Mechanic.
    My image preview on my camera, and my image preview in Photo Mechanic match and look the same.
    However, when I pull an image into Camera Raw, it looks dark and I can't easily make the changes for it to look like the preview.
    Any ideas? I'd be happy to supplement any additional information necessary.

    I hate to tell you this, but the histograms in both Photo Mechanic and ACR clearly show the image is underexposed.  Histograms don't lie.  It is really that simple.
    The first thing I would do is adjust the LCD brightness in the 5D3 Cfns
    http://www.kenrockwell.com/canon/5d-mk-iii/users-guide/
    Then I would make a habit of at least occasionally use the Info button on the 5D3 to view the histogram when chimping images.  You need to get a handle on how the camera copes with different situations.  I use a 1DsMK3 and 1DMK4 and I find that the default Evaluative metering tends to blow highlights in bright conditions, but will under expose in dim interiors.  So get into the habit of using AEC (Auto Exposure Compensation) to correct this.
    I am wondering why you use Photo Mechanic rather than just use Bridge and ACR?  ACR is obviously giving you a much truer representation of your image, whereas Photo Mechanic is distorting things making it look brighter than it really is.
    Do you have any sort of monitor calibration in place?

  • Disk IO efficiency in Bridge CS5 and Camera Raw 6.0

    After watching Microsoft Process Monitor (ex-sysinternals) while processing a large batch of DNG's that in Camera Raw were being converted to a different Process (2010 to 2003) and a different a different Camera Profile, I have the following questions:
    Why read files in sequential chunks far smaller than we could?  Why not 128KB or 64KB chunks for the DNG header read instead of 4KB?  Why not at least 256KB chunks for the main DNG read?   Why not 32KB chunks for the Camera Profiles, if we're going to read them over and over at all?
    Why read all the profiles for every single photo, when we can possibly use at most two (the original one, and the new one), and more often only one?  More to the point, if we're working on a large batch of photos on a machine with 6GB of free RAM, I would suggest loading them into RAM and leave them there.
    Why multiple Create/Close sets on Defaults\Preferences during large batch processing?
    Why so many CreateFile...CloseFile sets for the same main DNG file; we're operating on the same file through this process.  Why close it when we're just going to open it right up again?
    Summary over one file's processing
    00:49:58.72 CloseFile A
    00:49:58.72 Mess with Defaults\Preferences.xmp
    00:49:58.72 CreateFile B
    ...               ReadFile B in 4KB chucks out to just past Offset 167,936
    00:49:58.72 WriteFile B - write 11,187 bytes at Offset 780
    00:49:58.72 CloseFile B
    ...               Mess with some Adobe\CameraRaw\Database CreateFile, ReadFile, CloseFile stuff for very little time.
    00:49:58.72 CreateFile B
    00:49:58.72 ReadFile B in 64KB chunks out to just past Offset 19,165,184
         00:49:59.12 The last ReadFile; essentially, reading at ~45.84MiB/s for 0.4 seconds
    00:49:59:12 Start reading all the CameraProfiles\Adobe Standard\Canon EOS 50D xxx.dcp in 4KB chunks for 55-110KB or so: the order is Adobe Standard, Camera Faithful, Camera Landscape, Camera Neutral, Camera Portrait, Camera Standard,
        00:49:59.13 The last ReadFile for the profiles
    00:49:59.13 CreateFile B
    00:49:59.13 ReadFile B in 4KB chunks twice, at Offset 0 and Offset 53,248
    00:49:59.13 CloseFile B
    ...               Mess with some Adobe\CameraRaw\Database CreateFile, ReadFile, CloseFile stuff for very little time.
        00:49:59.13 Last CloseFile on the above
    ??? CPU use, I assume
    00:49:59.78 CloseFile B
        ??? The previous operation on B appears to also b a CloseFile.  I assume I'm failing to interpret Process Monitor; I must have missed an operation.
    00:49:59.78 CreateFile, CloseFile on Defaults\Preferences.xmp - Read Attributes
    00:49:59.78 CreateFile Cache\Index.dat
    00:49:59.78 ReadFile Cache\Index.dat in 4KB chunks then write it in 4KB chunks, about 24KB worth
    00:49:59.78 CloseFile Cache\Index.dat
    ??? CPU use, I assume
    00:50:01.40 CreateFile B
    00:50:01.40 WriteFile B in 256KB chunks
    00:50:01.42 CloseFile B
    00:50:01.43 Another Read Attributes Create/Close set on Defaults\Preferences.xmp
    00:50:01.43 CreateFile C
    repeat pattern
    Total: 2.71 seconds.
    The sum of the two long ??? CPU segments: 2.27 seconds
    The time not part of the two long ??? CPU segments: 0.44 seconds, or about 20% of the total for that file.
    Of that, changing the main DNG file read from 64KB chunks to 256KB chunks could have reduced that 20%, to about .35 seconds.  On a batch of 1000 photos, that's a savings of almost 6 minutes.  A hundredth of a second here, a hundredth of a second there, and pretty soon you're talking about real time.
    Note that SQLIO, with an outstanding IO queue of only 1 (as this appears to generate), with only 1 thread, dealing with only one 4GB file, for 120 seconds, rates the SSD which stores the DNG's at:
    4KB: 48.10MB/s
    64KB: 173.85MB/s  -- much, much faster
    256KB: 222.95MB/s  -- still significantly faster than 64KB
    While my SSD doesn't take up much more time doing the smaller reads, slower or more heavily used drives will make the lower efficiency more visible to the end user, particularly for batches.

    I don't know the specifics, but keep in mind this software is built to work on multiple completely different operating systems.  There might be some "minimum common denominator" stuff going on.
    -Noel

  • Bridge does not show my Camera Raw Adjustments in previews or thumbnails.

    Bridge CS6 on my Mac is not showing my Camera Raw adjustments in a preview pane or thumbnail.
    Here's how it worked until recently:
    I open a .CR2
    I make some adjustments
    I click "Done"
    The thumbnail and the preview show the adjustments I made
    Now, it works like this:
    Open a .CR2
    Make adjustments
    Click "Done"
    The preview and thumbnail don't show all the adjustments. I can't see the results of noise removal, but I can see a drastic change in Exposure
    If I double-click the CR2 file, it opens in Camera Raw, and I see all my adjustments, including noise removal.
    Here's what I've tried, but saw  no difference (I restarted Bridge every time):
    Purge Cache
    Purge Cache for Selection
    Replaced Camera Raw plug-in as described here: Camera Raw 8.4 | No metadata or Camera Raw edit
         (Doing so made Camera Raw disappear in Bridge, so I restored the original file)
    Reset Preferences
    Reset Standard Workspaces
    All the above fixes were inspired by this thread: Re: Bridge CS6 not showing Camera Raw adjustments
    Why don't I see the noise removal effect in the previews? I am sure I saw it a few weeks ago. I rely on that, to help me sort and cull photos.
    I'm hoping there's a preference toggle that I accidentally changed. It's definitely a puzzle. (Version: Bridge CS6 5.0.1.21 5.0.2.4)
    Message was edited by: moonatwork after updating Bridge version. I tried all the above fixes again, after updating Bridge. It actually got worse. I tried replacing the Camera Raw plugin, which failed as before. I then restored the previous plugin, as before, but Bridge now fails to honor the preference, "Double-Click Edits Camera Raw Settings in Bridge" and instead always opens Photoshop.

    Thanks, Omke. I tried updating, then applying all the same fixes to the updated version. No change.
    I can attach a screenshot, but I must block out names and faces. All you'll see is my Bridge interface, not the faces in the portraits. Hope that helps.
    My specs:
    Bridge CS6 5.0.2.4
    Mac OS X 10.6.8
    16 GB RAM
    65 GB free disk space
    2 monitors, 2 graphics cards:
    ATI Radeon HD 4870
      Type:    GPU
      Bus:    PCIe
      Slot:    Slot-1
      PCIe Lane Width:    x16
      VRAM (Total):    512 MB
      Chipset Model:    NVIDIA GeForce GT 120
      Type:    GPU
      Bus:    PCIe
      Slot:    Slot-4
      PCIe Lane Width:    x4
      VRAM (Total):    512 MB

  • Lightroom 1.1 - Adobe Camera RAW 4.1 (Bridge, Photoshop CS3) problem

    Dear all,
    I am having some problems with the appearance of files developed in adobe lightroom 1.1 or in adobe camera raw 4.1 from e.g. bridge or photoshop cs3. When developing in lightroom the images look great, however when using acr 4.1 and the same xmp sidecar settings imported from lightroom, the image in acr looks very pale in comparison. For example when using the export into photoshop option in Lightroom, the image in PS3 looks very pale to the one in lightroom. The same problem persists with developing using ACR 4.1 from bridge. I have turned autotoning in ACR off. Also in the color management of PS CS3, the desaturate checkbox is UNchecked.
    I am using an icc profile for my 30" cinema display, calibrated with colory eyes pro and a spyder2.
    Has anybody had similar problems with ACR 4.1 or am I just doing something horribly simple wrong?
    Thanks for your help!
    Immanuel

    Thomas,
    thanks for your reply. In Mac OS X Preview the images look all good and very much like what I see in Lightroom. In any case not as pale or like with a slight white overcast to what I see when using ACR 4.1 from Bridge or Photoshop CS3. In PS color settings, preserving embedded profiles is checked. Yes, it seems to me as well that this is some color management issue. The 30" Cinema display was calibrated using Color Eyes Pro and Spyder2 to Gamma 2.2 and 6500 temp. However, even when reverting to the standard Apple color profile for the monitor, the problem persists.
    No luck so far...
    Immanuel

  • Bridge freezes when applying camera raw settings to large number of files

    I have a folder with 32,000 frames from a time-lapse project that I'm doing. I'd like to apply the same camera raw adjustments to all of these files, and so follow one of the two methods below - neither of which are working with such a large set of files:
    Method 1:
    Select all files, open in camera raw.
    Apply changes to the first image
    Select all images, then synchronize the changes to all other images.
    Unfortunately selecting "Open in Camera Raw..." just leaves bridge to hang. It's using a lot of memory and processor time, so I would assume it's working, but there's no progress bar or similar to indicate that it is.
    Method 2:
    Open first file in Camera Raw
    Apply all changes, and exit camera raw.
    Select all files in Bridge, right click on one and select "Develop Settings -> Previous Conversion"
    Unfortunately the final step again leaves bridge just thinking. I waited around an hour, closed bridge, but unfortunately when I opened it again there was no sign that it had copied the camera raw settings onto any of the other files. My computer's pretty slow (see below) but it should have written one xmp file in an hour.
    Question:
    Does anyone have any workarounds other than repeating the process 32 times for 1000 images at a time?
    System Info From Photoshop:
    Adobe Photoshop Version: 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00) x64
    Operating System: Windows Vista 64-bit
    Version: 6.0 Service Pack 2
    System architecture: AMD CPU Family:15, Model:15, Stepping:2 with MMX, SSE Integer, SSE FP, SSE2, SSE3
    Physical processor count: 1
    Processor speed: 1808 MHz
    Built-in memory: 8062 MB
    Free memory: 4508 MB
    Memory available to Photoshop: 7140 MB
    Memory used by Photoshop: 70 %
    Image tile size: 132K
    Image cache levels: 4
    OpenGL Drawing: Disabled.
    OpenGL Drawing Mode: Basic
    OpenGL Allow Normal Mode: False.
    OpenGL Allow Advanced Mode: False.
    OpenGL Allow Old GPUs: Not Detected.
    Video Card Vendor: NVIDIA Corporation
    Video Card Renderer: GeForce 6150SE nForce 430/PCI/SSE2
    Display: 1
    Display Bounds:=  top: 0, left: 0, bottom: 1024, right: 1280
    Video Card Number: 1
    Video Card: NVIDIA GeForce 6150SE nForce 430
    OpenCL Unavailable
    Driver Version: 8.17.12.7533
    Driver Date: 20110521050100.000000-000
    Video Card Driver: nvd3dumx.dll,nvd3dum
    Video Mode: 1280 x 1024 x 4294967296 colors
    Video Card Caption: NVIDIA GeForce 6150SE nForce 430
    Video Card Memory: 128 MB
    Video Rect Texture Size: 4096
    Serial number: Tryout Version
    Application folder: C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\
    Temporary file path: C:\Users\MARTIN~1\AppData\Local\Temp\
    Photoshop scratch has async I/O enabled
    Scratch volume(s):
      H:\, 279.5G, 50.4G free
      D:\, 149.0G, 108.1G free
      E:\, 74.5G, 46.1G free
    Required Plug-ins folder: C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\Required\
    Primary Plug-ins folder: C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\Plug-ins\
    Additional Plug-ins folder: not set
    Installed components:
       A3DLIBS.dll   A3DLIB Dynamic Link Library   9.2.0.112  
       ACE.dll   ACE 2012/01/18-15:07:40   66.492997   66.492997
       adbeape.dll   Adobe APE 2012/01/25-10:04:55   66.1025012   66.1025012
       AdobeLinguistic.dll   Adobe Linguisitc Library   6.0.0  
       AdobeOwl.dll   Adobe Owl 2012/02/09-16:00:02   4.0.93   66.496052
       AdobePDFL.dll   PDFL 2011/12/12-16:12:37   66.419471   66.419471
       AdobePIP.dll   Adobe Product Improvement Program   6.0.0.1642  
       AdobeXMP.dll   Adobe XMP Core 2012/02/06-14:56:27   66.145661   66.145661
       AdobeXMPFiles.dll   Adobe XMP Files 2012/02/06-14:56:27   66.145661   66.145661
       AdobeXMPScript.dll   Adobe XMP Script 2012/02/06-14:56:27   66.145661   66.145661
       adobe_caps.dll   Adobe CAPS   5,0,10,0  
       AGM.dll   AGM 2012/01/18-15:07:40   66.492997   66.492997
       ahclient.dll    AdobeHelp Dynamic Link Library   1,7,0,56  
       aif_core.dll   AIF   3.0   62.490293
       aif_ocl.dll   AIF   3.0   62.490293
       aif_ogl.dll   AIF   3.0   62.490293
       amtlib.dll   AMTLib (64 Bit)   6.0.0.75 (BuildVersion: 6.0; BuildDate: Mon Jan 16 2012 18:00:00)   1.000000
       ARE.dll   ARE 2012/01/18-15:07:40   66.492997   66.492997
       AXE8SharedExpat.dll   AXE8SharedExpat 2011/12/16-15:10:49   66.26830   66.26830
       AXEDOMCore.dll   AXEDOMCore 2011/12/16-15:10:49   66.26830   66.26830
       Bib.dll   BIB 2012/01/18-15:07:40   66.492997   66.492997
       BIBUtils.dll   BIBUtils 2012/01/18-15:07:40   66.492997   66.492997
       boost_date_time.dll   DVA Product   6.0.0  
       boost_signals.dll   DVA Product   6.0.0  
       boost_system.dll   DVA Product   6.0.0  
       boost_threads.dll   DVA Product   6.0.0  
       cg.dll   NVIDIA Cg Runtime   3.0.00007  
       cgGL.dll   NVIDIA Cg Runtime   3.0.00007  
       CIT.dll   Adobe CIT   2.0.5.19287   2.0.5.19287
       CoolType.dll   CoolType 2012/01/18-15:07:40   66.492997   66.492997
       data_flow.dll   AIF   3.0   62.490293
       dvaaudiodevice.dll   DVA Product   6.0.0  
       dvacore.dll   DVA Product   6.0.0  
       dvamarshal.dll   DVA Product   6.0.0  
       dvamediatypes.dll   DVA Product   6.0.0  
       dvaplayer.dll   DVA Product   6.0.0  
       dvatransport.dll   DVA Product   6.0.0  
       dvaunittesting.dll   DVA Product   6.0.0  
       dynamiclink.dll   DVA Product   6.0.0  
       ExtendScript.dll   ExtendScript 2011/12/14-15:08:46   66.490082   66.490082
       FileInfo.dll   Adobe XMP FileInfo 2012/01/17-15:11:19   66.145433   66.145433
       filter_graph.dll   AIF   3.0   62.490293
       hydra_filters.dll   AIF   3.0   62.490293
       icucnv40.dll   International Components for Unicode 2011/11/15-16:30:22    Build gtlib_3.0.16615  
       icudt40.dll   International Components for Unicode 2011/11/15-16:30:22    Build gtlib_3.0.16615  
       image_compiler.dll   AIF   3.0   62.490293
       image_flow.dll   AIF   3.0   62.490293
       image_runtime.dll   AIF   3.0   62.490293
       JP2KLib.dll   JP2KLib 2011/12/12-16:12:37   66.236923   66.236923
       libifcoremd.dll   Intel(r) Visual Fortran Compiler   10.0 (Update A)  
       libmmd.dll   Intel(r) C Compiler, Intel(r) C++ Compiler, Intel(r) Fortran Compiler   10.0  
       LogSession.dll   LogSession   2.1.2.1640  
       mediacoreif.dll   DVA Product   6.0.0  
       MPS.dll   MPS 2012/02/03-10:33:13   66.495174   66.495174
       msvcm80.dll   Microsoft® Visual Studio® 2005   8.00.50727.6195  
       msvcm90.dll   Microsoft® Visual Studio® 2008   9.00.30729.1  
       msvcp100.dll   Microsoft® Visual Studio® 2010   10.00.40219.1  
       msvcp80.dll   Microsoft® Visual Studio® 2005   8.00.50727.6195  
       msvcp90.dll   Microsoft® Visual Studio® 2008   9.00.30729.1  
       msvcr100.dll   Microsoft® Visual Studio® 2010   10.00.40219.1  
       msvcr80.dll   Microsoft® Visual Studio® 2005   8.00.50727.6195  
       msvcr90.dll   Microsoft® Visual Studio® 2008   9.00.30729.1  
       pdfsettings.dll   Adobe PDFSettings   1.04  
       Photoshop.dll   Adobe Photoshop CS6   CS6  
       Plugin.dll   Adobe Photoshop CS6   CS6  
       PlugPlug.dll   Adobe(R) CSXS PlugPlug Standard Dll (64 bit)   3.0.0.383  
       PSArt.dll   Adobe Photoshop CS6   CS6  
       PSViews.dll   Adobe Photoshop CS6   CS6  
       SCCore.dll   ScCore 2011/12/14-15:08:46   66.490082   66.490082
       ScriptUIFlex.dll   ScriptUIFlex 2011/12/14-15:08:46   66.490082   66.490082
       tbb.dll   Intel(R) Threading Building Blocks for Windows   3, 0, 2010, 0406  
       tbbmalloc.dll   Intel(R) Threading Building Blocks for Windows   3, 0, 2010, 0406  
       TfFontMgr.dll   FontMgr   9.3.0.113  
       TfKernel.dll   Kernel   9.3.0.113  
       TFKGEOM.dll   Kernel Geom   9.3.0.113  
       TFUGEOM.dll   Adobe, UGeom©   9.3.0.113  
       updaternotifications.dll   Adobe Updater Notifications Library   6.0.0.24 (BuildVersion: 1.0; BuildDate: BUILDDATETIME)   6.0.0.24
       WRServices.dll   WRServices Friday January 27 2012 13:22:12   Build 0.17112   0.17112
       wu3d.dll   U3D Writer   9.3.0.113  
    Required plug-ins:
       3D Studio 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Accented Edges 13.0
       Adaptive Wide Angle 13.0
       ADM 3.11x01
       Angled Strokes 13.0
       Average 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Bas Relief 13.0
       BMP 13.0
       Camera Raw 7.0
       Chalk & Charcoal 13.0
       Charcoal 13.0
       Chrome 13.0
       Cineon 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Clouds 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Collada 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Color Halftone 13.0
       Colored Pencil 13.0
       CompuServe GIF 13.0
       Conté Crayon 13.0
       Craquelure 13.0
       Crop and Straighten Photos 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Crop and Straighten Photos Filter 13.0
       Crosshatch 13.0
       Crystallize 13.0
       Cutout 13.0
       Dark Strokes 13.0
       De-Interlace 13.0
       Dicom 13.0
       Difference Clouds 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Diffuse Glow 13.0
       Displace 13.0
       Dry Brush 13.0
       Eazel Acquire 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Embed Watermark 4.0
       Entropy 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Extrude 13.0
       FastCore Routines 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Fibers 13.0
       Film Grain 13.0
       Filter Gallery 13.0
       Flash 3D 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Fresco 13.0
       Glass 13.0
       Glowing Edges 13.0
       Google Earth 4 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Grain 13.0
       Graphic Pen 13.0
       Halftone Pattern 13.0
       HDRMergeUI 13.0
       IFF Format 13.0
       Ink Outlines 13.0
       JPEG 2000 13.0
       Kurtosis 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Lens Blur 13.0
       Lens Correction 13.0
       Lens Flare 13.0
       Liquify 13.0
       Matlab Operation 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Maximum 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Mean 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Measurement Core 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Median 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Mezzotint 13.0
       Minimum 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       MMXCore Routines 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Mosaic Tiles 13.0
       Multiprocessor Support 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Neon Glow 13.0
       Note Paper 13.0
       NTSC Colors 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Ocean Ripple 13.0
       Oil Paint 13.0
       OpenEXR 13.0
       Paint Daubs 13.0
       Palette Knife 13.0
       Patchwork 13.0
       Paths to Illustrator 13.0
       PCX 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Photocopy 13.0
       Photoshop 3D Engine 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Picture Package Filter 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Pinch 13.0
       Pixar 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Plaster 13.0
       Plastic Wrap 13.0
       PNG 13.0
       Pointillize 13.0
       Polar Coordinates 13.0
       Portable Bit Map 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Poster Edges 13.0
       Radial Blur 13.0
       Radiance 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Range 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Read Watermark 4.0
       Reticulation 13.0
       Ripple 13.0
       Rough Pastels 13.0
       Save for Web 13.0
       ScriptingSupport 13.0
       Shear 13.0
       Skewness 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Smart Blur 13.0
       Smudge Stick 13.0
       Solarize 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Spatter 13.0
       Spherize 13.0
       Sponge 13.0
       Sprayed Strokes 13.0
       Stained Glass 13.0
       Stamp 13.0
       Standard Deviation 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Sumi-e 13.0
       Summation 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Targa 13.0
       Texturizer 13.0
       Tiles 13.0
       Torn Edges 13.0
       Twirl 13.0
       U3D 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Underpainting 13.0
       Vanishing Point 13.0
       Variance 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Variations 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Water Paper 13.0
       Watercolor 13.0
       Wave 13.0
       Wavefront|OBJ 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       WIA Support 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Wind 13.0
       Wireless Bitmap 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       ZigZag 13.0
    Optional and third party plug-ins: NONE
    Plug-ins that failed to load: NONE
    Flash:
       Mini Bridge
       Kuler
    Installed TWAIN devices: NONE

    The files are only 2MP each, and I have the same issue when I apply the changes to RAW files and JPG files. The error occurs though before any changes are applied, before the images would need to be recached, as when the error doesn't occur the dialogue box I mentioned pops up asking what to change.
    Your specs sound more then enough I would think. Do you have set the option to Write cache to folders when possible and if so could you uncheck that option?
    I don't have experience with this kind of numbers but I do dump the Bridge cache manually on a regular base (every new cycle it seems to be more stable so more interval in the periods of dumping cache) but my main folder contains usually around 6 to 7 K of DNG files from 21 MP dSLR. This starts caching without problems but takes a few hours before done.
    Can't use the option cache for folder due to a longstanding problem with error message to replace the CacheT file, hence my question about your setting.
    Also I have set the option to previews Always HQ and in the prefs have set the option to build monitor size previews.
    As said, don't know the large numbers but the 2 MP files are very small and it should be possible for Bridge I would think?
    Did you also try to create a new folder and place the files inthere. Or divide them in to three folders for testing?

  • How do I turn off ALL auto adjustments in Camera Raw?

    SUMMARY:
    I am simply trying to open my images in Camera Raw (version 8.6.0.254) via Bridge CC exactly how they were shot in camera, with no auto adjustments whatsoever.  I already have all of the auto boxes unchecked in the Camera Raw Preferences dialogue box under Default Image Settings.  I am shooting raw on a Sony A7r.
    MORE INFO:
    This discussion is not being created without prior research on how to solve it.  Hopefully there is a simple solution that I have overlooked and missed when looking for it.
    I shoot my raw images flat on purpose.  The in-camera saturation is turned down, along with a lot of the other picture profile settings in the camera. 
    I use Bridge CC to sort though my images and make selects.  In Bridge, I have "Prefer Embedded" selected for my thumbnails in order to stop the auto processing to happen to the thumbnails there. 
    The problem is, as soon as I open my raw images in Camera Raw from Bridge, the auto adjustments kick in and the saturation and exposure are automatically adjusted.  I can't figure out how to stop Camera Raw from making adjustments to my raw images.  As stated above, all of the auto check boxes are unchecked in the Camera Raw Preferences.
    When the "Command U" shortcut is pressed after an image is opened, it applies the auto settings, making it clear the Camera Raw thinks that nothing has been applied yet.  Toggling between "Camera Raw Defaults" and "Image Settings" in the side drop down menu does nothing either.
    Below are two screen shots.  One of how the thumbnail looks in Bridge, desaturated and flat.  The other is how the image opens in Camera Raw with no user adjustments what so ever.  You can see how the saturation and exposure have been adjusted:
    Bridge Preview - this is how the image was shot in camera.
    Camera Raw - Straight after opening the file with no user adjustments.  You can clearly see the dramatic auto adjustments, but all of the sliders are set to default.
    I would love to get some help with this, so I can see and work on my images as they were shot.  Im really hoping it is a stupid oversight on my part with an easy fix.  Thanks for the help.

    As was already said: the camera's interpretation of the raw data is just one interpretation, and not the same as Adobe's. Don't confuse it with "exactly how they were shot", as this doesn't apply when shooting Raw. Granted it IS the manufacturer's interpretation, but you wouldn't be shooting Raw and using Adobe Camera Raw if you thought the manufacturer was always right.
    One thing nobody has mentioned is Adobe's "baseline exposure" compensation factor. Camera Raw adjusts the default preview exposure by a factor of EV based on their measurements of the camera sensor. My present camera is boosted by 0.35EV and my last camera by 0.5EV. There is a way of determining this using EXIFTOOL, but I can't remember how to do it offhand. For the last few years, I have adjusted my own Camera Raw defaults by reversing this compensation, so it more closely matches the exposure I was expecting.
    EDIT: here's the procedure, if you're interested. Re: Baseline Exposure

  • +++ Adobe Camera Raw - Frequently Asked Questions +++

    Q: Is my camera supported by Adobe Camera Raw (ACR)?
    A: Here is the list of cameras officially supported by the current version of Adobe Camera Raw and Digital Negative (DNG) converter. The page also provides links to the current version of ACR and DNG converter for both Mac and Windows.
    Q: what version of Camera Raw should I install?
    A: Photoshop CS6: see first question.
    Photoshop CS5: Camera Raw 6.7 Win | Mac
    Photoshop CS 4: Camera Raw 5.7 Win | Mac
    Photoshop CS 3: Camera Raw 4.6 Win | Mac
    Photoshop CS 2: Camera Raw 3.7 Win | Mac
    Photoshop CS: Camera Raw 2.4 Win | Mac
    For Photoshop Elements, Windows:
    Photoshop Elements 10: (See first question)
    Photoshop Elements 9: Camera Raw 6.5
    Photoshop Elements 8: Camera Raw 6.2
    Photoshop Elements 7 and 6:  Camera Raw 5.6
    Photoshop Elements 5: Camera Raw 4.6
    Photoshop Elements 4: Camera Raw 3.7
    Photoshop Elements 3: Camera Raw 3.6
    For Photoshop Elements, Macintosh:
    Photoshop Elements 10: (See first question)
    Photoshop Elements 9: Camera Raw 6.5
    Photoshop Elements 8: Camera Raw 6.2
    Photoshop Elements 6: Camera Raw 5.6
    Photoshop Elements 4.0.1: Camera Raw 4.6 ( 4.1 under Mac OS 10.3)
    Photoshop Elements 3: Camera Raw 3.6
    Q: What version of Camera Raw started to support my camera?
    A: This page: http://www.adobe.com/go/kb407111 lists when support for the raw files of your camera was added in Camera Raw. If the version listed is higher than the one supported by your version of Camera Raw, you first need to convert the files to DNG using the latest version of the DNG converter in order to open them in Camera Raw.
    Q: I do not have the latest version of Photoshop, how can I open the Raw files from my new camera?
    A: Only the current version of Photoshop will receive ACR updates that add support for the latest cameras. However, you can download the latest version of the DNG converter, and use it to transform your raw files to the universal DNG format. Camera Raw 2.4 in Photoshop CS and all newer versions of Camera Raw compatible with your version of Photoshop will be able to open the DNG files. Photoshop 7 and ACR 1.0 do not support DNG, therefore you will need to upgrade to the latest version of Photoshop.
    Q: When will the new update of Adobe Camera Raw be released?
    A: Adobe cannot comment on unannounced products, however, it is expected that ACR and DNG converter will be simultaneously updated 3 or 4 times per year (i.e. every 3 or 4 months).
    Q: What does "Unofficial Support" for a camera mean?
    A: Unofficial support means that Adobe's Quality Engineering department has not tested the support to the degree that they want, and thus cannot guarantee the results. So we don't include the camera in our official lists, and don't provide any technical support. Unofficial support means "use at your own risk".
    Q: How do I know that Adobe Camera Raw is installed correctly?
    A: For Photoshop CS customers, the most efficient way to ensure that you have the latest Camera Raw update installed correctly is to choose the Updates option from the help menu. For Photoshop Elements customers the best way to verify that the Camera Raw plug-in is installed correctly is to make sure it appears (only once) in the "About Plug-in" menu (see: Photoshop menu on a Mac or Help menu on a PC). The correct version is displayed when you pick its name and see its about box. If "Camera Raw" is not in this list, you have not installed it correctly.
    Q: Why is the profile listed in the Calibration tab showing a version of Adobe Camera Raw that's older than I am using ?
    A: What you are seeing is normal, and is due to the fact that the built-in profile for your particular camera model hasn't changed between that version of Adobe Camera Raw and the version you're using now. If you see the profile listed as "beta" then your camera has only unofficial support.
    Q: Why is there more than one profile listed in the Calibration tab of Adobe Camera Raw?
    A: The built-in profile for your particular camera model has changed since it was first supported. The profile shown by default identifies the latest version of Adobe Camera Raw in which the profile was updated. Other profiles in the drop-down list identify those included with earlier versions of Adobe Camera Raw, and are available in case you want to maintain compatibility with earlier versions.
    Q: My camera is listed, but Photoshop cannot read its raw files.
    A: Download and install the most recent update to Adobe Camera Raw.
    Q: Where can I download the latest version of Adobe Camera Raw?
    A: Adobe Camera Raw for: Macintosh and Windows
    Q: I am trying to replace my existing ACR plug-in with a more recent version, but cannot find ACR in my Photoshop/Plug-in/File Formats folder. Where is it located now?
    A: As explained in the "Readme", which can be found on the ACR download page, the correct location is:
    Photoshop CS2
    Mac: /Library/Application Support/Adobe/Plug-ins/CS2/File Formats/
    Win: \Program Files\Common Files\Adobe\Plug-ins\CS2\File Formats\
    Photoshop CS3
    Mac: /Library/Application Support/Adobe/Plug-ins/CS3/File Formats/
    Win: \Program Files\Common Files\Adobe\Plug-ins\CS3\File Formats\
    Note that "Common Files" is localized in non-english versions of Windows.
    Q: Why do I only see a small generic icon in Adobe Bridge instead of a thumbnail when I browse the folder containing my RAW files?
    A: Bridge occasionally has difficulty with RAW files, but this is usually because the user has installed ACR into the wrong location or browsed the folder prior to installing the ACR plug-in that provides support for their particular camera model. The fix for this issue is usually to make absolutely sure that ACR is installed correctly, then purge the Bridge cache. If you're in the habit of using the Distributed cache (Bridge 1.x) it would be prudent to manually delete the cache files from the folder containing your RAW files.
    Q: Whenever I open an image in Adobe Camera Raw a small explanation mark within a yellow triangle appears in the upper right hand corner of the image.
    A: This symbol indicates that a high quality preview is being generated by Adobe Camera Raw. It should disappear after a couple of seconds.
    Q: How do I turn off Auto Adjustments in Adobe Camera Raw 3.x?
    A: Open Adobe Camera Raw. On the Mac press Cmd+U or on the PC Ctrl+U. This keystroke combination toggles Auto Adjustments On and Off. Alternatively, disable the Auto Adjustments setting from the fly-out menu adjacent to the Setting drop-down menu. If you want the default to be Off for Auto Adjustments simply choose "Save New Camera Raw Default" from the fly-out menu adjacent to the "Settings" drop-down menu then choose Done.
    Q: What about Adobe Camera Raw 3.7 and newer versions?
    A: Camera Raw 3.7 no longer supports per slider auto adjustments. One Auto control at the top of the panel now sets the Exposure, Shadows, Brightness, and Contrast sliders to their auto values. The Default control at the top of the panel sets these same four sliders to their default values. The keyboard shortcut for the Auto control is CMD/CTRL-U.
    The keyboard shortcut for the Default control is CMD/CTRL-R.
    Double clicking on a slider to set that single slider to its default value.
    Shift double clicking on a slider to set that single slider to its auto value.
    Q: Why do I get the the following message: "Unable to create an .xmp sidecar file. The image settings will instead be stored in the Adobe Camera Raw database."
    A: This message means that Adobe Camera Raw is unable to write to the XMP sidecar file. Either the media is read-only (e.g. a CD), or you don't have write access to the folder containing the image, or the existing XMP sidecar file is locked.
    Q: I cannot see all the tools and buttons of Adobe Camera Raw.
    A: Set your monitor resolution to the minimum required for Photoshop CS and higher, i.e. 1024x768.
    Q: Where can I obtain a listing of Adobe Camera Raw keyboard shortcuts and modifiers?
    A: On the Photoshop online help file.
    Q: When I open my Nikon NEF files, all I see is the simple version of the raw dialog.
    A: You are running Nikon's plug-in, not Adobe's. Delete from Photoshop's plug-in folder and all subfolders all copies of the "Nikon NEF plugin". Nikon automatically installs this plug-in in up to two places inside Photoshop's plug-in folder, and both must be deleted. Otherwise it overrides the Adobe plug-in. An alternative to the deletion is adding ~ in front of the Nikon plug-ins names.
    Q: I installed the update. I can now open my raw files, but I still cannot see thumbnails in the file browser.
    A: Purge the file browser cache for the problem folder. Tools > Cache > Purge cache for this folder.
    Q: Is it better to resize my images in Camera Raw, or in Photoshop?
    A: The resampling code is fairly similar to (but not exactly the same as) the "Bicubic Sharper" resampling in Photoshop CS and CS2. It does not make very much difference which stage you do the resampling in. The exception is non-square pixel cameras (Nikon D1x and Fuji S2 Pro), for which it is best to upsample one size step in Camera Raw if you need a larger image.
    Q: What are raw images, and how do they differ from JPEG ones?
    A: Read this whitepaper (1MB PDF) written by Bruce Fraser for a concise answer.

    You can check compatibility yourself:
    1.  Go to this page to see the different releases:  http://forums.adobe.com/thread/311515?tstart=0
    2.  Navigate into the download link for the appropriate version of Camera Raw.
    3.  Follow the link to the ReadMe (e.g., http://www.adobe.com/special/photoshop/camera_raw/Camera_Raw_4.6_ReadMe.pdf).
    4.  Look to see whether your camera is supported.
    5.  If your camera is NOT supported, you can use the free Adobe DNG converter to create .dng files that your Camera Raw will be able to open.
    Photoshop CS6 is anticipated to be out in a few months, and Camera Raw is supposed to have a whole new approach, so a lot of us are excited about anticipating that.
    -Noel

  • Camera raw in cs5/cs6

    Attemting to upgrade CS5/CS6 to use camera raw..keeps asking to close Adobe bridge CS5.exe. cant't find it to close..tried shutting down no help..

    Hi
    Certain applications run in he background and we cannot see them.
    To close such application
    For windows
    Right Click on the bottom taskbar and click Start Task manager.
    In Applications Tab look for Adobe Bridge If found Right Click on it and select End Task
    If Not then go to the second ab "Processes" and then look for Adobe Bride.exe when you get it, Right click and select End Process.
    For Mac:-
    In spotlight search for Activity monitor
    launch Activity Monitor and select Adobe Bridge and Click on Quit Process.
    Hope It Helps
    Thanks

  • How to tell: Which version of camera raw do I have?

    How to tell which version of camera raw I have? The only Google search I found answering this question refers to is 2 years old and seems to no longer apply. There is no File, Edit etc. menu on the new version of Camera Raw with (Photoshop/Bridge CS6). I do use Adobe Application Manager to do my updates telling me if a new version exists or not, nevertheless I would like to know.

    The F key works as described for me in CS6-ACR7.4 with ACR as the window with focus.  The same function is available using the double-arrow-window icon at the right of the Preview checkbox near the top right of the preview area. 
    When in full-screen mode there is no title bar, but when I press the F key or click the double-arrow, again, ACR becomes smaller and I can see the title bar that includes the ACR version and camera model.  This is on Windows7-64-bit on a 1600x1050 monitor.  Perhaps you’re ACR’s title bar is off the top of the screen so you can’t see it, or maybe ACR optimizes some things if you have a smallish display—do you?
    A plug-in is a program that interfaces with another program but is not independently runnable application, itself, bit is independently updatable, so in this instance, Photoshop doesn’t need to be downloaded and installed every time Adobe adds support for a few more cameras.

  • Camera Raw missing color channel

    I am using PSE9 for images from my Pentax K5. All updates have been installed.
    The raw files (PEF) have always worked in Camera Raw.
    Today however, I have opened some raw files and found that ACR is not showing the red channel in any images. The JPEG thumbnails in camera are displaying correctly.
    I have also opened the same files with Pentax Digital Camera Utility 4.40 and it displays the images correctly. This confirms the data has been recorded - thank goodness it is not a capture problem.
    Any suggestions and solutions as to what has happened to Camera Raw?
    Thanks to all who consider my problem.

    I have been using a Pantone Huey colorimeter for many years now with great effect.
    Unfortunately, this appears to be the source of my problems although I'm not sure why it would suddenly fail.
    When I factory reset the Huey, i.e. there is no calibrated monitor profile, it displays all images accurately. As soon as I calibrate the monitor, the colors display incorrectly again.
    The latest version of the Huey software was made back in the days of Windows XP. Therefore, there is no guarantee it will work with Windows 7 although it has been doing so for some time.
    It may be time to replace it with a Colormunki or Spyder4.
    If I go ahead, I'll post the outcome.

Maybe you are looking for

  • Can you run Lion os and Lion Server os on the same Mac mini?

    I'm a windows convert to Mac and I'm interested in running a standard Lion Client, but at the same time running Lion Server on the same Mac Mini (Server Edition).  My needs for the Lion Server OS is to handle e-mail, a Web Site, and file sharing betw

  • [OIM 9.1.0.2] Trusted Recon Workaround

    Hi all, IHAC that uses a GTC (Flat file) for trusted recon. The generated file for reconciliation brings entries of actives and inactives users (So, the expected result is User Creation, User Update and User Disabling). AFAIK, the User Definition Fie

  • My Apple TV is not Cooperating!

    Okay. I"ll try to give as much detail as possible. I have an iMac desktop which is using Mountain Lion. I use this as my "wifi hotspot" as well. I have it hard wried to the internet via ethernet cable. Then I use internet sharing to get my other devi

  • How to View PDF slideshow created with Adobe Photoshop Album?

    Many years ago during the Windows ME era, I created several short PDF slideshows with software (Adobe Photoshop Album) that included audio.  I saved them to a flashdrive.  I believe I used Adobe Reader 7 to play them years ago.  I am now running Wind

  • My iTunes wont connect to internet althought my internet is on

    My iTunes wont connect to internet althought my internet is on