Zum Hauptinhalt gehen

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

Capture One 10.2 bug or hard disk error?

Kommentare

7 Kommentare

  • Christian Gruner
    The best thing would be to contact Support, and then have them help you report the issue to R&D.
    Remember to include logs, recipe, processed files and raw files (including your adjustments, save as .eip). That'll speed up the fixing process.
    0
  • SFA
    In addition to Christian's advice one easy and quick check would be to turn off Hardware Acceleration in the preferences to see if that makes any difference to the situation.

    If it does check the drivers for your Graphics Card.

    In theory the latest driver should be the best option and usually is but sometimes that is not the case. So if you have the latest driver for your card but a problem if using the card, try stepping back on release of the driver.

    Obviously if the Preferences setting makes no difference ignore the advice above and wait to see what Support come up with.


    Grant
    0
  • RobiWan
    You can try to disable OpenCL.
    0
  • cdc
    The same thing happened to me more or less with NEF files on every export. Both jpg & tiff files were exporting like your black & white image up above. Turning off hardware acceleration and restarting seems to have fixed it for the time being. Running 10.0.2.
    0
  • joshkuhn
    I was just about to start a thread with this exact same issue. If I restart C1 I can export 1 or 2 images without issue, then everyone turns into a blob of green streaks. I will turn off Hardware acceleration and see if that helps.
    0
  • Benjamin Liddle
    If disabling hardware acceleration does help, we'd still appreciate the tech support ticket so we can document it and work to resolve it
    0
  • SFA
    [quote="cdc" wrote:
    The same thing happened to me more or less with NEF files on every export. Both jpg & tiff files were exporting like your black & white image up above. Turning off hardware acceleration and restarting seems to have fixed it for the time being. Running 10.0.2.


    I wonder if this possibly suggests that the internal routines for GPU driving, built when C1 is first started or, nominally, after and update that requires a rebuild because something has changed, have not been rebuilt or not been rebuilt successfully for some reason?

    If so deleting them and allowing new routines to be created may be the solution (and effectively what happened in the process that you described above?)

    There is a post in a anther thread that seems to suggest this sort of solution.


    Grant
    0

Post ist für Kommentare geschlossen.