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. ⚠️

Leica M10P not supported

Comments

7 comments

  • Permanently deleted user
    Hi Patrick,

    I guess the M10-P will be supported in a next update. Meanwhile, using DNG neutral profile and curve seems to be a rather good alternative.
    I am not sure you would be able to create your own profile. A colour profile can be created for sure when a camera is already supported by Capture One, by shooting a target in very well defined conditions. But when a camera is NOT supported, it means that you have to enter into development lines with specific tags related to the camera.... The best would be to wait a little time and use DNG neutral as base characteristics meanwhile, IMHO.
    Robert
    0
  • Paul Steunebrink
    I fully support what user tenmangu81 answered. An additional note.

    DNG support for non-supported cameras is improved. I refer here to native raw DNG (straight from camera, not converted). Whether this applies to your Leica M10P files you can easily check.

    In the Base Characteristics tool, the ICC Profile is DNG File Neutral. But the Curve field holds the secret. It should go to DNG Standard for new images. If it is Film Standard, try DNG Standard instead.
    0
  • Patrick
    Thanks Tenmangu81 and Paul,

    will work with DNG neutral for some time and see how it goes.

    Patrick
    0
  • Gary Coomber
    I've been submitting support requests for the Leica M10P since its launch, so a request for version 11 of C1 and another request for version 12 of C1. I only upgraded to version 20 of C1 as the release notes referenced a fix to Leica M10 DNG files. Perhaps I was being a bit optimistic!

    If you look in C1 at the list of ICC Profiles and the supported M cameras you will notice there is not a specific mention of the variants for example M9P, M240P. I believe this will also be the case for the M10P if it is ever supported as the sensors are the same between standard models and the P variants. So I guess if support ever gets added we will still just select the Leica M10 profile.

    I raised this again recently with support and the response was the following:

    "Implementation of camera support by the R&D department can indeed take some time. But as I see, multiple requests have already been sent in regards to the camera support in question. Hereby, its release should be expected soon."

    Surely as the sensors are the same this is a very quick fix for C1.
    0
  • Permanently deleted user
    An M10-P user has encountered some trouble when using the M10 ICC profile : the new noise reduction algorithm doesn't work properly for noisy images. The "colour" noise reduction shows awful behaviour (turning colors to gray) when pushing the cursor above 10 or 20, and "luminance" correction shows very strong pixels artefacts when pushing the cursors at values larger than 50, for instance. The same is obtained when using DNG neutral, actually. The cursors should be accordingly pushed with caution...
    0
  • Patrick
    tenmangu81] wrote:
    An M10-P user has encountered some trouble when using the M10 ICC profile : the new noise reduction algorithm doesn't work properly for noisy images. The "colour" noise reduction shows awful behaviour (turning colors to gray) when pushing the cursor above 10 or 20, and "luminance" correction shows very strong pixels artefacts when pushing the cursors at values larger than 50, for instance. The same is obtained when using DNG neutral, actually. The cursors should be accordingly pushed with caution...


    This is exactly the problem I have as well. Thanks for the hint.
    0
  • Patrick
    Patrick6] wrote:
    tenmangu81] wrote:
    An M10-P user has encountered some trouble when using the M10 ICC profile : the new noise reduction algorithm doesn't work properly for noisy images. The "colour" noise reduction shows awful behaviour (turning colors to gray) when pushing the cursor above 10 or 20, and "luminance" correction shows very strong pixels artefacts when pushing the cursors at values larger than 50, for instance. The same is obtained when using DNG neutral, actually. The cursors should be accordingly pushed with caution...


    This is exactly the problem I have as well. Thanks for the hint.


    I seems to me that this problem is not solved completely but better than before with the new version 13.0.2.19 (20.0.2). Could someone confirm?
    0

Post is closed for comments.