メインコンテンツへスキップ

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

5.1.1 crashing and renaming RAW files???

コメント

4件のコメント

  • Paul Steunebrink
    The extra "<space>1" suffix in the file name is common with CO5 when it creates a file with a name that already exists. The suffix is determining it a the second version ("<space>2" is the third version of a file). You can observe this when you process a file multiple times to the same folder.

    The crash - for whatever reason - might lead to a status in which a file is renamed but the program has not yet update its counter for that number and renames it again after startup.

    Re. the crash: prevent renaming while CO5 is still generating proxies. Might help.
    0
  • Drew Altdo
    I'd be interested in seeing some specific examples. Screenshots and other details if you could provide them through a support case.
    0
  • Iain Philpott
    Last week I had exactly the same problem. C5 crashed after a new session had been started within the day's shoot folder created on the desktop. Re-booted it, opened the new session which was still there, shot the picture then while editing noticed it had used the filename/session name from the previous shot rather than the new one. Really annoying having to change 120 file names!
    0
  • Drew Altdo
    IJP,
    We sure would be interested in a support case with some details in regard to your issue. The OP is the only case that we currently have under investigation and haven't gotten details in regard to the issue in nearly two months.
    What we'd need is as follows, in a support case;

    1) 1 or more crash reports from your Mac. Please copy/paste into a document and send to us. You can find info about how to locate the log's here. http://www.phaseone.com/en/search/artic ... nguageid=1
    2) 1 or more files before and after the renaming
    3) Please inform at what state capture One is after the crash. Is it still open in processes or is it terminated?

    Also, since this was reported in 5.1.1, we'd like to ensure that your running 5.1.2 before digging into it.
    0

投稿コメントは受け付けていません。