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

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

Problem after updating engine to capture one 7

Permanently deleted user
I just tested this version 7 and opened session i shot today with CO6. I found interesting bug, after updating engine to Capture One 7 in Base Characteristics section i get stripes to processed file. No matter if i process 8 or 16 bit same issue is there. Here's example of the problem, i tested with few different files and no difference.

Kari

https://dl.dropbox.com/u/2380926/stripes.jpg

https://dl.dropbox.com/u/2380926/stripes2.jpg
0

コメント

10件のコメント

日付 投票
  • Drew Altdo
    Hey Karl,
    Check the preferences. Since OpenCL can now be used when processing files (for added speed) there is now an extra layer of depth to the process engine. As such, if your Graphic Card is running out of memory during the process it may leave the files as you have shown. Changing the OpenCL during Processing option to "Never" should solve this.
    We can look into the issue further in a support case with your system specifics should the error persist.
    0
  • Permanently deleted user
    So do you think AMD Radeon HD 6750M 512 MB is not enough for processing utilizing OpenCL?
    0
  • Drew Altdo
    [quote="Kari21" wrote:
    So do you think AMD Radeon HD 6750M 512 MB is not enough for processing utilizing OpenCL?


    No, OpenCL suggests 1GB or more for AMD and Nvidia. Sorry ☹️
    0
  • Permanently deleted user
    Thanks a lot, that solved my problem. But it's ok to keep OpenCL for display on automatic?
    0
  • nggalai
    [quote="Kari21" wrote:
    Thanks a lot, that solved my problem. But it's ok to keep OpenCL for display on automatic?

    It works here (also Radeon, also 512 MiB), but curiously I find CO-7 runs a tad faster with OpenCL disabled. Or rather, it seems more responsive. I have to compare some more methinks.

    This is with 18MP DNG files.

    Edit: Drew, the 1 GiB information is something that should be included in the System Requirements documentation and/or the OpenCL section in the FAQ. I don’t think it’s mentioned there yet.

    Cheers,
    -Sascha
    0
  • Drew Altdo
    [quote="nggalai" wrote:
    Edit: Drew, the 1 GiB information is something that should be included in the System Requirements documentation and/or the OpenCL section in the FAQ. I don’t think it’s mentioned there yet.


    It is in the release notes.

    [quote="Kari21" wrote:
    Thanks a lot, that solved my problem. But it's ok to keep OpenCL for display on automatic?


    Should be just fine for Display.
    0
  • Permanently deleted user
    I have been shooting tethered today with P45+ and if OpenCL for display is on, CO is sluggish and captured files appears much slower. After turning it off all is fast and smooth again.

    Kari
    0
  • nggalai
    [quote="Drew" wrote:
    [quote="nggalai" wrote:
    Edit: Drew, the 1 GiB information is something that should be included in the System Requirements documentation and/or the OpenCL section in the FAQ. I don’t think it’s mentioned there yet.


    It is in the release notes.

    Yes, but not on help.phaseone.com. That’s what I meant. 😊

    Edit: Just checked again – there’s no mention of 1 GiB of VRAM for OpenCL processing in the CaptureOne 7 Release Notes, either. Just a mention OpenCL won’t work at all on Mac OSX Mountain Lion.
    0
  • Drew Altdo
    http://i46.tinypic.com/2lbov2f.png
    0
  • nggalai
    It was just a suggestion, not my being obtuse, Drew. Point is, in the documentation OpenCL is mentioned about twice, and the 1 GiB VRAM thing is mentioned in the “recommended†section, next to “fastâ€. Well, obviously a fast and large memory video card is “recommended†when doing graphics stuff, isn’t it?

    The documentation though doesn’t mention that OpenCL may need 1 GiB of VRAM to work properly when processing files, and the Auto selection in CaptureOne apparently doesn’t turn it off when there’s not enough free video memory. Hence this thread got started. Hence my suggestion to spell it out in the FAQ rather than leaving ii on these forums only.

    No offense meant. 😊

    Cheers,
    -Sascha
    0

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