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

Heal/Clone on offline files

Implemented

Comments

4 comments

  • Lily

    Hi Andy,

     

    Thank you for feedback on Capture One - this is always welcomed and encouraged among our users and we appreciate the time you've taken to contribute towards the development of the software.

    I have forwarded your comments and suggestions to our Product Management team as something to consider in a future release.

    Whilst we cannot comment on future releases, we take all suggestions on board and hopefully your feedback contributes towards a future version of Capture One.

    0
  • SFA

    Andy, that an interesting comment.

    I suppose that, if one was using a large enough preview file and intending to output a jpg which was at least not larger than the preview, that might work in some way. You could then drop the original file completely. Otherwise just repeat the exercise when access to the source file is available once again.

    0
  • Andy Rudiak

    Hi thanks for your answer.
    In my workflow, I limit the time when the source disk (containing RAW) is attached. I believe that this is a safe style of work. The ability to use the clone / heal tool while the file is offline would save a lot of time, the disk would only be attached twice - when importing and previewing, the second time when post-processing updates and exporting.

    0
  • SFA

    Capture one has limited editing features available when working with offline images and catalogs. No editing options for off-line images if using sessions.

    Capture One makes extended use of access to the original source files for many of the more advanced editing features where working with the full data available in the source file is important for the best results Things like Cloning and Healing would come into that category.

    Presenting the results in a reduce resolution preview file after working with the full system is viable. It would be consistent wiht all other reduced resolution processing.

     

    Working with the reduced data of a preview and then applying that to the greater amount of detail in an original source file is probably less satisfactory in terms of results and programming options.

    I'm not sure why you are reluctant to have the drive attached.

    If you are trying to protect a massive catalog then I would highly recommend that you consider working on currently active projects in sessions on an attached drive (SSD would be ideal) and then take the result into your catalog when the project is complete. Do that would seem to offer benefits all round.

    You could also use a smaller working catalog instead of a session and then move stuff when work is complete.

     

    I suggest this as it provides you with an immediate solution.

     

    -1

Post is closed for comments.