Saltar al contenido principal

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

Batches Not Starting in 3.7

Comentarios

6 comentarios

  • p1138w
    We are experiencing the same problem with 3.7 (as we did in 3.6) and use the same remedy. Hopefully this issue can be alleviated easily.
    0
  • Anonymous
    Sometimes a continued problem from version to version is the result of a common file.
    It is always best to completely UnInstall older versions so that a clean install is made of the updated version. Some files remain on system that can create issues. One of these is the Preferences.pf file.
    With the software closed, delete the Preferences.pf file in the Capture One Preferences folder and then restart the application for it to rebuild.
    Location: C:\\Program Files\\Phase One\\Capture One PRO\\Preferences

    If this fails, you can try deleting Previews cache folder. There can be some inconsistencies in the way it sees .work and .preview files created in previous versions of Capture One causing the batch queue to stall.
    By default the Previews are located at C:\\Program Files\\Phase One\\Capture One PRO\\Previews

    Yes, with this attempt, you will lose any adjustments made to images; and it will take some time for the Previews and Work files to regenerate but your RAW data is intact.

    Sincerely,
    k c
    0
  • p1138w
    We tried those suggestions and still no dice....same problem. Then proceeded to completely uninstall 3.7 making sure to remove all associated directories. Reinstalled 3.7. Batch problem resurfaced shortly thereafter.
    0
  • Anonymous
    We’ve seen this situation before when new drive locations are added to a machine, and the Process To location is changed around.

    Please try this at:
    C:\\Program Files\\Phase One\\C1 Pro\\Preferences and within this location is the FoldersList.fld file. With software shutdown, delete this file and then relaunch.

    My theory is that a Refresh of available locations needs to occur. The FoldersList.fld file is a list of develop to drives and locations. Deleting it and letting it rebuild or refresh may be a solution here as well.

    Let us know how this goes for you.

    Sincerely,
    k c
    0
  • soszlak
    Keith,

    I'm experiencing the same annoying problem that Greg described in his first post.
    The program (since v3.6) sometimes refuses to process the batch. Sometimes it even process some of the files, and skip the rest. Temp files are generated on the output directory, but no developed file is created. However thumnails inside Capture one are marked with the little green square as if it was processed normally.

    For some batches it takes me as much as four program restart cycles to complete my job. Something that gets worse because C1 doesn't keep record of developed files after restarting, so I have to check manually which files were processed and which ones didn't.

    I found the situation to get worse (but this could be subjetive) if I switch to other programs during the process.

    I've tried both of your suggestions without possitive results.

    Needless to say that using the program in this situation is a real PITA... so I hope you can keep investigating on the solution. I will gladly test any suggestion that you may have. All of this started back at v3.6 and continue to happen in v3.7

    Thanks,

    Sebastián.
    0
  • Anonymous
    Sebastián,

    There were Batch Processing issues in v3.6 which is why it is import to have a clean install of v3.7 – if you updated through the v3.6 software, this is where pitching the Preference files I mention above will typically help. To be absolutely sure you get a good install, a complete cleansing of Phase One from your computer is a must.
    Knowledge Base article # 1665 has detailed instructions for cleaning a machine.
    http://support.phaseone.com/KB/Home/Sea ... nguageID=1

    There are currently no Batch Process issues in Support Cases, so this problem is not prevalent in v3.7, …lets figure out what my be happening on your machine.

    What comes to mind with your explanation is that the files cannot be found. The .temp tile is more or less a place holder for the developed file.
    Be sure that folders or file names have not changed. The location of these cannot change either.
    Having other programs closed is a good start to be sure you aren’t taxing your system resources.
    If images are located other than the Local C: drive, be sure you have permissions to access these other drives and be sure there is no FireWall enabled that can affect file transferring. These concerns apply to the Process To location as well.


    Sincerely,
    k c
    0

La publicación no admite más comentarios.