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 Monochrom files not being read after updating to build 13.1.0 earlier today

Antonio Penate

It's almost like the files are not there...  all I see is a blurry preview.  The files ARE in the computer (I can see them in Finder).  I've regenerated previews and nothing happens.  Also, I can't edit them with an external editor, either.  Anyone else having this problem?  It's only with M10 Monochrom files...  all the others behave as expected.

2

Comments

17 comments

Date Votes
  • Patrick

    Same with me. Previews of M10M files are totally unsharp. In this state CO 20/13 is totally useless for working with M10M files. I sent a request to technical support.

    0
  • Antonio Penate

    Patrick, I removed the files from my catalog and added them again.  They are now sharp.  I lost any adjustments I'd made to the files prior to the update, but I haven't had the camera long and they were nothing serious - just shots walking around and getting a sense for the files.  I think problem lies with the update process itself.  You may want to try it with some of the files that are problematic - delete from catalog and add them back - to see if it works for you.  It shouldn't happen, but better than nothing.  I had also sent a request to technical support.  Let's see what they say.  BTW no issues with files from other cameras (SL2, CL, Q2 or other makes)...

    0
  • SFA

    Were these files already in your system and known to C1 before the update?

    (I assume they were but thought it best to ask.)

    If a Catalog is in use was the catalog updated when first opened in 13.1? (Not being a catalog user I don't know if that would be required.)

    Were there any messages about updating the processing engine for the existing images?

    Did you try the option of creating a NEW variant? That might be interesting to compare with the option to remove and re-import.

    Of course one could simply import another copy for testing purposes and not lose the pre-existing edits on the first copy.

    0
  • Antonio Penate

    Yes, in system and known to C1 before update...  Yes, catalog was updated when first opened in 13.1...  No messages whatsoever regarding engine...  And I couldn't do anything with the files - create variants, edit in another program, etc.  It's like C1 just couldn't handle them at all, except for showing low quality preview.  But it all worked before the update...

     

    0
  • Patrick

    Antonio, thanks for your reply. I am working in sessions and I removed all proxy and sessions files. Then I created a new session and the new previews became sharp. As you mentioned with this approach one looses all adjustments for prior edits.

    0
  • Antonio Penate

    Glad to hear, Patrick.  Not ideal, but at least we know how to get around it (although losing prior edits)...

     

    0
  • Stephen Kimmel

    Same problem here.  Has anyone put in a formal ticket to support?

    0
  • Antonio Penate

    I believe both Patrick and I have done so (opened formal ticket)...

    0
  • Patrick

    A tip from the Leica User Forum: Toggle the film curve and the M10M files will redraw. No need to re-import again. No loss of earlier edits. It works for me.

    0
  • Antonio Penate

    Thanks, Patrick.  I've already re-imported, but will keep this in mind for the future...  

    0
  • Patrick

    The „toggle the film curve“ trick only works temporary. As soon as a session is closed and opened again, the previews are unsharp again and one has to toggle the film curve again. Re-importing the images might be the more comfortable option as long as CO does not fix the bug.

    0
  • Mark Nockleby

    I see I'm not the only one with this problem.  blurry M10M photos and processing the files for output produces error messages instead of output. I'm using a previous session generated from the previous (working) version of Capture One 20.

    0
  • Bernd Beykirch
    • Edited

    Same with me. With the old version it worked perfectly with the Leica M10 Monochrom, the latest version does not work. Trying to export a Leica M10 Monochrom DNG file ends up with the error code 50:

    Beschreibung: Bei der Verarbeitung der Ausgabedatei ist ein Fehler aufgetreten.

    Datei: /Volumes/Bilder/Locations/2020/2020 Deutschland/2020 Starnberg/M1001715.DNG

    Domain: com.phaseone.captureone

    Schlüssel: 50

    0
  • Bernd Beykirch

    I have found a workaround without losing any adjustments. First of all, export your Leica M10 Monochrom DNGs from your main drive to a second one including any adjustments you have done. Then you can delete the DNGs from the catalog and the main drive. Afterwards, import the DNGs from the second drive back to the main drive and you have your pictures back including any adjustments.

    0
  • Andres Nicholls

    Hey guys, has Capture one offered any solves that do not require to loose the adjustments? This seems to have been going on for a while, but i can't see to find a solution from this. Now all my catalogs are updated to 13.1 and I wish i could go back to the previous version and forget about this new one, but now i can't 

    0
  • Antonio Penate

    Hi Andres, I submitted a report to Capture One when I first noticed the problem. A few days ago - a week or two ago - they responded that they confirmed it was a bug and they’d be working on a solution. No promises it would be on next release, but they’re working on it.

    0
  • Andres Nicholls

    Thanks so much Antonio. I guess for now I'll import any new images to the previous capture one so I can work on them. Thanks again man. 

    0

Post is closed for comments.

Didn't find what you were looking for?

New post