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

M10-P and M10-D support in v12

scott kirkpatrick
When I process M10 files in COne, the M10 default profile is applied. When I process M10-D files, only the DNG generic profile appears. It is possible to manually substitute the M10 default profile, but this is not a good idea, as the files are not the same between M10 and M10-D. I presume this is also the case with M10-P files. I don't have a -P, but the two newer M10 derivatives run the same firmware. The DNG default profile is a safe starting point, but still takes extra work. Will there be M10-DS and M10-P support with a profile in a coming 12.x upgrade?
0

Comments

10 comments

Date Votes
  • Ian Wilson
    Moderator
    Top Commenter
    Don't ask us - we're only fellow users. If you would like support for these cameras, tell Phase One using the support case system. That way they can gauge the demand by reference to the number of users asking for it.

    Ian
    0
  • scott kirkpatrick
    I have.
    0
  • Gary Coomber
    I noticed this too in C1 11. I put in a support request for the M10-P while C1 11 was the current version, I was told C1 do not comment on future camera support. I ended up building my own ICC profile using Lumariver. I'm still using C1 11 and at the moment do not plan on upgrading to ver 12.
    0
  • Mark Moore
    Is a new profile even needed? Are not the sensor and in-camera RAW processing really not identical between the M10 and its P/D variants? It seems strange to make changes arbitrarily.

    If the M10 (or any other) profile is not selected by default, you should be able to select it and then use the Base Characteristics "..." menu to set this as the default for the camera type that was used.
    0
  • scott kirkpatrick
    Yes, a new profile is needed. Even if the sensor is the same, the files are not. The M10-P and -D run different firmware from the M10. I did some side by side comparisons when I found that using the COne M10 profile did not work -- it blew out some highlights in the red channel.
    0
  • David Toose
    I also had to build a profile for my M10P using Lumariver. The generic profile does not look good.

    It seems that they metadata identifying the newer models is missing from C1, and this should be an easy fix. Hopefully soon
    0
  • Gary Coomber
    Has the M10-P been added to supported cameras in the latest release 12.0.1? I'm still running version 11 so can't see and couldn't see any news of newly supported cameras.
    0
  • SFA
    [quote="NN635937406568427633UL" wrote:
    Has the M10-P been added to supported cameras in the latest release 12.0.1? I'm still running version 11 so can't see and couldn't see any news of newly supported cameras.


    No new cameras added in 12.0.1 according to the release notes.
    0
  • Gary Coomber
    Thank you for confirming this.
    0
  • FirstName LastName
    We are at 12.1 and still no profile for M10-P

    the M-10 is unusable for M-10P

    Phase one should look at how camera raw does the color of the M10, really beautiful color and highlights. I will try to convert the profile for myself to C1Pro
    0

Post is closed for comments.

Didn't find what you were looking for?

New post