Skip to main content

Comments

22 comments

  • Carsten Wortmann

    Pentax K3iii monochrome

    6
  • FirstName LastName

    If you support K3 monochrome, I will switch from lightroom to C1, lol

    2
  • Jean-marc

    Pentax K III monochrome please 

     

    2
  • Jean-marc

    Pentax KIII Monochrom 

    2
  • Jacques Linssen

    Any updates on this? 
    C1's default DNG-engine gives poor results, so support for the camera would be highly appreciated!

    1
  • Gaylord McCurdy

    Pentax K III Monochrome use too.

     

    1
  • Tim Miller

    Pentax K III monochrome please 

     

    1
  • Sébastien LEDUC

    Hello. I have a Pentax K3 Monochrom. My JPG files are ok. DNG files are ok for an instant, but they are immediately blurred. Like a soft effect.  If I apply and effect (contrast, exposition,...) it's sharp for 1 seconds and after stil not sharp. In Affinity Photo software I haven't the problem. 

    Support, said that " It looks like this softness is due to the Wrong Noise Reduction settings applied automatically, and we still do not support this camera model, which is why there could be some other issues. "

    They propose to set Luminance to 0 in the Noise Reduction tool.

    It works and now my DNG files are sharp.

    1
  • Sébastien LEDUC

    Jacques Linssen. It's my first step with my K3 Monochrom. Do you really need NR ? Even at high ISO files seems to be very very clean.

    You are right that Capture One should update...

    1
  • Gaylord McCurdy

    I think the softness in Capture One with this camera might be the demosaicing which is part of the Bayer color sensor array.  I think it needs to be disabled on a a monochrome camera like the Leica or Pentax, but not sure.

     

    1
  • Uwe Heimburger

    I'm also a K3-iii Monochrome and C1Pro user. My observations using Capture One Pro 22 - DNG raw files:

    • low ISO seems to work ... at least I didn't see bigger problems
    • higher ISO works bad. Details are lost. Observed this already at ISO 5000. I think as soon as (maybe) color channel based Noise Reduction sets in, things are getting out of control. Same as described above. For a short moment the preview looks ok, and a split second later it gets slightly blurred.
    • just tested: HDR merge of bracketed images doesn't work - no usable result
    • just tested: Pano merge of a number of images doesn't work - no usable result

    Hope there will be solutions because Capture One Pro is my main raw converter. Demosaicing needs to be skipped.

    1
  • Jacques Linssen

    @Capture One: The camera has been out 9 months now. Do you have some update? Would be highly appreciated, thanks a lot in advance!

    1
  • Carsten Wortmann

    Affinity Photo will support the K3iii monochrome with the next update. This would mean half of my tools are ready for my photos. It would be nice if this post got a green label so we know what happens next. With the support of the Pentax K3iii monochrome, CaptureOne can only get better. Thank you for your work.

    BTW, Darktable already supports the Pentax K3iii monochrome.

    1
  • Stefano Ghezzi

    I'ma capture one user moving from Sony to Pentax and I have a k3 III monochrome, which is the best tool right now since c1 doesn't really work?

    1
  • Stefano Ghezzi

    Thank you Jacques! i will give it a try

    I still have to decide what other tool to buy to manage the files while C1 updates.

    In a couple of day i've became able to work things out with the digital camera tool shipped with the k3iii mono, its very basic but substantially has all you need, also because, as you said, file out of the camera are very clean. Incredible camera 

    1
  • Walter Rowe
    Moderator
    Top Commenter

    All the feature improvements since version 13 are not enticing you to upgrade?

    1
  • Jacques Linssen

    @Sébastien LEDUC: That was also my finding, that setting Noise Reduction to 0 helps. But then I will have to apply NR in another program.

    @Capture One: Do you have an update on the K3iii Monochrome? Are you running into some issues with making profiles for the camera, or other technical challenges?

    0
  • Jacques Linssen

    Sébastien LEDUC Well there are certainly situation where I want to use NR. At e.g. pub-concerts ISO goes beyond 16.000, and a bit of NR helps a lot to clean up the shadows.

    0
  • Jacques Linssen

    @Stefano Ghezzi My main problem is that C1's noise reduction is useless for the K3iiiM files. I use Topaz AI for files where I want to remove noise. The good news is that the files are pretty clean, so it's not always needed, even at ISO 16k. My base setting for Noise reduction in C1 on the k3iiiM files is as follows:
    Luminance 0
    Detail 79
    Colour 0
    Single pixel 49
    I made a user-style that I apply on all files in a new folder after a shoot. These settings will work around the detail-erasing effect of C1's default NR-settings. There's still a bit of room to tweak, but if you go beyond approx. 20 for Luminance NR, the effect is very ugly (overly smooth)

     

    @C1-crew: Could you kindly update a tentative timeline for support for the K3iii Mono?

    0
  • Jacques Linssen

    Stefano, I'll simply stuck to C1 v.13, as besides the noise reduction, I don't encounter any issues for my workflow. If and when C1 provides the camera-support, I'll happily upgrade.
    However, experience learns that C1-support for new cameras can take up to several years. The silence from C1's team in this thread is also not very reassuring.
    If for whatever reason, you can't wait because your C1 does not work up to expectations with the K3iiiM-files, you will have to look around. Myself, I found the UI of the software supplied with Ricoh/Pentax-cameras a bit too "nostalgic". If it does the things you want on the Raw that you can't do in C1, then why not :) You can then export as TIFF and edit that further in C1. 

    One tip if you work with several programs on 1 photo: Wait with cropping until all other edits are done.

    0
  • Jacques Linssen

    @Walter Rowe  Good question! As I would really like C1 to improve, I'll give an honest and detailed answer, as this could help both C1 (in keeping customers on board) and myself (as I'd rather stay with C1 due to the speed, overall quality, workflow and familiarity.)

    Several of the post v.13-updates are really nice indeed (in particular recent masking/layer upgrades come to mind) Some are for very specific cameras only (such as tethering), some can be done very well in other software I already use (e.g. stitching or HDR, which I rarely do) and some I don't really care about (e.g. dehaze) But the camera-support is key to me. To achieve this, I found that Topaz had a better value-proposition for my current situation, whilst keeping most of the process in familiar C1. If C1 had been faster with camera-support (not only for K3iiiM, this has been an issue with other cameras too) I would already have upgraded to v.16.

    Or to reverse the question: Would you pay for a package that does not support your camera, and also does not provide any (tentative) timeline on the camera support?

    And we know C1 can be fast with support too at times. Even for some expensive or even exotic niche-cameras (think Leica M11 Monochrom, Phase One, Z9, ...) support was ready (nearly) upon release of the camera. NB - I also use some Leicas, and considering a Z9 or Z8, so absolutely no bashing intended :)

    0
  • John Schwarz

    +1 for request Pentax K3 Monochrom support.

    0

Please sign in to leave a comment.