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

Processing files with v6.2.2

Comments

6 comments

  • Paul Steunebrink
    Hmmm, strange. Are the images stored on a local disk? What version of OS X are you using? Did it work fine with previous version of CO 6? Any info in the Event log (Window menu)?
    0
  • Mat Fretschel
    The images are stored locally. Currently shooting to my Shared folder. I am running OSX v10.6.8. My previous C1 version was 5.2.1. Due the constant problems upgrading software, I can't afford to update software every time a new version is released. It was recommended that this version (6.2.2) was stable and worth trying. Nothing in the Event Log except for "the processing queue has been paused."
    0
  • Paul Steunebrink
    Maybe a long shot, but if you have not recently repaired permissions, this may be a good moment.
    0
  • Jeff12
    just went through the same issue and believe my session somehow was corrupted during the shoot. It seemed to me and my crew that the problem began either when I was shooting while c1 was processing a few jpegs or when we started a second process queue while the first was processing.

    I was also unable to process when I replaced the session, Stopped and restarted the queue, restarted my machines , repaired permissions and finally did a clean install of C1.

    I can process from newer or older sessions and when I drag selected files onto the desktop and then the C1 alias in the dock.
    0
  • Mat Fretschel
    Hey Jeff.

    I did the same thing. Wiped my machine clean. Downgraded to v6.2.1 Watched it crash a few times while processing out v6.2.2 files. Wiped my machine clean again. Repaired permissions. Re-downloaded v6.2.1 and finally started shooting late today. At the end of business today, I've taken all of two shots (but it looks like processing works and crashes are at a minimum). Of course, I just jinxed that.
    0
  • Eric Brazier
    I ran into this problem (or a problem like it) yesterday on-set.

    I believe I've found a simple workaround solution to this 'bug':

    Do not have multiple recipes enabled.

    Give it a try; let me know if it works or is applicable to your situation. I'm going to do further troubleshooting today on-set.

    Also, did anyone else experience this Events Log error the FIRST time they started the batch queue (but not subsequently):

    Description:     There was an error during the processing of the output file.
    File:             /Volumes/Photo Capture Disk/Sears Houseware VE103D111 (Single Monitor)/Capture/611_47042_VE103D111/611_47042_VE103D111.EIP
    Domain:         com.phaseone.captureone

    Cheers,
    Eric
    Code:         1
    0

Post is closed for comments.