RAW+JPEG Workflow issues

When shooting RAW+JPEG Im having trouble finding a good workflow (Canon 5D Mark II, LR 2.2, Windows), whether or not I import with LR treating the RAW and JPEG files as separate photos. (Im drawn to shooting RAW+JPEG as the Mark IIs JPEGs are often very good.)
One major problem with importing RAW and associated JPEG as one unit (i.e., not as separate photos) is what I consider to be a bug: when I export metadata and ratings, they are applied only to the RAW file and not to the JPEG. Is there a setting I havent noticed or an easy workaround?
Also, after importing as one unit, it would be very convenient to be able to separate the RAW+JPEG into separate photos (e.g., for editing and export). Why does the combined vs. separate approach have to be decided on at import time without being able to change it later?
In trying to work around the above problems, I import as separate photos and try to treat each RAW+JPEG pair as a unit. As some have suggested, perhaps the best approach is to create a stack for each RAW+JPEG pair (easy with auto-stack). But this approach is very limited because you cant really treat a stack as a unit, i.e.:
- quickly apply metadata and ratings to a stack
- delete all photos in a stack
- move a stack for sorting and into collections
You can work around these limitations by unstacking each pair and selecting both, but thats a bit clumsy.
Any advice or info would be appreciated.
js

I think I already commented on that in an earlier post.
ACR until quite recently had a very bad habit of bad colors by default... why would I want to create a .jpg from that ugly RAW using LR when they whole purpose of having the .jpg was to have some reference of 'reasonably close to what I'm after.' Or perhaps you needed some quick prints, and don't feel like messing with tweaking colors in RAW at the moment... and camera generated .jpg is 'good enough' with just some simple minor adjustments.
The new profiles are a huge improvement, but at times I still shoot both... just to check up that its still doing what I expect of it. And most of all, I want to use LR to manage ALL my images. Stacks are a handy way to hide the clutter if that's what you want to call it... their functionality just isn't what you'd expect to be there.
Others may have their own reason for wanting to use both. But again... I'm not arrogant enough to presume that everyone should be doing things just as I do, that's the beauty of options - it makes the program more powerful for a wider userbase. If options like this are more difficult to implement than the GND or adjustment brushes... then perhaps some poor initial decisions were made in how they based LR in the first place.
Besides... it wouldn't be as much of a 'hassle' if the proper tools were in LR in the first place. ;)
Plus, aren't there ways to filter so you only see RAW if that's what you are after? I honestly don't know, because I personally don't see the 'duplicate' files as a hassle - though their management could be eased... which I think was the intent of all the suggestions.

Similar Messages

  • Looking for some RAW + JPEG Workflow suggestions

    I'm looking for some suggestions on how best to organize my workflow now that I've started shooting with RAW +JPEG. I previously shot only in RAW, but the time spent in post-production was killing me. I've realized that for 95% of my shots that already have the correct exposure, white balance, etc, a JPEG photo is really all I need and saves me a ton of time. I've become convinced that editing every single photo from a shoot in RAW is overkill. I want to have the RAW versions, however, to rescue that occasional great shot where I unfortunately miffed the settings.
    Through reading other posts here and experimenting, I've found that Aperture basically defulats to showing me only the imported RAW photos and that I need to click "New Version from Master JPEG" to see the JPEG version. This seems counterintuitive to the workflow I'd like to establish though. (i.e. I'm thinking it would be nice to see only the JPEG versions, and then only bring up the RAW version when the photo needs some serious correction).
    I suppose I could highlight the entire batch of imported photos and select "New Version from Master JPEG" and then sort through each RAW/JPEG stack, but I'm still hoping there's a less cumbersome way. Anyone out there have any good workflow suggestions for this issue? I'm curious how other people out there deal with this issue in their workflow.
    Thanks in advance!
    Message was edited by: Nate Cannon

    Try this - I do this as a matter of course:
    -select all of the photos after importing them into a project
    -create a new album from selection/call it JPG
    -with all of the images still selected create new version from master JPEG. all of these should now be the album pick
    -close all stacks, the JPEG will be the one showing up on top for that album.
    RB
    More here: [Aperture RAW+JPG|http://photo.rwboyer.com/2009/01/14/aperture-2-quick-tip-shooting-rawjp g>

  • RAW+JPEG workflow solution needed

    Question to any pro's out there-nitpicky. Aperture 3. I have imported 1000's of files via seperate RAW and JPEG import option into projects, then created a RAW album and a JPG album within each project via a file type filter. I have done this because I want to have the ability to choose to save space by deleting some unwanted RAW files that I know I will never edit, but keep some of those JPEGs. For some I might want to keep RAW and not have the JPEGs. Sounds funny, but the space adds up when shooting 7fps, thousands of 6 MB JPG add up. Here is my question. I have been rating a bunch of the RAW in my RAW album within a project. I have lots of files that I have rejected. Is there a way to automatically match the associated JPEGs of these already rated rejected files that I don't want either RAW or JPEG without doing so manually in the project "parent" folder. HELP! I didn't see this hiccup and I have manually seperated all my projects this way. Is there a better way to do this workflow in the future once I have found a way to straighten this mess out?

    Sorry - how thoughtless - here are the steps (pretty much off the top of my head)
    -Autostack the RAW JPEG pairs
    -Make album of RAWs and album of JPEGS with corresponding file types as album picks
    -Go through RAW album w/ stacks closed and label all RAWs to be rejected.
    -Go to JPEG album and open all stacks filter by label to pick up the image stacks with JPEGs to keep select all and create new album called KEEP JPEG
    -Go to JPEG album filter by label select everything, get rid of filter, invert selection
    -Create new album called KEEP RAW
    -Go to KEEP RAW album open all stacks filter by file type JPEG, select all, delete images
    -Go to KEEP JPEG album open all stacks filter by file type RAW, select all, delete images
    I just did that off the top of my head without being in front of Aperture so it might a little wrong but you get the idea. With short cut keys it isn't a huge deal but still too much for me to do on a regular basis to save a couple megabytes.
    RB

  • Aperture and shooting Raw+Jpeg

    In camera Jpeg processing becomes better and better with each generation of cameras. One example is the dynamic range optimizer in my Sony A700. You often have a hard time to get similar results from the Raw. So for quite a lot of shots - especially the not so important ones - using just the Jpegs is a real time saver. Still it is good to have the Raw handy in case the camera processing went in the wrong direction, which still happens occasionally. With 8 or 16 GB cards it is not an issue meanwhile to shoot Raw+Jpeg. Unfortunately IMO there is no smooth Raw+Jpeg workflow within Aperture. Especially it is almost impossible to delete the Raw without loosing the Jpeg and vice versa in a managed library (see thread mentioned below).
    Thus I just posted this to www.apple.com/feedback. If you think this is an important issue, that should be added in a future version of Aperture, you might sent your feedback as well:
    It is nice, that Aperture already imports both pictures, if you shoot in Raw+Jpeg mode. But the further workflow of dealing with the Raw+Jpeg combo is not optimal:
    The main reason to shoot Raw + Jpeg is, to save time in using the ready processed Jpegs for the less important shots or the ones, where the in-camera processing left not much to improve, but still having the safety-net of the Raw for a more advanced development, in case the picture asks for it.
    So instead of showing the Raws and hiding the Jpegs by default it should be vice versa. If there is a Jpeg accompanying the Raw, the Jpeg should be displayed and the Raw should be hidden. At least you should be able to set in the preferences, whether you prefer to see the Raw or the Jpeg. If you realize while rating the picture or doing adjustments, that the Jpeg doesn't fit the bill, you should be able to give precedence to the Raw, aka showing the Raw and hiding the Jpeg.
    After having finished the work, you should be able to either delete or archive the not used version (either Raw or Jpeg), without loosing any metadata or adjustments already applied to the other version.
    Currently it is an extremely complex task, to get rid of the unused version. Workarounds are suggested in this thread: http://www.oreillynet.com/digitalmedia/blog/2007/09/gettingrid_of_unwanted_manage1.html
    Peter

    SierraDragon wrote:
    I am unfamiliar with Sony DSLRs and do not know what might make a Sony JPEG visually equal to a Sony RAW image file.
    What I refer to is the dynamic range optimizer, which is based on Apical’s IRIDIX image processing engine. I think it is used in recent Nikons as well, but as I have only a Sony DSLR I mentioned this.
    Basically it is a kind of highlights and shadows adjustment, but it works very well and in many cases you have a hard time to generate similar good results with your RAW processor (aka. Aperture).
    However, JPEG is still a lossy image format that IMO should only be used for low end usages. RAW converted by the camera vendor's software to non-lossy formats like TIFF should generally be quite superior to JPEG.
    Of cause the RAW holds more information and carefully processed often leads to better results than the in-camera JPEGs. But not every picture will be printed in poster size. And although JPEG is a lossy format, with a low compression setting the artifacts are almost undetectable at least with my DSLR.
    Shooting in RAW+Jpeg mode can be a real timesaver. You look at the Jpegs firsthand, rate them, make small adjustments, if neccessary. For the majority of the pictures you can use these Jpegs even for slideshows and prints. If you step over a picture, where the in-camera processing went wrong, like oversharpened, oversaturated picture with wrong WB etc., you can easily resort to the accompanying RAW and process it to your heart's content. The only drawback with this workflow is the increased temporary storage capacitiy you need. But with today's low memory card prices, the benefits outweigh the cost by far IMHO.
    That said, the reason for my post was not to discuss the benefits of a RAW+Jpeg workflow, but Aperture's issues in dealing with it.
    Peter

  • RAW + JPEG =  ExifTool

    Some people have indicated that they want to shoot RAW + Jpeg for a few reasons, principally speed issues.
    Running a 'pure' RAW workflow can be very slow (without shooting JPEGs at the same time as the RAW and storing both files on the card), because LR has to Import->build Previews->Export just to get some simple sample JPEGs.
    I did a little research, and it turns out that, as we have mentioned before, every RAW file contains at least two JPEG files internally, a large preview and a thumbnail. These images can actually be extracted from the RAW and used for 'quick and dirty' work if you need a fast JPEG workflow.
    For a Canon 5D, the large Preview embedded in the RAW is 2496x1664, which is plenty for many uses, such as a quick index.
    The tool for extracting embedded JPEG files is called ExifTool, and can be found here:
    http://www.sno.phy.queensu.ca/~phil/exiftool/
    It is a 'command line' tool, and is available in both Windows and Mac versions.
    The following command will take all the RAW files in a folder and create a subfolder named JPG with all the extracted files inside the new folder:
    exiftool -b -PreviewImage -w JPG/%f.jpg -ext CR2 -r .
    Notice the "." at the end of the line. It is necessary.
    Also notice that it uses CR2 as the RAW file extension, you will need to change that to CRW or NEF or whatever your RAW files are named as for this to work.
    I strongly recommend experimenting with some copies of your images in a 'Test' folder, and I am absolutely positively 100% not responsible for anything that happens when you use this tool.
    So, it is not for the meek, but if you want to have a mixed RAW+JPEG workflow for some reason, this may be a better solution that shooting both formats to start with.

    For Canon users, another option is to use Zoom-browser to batch convert your .CR2 files to .jpg. For me, at least he standard settings seem to match near exactly to how in camera .jpg's appear. You can even use lower compression than camera itself uses.
    (I had emailed to Canon awhile back when first shooting RAW asking what settings could be used in DPP to match the .jpg, they said there were none in DPP, but they claimed Zoombrowser comes extremely close since it uses conversion alogrithms more like the Digic chips do.)

  • I am having issues when I shoot raw + jpeg. Raw files seem corrupt!!

    I am having issues when I shoot raw + jpeg.  It seems the raw files get corrupted.  I have shot raw without an issue.  It is only when I shoot raw + jpeg.  The raw files will not show in Photoshop elements.  I installed the Canon software and was able to see all the raw files; however, I noticed that when I tried to view some full screen they would not show.  I also noticed that these raw files look block-ish.  They appear more digital looking.   Is there a specail card needed to shoot raw + jpeg?  I formatted the ones that I have prior to using them.
    Solved!
    Go to Solution.

    While it could certainly be a card-reader problem, data corruption of any kind can be any of the following:
    1) the card
    2) the cable (if used)
    3) the card reader (if used)
    4) the computer RAM,
    5) thecomputer hard drive (or SSD)
    A failure of any one of the above will result in corrupted images when viewed.  Since it seems to be RAW file related, as they are signifantly larger than JPGs, it's likely anything but the card reader or cable. 
    The only way to 'beat it' is eliminate each of the possibilities, starting with the easiest/cheapest fix. 
    1) Use the cable.  If that solves the problem, replace the card reader.
    2) Use a different card.  If that solves it, toss the old card.
    3) If multiple sticks of internal computer RAM, swap them.  If that fixes it, or, the problem 'moves' to other images, replace the RAM.  It could be only 1 of 2 sticks bad, though, so use only 1 of the old sticks for a while to see if the problem recurs.
    4) If you have multiple hard drives in your computer, or an external one, use that to store the photos for a while.  If the problems go away, it's the drive.  Note that hard drive failures typically start slowly and increase gradually.  On occassion, though, your computer won't boot and it's all over.  If you are down to thinking it's the hard drive, it's time to get a good backup...NOW! 
    For what it's worth, I had a similar problem with corrupted photos.  Both RAW and JPGs were affected.  But as the problems were after having loaded and initially viewed them on my HD, I knew it was a computer problem.  It dogged me for a couple of weeks.  I even played swap the memory sticks, pull one out and run on one only, swap the one for the other (running on one), and it STILL kept happening.  I finally gave up and replaced both sticks of RAM.  That solved the problem.  So much for lifetime warranty from Hong Kong.  A very well regarded brand of RAM, no less.  My SSD drive was the next one on the list, it the new RAM didn't solve it.

  • Import issue - RAW + JPEG Pairs Both (Separate Originals)

    I am trying to import my Olympus OM-D files into Aperture using the RAW + JPEG Both (Separate Originals) setting but it doesn't seem to work. I only get one file (the ORF). I want to use this option for when I use the camera's Monotone setting (it essentially creates a B&W JPEG from the RAW file). What is currently happening is that during import I will see the B&W thumbnail in the import dialog, it will be imported as a B&W thumbnail into the project but as soon as I select it the preview refreshes and becomes the coloured RAW file.
    Thank you for reading my post.
    Michel
    P.S.: I am on 10.9 with Aperture 3.5.

    Are you sure you are setting the camera to shoot both Raw and JPG?
    If you are only getting the Raw imported it sounds like you are not producing a JPG file. The B&W preview you see is the preview imbedded in the raw file. This is not the same as the camera producing a separate JPG file.

  • Aperture 2.3 update and Canon 350 (xsi) RAW+JPEG issue

    Anyone know if this update fixes the problem with importing RAW+JPEG captures from Canon 350 (xsi)? I'd hate to download this update and then have to un-do it (again).
    Thanks!

    Not using a canon 50d, using a Sony a900 instead. Actually, DPP is special because it does absolutely no noise reduction (at least in AHD mode). You can see that it is actually noisier but with a much finer grain pattern than ACR, aperture, raw developer, etc. You don't get the blotchiness associated with the NR of these other converters. The beauty of this is that when you run it through your grain reducing software it is much better for the software to deal with (the noise hasn't been processed by any NR software- which makes the noise non-random) and as such produces much cleaner images. I just did a comparison of the noise with the A900... here are links of the comparison using a publicly available Imaging Resource Raw file:
    http://idisk.mac.com/kshuler/Public/3200resultsarea1.jpg
    http://idisk.mac.com/kshuler/Public/3200resultsarea2.jpg
    http://idisk.mac.com/kshuler/Public/6400resultsarea1.jpg
    http://idisk.mac.com/kshuler/Public/6400resultsarea2.jpg
    Aperture doesn't do a bad job, better than most others, but still not as good as RPP.
    Klaus
    http://www.bokehtests.com

  • HT2297 Raw+jpeg issues for exporting

    I have a Nikon d5100.  I accidentally shot some footage in Raw.  It was imported on my Mac Pro as raw+jpeg now I can not export, copy to disk, or flash drive.   I just want to print the photos can anyone help me?   I also tried to export to costco but file is still too large.  Thanks Melissa

    I think I already commented on that in an earlier post.
    ACR until quite recently had a very bad habit of bad colors by default... why would I want to create a .jpg from that ugly RAW using LR when they whole purpose of having the .jpg was to have some reference of 'reasonably close to what I'm after.' Or perhaps you needed some quick prints, and don't feel like messing with tweaking colors in RAW at the moment... and camera generated .jpg is 'good enough' with just some simple minor adjustments.
    The new profiles are a huge improvement, but at times I still shoot both... just to check up that its still doing what I expect of it. And most of all, I want to use LR to manage ALL my images. Stacks are a handy way to hide the clutter if that's what you want to call it... their functionality just isn't what you'd expect to be there.
    Others may have their own reason for wanting to use both. But again... I'm not arrogant enough to presume that everyone should be doing things just as I do, that's the beauty of options - it makes the program more powerful for a wider userbase. If options like this are more difficult to implement than the GND or adjustment brushes... then perhaps some poor initial decisions were made in how they based LR in the first place.
    Besides... it wouldn't be as much of a 'hassle' if the proper tools were in LR in the first place. ;)
    Plus, aren't there ways to filter so you only see RAW if that's what you are after? I honestly don't know, because I personally don't see the 'duplicate' files as a hassle - though their management could be eased... which I think was the intent of all the suggestions.

  • How to import only RAW images from folder with RAW & JPEGs?

    My system is set up that I have both RAW & JPEGs in the same folder since I shoot JPEG+RAW. How can I import just the raw images without also sucking in the jpegs? There is no way to distinguish the difference in the Import box and also no way to easily separate the the two in the Import box. I've tried using the List View and separting them by File Size, but Aperture has a stupid bug here and it tells me that the JPEG file sizes are in the teens (like 17-18 megs) and they are still hard to separate from the RAW which are about the same size.
    Why can't Aperture do this basic thing?

    I'm not doing anything. What I wrote in my workflow example above is exactly what I'm doing. I've been trying some experiments to see if it was "A Better Finder Rename" that is causing the issue. So far, no go. I have taken just a couple of JPGs only and pointed Aperture's Import to the folder that contains them. Aperture is reading that there are only 2 jpegs (which is what there is) and their file size is right on the mark.
    Ok. I just narrowed it down to something. The flaw is showing up after the RAW files are converted to DNGs. The JPEGs do not show up in the Import box when there are camera raw files like NEFs or CR2s and the corresponding JPEGs. That is Aperture's normal behaviour. But, and this is a big BUT, when the raw files are converted to DNGs and they are in the same folder as the corresponding JPEGs, that's when Aperture pulls its shenanigans. It has something to do with the JPEGs and DNGs having the same name. Even though the files have different extensions, Aperture is doing something to the file size of the JPEGs that make them seem that they are much larger files than they actually are.
    I figured it out like this:
    I had 2 CR2 files and the corresponding JPEGs in a folder. Pointing Aperture's Import to that folder, Aperture did what it is supposed to do; it saw only 2 raw files (doesn't matter that the G9 CR2 files are not supported yet). So, I renamed all the files using A Better Finder Rename and Aperture still only saw 2 raw files.
    So far so good.
    Then, I converted just the 2 CR2 files to DNG and kept them in the same folder. Aperture saw 2 DNGs and 2 CR2 files. No jpegs were seen. Business as usual. Then I removed the CR2s and renamed the jpegs so they had the same names as the DNGs (except for of course different extensions) and that's when Aperture saw the jpegs as separate files and saw them with bogus file sizes.
    So I tested that by altering the jpeg names so that they were different from their corresponding DNGs and Aperture went back to seeing the jpegs with the correct file sizes.
    Therefore, Aperture is having some difficulty with two separate files, one JPEG and the other DNG, when they both have the same name (different extensions, of course).
    Try it if you have a moment. Take one raw file and convert it to DNG and place it in a folder with its corresponding jpeg. Rename both to the same name and different extensions (.dng + .jpg) and see what happens when you try to get Aperture to import. Chance are Aperture will show bogus file sizes for the jpeg.
    Let me know if that's clear.
    Antonio

  • Aperture Raw & Jpeg import Problem

    I'm on the current Aperture and face the following situation: I have a memory card containing photos shot partly as jpeg-only and partly as jpeg&raw.
    No problem one should think since Aperture has the option to only import either raw or jpeg if there are more than one format per photo. Unfortunately, that is not working. If you select raw only, which I do for the raw&jpeg photos, Aperture does not import Photos which only have a jpeg-version at all.
    This is not consistent with the options name and at all renders the whole import options useless in my case.
    Am I missing something or is Aperture having an issue here?

    I shot raw and jpeg since I was on a trip through the US and my Macbook broke so I had to use my iPad to upload the photos to my blog. Unfortunately the iPad software (iPhoto etc.) does not allow to change the resolution and with that the filesize of the photos. Uploading of hundreds of photos of more than 2 mb over public wifis on campgrounds etc is simply not possible, so I used the following workaround: Set raw+minimum jpeg size as file format and upload the small jpegs to the blog while keeping the raw on the memory card for later use.
    That's why I shot both raw and jpeg and why I have photos shot as jpeg or raw only (before the laptop crash) and both raw and jpeg (after the crash) on the same memory card.
    I'm Aperture user from the the very first version (when it was like hundreds of Euros), and I sadly cannot say that I'm surprised of the lack of support for non-standard workflows.
    Well, so be it. Thank you for your help!

  • "Error while relocating" after deleting RAW from RAW+JPEG pairs (Important FYI)

    This is not a question, but something I recently discovered that I think will be important for the Aperture community.
    Not too long ago, I asked a question about how to remove the RAW files from RAW+JPEG pairs. The concensus was that it couldn't be done through Aperture, but that one could delete them through the Finder. The answer I got (and that has popped up in other threads on similar topics) was "it's probably not wise, but as far as I know, it won't have an adverse effect." I don't think any response along these lines has been able to point to a specific problem that can arise from such a "hack." Well, I found one today...
    It appears that if a user uses Finder to "break" RAW+JPEG pairs by deleting the RAW file and leaving the JPEG (and I assume this goes for deleting the reverse), Aperture will NOT be able to "Relocate Originals..." Instead, "Aperture will return the error: Error while relocating (File not Found): "(null)". I ran into this error the other day while trying to change my file structure by relocating all files. I regularly ran into this error, and it was only after some extensive that I was able to narrow it down 100% of the time to the RAW+JPEG pairs I had "broken." I haven't encounterd any other adverse behavior from "breaking" these file pairings, but this one, at least, could be serious.
    So, for future reference, I think the response by the Aperture community when someone asks "How do I delete the RAW file from RAW+JPEG" pairs, should be "Use Finder if you must, but please note Aperture will not be able to 'Relocate Originals..
    PS This should NOT be understood as a criticism of those who have responded to this question in the past. There's obviously no way to know about these little quirks until one of us stumbles across them. I hope this information will be helpful going forward, both as a caution when deleting one of the pair, and as a possible answer for the "Error while relocating" message.
    PPS I don't think I ran across an explanation for this when I originally searched for the error message bolded above.
    If someone has already provided this information, my apologies.

    Frank Caggiano wrote:
    Interesting the last post before this one you posted was back in May 2011 Removing RAW, keeping JPG?
    Thanks for that thread. That helps jog ye olde memory. As such, I would edit my original thread to read "The concensus I gathered from researching multiple responses to questions similar to mine was that it couldn't be done through Aperture*, but that it was possible from Finder though highly inadvisable." I won't bother recreating my research at the time (not even sure I could, since it was more than two years ago), but suffice it to say that the thread you've linked was not my sole encounter with this problem. I do appreciate that you've reminded me that this was not something I had done solely through numerous posts on Apple Discussions. I imagine I likely spent time reading multiple posts here and elsewhere, uncovering the concensus (which i think is still a fair term) that it could not be done through Aperture*, could be through Finder, but was inadvisable.
    *This is still accurate, afaik. You cannot delete the pair from a RAW+JPEG pair in Aperture. Exporting, then deleting in Finder, then reimporting is still not something "done in [entirely] Aperture."
    Frank Caggiano wrote:
    No one actually told you to delete anyting in in the Finder you came up with this yourself as your own solution
    This comes from the critical mistake on my part of not making clear that I was paraphrasing multiple responses rather than saying "Bob told on a Monday that i should..." That is one huge mea culpa and I'd edit it if I could. To be clear, my comment that "it's probably not wise, but as far as I know, it won't have an adverse effect" is a paraphrase of multiple answers to the broad question dealing with how Aperture handles files that have been deleted in Finder. At the time, it was known that you could delete a file in Finder, that Aperture could be made to accept that, that it might cause issues further down the road, but that those issues were unkown. I paraphrased that but failed to make it clear that's what I was doing. Again, my apologies.
    Frank Caggiano wrote:
    So I'm not really sure what it is you are coming back here now to say? There was no 'consensus' to do this, it was your own 'solution'
    In this respect, I think you've misunderstood me. At the time I made this post, I still was not seeing a direct connection between deleting files in Finder and adverse consequences in Aperture (or perhaps I should say my searches did not turn up such a connection). As such, I made this post to provide the community with clear evidence of why one should not delete one-of-a-pair files in Finder. Again, I may have simply missed the thread that detailed that to do so would result in a null error when relocating Masters. That said, in July 2013 I had been pulling my hair out trying to figure out why I was getting the null error and I did not see a thread that asked "have you deleted files in Finder" as a way to troubleshoot.
    Hopefully, I've cleared up any confusion now. To bring this all back around to my original point for the thread, I intended it to (1) offer a more direct way to troubleshoot the null error on relocating Masters, and (2) to offer a cautionary tale for those who choose to delete one of the RAW+JPEG pair in Finder. There are better (though more time- and space-consuming) ways to get it done, and my original post should help demonstrate why.

  • RAW files not showing when I shoot raw + Jpeg!!!

    I have a strange issue that has only recently started happening.  I have started shooting raw + jpeg to speed up post processing.  However, after I import the files into Organizer the raw files will not show.  At first I thought it was the camera.  So I used a different brand DSLR.  I had the same issues with my Sony and my Canon.  I have shoot raw with the Sony for years and never had an issue.  I have shot raw with the Canon and haven't had an issue.  It is only when I shoot raw + jpeg.  I formated both cards prior to using them.
    The files are there and not damaged.  I used the software from Sony and the software from Canon and was able to view the raw files.  I wanted to make sure what I put was accurate so I tried viewing the files again.  Even with the Canon software when I tried to view some of the raw files full screen it wouldn't let me.

    I am using PhotoShop elements 10. My cameras are a Sony a230 and Canon 60d.

  • Import of RAW+JPEG pairs?

    Just when I thought I had it all together...I seem to have forgotten where I put it. I need some expert assistance.
    Aperture manages my Library which is kept on an external HD.
    I shoot RAW+JPEG on my D200--two image files for every shot. To anticipate the question--I'm learning about the D200, and I want to be able to see the IQ differences between an Aperture-adjusted RAW image and a D200-adjusted jpeg.
    I understood that when I imported my image files into Aperture, both files of the pair were imported and saved in my Library. I know I was working with the RAW file for all my adjustments and exports, but I believed that if I wanted that camera-adjusted jpeg, it was available from my Library. I'd also understood that I could call up that camera-adjusted jpeg using Option+J while selecting the paired RAW image in the Viewer. I know I can get a jpeg counterpart to the highlighted RAW image using Option+J--but whether it is generated by Aperture or camera is now uncertain.
    Can someone who knows answer the following:
    (1) Are both images in the shot pair (.nef and .jpg) imported into Aperture?
    (2) If the Option+J image is not the downloaded, camera-produced image--then where does the resulting jpeg file which appears come from, and where are the adjustments for it set?
    (3) If my original understanding is correct and both images in the pair were loaded into my Library--why can't I find the paired jpeg? It's not listed with the RAW files in my Finder, and my Spotlight doesn't find it either.
    (4) Is there a way to get that paired jpeg into my Library along with its RAW counterpart.
    One note on backup workflow: If those paired jpegs aren't imported into the Library, I'm fortunate to have followed advice from some of you here in the forum. Thanks to you, I always download my files using a reader and save them to a folder on my desktop. After importing them into Aperture from that folder, I move them to a folder I use to accumulate a batch for burning to a DVD for archiving. Only when burnt, do I erase them from the desktop and reformat my card. If, in fact, I've been wrong about those paired jpegs being in my Library, then I've still got them on my DVDs. Instead of being redundant with my Vaults, the DVDs will be my only source for them. Thanks to those of you who got me to buy into that workflow.
    Terry

    Thanks. A little Tough Love from the experts sent me back to try one more time to puzzle through the pages of posts on this subject. Sorry, but there's too much noise and contradiction in those pages of posts for me to buy in.
    I did what each of us probably should do--an experiment. I noted the "New Version from Master JPEG" aka Option+J was grayed out if only one of the pair (either .nef or .jpg) was imported. Only having the pair imported activated thet Option+J pick. Excellent, and just what I hoped to see.
    I also drilled down to the lowest level of the imported image folders in the Library. I'd previously stopped when I saw the image name but for some reason neglected to open the lowest folder to check for file extensions. Careless on my part. I confirmed what everyone here is regularly assured--that all the imported image files are available in the Library (and Vaults) should Aperture fail, or someone decide to leave Aperture for the dark side. Again, just what I hoped to see.

  • Lightroom 1.4.1 won't read RAW  or RAW+JPEG from Canon Rebel Xsi

    I use Windows. I started with LIghtroom 1. Technical support said Lightroom 1.4.1 update would let allow me to import RAW and RAW+JPEG files from Canon Rebel Xsi into Lightroom. I downloaded the update. Lightroom still will not recognize RAW or JPEG+RAW photos taken with my Canon Rebel Xsi. Lightroom will read straight JPEG photos taken with this camera. Any suggestions as to how I can fix this (e.g. be able to import RAW and RAW+JPEG files)? Sorry if there is a simple thing to fix to this or if I could have found the solution somewhere else on this site. I am a Lightroom novice and have been struggling with this issue for some time now. Thanks in Advance.

    Thanks everyone for all your help! I am now able to import the RAW files. Steve and Don especially thanks so much! I am posting my solution in case someone out there has had the same problem.
    In the past, using the prompt generated from within LR, I downloaded the update and ran the install. However using Don's information I realized the splash screen indicated 1.1 and the number did not match the build # provided by Don.
    Based on this information, I went to the Adobe site, reran the download via the Adobe site (not LR) and reran the install. Of note, this install process gave different screens from when I ran install from the files downloaded accessed via the LR prompt. The biggest difference is that this time I got Adobe directions for how to execute the update. I next confirmed that I had the update files on the hard drive, opened the file as directed by Adobe and the install updated. However I was still getting the LR 1.1 splash screen.
    Based on information posted elsewhere, I determined that I needed to delete the LR icon from my desktop. I moved "LR 1.4.1" from the start menu to the desktop. I now launch LR 1.4.1 when I hit the LR icon and I have successfully downloaded a boatload of RAW files. Thanks All! You are geniuses!

Maybe you are looking for

  • Java 1.6.0 amd64 problems

    Hi. I've installed the lastest AMD64 binary of the JDK and JRE (1.6.0u3 at the moment) and I have a problem. I'm running Windows Vista x64 and , even after installing the two packages , the JVM is still not seen by the system. When I try installing N

  • Listener for CheckBoxes in JTable

    Hi, I have a table that displays a checkbox in one of the fields. Which event handler/ listener should I use? Eg: Checkbox listener, List listener or otherwise? A change in the checkbox value (tick or untick) will trigger recalculation. Thanks.

  • Only D-Z Contacts Synced To iCloud

    I'm using iPhone 5 and have an iCloud account set to sync my contacts with iCloud. I jumped in a lake with the phone in my pocket so now it's dead and I'm looking at iCloud and only my D-Z contacts got synced. What's the deal with this? Do my contact

  • Why does it flash when you get a call or text

    Why does my phone have a light flashing when I get a text or call

  • Buttons on top of full-screen pan

    How to create buttons on top of a full-screen pan? I created buttons to navigate to the next an previous page and are inside an MSO, but the buttons don't work.