Skip to main content

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

Capture One 8.3.3 released

Comments

22 comments

  • NNN635158767546269381
    Well done.

    M3 support ist much welcomed for us.

    Keep going 😊
    0
  • CFX
    Still no raw support for Samsung NX500 😡ðŸ˜ðŸ˜ 
    0
  • NNN635158767546269381
    Sarcasmus: Buy a Canon 😜
    0
  • NNN635371817475517903
    So still no performance improvements for the iMac 5K... this seems really short-sighted. Possibly the best hardware and value configuration for photo editing yet slower than a good MacBook? Is this just too much screen resolution for the internal design of Capture One? The software has always been able to deal with large files from the digital backs. Is it a matter of not being compatible with the GPUs in these machines? What's the basic issue here?

    Are most iMac 5K users happy with the performance and only those that are not are posting?
    0
  • Richard Seldomridge
    With Canon EOS M3 files, adjusting the white balance in any way causes the image to go black. Can anybody else confirm this? I just filed a support ticket. Can't believe I've been waiting for M3 support since this spring and it still doesn't work... the bugs in CaptureOne are driving me crazy.
    0
  • CFX
    [quote="NNN635158767546269381" wrote:
    Sarcasmus: Buy a Canon 😜


    Haha, I do have a Canon 5Ds R, and several digital backs including an IQ180 back.

    C1 Pro is supposed to be an application that develop raw files, but it is currently ½ a year behind, when Bridge and Lightroom have the ability of supporting new cameras within the week.

    It's not professional.
    0
  • Thorsten Kratz
    [quote="Richard Seldomridge" wrote:
    With Canon EOS M3 files, adjusting the white balance in any way causes the image to go black. Can anybody else confirm this? I just filed a support ticket. Can't believe I've been waiting for M3 support since this spring and it still doesn't work... the bugs in CaptureOne are driving me crazy.


    Hi Richard,
    I have the same problem. It is a Bug. With the pipette Tool you can change the white balance.

    Thorsten
    0
  • ALESSIO FURLAN
    [quote="space is the place" wrote:
    [quote="NNN635158767546269381" wrote:
    Sarcasmus: Buy a Canon 😜


    Haha, I do have a Canon 5Ds R, and several digital backs including an IQ180 back.

    ............

    It's not professional.


    Since September I have converted the workflow to Lightroom. Although I am a historical customer of PhaseOne. ☹️
    0
  • Jim_DK
    [quote="Alessio Furlan" wrote:
    [quote="space is the place" wrote:
    [quote="NNN635158767546269381" wrote:
    Sarcasmus: Buy a Canon 😜


    Haha, I do have a Canon 5Ds R, and several digital backs including an IQ180 back.

    ............

    It's not professional.


    Since September I have converted the workflow to Lightroom. Although I am a historical customer of PhaseOne. ☹️


    Sorry to hear that. Would you elaborate as to why?
    0
  • Jim_DK
    [quote="Thorsten_K" wrote:
    [quote="Richard Seldomridge" wrote:
    With Canon EOS M3 files, adjusting the white balance in any way causes the image to go black. Can anybody else confirm this? I just filed a support ticket. Can't believe I've been waiting for M3 support since this spring and it still doesn't work... the bugs in CaptureOne are driving me crazy.


    Hi Richard,
    I have the same problem. It is a Bug. With the pipette Tool you can change the white balance.

    Thorsten


    We can not repo this in house. From the error description, does changing OpenCL prefs (to off for display) have any effect?
    0
  • Richard Seldomridge
    [quote="Jim_DK" wrote:


    We can not repo this in house. From the error description, does changing OpenCL prefs (to off for display) have any effect?


    I've tried changing the OpenCL prefs and it doesn't help anything. Happens with every M3 RAW file but not with any from any of my other cameras.
    0
  • Thorsten Kratz
    [quote="Jim_DK" wrote:
    [quote="Thorsten_K" wrote:
    [quote="Richard Seldomridge" wrote:
    With Canon EOS M3 files, adjusting the white balance in any way causes the image to go black. Can anybody else confirm this? I just filed a support ticket. Can't believe I've been waiting for M3 support since this spring and it still doesn't work... the bugs in CaptureOne are driving me crazy.


    Hi Richard,
    I have the same problem. It is a Bug. With the pipette Tool you can change the white balance.

    Thorsten


    We can not repo this in house. From the error description, does changing OpenCL prefs (to off for display) have any effect?


    Same Problem. OS X 10.10.5. I have open a Support Case with RAW File.
    0
  • Maraker
    I switched back to lightroom, dxo. Ouh Yeah, my colors is back 😊
    CO1 never render colors correct way my nikons. d800, d7100, d7000, d90
    Impossible to fix bad colors with 100000 images. Support never fix anything what I ask. Only answer is change icc profile ☹️

    Colorchecker is my friend, and CO1 + colorcheckker = impossible.

    Good bye, and lucky for other users.
    0
  • CFX
    [quote="Maraker" wrote:
    I switched back to lightroom, dxo. Ouh Yeah, my colors is back 😊
    CO1 never render colors correct way my nikons. d800, d7100, d7000, d90
    Impossible to fix bad colors with 100000 images. Support never fix anything what I ask. Only answer is change icc profile ☹️

    Colorchecker is my friend, and CO1 + colorcheckker = impossible.

    Good bye, and lucky for other users.



    Colors is a very personal thing. For me, its one of the things that C1 Pro gets right. I'm working with both the Canon 5Ds R, Nikon 800/810, Phase and Leaf backs which I own. (but still, its important that Phase don't rest on the laurels just because they do colors nicely). Please see the rotation issue in another blog post and the lack of raw support for high end cameras.

    I have the color checker by the way, but never use it. I don't want my colors to be correct or "true". Today's clients are paying me for my personal style (IMHO).
    0
  • CAPTURE NIKON D700
    For NIKON user !
    for this color issue i suchest you to make a compression to a demo Silkypix Developer Studio Pro 6.
    0
  • Keith Reeder
    The "colour issue" isn't just a Nikon problem - lots of complaints from the Canon camp, too.
    0
  • Thomas Günther
    [quote="Keith Reeder" wrote:
    The "colour issue" isn't just a Nikon problem - lots of complaints from the Canon camp, too.

    I did some cross-checks after I read this and some other threats here.
    System I: MBPro i7/16GB RAM/2GB GC : Yosemite: C1 8.2.2 no problems: specially no colour problems.
    System II: iMac(2009)/intel core2 duo/8GB RAM/internal Graphics 256MB : Yosemite-El Capitan Beta1 to 6, GM: C1 8.2.2/3
    no problems: specially no colour problems.
    I have the feeling that the old iMac is faster in rendering with combo El Capitan/8.3.3 than with Combo Yosemite/8.2.2

    C1 renders colour on various RAW sources still as best!(but that is my subjective opinion, and this cannot be discussed!)
    It applies changes faster on originals: LR uses the embedded preview picture within the RAW file to display and does immediately render changes upon RAW data like C1/CNX/Phocus ... and aperture)
    The only competitor (with different rendering engine source) regarding to colour rendition quality is RPP. (AFAIK Phocus uses the same graphic framework as C1 (and Aperture)
    I personally do not like the rendering of PhotoRAW.
    Nikon CNX is a little bit more on the yummy colour side
    Hasselblad Phocus is a little bit flare compared to the standard rendition of all other mentioned Applications.
    Filetypes used:
    .dng(M8/M(240))
    .cr2(5D/5DII/5DIII)
    .nef(50/80/200/300/700/800)
    .rw2(Panasonic)
    .arw(Sony NEX)

    A tip: If i compare the quality of colour rendition, I take the respective files apart and render them without any preset values regarding film curves:
    1. The most neutral approach is to set film curve with all to "Linear".
    2. Then uncheck the WB upon Auto and do an "Auto Exposure Correction" an all pictures. This often leads to some overexposing, but this can be fixed with a mouse click.
    3. Process the resulting images as 16bit TIFF.
    4. Then compare these resulting TIFFS with Preview! Why? because there you have the ability to change the colour space by mouse click and the pictures are shown in pixel quality (if preview is preset to this option)

    just my 2cents, tom
    0
  • NN635770922769309595UL
    Those who are not happy with aspects of CO8 should take a look at Affinity Photo, a low cost and very good editor available from the MAS. You can call it from CO8 as an external editor, do your thing, and then CMD S to round trip back to CO8.
    0
  • HansB
    [quote="NN635770922769309595UL" wrote:
    Those who are not happy with aspects of CO8 should take a look at Affinity Photo, a low cost and very good editor available from the MAS. You can call it from CO8 as an external editor, do your thing, and then CMD S to round trip back to CO8.


    The round-trip doesn't work for me. CO is rendering the colors of TIFF and JPEG incorrect. Strong reds are shifting towards orange, strong yellows are losing saturation. Discussed for example here: viewtopic.php?f=55&t=20671. PO is aware of the problem. Support says, it will be fixed in a future release. I hope it's done soon. For the time being, round-trip is a one-way ticket for me, and the generated TIFF only a reminder.

    Affinity Photo works great. It is getting close tho replace PS for me.

    I am filing support requests for the inconsistencies and bugs I find in CO. Support does a good job and responds pretty quickly. There are still some things I am waiting for to be fixed. (At all PhaseOne staff: Sorry for making your to-do list longer. 😉 )

    Now about the colors: Here on my installation, Canon 350D, 450D, 7D, 1Dm3, 1DX and Nikon D300 and D3s RAW images are spot on. Really fully natural just like they have been in reality. I see some other software rendering the colors brighter, shinier and more intense, But if I want the colors to pop, I want to do it myself. Nevertheless, that's my opinion. I agree with Thomas248, a 'beautiful' color is a very personal thing.

    What I don't like so much is the Auto-Adjust function. 7 out of 10 images become too bright, mid-tones fading into brightness, shadows drawn into light. But that's a different story. Many of my images have hard light / shadow contrasts. Not sure if CO7 gave me better results, because my photographs have changed a lot since then.


    Regards,
    Hans
    0
  • Keith Reeder
    [quote="HansB" wrote:
    Now about the colors: Here on my installation, Canon 350D, 450D, 7D, 1Dm3, 1DX and Nikon D300 and D3s RAW images are spot on. Really fully natural just like they have been in reality.

    Which are all older cameras.

    We've pointed out many times in other threads that the broken profiles people are complaining about are all for newer cameras - old bodies' profiles are usually much better.
    0
  • HansB
    [quote="Maraker" wrote:
    CO1 never render colors correct way my nikons. d800, d7100, d7000, d90


    Keith,


    You are right about for quite a number of cameras from new camera generations of both Nikon and Canon. Never doubted that.
    But in this thread it started with the list above. They are not really new ones. D800 was presented in 2012, D7100 in 2013, D7000 in 2010 and D90 back in 2008.


    Regards,
    Hans
    0
  • Maraker
    Oh man, I reinstall 8.3.3 and colors are much better now, I don't know what is a problem early. Now saturations and color is good.
    Maybe I can switch back to C1 now, I hate to adobe subscriptions.
    I thinking problem is too many upgrade, now clean install is extreme better.
    0

Post is closed for comments.