Zum Hauptinhalt gehen

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

colormanagement and truncted files

Kommentare

8 Kommentare

  • Darko1
    Tobin,

    Normally you would want to specify your working color space in the destination panel. In your case - Adobe RGB, instead of embedding the camera profile. That way the image preview in C1 will be showing you what it looks like in that destination space. This may be the cause of the color difference between the two programs.

    Also though, if that's not the problem I'm wondering if you are having the same issues that I am having right now. I have the same setup (MacBook Pro / 5D) the only difference being that I'm running C1Pro. Let me know if when you select a grayscale profile (generic gray) in the destination space, does it turn the preview image gray as it should or does it stay in color?
    0
  • roman111
    Hi,

    May I add my problem to the discussion? I've spent so much time trying to fix it, I'm giving up. Please help!

    When using the process tool in Capture One I need to export images into sRGB color space. There is a possibility to choose destination color space, but this seems to only ASSIGN, not CONVERT into the color space. In other words as soon as you change the 'embedded camera profile' into anything else, color is miscalculated and the result is awful.

    If you import the image with 'embedded camera profile' into Photoshop and click 'convert to sRGB' colors are preserved perceptually and the image looks great. In the image attached you'll see on the left a photo converted into sRGB from Phase One, and to the right an image with the embedded camera profile converted into sRGB inside of Photoshop. Big difference!

    http://img154.imageshack.us/img154/1895/picture12vh.png

    I keep all images in RAW and export as needed (for development). If I cannot export directly into sRGB color space it poses a big detriment to using Capture One. There just must be a way! 😊

    Thanks for your input,
    Roman
    0
  • alexdow
    I too am having these dreadfull colour management problems on the MacBook on the final release of 3.7.4. It only happens on the MacBook Pro it seems as a Powerbook G4 an G5 Dual 2 gig are behaving fine. I went back to using a Release candidate an this works fine. It expires in 4 days however - right in the middle of a massive job with a new client. I also finf that the new way of drawing previews whilst buffering the files is anoying - After a minute of shooting I have about 15 images in the block waiting for their prievies to be rendered. I have uptated the Camera firmware to v 2.2 and to be fair I can now capture about 33 frames per minute as opposed to 27 on the pre release, but the way it was done before was far smoother. I also found with the pre realease that when a clients art department tried to open the RAW files in 3.7.3 these could not be read - the preview was corrupt.

    We have been given an amazing piece of technology with the P30, a fast shooting, with relativly fast ASA speed/quality, and no Moiré to boot. However there seems to be a problem somewhere with this latest version. It can't be happening to everyone with a Macbook pro but it is affecting a lot of us I think.

    Any information woukd be gladly recieved by a lot of people.

    Good luck everyone!
    0
  • Darko1
    I just got word through support that they are working on this bug and are releasing a new build later today.
    0
  • Darko1
    They've posted the updated software in the C1 download section. Color profiling is back to working properly!
    0
  • roman111
    Darko,

    thank you very much for letting me know it was a bug. I will check the download section right away. I'm a little irritated for how much time and effort I've spent unceasingly trying to find a solution. ☹️ Technology can be so discouraging at times!

    Best regards,
    Roman


    --
    www.menyhart.net
    0
  • Guy Gonyea
    I just downloaded C1 Pro early this morning, May 3rd in SE Asia. Does this mean that I downloaded the updated version with the bug corrected or do I have to download again?

    Guy
    Contax/P20/Mac
    0
  • Anonymous
    Guy,

    This issue ONLY affected Intel-based Macs and it has now been solved.
    Previous Build was 3.7.4 2780
    The update was posted on May 1st, so you are good.


    Cheers,
    PhaseONEsupport
    0

Post ist für Kommentare geschlossen.