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

Just a Simple Question: When ImgCoreProcess ERROR will stop?

Kommentare

7 Kommentare

  • Paul Steunebrink
    OK, you suffer a fatal error repeatedly from the first release of CO 4 til today (4.8). Different hardware, different OS. Still that problem.

    Now I will be the last one to say that CO4 is error free (never seen error free software lately), but has it ever occurred - without to offend you - that it might be caused by something in your system's setup or something else to which Capture One is not resistant?
    0
  • Nando From Brazil
    Paul, i work great with photoshop that uses a lot of RAM and never crashes.

    A lot of Capture One users know this name: ImgCoreProcess.exe ERROR
    I suppose that many "support cases" about it are open...

    It is like "bad preview" case... A lot of time and versions to Phase One correct V4 bad preview (now is OK)

    Sorry about my English, it is like (or as good) "ImgCoreProcess.EXE error" 😂
    0
  • Nando From Brazil
    [quote="Paul_E" wrote:
    OK, you suffer a fatal error repeatedly from the first release of CO 4 til today (4.😎. Different hardware, different OS. Still that problem.

    Now I will be the last one to say that CO4 is error free (never seen error free software lately), but has it ever occurred - without to offend you - that it might be caused by something in your system's setup or something else to which Capture One is not resistant?


    ImgCoreProcess.exe error appears more times when i use CROP/ROTATE or when i use (and pan with hand) 100% image view (to adjust sharpen)
    ImgCoreProcess.exe error appears more times when i work with "medium to big files" (my EOS 5D and 50D files) . With OLD Canon 20D files or Rebel files, all is OK.

    I do not use "overclock" and my computer have no problem with overtemp etc.
    I do not have bugs with another softwares (that i can see)
    I have FSECURE antivirus and also with antivirus off, ImgCoreProcess.exe error persists.

    Thank you!
    0
  • Paul Steunebrink
    I was more thinking in the direction of ICC profiles: monitor profile in the first place, next the output profile, and last the input profile.
    0
  • Paul Steunebrink
    Do you perhaps have Adobe CMM installed?
    0
  • Nando From Brazil
    Hi Paul,

    My monitor icc comes from Eye One calibration. I use only one monitor.

    For "input" icc i use "auto" from Capture One (50D camera profile for 50D, 5D for 5D) i also have olds Etcetera profiles, for 20D...
    ... (about input or camera profiles, Capture One 4.7 or 4.8 comes with 2 profiles for EOS 40d - 40D and 40Dv2, more saturated and rich colours, a very good icc) Why software CO comes with only one profile for EOS 50D? ...

    For output i use basic sRGB and some times aRGB.

    I do not have CMM or Adobe Gamma (or any other gamma corrector) installed.

    Sorry if i can not understand your question (bold) :
    "I was more thinking in the direction of ICC profiles: monitor profile in the first place, next the output profile, and last the input profile. I was more thinking in the direction of ICC profiles: monitor profile in the first place, next the output profile, and last the input profile. "

    Thank you very much. (I will try change my sRGB output profile - i have 2 ??? in my computer and 2 are listed at CO menu... )
    0
  • Paul Steunebrink
    Hi,
    As you see I try to determine what might cause the specific error. Thanks to your description:
    ImgCoreProcess.exe error appears more times when i use CROP/ROTATE or when i use (and pan with hand) 100% image view (to adjust sharpen)
    ImgCoreProcess.exe error appears more times when i work with "medium to big files" (my EOS 5D and 50D files) . With OLD Canon 20D files or Rebel files, all is OK

    I was suspecting an issue with color management or color profile. To explain the line you did not understand entirely (due to cryptic use of English on my behalf) my prime focus was on the monitor profile, in the second place I suspected the output profile and the input profile I suspected last. You removed suspicion of the two latest although it is a good idea to try another version of the sRGB profile.

    Based on your latest reply, I suggest to run a test with your current monitor profile (from Eye-One calibration) on a few images in particular zooming in and rotating, and with a standard sRGB profile. You can change your monitor profile by right-clicking your desktop, Properties, Settings tab, Advanced, Color Management. You might have a localized version of XP with different names.

    I suspect either a problem with your monitor profile or your graphics adapter or its driver. My suspicion is based on the fact that problems arise when you put pressure on the graphics components of your setup while working with larger images and during intense video movements (panning zoomed in image, rotating).
    0

Post ist für Kommentare geschlossen.