Single Pixel adjustment not reflected in preview image

EnderWiggins

• 2015年07月13日 17:53

I have an issue with a red hotpixel on my 7D sensor. I just followed the instructions from the blog post here to remove it using the Single Pixel adjustment from the noise reduction panel:
http://blog.phaseone.com/how-to-fix-per ... ot-pixels/

Problem is, the pixel gets removed in the actual image when I'm zooming in using the loupe or just going to 100% in the viewer, but the zoomed out image in the viewer still contains the hot pixel. When I process the image, it is also correctly removed. I tried re-generating the preview, but it does not change anything, in the viewer the hot pixel is always there.

Anybody?

8.3.1., latest build.

0

• 

  Ian Wilson

  Moderator

  • 2015年07月13日 19:38

  

  I think that several things work like that - get sorted well enough if you look at it at 100%, or in the output, but don't show up in the preview - for instance noise reduction, correction of chromatic aberration and so on. What counts is whether it is really sorted in the final output, which it apparently is. I don't know why it doesn't look any different in the preview, but as several things seem to be like that and yet work OK, I wouldn't worry too much.
  
  Ian

  0
• 

  EnderWiggins

  • 2015年07月14日 06:07

  So it's not a bug, it's a feature?
  
  That's pretty disappointing. C1 is for sure not the fastest software out there for RAW editing and I would expect that the poor performance at least has its origins in a high quality realtime output on screen. Aperture is way faster than C1 (despite having seen no major updates since years) and it always held up its WYSIWYG approach. The image on screen was exactly what was put out by the engine when you exported a JPG, there was zero deviation.
  
  How can I know what images need some work if what I see on the screen is not what C1 has actually done to the image? I scan through my catalog, see a big red pixel in my face and think I need to correct it. And then I zoom in and....it is gone. Great. 😕

  1
• 

  Rob

  • 2020年08月30日 21:31

  By the way this bug still exists in the latest version of C1 20. Shows you the state of development.

  0

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