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

"Only editable, online variants can be processed."

Comments

5 comments

  • Marcin Mrzygłocki
    Top Commenter

    I had the same problem last week. 23k photos tethered and on export I got an error message. Had to manually nail down that one exotic failure... No idea, how I got this one, as within a second or something another shot landed in, so it was not something like camera crash, truncating the file transfer by accident.

    1
  • Den Denyer

    My suspicion was a corrupt file too, but a simple copy of the offending image was accepted by c1 without complaint!

    1
  • BeO
    Top Commenter

    C1 never writes to any image file. "editable" in the context of C1 always means that you can make edits which are then stored in catalog (or .cos files). So my guess is that read-only or another file system attribute wouldn't matter, but I share the assumption that during tethering this file was not correctly identified by C1 as a file which can be edited in C1.

    Further, is there a filter I can use to identify such images? I

    Similar to this request, maybe upvote and add a comment for your case:

    https://support.captureone.com/hc/en-us/community/posts/9754059496605-Option-to-show-missing-offline-files

    2
  • BeO
    Top Commenter

    Yes, a simple check, and a real possibility for a software glitch. No worries John.

    On Windows, write-protected files can be xmp synced and star rated.

    EDIT: But only checked with C1 15.2.

    0
  • Den Denyer

    "Any chance the offending NEF file is marked read-only in the file system or isn't allowing write privileges?  I know C1 probably doesn't need to write to it, but perhaps it tries to open it with write privileges?

    It could also be that some other process has a lock on that file (maybe a backup program) so maybe reboot your system and don't run any other programs and try again."

    I checked in the filesystem but there were no file attribute flags set, and the file manager allowed me to move and delete the file without issue, too.
    My workaround was to just copy and paste the file and delete the original. Very irritating, as the only way to discover such a file is to either scan the thumbnails for the eye icon (Eyecon?) , or perform an operation known to trigger the error and then filter the files that were successfully affected, such as  moving everything to Selects or trying to apply metadata.

    Further, the laptop I was tethering with had no internet connection and no other software (Beyond Excel to track the shoot) running - There's a remote possibility that Windows Defender was interfering, though it didn't trigger any notifications or such, but I'll add a Defender exception to the shoots folder all the same and see if it happens next time.


    So far, no closer to even a good guess as to what's going on at this end. The mystery continues.

    0

Post is closed for comments.