Skip to main content

"Edit with" creates file that cannot be opened by C1

Comments

15 comments

  • Ian Wilson
    Moderator
    Top Commenter

    What version of Capture One are you using? 

    Is editing of TIFF and JPG files enabled in Capture One preferences?

    0
  • Ivo HUTH

    Hello Ian,

    I use v15.3.1 and all 3 kind of files are enabled.

    Ivo

    0
  • Ivo HUTH

    This is what I get:

    0
  • Ian Wilson
    Moderator
    Top Commenter

    What happens if you change the ICC profile to Adobe RGB or to sRGB?

    Ian

    0
  • Ivo HUTH

    Same thing. Strange as it used to work great before, I only updated from 15.3.0 to 15.3.1.

    (And I installed Topaz Labs GigaPixel beta, but I also have the error when using Affinity and the error occurs before the actual external program is opened.

    0
  • Peter Uhlemann

    I have the same issue - C1 15.3.1 and Windows 10 21H1 and working in a session.

    When I "edit with" Photoshop I get the same message as you in the event window, but Photoshop is opened the processed RAW file is handed over to PS as PSD file and I can work in PS like normal. When I save the file in PS, it returns to C1 but it has 2 variants. The browser actually reflects the changes in PS - which is good at least.

    0
  • Ivo HUTH

    Thanks Peter

    so I’m not the only one with this glitch. Both the returned files are reflecting the edits of the program called from the edit with menu, so there is no need to downgrade. 
    In my case also a session, WIN 10 AMD.

    I will report this bug to C1.

    Ivo

    0
  • Michael Kluth

    Can you try to set the colorspace to Pro Photo and the TIFF format to compressed. This should work at least with Affinity Photo.

    0
  • Jeff O'Connell

    Add me to this same glitch.   I get the Error and the doubling effect for every file. 

    Windows 11 Pro, version 21h2, os build: 22000.795

    0
  • Jeff O'Connell

    Ivo,

    have you gotten anywhere on your support request?  I have one in as well and nothing as of now after a few days in "open" status.   To be honest I don't know what the expected SLA for request.

    0
  • Ivo HUTH

    Hi Jeff,

    no, so far no reaction and I don’t expect a reply soon. My other bug report stayed open while the problem was solved in the last update. Most of the support is / was done from Ukraine and the war is not helping.

    1
  • Ivo HUTH

    @Jeff O'Connell:

    This weekend I received a mail from support to give some more information and to send some log files.

    So it seems they are looking into it and a solution will be available soon.

    Cheers,

    Ivo

    0
  • Jeff O'Connell

    @Ivo Huth, would you mind telling me what they asked for so I can add the same to my ticket.

    -Jeff

    0
  • Ivo HUTH

    @Jeff:

    this is what support asked for:

    To have more info please:
    - let me know the exact camera model you're using
    - attach a sample of the RAW file (Are you experience this issue with all the RAF files or only with the particular ones?)
    - share a pack of your logs, so that we can look under the hood of the software and better understand what's going on: How do I retrieve logs?

    I didn’t send a RAW file as it doesn’t really matter what kind of file or from what camera is to be edited.

     

    regards,

    Ivo

    1
  • Jeff O'Connell

    Thanks Ivo,

    I submitted the same to my request.

    0

Please sign in to leave a comment.