Slightly OT - D300 / RAW / Colorprofiles

Hi
This is slightly OT ... but since I am an LR user and found that in this forum are a lot of experts ...
Does the selected Colorspace on my D300 (AdobeRGB or sRGB) have an influence if I shoot RAW?
It clearly has its influence if I set the camera to save jpeg's. I am just not sure what happens when I shoot RAW.
I tried to ask this question to the Nikon support. However, the response was not very satisfying. In fact, I asked myself if the person who answered the question really understand my question.
What are the suggestions? Always shoot AdobeRGB?
Thanks
Franz

>This means that I can produce pictures with a colorspace even wider than Adobe RGB.
Upon import to LR, the internal Melissa colorspace will be applied and upon export or
Just to make sure you understand. Lightroom renders the RAW data, using profiles that are internal to Lightroom and specific to your camera type and derived by shooting test charts under controlled conditions into the Melissa space. It does NOT apply the melissa space. Melissa is just its "working space." The profiles used represent the actual gamut of your camera and therefore you always get the widest gamut your camera can record. Furthermore, if you start playing with the sliders in Lightroom, you can easily push the colors even further out. The melissa space makes sure you can encompass it all.

Similar Messages

  • Lightroom doesn't recognize ACR 5.5 and my D300s RAW images

    Lightroom 2.4 does not recognize my Nikon D300s RAW images. I downloaded ACR 5.5 and after install both Bridge and Photoshop CS4 handle the D300s RAW images but my Lightroom 2.4 will not import them saying that it is a damaged or unrecognized file type. I have rebooted my entire Vista system and the problem persists. Any suggestions on how I might make Lightroom recognize ACR 5.5 and my D300s RAW images? Thanks in advance.
    Harry Campbell

    Harry Campbell wrote:
    Any suggestions on how I might make Lightroom recognize ACR 5.5 and my D300s RAW images?
    You don't want Camera Raw 5.5 (unless you want to use Photoshop CS4), you want the DNG Converter 5.5 which can convert the D300 raws into DNGs that are compatible with Lightroom 2.4. The next version of Lightroom (presumable 2.5) will have the support built in without needing the DNG Conversion...

  • Nikon D300 RAW and PSE 5.0 (Win)

    I have just started to process my Nikon D300 RAW images in my ACR / PSE 5.0 (Win) installation.  The RAW conversion works OK but when I want to remove the actual RAW files from my computer to store elsewhere, the computer will not let me move or delete them because "they are being used by another program or person."
    I have also noticed other strange goings on with these RAW files sometimes causing PSE to freeze.
    A quick check with the Process Explorer diagnostic tool from Microsoft indicates that something called Photoshop Elements File Agent.exe is still running in the background.  Is this a problem of the RAW files themselves or PSE?  Has any other user met this?  I have backed up "My Catalog", restarted my computer and uninstalled / reinstalled my PSE 5.0 to no avail.
    Any help gratefully received!

    Hi dj_paige
    1. Sorry but Windows XP (SP3).
    2. My current RAW workflow involves deleting the
    NEF RAW files from the PSE Organiser after
    conversion, copying / backing up the NEF files to
    an external HDD (which works OK) and then moving
    them (via standard Windows Explorer
    drag-and-drop) from the "Download" folder to an
    "Archive" folder on my computer internal hard
    drive.  I got the same error message when I tried
    to delete them from the "Download" folder.  My
    son, who works in computers, put me onto the
    Microsoft "Process Explorer" utility, to try and
    find which program was still using the files.
    3. I have had no problems with this workflow with
    my previous Nikon D70.  My suspicions about the
    D300 RAW files arose when the problem happened
    with the first one I tried to move / delete.
    4. The other "strange goings on" relate to trying
    to reopen one of the affected D300 NEF RAW files
    back into PSE Editor.  My PSE5 installation just
    stopped.  Today, after having reinstalled my PSE
    software, when trying to import one of the
    affected D300 NEF RAW files back into PSE
    Organiser, I got an error message relating to
    "Memory".  As this is all somewhat vague, I will
    try to recreate and note the error messages received.
    I look forward to any progress on this matter.
    Kind Regards
    Adrian Law

  • Bridge won 't recognize nikon d300 raw files

    What is it with Adobe?  Every time I attempt to use their product I hit another road block.  First it was using LR and PS on a high resolution screen.  Then I purchased their monthly subscription and got multiple versions of PS, not knowing which is the newest and correct version to use.  Is Photoshop CC or Photoshop CS5 the newest version. Now I can't get Bridge CS5 to recognize my Nikon D300 raw files.  Has Adobe lost it's footing?   I am extemely frustrated with Adobe products and apparently so are thousands, if not million of other customers

    Not possible in CS5
    Camera Raw plug-in | Supported cameras
    Camera Raw-compatible Adobe applications
    You can use the DNG converter to workaround this problem.

  • D300 RAW files converted to TIFF Anomally

    Ok....heres the thing! I recently spent 2 months in Argentina working on shootshorses.com. I used a Nikon D300 RAW (12mb) and downloaded everything (70 gig) to an 80 gig ipod. Aperture at this point could not read the nikon nef file so viewed them in nikon view nx, picked 50 or so I wanted, converted to 16 bit tiff on desktop and imported to Aperture. (now 77mb files)
    When upgrade for aperture 2 came out, installed and attached ipod and imported all the work. Started working on some of the same images in the new projects in order to uplaod more to web site. wanted to lift and stamp changes from tiff files and apply to freshly imported raw duplicate files then delete much larger tiff files. Point...the identical stamped changes make a completely different image.
    Checked the new raw file against the previous tiff file with no adjustments on either, on screen (apple 30 inch) and the tiff files blow the raw masters away for depth and sharpness. do not understand why as they are both the original Raw file from the ipod.....Question is, why is this? Suddenly the raw files really look digital and the tiff files have a depth that approach the work done on the kodak DCS pro.... and that is a bench mark!
    If anyone has any explanations it would be great. Many thanks
    A perplexed David Sinclair.

    AHHH... . amazed there is such a notable difference.... simple really. Only problem ,natural I suppose, Capture nx being same manufacturer, but makes me ask what else might be missed in the way of picture quality with Aperture. Many thanks for your answer

  • Aperture suddenly displaying "unsupported format" for Nikon D300s RAW files

    I am using Aperture 3.1.3 on my iMac 24 with Snow Leopard 10.6.8.   A couple of days ago I applied an update for Aperture RAW files that was in my update list, even though I don't use any of the cameras involved. 
    After that update Aperture gives me an "unsupported format" error on all my Nikon D300s RAW files. Every RAW file in the library.  I have never had a problem with this at any time over the last 2+ years of using Aperture.
    I have tried using time machine and rolling Aperture back to the end of July (my most recent backup) along with rolling back the RAW file plist. I then did a repair permissions, and reimported the photos after this.  I have rebooted numerous times.  All to no avail.  I have not yet tried a library rebuild that would be next if I must.
    I use a Referenced library, so I was able to check out individual RAW files with Adobe Camera RAW.   They open fine so there is no file corruption issue. 
    Any thoughts on what might be happening?  Any other file(s) associated with RAW conversion that I might need to roll back?   I do not see any mention of a problem like this when searching the web or the forum (although I may have missed something by not searching the correct terms).
    Any help would be greatly appreciated!

    The raw camera bundle is  /System/Library/CoreServices/RawCamera.bundle
    Go to /System/Library/CoreServices with the Finder, locate the the RawCamera.bundle package, select it and then do a File->Get Info on the package. You should have version 3.8.0, that is the latest and the one that you should have downloaded last week. If it is not 3.8.0 stop here and post back what version you do have, something isn't right.
    Assuming you have 3.8.0  use the Finder to navigate to /System/Library/CoreServices and then delete the RawCamera.bundle package. The Finder will ask you to authorize the delete.
    Then go to Digital Camera RAW Compatibility Update 3.7 download and install it. That will put you back to the last CameraRaw update before this one.
    See if that fixes your problem.
    As always when messing around with system files it is possible to mess things up so make sure you have a good backup before proceeding, And if any of these instructions make you nervous you might want to hold off doing them.
    good luck

  • D300 raw files in A2 - Colors are terrible?

    I've been using Nikon's Capture NX software to edit my D300 raw files since Aperture 1.5 didn't support D300 raw files. Tonight, I downloaded the trial version of Aperture 2.0 and imported some of my D300 raw files into A2. Side by side comparison is night and day - The colors in the NX software are brilliant, while the exact same raw file viewed in A2 is pathetic. I also noticed that you can do a lot more correcting of the files in NX than you can do in A2, like adjusting active-dlighting and built-in picture control (vivid, etc.)
    My first impression of A2 for editing D300 raw files is very poor. Capture NX does a much better job, probably because it's made by Nikon for a Nikon camera. A warning to A2 users - the raw images from a D300 are REALLY raw, they don't appear to include any in-camera corrections. Making these corrections in A2 is almost impossible because the Nikon-specific controls aren't in A2.
    Am I losing my mind or has anyone else noticed this?
    I still plan on using A1.5 or A2 to manage my libraries, but can't see any reason to use Aperture to edit my D300 raw files!

    NoMoreDells4me wrote:
    A warning to A2 users - the raw images from a D300 are REALLY raw, they don't appear to include any in-camera corrections.
    Ask anybody who knows anything about raw converters what the principal difference between Capture NX and other raw converters is and your observation will be first thing mentioned. This probably was not your intention, but by making the obvious appear sensational you created the impression that Aperture has been unduly hyped in an insincere manner. Which is not true since what you describe is one the first things people learn about raw converters and therefore cannot be hidden behind any hype.
    That does not change the fact that your observation is absolutely correct. Unfortunately, there is far no software available that would make switching between different raw conversion engines simple and easy (except Aperture with raw version 1.0, 1.1 and 2 but almost nobody would want to choose any of the older converter versions over the current one). So, you cannot have the raw conversion of Capture NX and the ease of use of Aperture in one simple package.

  • Why won't my D300 Raw pictures work properly in iPhoto 7 ?!?!?!?

    I am getting extremely frustrated with my Mac & iPhoto. Just got a Nikon D300 and was trying to upload my first shots in Tiger. No dice, Tiger doesn't support the D300 Raw format.
    OK, so I upgrade to Leopard. Nope, iPhoto 6 doesn't support the D300 Raw files either. I've been using iPhoto to organize and do light edits on my D40 shots, and everything was fine. So, I upgrade to iLife '08 and iPhoto 7 and now something is really screwed.
    The pictures seem to download fine off the camera but when I try to edit them or view them full screen I get. . .nothing. A blank screen. Anyone have any suggestions? I'm at my wits end. Thanks,

    Welcome to the Apple Discussions.
    Back Up and try rebuild the library: hold down the apple and option (or alt) keys while launching iPhoto. Use the resulting dialogue to rebuild.
    If that doesn't help:
    Start with the troubleshooting basics:
    1. Repair Permissions using Disk Utility
    2. Delete the com.apple.iPhoto.plist file from the HD/Users/ Your Name / library / preferences folder. You'll need to reset your User options afterwards.
    3. Create a new account (systempreferences -> accounts), create a new library there, import a few pics and see if the problem is repeated there. If it is, then a re-install of the app might be indicated. If it's not, then it's likely the app is okay and the problem is something in the main account.
    Regards
    TD

  • Lightroom5 not recognising Nikon D300s RAW files

    Hi,  I have recently upgraded to a new iMac running OSx Mavericks.  Lightroom 5 is not recognising my Nikon d300s raw files (NEF).  According to everything I have read on the net it should as Lightroom is brand new and up to date.
    Any advice.?
    Thanks

    They all show up in the preview view finder but then I get the error message "The following files were not imported because they could not be read" with a list of the files underneath.
    This is the first time I have used Lightroom 5 with the D300s... having just changed computers and upgraded from Lightroom 4. I have also now found out I can't download JPegs either!?!?!? You know that feeling when you think "if it isn't broken don't fix it" that's how I'm feeling right now about buying the new computer and software!!

  • Aperture 2 - Nikon D300S RAW

    I really love using Aperture 2 over Lightroom for a while... Just until I just bought a Nikon D300S. Apple doesn't support the Nikon D300S RAW format (yet). The people at Adobe responded far more quickly and already have a free update. Does anybody have an idea when Apple will release it's new RAW update including the Nikon D300S? Is there a workaround in the mean time to be able to work with the RAW format in Aperture (not switching to LR)?

    The D300s was released in September 2009. Now we have December and there is still no support for the Nikon D300s!!
    I love Aperture, I am a Certified Aperture Pro. After four months of non-supporting my RAW-Files I am going to switch to Lightroom... what a pity!
    I hope that no one of Apple's staff wonders why people uses LR more often....
    Goodbye Aperture, hello Lightroom!
    It's really, really sad.
    Greets,
    Holger
    Message was edited by: konzept360.com

  • Nikon Df RAW (NEF) files will not load previews into Lightroom 5.4. Nikon d300s RAW (NEF) files load just fine. Df files do not.

    Nikon Df RAW (NEF) files will not load previews into Lightroom 5.4. Nikon d300s RAW (NEF) files load just fine. Df files do not.

    Thank you for your response.
    I have loaded directly into Lightroom using import and via Nikon Capture NX2. RAW files display fine in Capture.
    In Lightroom, blank previews are created for each available image, with the message "Preview unavailable for this file."

  • Aperture Nikon D300 RAW: 4304×2852 instead of 4288 × 2848?

    Aperture 2.0 seems to squeeze extra pixels out of my Nikon D300 RAW files compared to Capture NX.
    This messes up Apertures "+auto detection & import+" of RAW+JPG sets when you generate the JPGs using Capture NX. No problem when using the JPGs the camera created: Aperture silently imports those JPGs alongside the RAWs so you can "Generate Version from Master JPG"
    Where do these extra pixels come from, and is this "feature" unique to decoding of D300 files?

    Well both a pain and a blessing
    I used to shoot RAW+JPG and whenever I felt my JPGs were good I just used 'New Version From Master JPG' and select that one as the pick.
    I just imported a bunch of RAWs from a directory in which I also placed the batched Capture JPGs and Aperture was able to 'auto-stack' them by 2. A pitty the order of the first image isn't always the JPG...
    I'm not sure which RAW+JPG workflow is better at the moment

  • Lightroom 2.2 D300 Raw file

    Hi,
    Currently I have a Pentium M 1.6Ghz and it takes to render a full size
    preview of a single photo
    20 Sec for D300 Raw
    10 Sec for D300 Jpg
    4 Sec for F31fd
    I I upgrate to a Core 2 Due (low specs) 1.6/2 Ghz, may I expect a big improvement?
    As of today I really can screen my picture at full size for correct focus, it takes too long.
    Thanks

    I have a dual core AMD processor running at 2.8 GHz, and I'm seeing around 7.5 to 8.0 seconds per 1:1 preview of .nef files from a D300. Lightroom uses all cores to produce previews, so doubling your core count ought to halve your time, all other things being equal.
    If you request 1:1 previews to be built on import, you can get the import started (even with your current machine) and go find something else to do while the previews get built. After that, you ought to be able to view at full size without undue delays.
    Hal

  • Aperture 2.0 Corrupt export on D300 RAW image?

    I've been experimenting with Aperture 2.0 to see if I want to upgrade my 1.5.2 install, and have run into a problem where an image looks just fine in Aperture but when I try exporting it (JPEG or TIFF, 8 or 16 bit) there's terrible banding and corruption in the background.
    http://www.cheeseplant.org/~daniel/images/BadApertureExport.jpg
    Has anyone else had a chance to play around with adjustments on D300 raw images and have they run into anything like this?

    I was having the same problem, this was my older post:
    I have been seeing many artifacts after starting to export from Aperture 2.0,
    Camera used canon 5D
    1. I see color pixel that are not visible in raw, or processes with Capture one
    http://boinghost.com/aperture/pixel.jpg
    2. A banding problem separated the picture in 3 sections..
    http://boinghost.com/aperture/banding.jpg
    has anybody a solution?
    I don't see it with in the application, i think that is a bug that need fixing.
    it should not show in the exported image if it doesn't show in Aperture, even if you take the recovery slider to maximum.

  • D300 RAW conversion issue

    I was messing around with the D300 in ISO 6400 recently and noticed something strange in a couple of the images. An example is shown below. The two images below were generated from the same D300 RAW file.
    Both the RAW view and JPG export from Aperture2 show a strange extreme "noise" patterns in the lower 3rd of the frame. When loading the same RAW file in CaptureNX, the RAW preview and JPG generation show a relatively clean and normal lower 3rd.
    Has anyone experienced this? I'm not too concerned as I can of course use NX for these instances - it does raise concerns though on the quality of the D300 RAW converter in Aperture. Additionally, Mac OS X 10.5.2 Finder Quick Preview shows the same "normal" clean-ish (for ISO 6400 anyway!).
    Aperture jpg from D300 RAW at ISO 6400:
    http://farm3.static.flickr.com/2113/2280589984_f9d407cb90.jpg
    CaptureNX jpg from D300 RAW at ISO 6400:
    http://farm3.static.flickr.com/2085/2280589988_cdc00d7593.jpg

    Thanks for the info, ssprengel.
    That's a shame.
    Yes it's really unusable, which is a killer as the camera is great. 
    I hear what you're saying but for me I can't let my RAW-processing software dictate what camera I can/can't have...particularly after doing lots of research (on which camera to get) and settling on the X-T1.
    During my research I did stumble upon this issue, but really though (more like 'hoped...with all my being') that the 5.4 updates had fixed it.
    Perhaps if I'd seen it with my own eyes first I might've reconsidered the purchase of the X-T1.
    Oh well, where there's a will there's a way!
    I guess for now I'll see what other options I have on Windows. With a quick google I think my current options are Photo Ninja and Capture one, so I'll hope they have trial version to try out.

Maybe you are looking for