Skip to main content

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

When making adjustments to an image I'm getting black areas

Comments

9 comments

  • Permanently deleted user

    I reported the same issue to P1 a month back. Are you using a 27 inch iMac? My support case was closed saying that they don't know when they will fix the issue. Very disappointed, as it makes the program basically unusable, since every time to you make an adjustment you get this flashing or black blocks.

    The only workaround I have found is to set the image preview size (settings -> image -> preview image size) to a very small number like 1024. This forces C1 to not use a preview when editing and prevents the glitches. It does make editing much slower since it has to render the raw data each time.

    0
  • SFA

    Have you tried turning off the "Use Hardware acceleration" options in the Preferences?

    It's a quick test to see if it changes anything. If often does, but not always.

    0
  • Permanently deleted user

    Yes I tried disabling hardware acceleration, to no effect.

    0
  • ---

    maybe you have tried this already....

    1. does the problem also occur with a fresh session and browsing a folder with raw files but without any (c1) junk files on you start HD ? 

    2. do you have other software running ?   startup items ?  if yes deactivate them for a test, activity monitor is helpful to see what is running in the background.

    3. clean all system caches  ( https://www.maintain.se/cocktail/ ) remove everything c1 / p1  from the system ( https://apps.apple.com/us/app/find-any-file-faf/id402569179?mt=12 ) and reinstall it

    4. create a new user for a test & reset pram

    0
  • SFA

    Ok.

    This seems to be more commonly reported on the Mac forum than Windows.

    However I am currently setting up and learning about a new Win 10 PC with only C1 installed in addition to what comes with Windows 10 and I have once seen some oddly processed blocks on the screen during editing.

    They vanished quickly. 

    It seemed to be simply a processing delay at one point in the process that made visible that which our eyes do not normally see.

    One thing I have noticed is that getting the system to use the dedicated GPU was not easy. It preferred, for most processing, using the CPU and internal Intel GPU. The dedicated NVidia only appeared to be active during batch output testing and even then the Intel internal GPU was slightly preferred.

    Having now forced the use of the dedicated GPU (and this being a laptop I use on my lap) I think I may have some idea why.

    The machine now gets rather warm - which it never did previously. To be quite honest I have not noticed an especially obvious improvement in on screen performance although first impressions are that output batch processing seemed faster by a significant factor.

    Interestingly having just looked at the three "power saving" options available in the windows controls (via Dell) the Performance option, which I had open,  has just disappeared from the screen as I selected the "Dell" balanced option above it. It seems to have completely disappeared never to be reselected.

    Research required. Are the machines really taking over?

    But despite that I think the main point seems to be that internal power management can be applied in ways that have potential to temporarily and intermittently disrupt power hungry processing steps and these activities when combined with whatever activities the system is running at the time (may not be visible) might well cause display presentation delays which become visible - in much the same way that a failing electrical ribbon strip may present as on-screen glitches because the signal is not arriving at the expected time. 

    More permanent problems on output files could be symptomatic of something similar under-the-hood but things that do not wait around for possible rectification of the problem in the same way the a screen can do.

    0
  • billtils

    I get the same on my iMac running Catalina but not on my MacBook Air running BigSur. 

     

    0
  • billtils

    Update:

    Works fine on the iMac with BigSur and hardware acceleration at auto for display and processing.   Got the blocking/white-outs when display acceleeration was at "Off".

     

     

    0
  • Michael Irvin

    I have the same issue with some files.  The problem shows up with TIFF files that had been round tripped out to Topaz sharpener AI, or Denoise AI.  It doesn't show up on NEF, PSD, or DNG files.  So far only on files that were processed last June/July from a BIF shoot on my D6. Going back and re-creating the "round trip" with the original NEF files the problem does not exist every thing works as expected.  That makes me think, at least in my case that there was a problem with the TIF files coming back form the Topaz plug in.  At first I thought just regenerating preview would solve the problem, but that didn't work.  

    0
  • Michael Irvin

    Spent some more time with the issue found I had more files exhibiting the behavior than I originally thought.  Did resolve the issue by removing the files from the catalog.  ie.. putting them in the trash, and deleting from the catalog.  Re-syncing the folder and re-importing the file.  That cleared up the problem for me.  I had tried to repair/verify the catalog but didn't seem to solve the problem.  Fortunately for me it only effected a few dozen files.

    Mike

    0

Post is closed for comments.