Different colors from RAW+JPEG mode of my camera

The same issue of always... color profile.
I shot my entire trip thru Europe using RAW + JPEG Basic mode of my Nikon D40 digital camera. Oddly, the JPEG files are looking MUCH MUCH better, because iPhoto assigned the correct color profile to the files, instead of signing all RAW files as Adobe RGB. (I have Adobe RGB option on my camera, but I shot as sRGB).
I tried installing Aperture trial to reprocess all RAW files and no success. Looking RAW and JPEG side by side makes me sad.
What should I do to make iPhoto recognize my RAW files as sRGB?
Sorry for posting this again... I read more than 20 threads about color issues and I didnt managed how to fix my problem.

Hi Dave,
yes, thats generally what i want to do.
I have the PEF-Files out of my camera and i convert them with the Adobe DNG converter to the DNG format. The old Pentax K100D is using uncompressed PEF, thats why the pictures are twice the size than the converted DNG
If i import these files for further processing into Lightroom, they are looking similar to the originals viewed with another application (e.g. the pentax development tool) for a second, after that Lightroom is changing the preview to the settings of the Adobe Profile. Colors are much more colder and less colorful. If i try to change the profile in the developement tab, there are no visible changes to the picture.
I've downloaded the DNG Converter and Camera RAW. There are several profiles included, but i don't know how to use them with Lightroom or Photoshop CS4 (with installed ACR).
I've created a screenshot of the differencies so you know what i mean.
Screenshot
On the left side you can see the developed JPEG via PEF out of the Pentax-Software (Silkypix), on the right is the developed JPEG out of the DNG via Lightroom. Both files are without any further changes to the development process.
The left picture corresponds to the original conditions.

Similar Messages

  • "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.

  • How do I delete the jpeg from raw+jpeg imported images?

    Hi,
    Back in the day, I shot lots of images using raw+jpeg and imported them into Lightroom.  Now I realize those jpegs add no value and I'd like to recover the disk space that they're collectively occupying.
    Is there a good way to:
    1. Identify all images in a catalog which have raw+jpeg?
    2. Remove just the jpeg for these images?
    Thanks!

    $$PhotoHobby wrote:
    I'm very hesistant to take the chance on any 3rd party script.
    Just so ya know, what the deletion feature in RawPlusJpeg does is ultra simple:
    1. Identifies extraneous jpeg files.
    2. Presents them for you to review.
    3. Deletes the extraneous jpeg files, if you approve. (puts them in the recycle bin if possible).
    It does nothing to the database nor anything else.
    You sync folders with 'Treat JPEG files next to raw files separately' afterward, which is what sets the database right.
    The only potential for trouble is the criteria for determining which jpegs are extraneous.
    It has no direct access to the database, so what it does is check for jpegs with same base name as raw (which *must* be present in catalog, and on disk), that aren't in the catalog, which includes the jpegs associated with RAW+JPEG (imported as a unit), *and* any jpegs that were imported separately, but subsequently removed from the catalog, or had never been imported.
    So, what it does will be the perfect thing to do, *if* you first synchronize folders (with 'Treat JPEG files next to raw files separately' checked) to pull any jpegs in to the catalog that were previously imported separately, but may have been inadvertently removed from the catalog (or had never been imported), before invoking the delete feature of the plugin.
    Note: You must do that for any manual procedure too, or you will have the same problem, except in the manual case, you won't have the benefit of the plugin checking your work, and presenting the files to be deleted, before you commit.
    It's your call, obviously, and to save Geoff the Kiwi from pointing this out: the plugin comes with no guarantee, warranty, or any other kind of tea.
    Consider backing up catalog and photo files before doing this maintenance, whether manual, or plugin-assisted.
    In my opinion, the plugin-assisted method is much safer than the manual method, which is the only reason it was written, *not* to save steps, although it does that too. For example, you can not, with the plugin, delete any jpegs that do not have a corresponding RAW in the catalog and on disk, period. - unless there is a bug of course, but there probably isn't , at least not one that would change the aforementioned assertion... - it wouldn't take much of a bug to cause it to barf, but it would take a big bug to cause it to delete files that weren't on the list, etc...
    Seriously, I don't think you have to wait for Adobe on this one. I wouldn't (I didn't - my catalog is all clean now!...).
    PS - there is *very* little recorded in the database about the jpeg sidecar - it's existence upon import (when "as a unit") - that's about it. Most of the funny business about updating that we were fumbling with above, stems from the software (and the person at the keyboard), *not* the database. Syncing folders with 'Treat JPEG files next to raw files separately' checked, once the jpeg sidecars have been cleaned up, *will* set the database straight!
    Cheers,
    Rob.

  • "Recovery" missing from RAW editing mode in PSE12?

    I had just discovered the brilliant Camera RAW editing mode (for photos in other formats) in PSE 10. When I tried it in PSE 12 I noticed the "recovery" slider, which is essential to getting the best exposure results, is no longer there.
    What am I missing? Is there something else I should be doing to compensate for overexposure (as indicated by the red when the alert is turned on)? I had some success adjusting the "white" slider-- is that my only option now?
    Thanks.

    The whole raw engine got a serious overhaul and has been greatly improved from what you're used to in PSE 10. I'd suggest googling for a tutorial on how to use the new process, but if you really want to go back to the old version, in the Calibrate tab just choose the older version:

  • Different Color in RAW as compared with Editor?

    When I open a NEF file in elements 9, work on the file and finally click on the icon 'open picture' the color in the editor is different as compared with may raw. what happend??? klaus2337

    thanks for your help. I checked whether the color settings are in sync...they are. but whatever i used (either without color or user oriented etc. The result is, that either the JPG file, which I open in the editor, or the raw file (from the same picture using the option JPG and RAW in the Nikon Camera) is different when I save the raw file with the icon 'open picture'
    klaus2337

  • Different colors in Raw and Ps5

    My tiff picture is scanned in Adobe RGB, but looks different in Cam Raw and Photoshop5 even though I set the color profile to Adobe RGB in both programmes. When I make corrections in Raw, the colors doen´t match when I open it as an object in Photoshop. I´m really puzzled and hope someone out there can help me

    Problems like this are often borne from ill-formatted or faulty color profiles associated with the monitor.  The monitor profile (which is a complicated beast under the covers) may not be interpreted correctly by all the different parts of Photoshop.
    Try changing the monitor profile temporarily to sRGB and see if the display is now consistent.  You do this through the OS dialogs.
    If this helps, you may want to seek out a better profile for your monitor, or possibly get a calibration/profiling device to create one yourself.
    -Noel

  • Different colors from original footage

    Hello,
    i got footage from a HMC151 Panasonic. I edit in prores 422 and then export in quicktime self contained, and then compressor to obtain a standard dvd. I notice that the colors are quite different from original footage, they seems like colds. There's a way to retain original colors. Is up to compressor the difference?
    Thanx
    Fran

    I don't believe you want to over do this adjustment.The preview window will show a true compressed frame, as in what you'll get in the end when you submit the job... so if you make this too dark or whatever, you'll also do this to the resulting files. i.e, this preview should match the resulting file as it is actually applying the change in the preview window. What you see there before you compress should be what you see with the compressed files.
    Jerry

  • Digital clock which randomly selects different colors from Applet

    Hi,
    I relatively new to java, what I'm trying to do is list about five colours in my Applet and pass the colours into my java code, and maybe the font.....
    I want to be able to Display a digital clock which randomly selects different colours which were passed from my Applet
    Thanks for any help
    Zip
    Clock Code:
    import java.awt.*;
    import java.applet.*;
    import java.util.*;
    import java.text.*;
    public class dclock extends Applet implements Runnable{
    Thread animThread = null;
    int delay = 1000;
    public void init(){}
    public void paint (Graphics g){
    // get the time
    Calendar cal = Calendar.getInstance();
    Date date = cal.getTime();
    // format it and display it
    DateFormat dateFormatter =DateFormat.getTimeInstance();
    g.drawString(dateFormatter.format(date), 5, 10);
    public void start(){
    if(animThread == null){
    animThread = new Thread(this,"Animation");
    animThread.start();
    public void stop(){animThread = null;}
    public void run(){
    while(animThread !=null){
    try{ Thread.sleep(delay);}
    catch(InterruptedException e){};
    repaint();
    //sec++;
    }

    Why doesn't the clock just decide what colour it is going to be? If you need to pass the colour choices in, just let the clock accept a collection of colours in its constructor or something. I don't understand what bit of this you are having problems with as you haven't really explained. Please also use code tags.

  • AVC HD from Panasonic Lumix movie mode does not play on the iPad. Motion JPEG mode does play the videos, however there is no sound. Any suggestions?

    AVC HD movie mode from a Panasonic Lumix camera will not play on the iPad, the format in the camera is not compatible. However, Motion JPEG mode in the camera will play the video on the iPad but there is no sound. Any suggestions?

    Ok, I was an old fool, there is indeed a setting on the Lumix LX5 camera which seems to allows both audio and video, although not AVC HD, the camera must be set to Motion JPEG and subsequently NOT to PICT Bridge, rather to PC for the output. Anyone who decides to purchase a Panasonic Lumix should be aware of this. The iPad 2 will display Lumix perfectly in 720p which is enough for the old fool. The Sony NEX5N at twice the cost will do 1080p, but on the iPad and our TV the difference I suspect will not be noticeable.

  • 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

  • How to differentiate PO's in different colors in abap editor

    Dear sir,
              I had created five Purchse request using ME51N Transaction.  I would like to write each PO in each color using ABAP editor.
    With Regards,
    Baskaran

    Hi,
    You can try the following,
    Get the PR's you have created into a internal table, by writing a select query.
    Before writing out the internal table fields, do the following
    loop at itab.
    if sy-tabix = 1.
    format color 1  intensified on.
              skip.
              write:/1 'field1',18 '-' , 20 itab-field .
              format color off.
    endif.
    if sy-tabix = 2.
    format color 2  intensified on.
              skip.
              write:/1 'field2',18 '-' , 20 itab-field .
              format color off.
    endif
    endloop.
    You can use up to 7 different colors  from 1 to 7.
    Regards,
    Vik

  • Not importing JPEGs in case of  "RAW+JPEGs" files

    When I import "Raws+Jpegs" from me card in to Lightroom, can I avoid importing ther JPEG's that come with the Raws, and for which I have no need?

    Jimburgess suggests the following options for avoiding/eliminating JPEGs from RAW/JPEGs:
    1) The obvious way to avoid importing them is to set your camera to produce RAW files only, if it's capable of doing that. I JUST PURCHASED THE SONY A700 AND I DON'T KNOW WHETHER ZOOMING ON ITS LCD WILL BE POSSIBLE WHEN I SHOOT IN RAW ONLY? IF YES? THIS WOULD SOLVE THE PROBLEM.
    2)Copy your images from the card to the hard disk, delete the JPEGs, then do the LR import of the RAW files AND 2) Make sure "Treat JPEG files..." is checked in LR preferences, import the RAW + JPEGs, then delete the JPEGs from LR and the disk, isolating them using filter on file type or sort by filetype.
    I AIM AT IMPORTING MY RAWs IN LR IN A STRAITHFORWARD SIMPLE WAY: DIRECTLY FROM CARD INTO LR, WITH DNG CONVERSION AND BACK UP TO EXT. HD. SOLUTIONS 2&3 ARE TOO LABOUR INTENSIVE AND CAN CAUSE ALL KINDS OF MISTAKES.

  • I installed the new update of OS X and now find the iMessages are different colors or shades of gray.  Why?

    Why are iMessages coming thru in different colors from different people?  I haven't assigned color tags to these people.  How did this happen and how can i change it?

    http://www.apple.com/osx/whats-new/

  • RAW + JPEG Import Settings Confusion

    I recently bought a new camera which allows me to shoot in RAW and RAW+JPEG mode. I have at present set it to the latter, partially to be safe, and also for allowing quick image loading when out and about and can quickly upload the JPEG files to my ipad.
    But having just purchased Aperture 3, I am really confused over the RAW+Separate import brick's choices.
    I really cannot work out which is the best option,
    Both (Raw as Master),
    Both (JPEG As Master),
    Both (Separate Masters)  or
    Just RAW.
    I have been reading  a book  called "Aperture 3 Portable Genius, but to be honest, it has only made things even more confusing!
    Can someone please advise which are the best settings to use, and under what circumstances I would use the particular setting.
    Thanks :-)

    "best settings to use" is hard to answer, since it depends what kind of photography you're doing and how you like to work.
    It might be useful to understand that if you import 'jpeg as master' aperture treats the jpeg/master pair as one entity. When you edit the photo in AP you'll be editing the jpeg. If you want to get to the RAW, you'll have to choose "Set Raw as Master". Vice-Versa if you import 'raw as master'.
    If you import 'both (separate masters)' you'll see both jpeg and raw in AP as 2 separate files which can be edited separately.  I've never actually used this option, so I could be wrong about that.
    I guess the first thing to decide is which format you most want to work with in Aperture. If you only want to work with RAW in AP, then choose 'RAW files only'. In this scenario the only reason you're shooting raw+jpeg is for the quick upload to iPad.
    Maybe it would help if I explain how/why I use pairs. I shoot a lot of architectural interiors and most of the time I work closely with an art director who needs to see what the shots are looking like as the session proceeds. I shoot raw+jpeg for this and send the jpegs to my laptop over wi-fi for review. This is the *only* reason I'm shooting pairs, as the tiny jpeg makes the journey so much quicker than the large raw and is of sufficient quality for the purpose. I have the camera set to produce the smallest jpeg possible for fastest transfer.
    Back at base I'll import the raw files only. Even if I was using a higher resolution jpeg I'd still only import raw. For me it's what Aperture is all about, and unlike say... wedding photography, this type of shoot is low volume so there's no advantage in working with jpeg, and many advantages in working with raw.
    Actually, I use another import option for pairs: 'matching Raw files only'. This is a huge timesaver. It means that during the shoot we can rate the photos (jpegs) as we go, and I'm only importing the raws that meet that rating. IE I don't have to import the entire shoot and try to remember which lighting set-up (for eg)  the director liked best.
    Hope that helps. Also, take a look under "more like this" upper right on this page. Some good stuff in there.
    Charles

  • Canon's raw files (.CR2) in Adobe Camera Raw

    I shoot in RAW+jpeg and have my camera set at a 'picture style' where it adds a small amount of contrast to my images.
    I think if I open up the RAW file in Canon's proprietary RAW converter it will read that contrast information and apply it.
    But I heard that ACR will not recognize that embedded Canon information.  Is that true?  I hope it is not true, I would like to start with a blank slate when dealing with RAW files.
    Thanks for reading,
    Kkamin

    Correct - ACR cannot read the undoumented, proprietary tags that camera makers add to their images, nor can it exactly reproduce the undocumented, proprietary algorithms in the manufacturer's software.
    If you don't like that situation, please let the camera maker know that.  Even better, you can ask them to support standard RAW formats like DNG.

Maybe you are looking for