Lightroom versus Aperture: Nikon 5700

I'm using both an Olympus E-500 and a Nikon 5700.
iPhoto and Aperture will not "see" my 5700's NEF files; but Lightroom handles them just fine.
What gives?
I hear the OS being blamed but that doesn't explain why Lightroom works fine with the Nikon RAW files.

I'd think your Nikon 5700 is not among the list of supported cameras for Aperture, at least where its NEF files are concerned.
Lightroom is a software that's different from Aperture. It also works differently. It does not use the same software pieces for processing RAW files as iPhoto and Aperture. These software pieces that Aperture and iPhoto use (and share) reside within the system. The software piece that Lightroom uses resides within Lightroom (and again, in a slightly different form, in Photoshop). The Apple provided software pieces don't (yet) know how to handle the 5700's NEF files, while the Lightroom software piece know that.
And that explains exactly why Lightroom works with the Nikon's RAW files while Aperture doesn't.
Cheers,
k.

Similar Messages

Nikon 5700 NEF and DNG

Does iPhoto '08 import DNG photos?
I've tried converting some Nikon 5700 NEFs converted to dng by either Lightroom or Adobe Converter, but get the unsupported format dialog. Odd that it attempts to import and then warns you, rather than telling you right away that it won't accept the files.

kenneth,
i think the problem is not all with aperture but in Mac OS X. try opening the nikon 5700 nef file with Preview and you'll see. my brother has a nikon 5700 and he had no problems opening nikon 5700 nef file on mac os x prior to 10.4.(?) running on a third-party upgraded powerbook (the wall street). he finally bought a new mac and this is when all his nikon 5700 nef files became incompatible. so something happened during the series of Mac OS X upates that broke the support for the nikon 5700 nef file.
i suggest that you also submit a feedback requesting support for the nikon 5700 nef file.
ps: they do listen, just be patient.

Nikon 5700 NEF unsupported format

Haven't found a solution in 1.1 for my problem getting NEF files from my 5700 into Aperture. Tried importing into Lightroom with no metadata and then importing from the LIghtroom library. No luck. Someone must have solved this. I thought 1.1 would but it obviously hasn't. Any workarounds. I did read a thread about exporting from Bridge as a 16 bit TIFF and then bringing that into Aperture. What do you pro's think?

kenneth,
i think the problem is not all with aperture but in Mac OS X. try opening the nikon 5700 nef file with Preview and you'll see. my brother has a nikon 5700 and he had no problems opening nikon 5700 nef file on mac os x prior to 10.4.(?) running on a third-party upgraded powerbook (the wall street). he finally bought a new mac and this is when all his nikon 5700 nef files became incompatible. so something happened during the series of Mac OS X upates that broke the support for the nikon 5700 nef file.
i suggest that you also submit a feedback requesting support for the nikon 5700 nef file.
ps: they do listen, just be patient.

Nikon 5700 Puzzle

I cannot understand why the Nikon 5700 NEF fiiles are not importable to iPhoto or Aperture, but on the same machine are importable with Lightroom. People suggest that it's the OS but obviously it's the same OS.

Because it is the OS...
iPhoto, Preview and Aperture all use the RAW-conversion engine that is built in to the OS, obviously with different levels of control. That's why all three apps support exactly the same RAW files.
LightRoom (being cross-platform) doesn't.
Have you asked for support for the 5700 on the feedback page?
http://www.apple.com/feedback/aperture.html
Ian

Does Adobe photoshop lightroom 5 support Nikon D 600 NEF files

Does Adobe photoshop lightroom 5 support Nikon D 6oo NEF files ?

birdlife wrote:
Yes Im am shooting in RAW and jpeg
On 21 Oct 2014 15:59, "Benjamin Root Photography" <[email protected]>
Sorry to butt in. We used to double-shoot, too, but after a couple of years we discovered it was unnecessary when using both Aperture and Lightroom. Your workflow will be different from ours of course, and one does what one needs to do. We found the duplicate images were tedious and, even though they were quite small compared to the NEFs, they occupied a lot of space that was needlessly redundant. The Mac (or PC) is so instantly responsive that the NEF is offered up quickly so the jpg has no real purpose.

Nikon 5700

Hi
Most of my photography is done on my Nikon D2X, but sometimes I still use my Nikon 5700. Is there anyway I can import the RAW NEF files from this camera into Aperture? I have tried direct import and also converting them to Adobe DNG filoes but neither method works.

kenneth,
i think the problem is not all with aperture but in Mac OS X. try opening the nikon 5700 nef file with Preview and you'll see. my brother has a nikon 5700 and he had no problems opening nikon 5700 nef file on mac os x prior to 10.4.(?) running on a third-party upgraded powerbook (the wall street). he finally bought a new mac and this is when all his nikon 5700 nef files became incompatible. so something happened during the series of Mac OS X upates that broke the support for the nikon 5700 nef file.
i suggest that you also submit a feedback requesting support for the nikon 5700 nef file.
ps: they do listen, just be patient.

DAM I need to evolve (Lightroom vs Aperture)

I have been quite reluctant to change my photo workflow due to my hardware limitations, but now that Im getting a new Macbook Pro new doors are opening for me. So, Id like to change from my current workflow into Lightroom or Aperture. I have looked quite heavily into Aperture, but wanted to make sure I cover all the basis before choosing a solution and who better than Lightroom users to comment on Lightroom!
My Current Workflow:
Ok, my current workflow revolved around using iView Media Pro to sort, catalog, and caption images. I then use Photoshop to adjust and batch/export images for clients. I use the finder to download CF cards (just drag them to folders organized on the hard drive). I then import those folders into an iView catalog. Oh yeah, Im using iView Media Pro v1.5.7 (really old one) which is super fast and ignores all the RAW files (which for me was a benefit). Once inside iView I used the Batch Rename feature to change the file names... I remove the camera specific tag (in my case LG4Y) and replace it with the shooting date and a card number (20081025_1).
I then go through the photos and tag the keepers (I give them a color label). After I have sorted through the images I copy the tagged images to another folder on my computer for additional processing (this is once place the non-destructive adjustments will be great). I then batch run a photoshop action (scale, sharpen, etc.) on this folder. Once the action has been run, I create a second iView catalog with only the keeper images.
In this second iView catalog I will do my captioning. One of the features that I really liked at iView was the ability to create custom metadata fields (ex. Race Series, Track, Driver, Team, Car, Number, etc.). In the number field I put the car numbers for each photo. I then sort the photos by number and batch caption all of the photos for a given car with the driver, team, etc. at one time. These captions are then exported to an Excel file for importing into a web database.
Once the weekend is over I move the original files from my laptop to a desktop/server. One of the nice things about iView is the ability to search the catalogs without the associated images needing to be on the computer.
Things I need:
1. File importing and management: Im planning on using the software to import the photos from CF cards. I would like to rename the files on import (so need the ability to replace LG4Y something I enter for each card). I also plan on letting the software manage the images, but will also need to move the photos off of my laptop and onto my desktop/server. I plan on using the laptop for the main source for the library and only use the desktop for storage.
2. Image sorting and ranking: I think both pieces of software have what I need here. I do welcome comparisons in this are if people have them. Are both programs equally capable and speedy at the process?
3. Metadata: This is the most time consuming part of my current workflow. Unfortunately, because the majority of the captions are image specific I cant just batch caption on import. I really need the ability to create custom metadata fields. If these fields can be embedded into the images (or included in sidecar files) all the better. I also need the ability to quickly sort/search by these custom fields so I can add fill-in the other fields. Next, I need to be able to paste the fields across multiple selected images. Lastly, I need to be able to export the metadata into an txt/Excel file for integration with a web database.
4. Any other really cool things that I should be using or doing differently? So often I get close-minded on what Ive been doing... and dont see other things that I could be doing.
Wow, if you made it this far I give you a round of applause! I am planning on using both the trials, so should get a feel for both pieces of software. Thank you all for info.
-Todd...

1. Both programs do this fine. They both have elaborate rename tools that you can already apply at import or after import. Aperture hides the actual file structure a little more but can be used in the same way. They have more of a "iTunes"-like approach to file organization. I'd also point you towards Bridge, which is part of Adobe's creative Suite and does file organization more like a file browser than a database as both Aperture and Lightroom do.
2. They are both quite good by now. The latest version of Aperture has an amazing quick browse method for very quick initial selection that has to be seen to be believed. It uses the previews in the RAW file or the previews you have generated and just flies through. In my opinion, Lightroom is slightly more flexible in general.
3. Very comparable. I love Lightroom's spray paint for metadata, but Aperture is quite comparable. However exporting the files for external integration will be tough. There is a great plugin for Lightroom called
LR/transporter that will do this, or you can use database tools on your database file, but neither program does this natively.
4. If you go for either of these programs you might want to give up on trying to control the filenames/locations etc. too much. Just let the programs take care of it and use collections/projects and metadata integrated with searches to organize your files, just like you would in iTunes. This is a new paradigm for lots of people but it is very liberating and far more flexible than a harddisk/folder based organization paradigm.

Lightroom brighter than nikon view

Windows Vista, lightroom 2.3, nikon d300 shooting raw images. Monitor calibrated using spyder3
If I open an image in nikon view and compare it to lightroom, the lightroom version is significantly brighter than the nikon view display even though the histograms look the same. When the full size view initially pops up in lightroom, it looks the same, but when it finishes rendering it, it suddenly jumps brighter. If I export the image from lightroom to a jpg and compare its histogram to the orginal in nikon view, the exported jpg histogram is significantly slid to the right and no longer matches the one lightroom (or nikon view) orginally displayed for the image. Color and tone seem pretty close. My question - is there some setting that lightroom is using that bumps up the brightness or is it just the difference in the programs? I love lightroom, but its display and the proofs it exports just aren't as good as I'm getting from nikon view

The forums may not yet be up to full speed.
BTW: It doesn't help when you add off topic material to an existing thread. The best place to raise issues with the new forums is at http://forums.adobe.com/community/general/forum_comments

Import from Lightroom to Aperture 2.0?

Would like to give Aperture a second chance, but I have already built up my lightroom library. Is there a clean way to do this?

Has any additional progress been made on migrating from Lightroom to Aperture without losing develop settings and metadata?
I tried the Aperture 2.0 demo and really wanted to switch. Lightroom gets absolutely bog-slow once you start accumulating "professional" quantities of photos in your library (I'm managing about 25,000 DNG images) and not only is it slow on its own, it takes a death-grip on anything else running on your Mac as well. Aperture 2.0 was unchained lightning by comparison. And the new plug-in architecture and brush-on dodge/burn effects in 2.1 are deal-sealers for me.
Problem is, I've invested hundreds of hours in cropping and exposure adjustments of my images in Lightroom, and I can't face walking away from all that work and then having to re-do it, even with a superior tool.
Since both of these applications are nondestructive editing tools, all that crop and exposure setting data is just data in databases... I can't believe there's NO way to export that data out of LIghtroom's database format and convert it into Aperture's database format! Surely there's a third-party opportunity here -- I'd certainly be glad to pay for a Lightroom-to-Aperture converter that really worked, and I'll bet a lot of other people would as well.

Migrated from Lightroom to Aperture: TIFF's in LAB mode don't work

I migrated from Lightroom to Aperture and I noticed many TIFF's were black, or strangely colored (reddish, greenish). I couldn't figure it out, but I think I know what is the problem. I used to work in LAB-mode in Photoshop for quite some time, and I see that those files cause the problems.
Not only can't I see the previews correctly, Ican't do anything with these files (not even open them in Photoshop). What can I do? Because these files are my portfolio (the material I sell, exhibit, etc.). They're extremely important for me. What can I do? I'm willing to convert them to RGB if necessary.

There have been some issues with greenish previews lately. Browse this forum for threads with the tags "green" and "Previews". If that is the problem, then only your previews look strange and your original images might still be o.k.
So I recommend to check if the images or only the previews are faulty.
If you have a referenced Library reveal the masters in the Finder and look at the master with Preview or another Photo Browser.
If your library is managed, you can reveal the masters inside your Aperture Library by opening the package (in Aperture 3.2.1), select the Library in the Finder and click "Show package contents". You will see folders "Masters" and "Previews". Compare the Masters and the Previews.
If only the Previews are faulty, then select the the images in question in the Aperture Browser, ctrl-click them and select "Update Preview". If that does not help ...
What can I do? Because these files are my portfolio (the material I sell, exhibit, etc.). They're extremely important for me. What can I do? I'm willing to convert them to RGB if necessary.
I assume you have a backup or can access the originals you imported into Aperture.
Convert a copy of one of pictures to TIFF in RGB mode and see if Aperture can handle that properly.
If you are satisfied with the quality do that with all your important pictures.

Does Lightroom 3 support Nikon D800 Camera RAW

Does Lightroom 3 support Nikon D800 Camera RAW

No, you can either upgrade to LR4 or use Adobe's free DNG Converter to work with your images in LR3 as DNGs.

Behaviour sRGB embedded pictures in Lightroom versus IE

hello,
I have a calibrated monitor (6500K and a gamma of 2,2). I'm working with Windows Vista. When I view a picture with embedded sRGB profile in InternetExplorer (uses no colormanagement) and Adobe Lightroom (uses colormanagement), there is a very little difference in color between Internet Explorer and Lightroom or Windows photo gallery. IE shows the colors a little bit more saturated. The grays look the same.
I know that when I view a picture with embedded Adobe RGB profile or Prophoto profile, It will look completely different in Lightroom versus Internet Explorer.
sRGB is the default color space for Windows IE. Is it normal, even with a calibrated monitor, that there is still a little difference visible with sRGB embedded pictures, between applications using profiles (like Lightroom) and applications not using profiles (like Internet Explorer)

>s it normal, even with a calibrated monitor, that there is still a little difference visible with sRGB embedded pictures, between applications using profiles (like Lightroom) and applications not using profiles (like Internet Explorer)
Yes. You will only see the correct color in managed apps even on calibrated monitors. This includes Safari and Firefox
with the secret setting, but excludes Internet explorer and very surprisingly Google's Chrome (Boooo Google!!!). The reason for this is that the color primaries (i.e. the actual colors of your monitor's red, green, and blue emitters) are never exactly the same as sRGB's.
There is also a small knee in the shadow portion of sRGB. Most calibration software will calibrate not to this tone curve, but to simple gamma 2.2, so you will always see a small difference in the shadow portion between managed apps and unmanaged apps.
Now as Sean notes, you cannot really predict what your image will look like on other people's monitors. In general it will hover around to the look of sRGB on your calibrated monitor in managed apps, which is why everybody will recommend sRGB. But individually, you can get quite large deviations. Especially because of the current prevalence of laptops, which without fail almost always have terrible screens. They usually give rise to very strong shifts of the blue component (which some people erroneously interpret as a problem with sRGB). Unfortunately there is really nothing you can do about it.

Lightroom camera raw nikon d750

lightroom camera raw nikon d750

Use the DNG Converter 8.7 RC at Adobe Labs: http://labs.adobe.com/

Lightroom and Aperture problem

Help! I have both Lightroom and Aperture installed on my computer. I should have never installed both because neither one now works right. I think I need to uninstall Aperture but I am afraid to because Lightroom doesn't seem to be importing pictures correctly! Help me please!! I have over 4000 pics that need to be downloaded off of my camera disc! Also, if I uninstall Aperature, will iphoto still function?

You got a mess on your hands -- don't worry, happens to all of us.
1. Choose one or the other, but not both. Either LR or Aperture. If you have to, play a bit with each. But once you commit, commit all the way and _don't use the other_.
2. Find, isolate, and quarantine your digicam "negatives". Where they are is anybodies guess. Figure it out, for Aperture and for Lightroom. Separate them from these programs. Group them together. Back them up.
3 Export all "developed" images. If you already know which program you are going to use, export only those developed in the other program.
4. Once you have selected to work with either LR or Aperture, import all digicam files and all previously-developed-files into the program you selected.
I have no idea why you LR pics are pixilated, but I would ignore it for now. You have bigger problems, all caused by an un-flowable workflow.
HTH.

Lightroom versus Elements

I am considering changing to Adobe for handling and editing my photographs. My impression is that Lightroom is a more sophisticated product than Elements. What are the feature differences between Lightrooom and Elements? Why Lightroom versus Elements? Do you have both and if so, why?

http://forums.adobe.com/thread/536430?tstart=0

Lightroom versus Aperture: Nikon 5700

Similar Messages

Maybe you are looking for