RAW DPI settings going in reverse?

Hello.
I have Bridge and P/S CS3 with the most recent RAW download. If I take a 12MP image into RAW with settings: Abobe 1998, 8 bit, 12MP, 250 DPI. Then open it into P/S, I get an image size of around 17 by 11 inches...
When I change the DPI in RAW again to say 100 DPI, I open in P/S again and I get a much larger image size.
Shouldn't it be the other way around?!

Less PPI (there are no dots in Photoshop) = larger image dimension...more PPI = smaller image dimensions, if you think about it, it will make sense to you. Camera Raw is only assigning the PPI for Photoshop, it's not resampling unless you tell it to.

Similar Messages

  • I use a two button mouse with my Mac Book Pro.  It works fine, but after installing Lion, the mouse wheel goes in reverse of what it did (rolling the wheel towards your palm goes up not down the page).  Anyone know how to fix this?

    I use a two button mouse with my Mac Book Pro.  It works fine, but after installing Lion, the mouse wheel goes in reverse of what it did (rolling the wheel towards your palm goes up not down the page).  Anyone know how to fix this?

    First sentence in OPs question:
    I use a two button mouse with my Mac Book Pro
    I guess the track pad settings would look similar to my screen shot?
    Regards,
    Colin R.

  • "Unable to save the raw conversion settings. There was a write permission error."

    I just built a new workstation for processing photos using PS CS5. I use external drives to store my images as I find it easier for backing up as well as for when I want use my laptop for sorting, etc.. I copied over all my old "Collection" files, and of course, had to "fix" them once on the new machine. Once pointed in the right direction, the collections all fill out correctly.
    When I go to process a collection though, I encounter an odd problem I can't seem to sort out. I can delete files, rename files, copy/paste to the external drives, etc.. What I can't seem to do is add Labels, Ratings, or modify RAW settings. I mean, I can use ACR to make adjustments, I just can't seem to save them.
    The system just ignores label, rating commands completely. When I try to save an ACR adjustment I get this error. "Unable to save the raw conversion settings. There was a write permission error."
    The files are NOT write protected. I'm set up as the owner of my workstation, with complete control of the system. I can't seem to find any useful information about this error because the "write permission error" seems to only be happening on installs, so that's all I can find help for.
    My system:
    Intel Core i7 970@ 3.20GHZ
    24.0 GB RAM
    64-bit OS - Windows 7 Pro
    DX58S02 Motherboard
    NVIDIA GeForce GTX 580

    Thanks for replying. I've been going crazy trying to fix this.
    To answer your first question; I use sidecar XMP files. If everything from my archive was shot in RAW I'd try converting to DNG and see if embedding the changes directly in a file worked. Unfortunately, a lot of my old stuff was shot in JPG, so sidecars seems to be the best choice.
    When I add labels, ratings, as well as change RAW settings on files I place on my workstations HD everything works. It's only when I try to do these things with the same files on removable drives that I run into trouble. The drives I use are Transcend 640GB StoreJet 25ms connected via USB.
    I don't think it's a UAC problem. At least, to my understanding, doesn't that control how your machine alerts you to program changes? I looked into how to change ownership, and did so, but that didn't work. Here's a link to what I mean: http://www.addictivetips.com/windows-tips/windows-7-access-denied-permission-ownership/
    I'm stumped. I also hate the idea that I'll have to go through various folders to find images from already created collections, copy them to a new folder on my HD and then work on them. Then I'll have to put them all back... ugghhhh

  • Where are the RAW adjustment settings kept?

    I have imported my pictures (a complete folder) into Lightroom, made all the adjustments, exported the jpegs... great! Now I want to backup my folder and the RAW adjustment settings I have made.
    But where are all the adjustment settings kept, and can I backup those settings for later retrieval with my original RAW files?
    Thanks for all your advice.

    > That's the point, my folders have no .xmp files any where! I did a search on my only drive c: and there is no .xmp files at all. But I can assure you that all my 400 or so RAW files retained all the adjustments in Lightroom. What's going on?
    <br />
    <br />Your adjusted files may be residing elsewhere. So, select one RAW image on which you are sure you've edited, and then reveal it in the Finder or the Windows equivalent. Look around there; there certainly should be .xmp files if you've run Export xmp on that folder.
    <br />
    <br />Another neat way, for me, anyway, is to Convert all the edited RAW files to DNG; then they'll contain the edits within the file, as currently to JPEGs, TIFFs, and PSD files.
    <br />
    <br />
    <span style="color: rgb(102, 0, 204);">John "McPhotoman"</span>
    <font br="" /></font> color="#800000" size="2"&gt;~~ John McWilliams
    <br />
    <br />
    <br />
    <br />MacBookPro 2 Ghz Intel Core Duo, G-5 Dual 1.8;
    <br />Canon DSLRs

  • Xorg DPI settings won't save

    Following the wiki, I decided to check if my DPI settings were correct, and fix them if they were not. These are the results I'm getting (full commands typed out for clarity):
    First, without any configuration, the screen settings:
    $ xinit /usr/bin/awesome -- :0
    $ xdpyinfo | grep -B2 resolution
    screen #0:
    dimensions: 1920x1080 pixels (508x285 millimeters)
    resolution: 96x96 dots per inch
    This is wrong. Altering the commandline -dpi parameter results in the following:
    xinit /usr/bin/awesome -- :0 -dpi 165
    $ xdpyinfo | grep -B2 resolution
    screen #0:
    dimensions: 1920x1080 pixels (295x166 millimeters)
    resolution: 165x165 dots per inch
    This is right. For a more permanent solution one might alter xorg.conf settings, which I did:
    /etc/X11/xorg.conf.d/10-dpi.conf
    Section "Monitor"
    Identifier "Monitor0"
    DisplaySize 295 166
    EndSection
    However, it results the default 96x96 DPI, as you saw in the first code snippet. Furthermore, directly editing the DPI in xorg.conf such as this:
    /etc/X11/xorg.conf.d/10-dpi.conf
    Section "Monitor"
    Identifier "Monitor0"
    Option "DPI" "166 x 166"
    EndSection
    again results in the default 96x96 DPI.
    Interestingly enough, if I deliberately put some bogus values into the config, Xorg complains about it and will not start up. So the config file IS being read, and there are apparently no errors in it. As well the other .conf files in the /etc/X11/xorg.conf.d/ directory is working (such as fonts.conf, which I am using to include /usr/share/font directories).
    Why is the config not applying?
    Last edited by Whef (2012-09-04 07:10:13)

    hellomynameisphil wrote:
    I think you can put it in .Xdefaults or .Xresources:
    Xft.dpi: 166
    If this does infact work, then it didn't for me.
    Lone_Wolf wrote:
    I looked this up also, and found that Xorg0.log gives different results then xdpyinfo :
    $ xdpyinfo | grep -B2 resolution
    screen #0:
    dimensions: 1920x1200 pixels (508x317 millimeters)
    resolution: 96x96 dots per inch
    Xorg.0.log
    [7232.286] (**) RADEON(0): Display dimensions: (520, 320) mm
    [ 7232.286] (**) RADEON(0): DPI set to (93, 95)
    No 90-monitor.conf file present, and Xorg.0.log only has 2 other lines with dpi , both about font paths.
    So the question seems to be : which is right, Xorg.0.log or xdpyinfo ?
    Interesting... The xdpyinfo one is correct (I can tell because of text sizes). However, when starting X without the -dpi argument it shows this:
    [ 2194.180] (**) intel(0): DPI set to (174,171)
    Not only is this the wrong DPI for my monitor, but it isn't the actual DPI that X is using. xdpyinfo correctly displays that the DPI is 96x96. However, if I launch X with the -dpi argument then Xorg.0.log will report the correct DPI (what I set it to). I really have no idea what's going on. I just wish my DPI settings would save!
    Last edited by Whef (2012-09-05 08:47:33)

  • Recommended DPI settings

    Looking for some advice on DPI settings when exporting Nikon D200 RAW images to print photos, books, converting from RAW to JPEG etc.
    At what point does it make no difference except file size?
    Thanks.
    iMac Intel Core Duo 20", 2 GB RAM   Mac OS X (10.4.4)   Nikon Coolscan V ED, Nikon D200, Iomega MiniMax Drives

    DPI is used only to determine how large to print an image. In other words, if you have an image that's 3000 pixels wide and you set it to print at 300 dots per inch, it will print at 10 inches wide. If you have an image that's only 300 pixels wide and you print it at 300 dpi, it would only be 1 inch wide.
    That is the only use of DPI. DPI does not determine an image's digital resolution. The number of pixels determines the image's resolution.
    Generally speaking, if you're printing an image on paper you're better off with the largest image you can get.
    At what point does it make no difference except file
    size?
    When you are exporting an image to be used in a digital presentation, such as on a web page or on TV, that's when you don't need to worry about DPI. That's when what only matters is the number of pixels in the image.
    For example, if you export that image that's 300 pixels wide to display on a computer screen that's 1280 pixels wide, the image will take up about a quarter of the screen. And it doesn't matter at all what DPI setting you might have set.
    You can download a PDF file of a chapter from one of my old Photoshop books that explains digital imaging resolution at http://www.seekpeace.com/viz/res/Resolution.pdf.

  • LR 5.5 - Camera RAW Cache settings reset non-stop

    Lightroom doesn’t remember the folder path in Camera RAW Cache Settings section in File Handling tab in Preferences window. I want to set my own folder Camera Raw Cache and its maximum size but every time Lightroom sets default path (C:/Users/Name/AppData/Local/Adobe/CameraRaw/Cache/) and also maximum size as 1GB. When I set all the parameters Camera RAW Cache and click OK or switch between the tabs in Lightroom preferences window or restart Lightroom and I return to the File Handling tab all the data is reset to default. The same happens when I want to change the parameters Camera RAW Cache from Adobe Bridge and Photoshop.
    Second question:
    When I use DNG file format with Embed Fast Load Data option in the folder Camera RAW Cache the “DAT” files doesn’t appear. Is it connected with the use of Embed Fast Load Data option? When I use the original NEF files from my Nikon “DAT” files appear.
    [Win 7 64-bit, LR 5.5, Web&Design CS6]

    I have no trouble placing my Camera Raw cache where I want to put it. Perhaps deleting your Preferences file would help with that problem.
    Yes, if you embed fast-load data in your DNGs, LR will use that instead of the CR Cache.
    Hal

  • PS CS6 / Bridge / ACR 8.5 - Camera RAW Cache settings reset non-stop

    Adobe Bridge/Photoshop doesn’t remember the folder path in Camera RAW Cache Settings in Camera RAW Preferences window. Every time when I want to set my own folder Camera Raw Cache and its maximum size, I click OK and return to Camera RAW Preferences, I see default path (C:/Users/Name/AppData/Local/Adobe/CameraRaw/Cache/) and maximum size as 1GB.
    [Win 7 64-bit, LR 5.5, Web&Design CS6]

    Problem is solved!
    I delete folder "C:\Users\USERNAME\AppData\Roaming\Adobe\CameraRaw\". Then I start Lightroom and I pick my own folder in Camera Raw Cache Settings, set 20GB size and click OK. Now everything works fine. Bridge and PS also fine.

  • Camera Raw Workflow Settings - where?

    Hi!
    In Bruce Fraser's and Jeff Schewe's "Camera Raw with .. CS3", p 134, a dialogue box Workflow Options is shown. Likewise, Photoshop CS3 Help > Camera Raw > CR Settings > CR Workflow Options promises "You can see and change these Workflow settings at the bottom of the Camera Raw dialog box."
    I wonder which dialog box the text is referring to. I can not see the Workflow dialog box at the bottom of the dialog box shown in Bridge > Camera Raw Preferences, nor in Bridge > Preferences, nor in Photoshop > Preferences, nor in Photoshop > Edit > Color Settings.
    All the entrances on the Adobe site only lead me to the same PS Help document.
    It would indeed be useful to be able to specify e.g the bit depth as a default, because the PS default seems to be 8 bit (PS > Image > Mode), so I have to remember to set it to 16 for every single image anew.
    I use Mac 10.4.11 on a MacBook Pro, 2GHz processor, 2GB RAM , PS CS3, ACR 4.5
    Thanks for help! Hening.

    >Well, the save button is alongside the hyperlink (to it's left) and that opens a fresh panel to allow various options to be set, so I find the explanation advanced by the ACR Team bit hard to understand.
    You running a display at 1024 x 768? Because that's Camera Raw's real estate minimum that HAS to be supported...so what you can do in a dialog whose display ends up at a much higher resolution is severely limited because of the minimum requirements. That's why...

  • Do you change the default RAW conversion settings?

    I have used Sony (and formerly used Panasonic MFT) cameras (a900, a850) for two or three years and never had any reason to change the default RAW conversion settings.  Five weeks ago I started using Sony's new a77, and for the first time am not satisfied with Aperture's default RAW conversion.  (I recalibrated all my monitors -- twice -- thinking that something in my color workflow had got busted.)  The default a77 RAW file conversion results in an overly-saturated, "Disneyfied" picture.  I have found that by sliding "Boost" almost to zero, and cutting "Hue Boost" by half, I end up with a much more life-like, atmospheric, picture -- and one that closely matches the default rendering of RAW files from the a850 and a900.
    1.  Do you change the default RAW conversions settings?  Why?
    2.  To what units, specifically, do the scales of these controls refer?
    3.  It seems that Hue Boost provides a range of settings that corresponds to the print settings "Perceptual" (= zero hue boost) to "Relative Colorimetric" (= full hue boost); does that make sense?
    The User Manual, as usual, provides a solid concise explanation of the RAW Fine Tuning Brick.
    Any experience you can share is appreciated.  Thanks.
    (Added:
    (It seems conceptually wrong to me to have these controls be part of the RAW converter.  Are there other adjustments in Aperture that do the same thing?)
    --Kirby.
    Message was edited by: Kirby Krieger

    William -- many thanks for your help.  I will almost certainly change the default for my a77 (as well as for the Nex-7 I used for a week).
    Are there is any other adjustments mathematically similar to the "Boost" or "Hue Boost" sliders in the RAW Fine Tuning Brick?  I ask for two reasons:
    - Mostly I'm just trying to figure out what they do, and strengthen with knowledge my quiver of Aperture effects.  According the the User Manual, they change the overall contrast, and the amount to which the hue is changed as the overall contrast is increased. 
    - In practice, it makes sense to me to have the RAW conversion produce the "flattest", least "effected" image possible -- to leave _aesthetic_ adjustments to me.  I don't want to use the RAW Fine Tuning controls as part of my workflow; I want to know how to get the same increase in contrast and control of hues using other adjustments (that, specifically, don't require de-mosaic'ing).  Apple seems to indicate that the use of the RAW Fine Tuning controls may be the best approach:
    For images that consist of saturated primary and secondary colors, such as an image of flowers in a lush garden, shifting the hues to their true values has a desirable visual effect. However, this is not visually desirable for images containing skin tones.
    The implication is spelled out in the sentencesthat follow: use the max setting for flowers, and the minimum setting for portraits.  Isn't it odd that this recommendation is left to the RAW converter, and is buried deep in the User Manual?

  • What camera raw default settings would you use for the Canon 5D Mark 3. I have PS CS6.  Thank you.

    What camera raw default settings would you use for the Canon 5D Mark 3. I have PS CS6.  Thank you.

    Really, this is a question you should be asking yourself...
    What do you shoot? Makes a difference...
    Typical ISO that you shoot? Makes a difference...
    Shooting for clients or yourself? Makes a difference...
    Look, there is no magic bullet...the ACR/LR "Default" should only be changed for those adjustments you make 70-90% of the time and sould not be confused with image by image adjustments...
    So, as asked, your question can not really be answered other than to say, use a default that suits you.

  • CRSS : Camera Raw Saved Settings - documentation ??

    Hello,
    I generated a DNG from Lightroom, and I get a XML tree using a crss (Camera Raw Saved Settings) schema.
    Where could I get about this ?? I didn't find aything with Google.
    Thanks.

    Panoholic wrote:
    I guess the meaning of "open standard" is, that it is open to anyone to write the documentation.
    Well, considering that "Camera Raw Saved Settings" are not specifically a function of DNG I think that comment is inaccurate and unfair. XMP allows new and custom name spaces and fields as part of the XMP specification (which is not directly tied to the DNG spec). The fact that Adobe has chosen to extend (XMP = EXtensible Metadata Platform) the XMP fields to include CRSS (Camera Raw/Lightroom "Snapshots") is more a proof oc concept of the usefulness of XMP metadata and less am indictment of DNG's "openess".
    Snapshots in ACR/LR are proprietary and thus are prolly intentionally "undocumented", don't ya think?
    If you want to see what _IS_ stored in DNG/XMP, the "crs schema" should be able to enlighten you...

  • Best in Camera Raw Image settings

    Not that the camera model matters, but is there any unique in camera RAW image settings that will improve how the RAW file is interpreted by Aperture?
    For example, I shoot with a Nikon D200. I can customize how the camera "Optimizes" the RAW image by adjusting:
    1. Image Sharpening
    2. Tone Compensation
    3. Color Mode
    4. Saturation
    5. Hue
    Does Aperture recognize any of these adjustments or does it just look at the actual RAW data and compensate just for what it thinks the white balance should be?

    You don't need to do anything "in camera." Most (if not all) of those settings are ignored by Aperture, because they don't really apply to the RAW files (they are processing settings, and RAW files are effectively "negatives.").
    So color space, sharpening, saturation, etc... doesn't matter what they're set to.
    Of course, color space affects how the images are named on camera... the Adobe RGB spec mandates an underscore as first character, e.g. MG1005.jpg versis IMG_1005.jpg.

  • Server 2008 SP2 DPI settings

    We are running a Windows 2008 Standard SP2 32-bit terminal server. One of the users would like to have the option to change the DPI settings under their session. I found a MS hotfix, but it does not apply to this version (http://support.microsoft.com/kb/2726399)
    Does anyone know if there is another hotfix or update planned to address this? We have changed the resolution settings on the client computers, but was curious if anyone had any additional information on whether this may be
    addressed or not. Thanks.

    Hi,
    I would like to check if you need further assistance.
    Thanks.
    Jeremy Wu
    TechNet Community Support

  • Unable to save raw conversion settings

    CS5 user.I 've been using Bridge for a while and never had this problem before.  Why am I getting the following message. "Unable to save raw conversion settings. There was an error parsing the files."

    Storing on external drive will not corrupt them. 
    However, it can cause permission problems in writing data.  A workaround is the right click on Bridge Icon and choose "Run as Administrator"
    Also, if you access files on network there can be permission problems.

Maybe you are looking for