alan_hodges

What I have been trying to do in Vuescan is to make my scan a raw file as I like to work in the Develop Persona in AP (at least to begin with) and believe I can extract more detail from my negatives by so doing (yes, I know you can work on jpgs in this persona but a jpg scan is lossy). I have not found this easy and there has been much experimentation. This particular image was an early effort and shows that my experiments were not going particularly well at that stage. I regret that I had not noticed the unusual stats. I have now gained a modicum of success with scanning to raw and will rescan the dodgy image. However, it would be very nice to know whether my poor scan was the cause of my two problems with inpainting. My grateful thanks to all responders.

Thanks for the suggestion that the Stabiliser is enabled but I have checked and this is not the case. The pixel dimensions of the document are 16008 x 961 @ 3200dpi. The .dng file I started with was 3.2MB but currently the .afphoto file is 2.42GB! I have no idea why the size of the file should have increased so dramatically, especially as I have done relatively little processing to the document. The inpainting brush is 66.4 px. I have failed to ascertain which brush I am using but, as I have not picked one, it will presumably be the default brush.

Thanks Lee D. No, I haven't been holding any key down when using the inpainting brush. After posting yesterday, I saved the image (with history) and then processed several other images without the problem repeating itself. I've just reloaded the problem image and used the inpainting brush with the very same results. That makes me think there must be something about the image itself which is causing the inpainting brush to misbehave. The image is a Vuescan .dng scan and I have processed dozens of similar scans without experiencing the same problem. All I have in the layers panel is the background layer, a levels adjustment, a curves adjustment and a high pass filter. I have tried turning off the filter (in case I should have applied it after completing the inpainting) but the problem remains....

Today the inpainting brush is driving me mad. I'm working in the Windows version with all drivers up-to-date. My image is black and white and peppered with small white blemishes which I'm trying to remove. Usually this brush lets me move from one blemish to the next very quickly but, today, it insists on displaying the inpainting progress dialog every time, slowing me down by a factor of about 7 or 8 per blemish. Worse still, now and again, I click on a blemish with the brush and it goes off on a frolic of its own, drawing a red line diagonally across the image and ending at the click point. The progress bar appears and I wait for well over a minute for it to do its stuff. Then it's press <CTL> <Z> to remove its depradations. It's never behaved like this before and I'll be grateful to anyone who can suggest a solution.

2.25 million files scanned but no threats detected. However, I have 1,103 files with a .lnk extension. Every photo I've accessed recently has one of these shortcuts and they are all useless, apart from those on the desktop. I must ascertain why this is so but I feel I'm in danger of exceeding the scope of this forum. My grateful thanks to all respondents.

I've created a new file with Notepad and confirm that a file with the same name has been created with an LNK extension. I'm now running a full scan with Kaspersky.

Sorry about the mistake with the file extension. Looking at it more carefully, Walt is right and my 81 year old eyes were not. LNK it is.

I've located the .Ink file and attached it. Windows classifies it as a shortcut in Explorer. IMG_20210714_124033-3.lnk

Hi, Walt, and thanks for your reply. Just tried your suggestion but nothing happened at all. No error message, Nothing. The INK file was created as before and Windows is still looking for the document file. I have tried saving to a different drive but no luck there either. I also tried a different local folder without success. Although I must have tried saving or exporting my document dozens of times, I have never seen an error message.

I have spent hours perfecting a document in AP but now I cannot save or export it. A shortcut (INK file) is created but double clicking on that results in an error message saying that Windows cannot find the file. Immediately after exporting or saving I normally see a progress bar but now there is nothing at all. I am loathe to shut down or I shall lose hours of work so any suggestions will be much appreciated. I have not done anything out of the ordinary in processing this document apart from using a very large number of clone brush adjustments. I have tried saving/exporting every possible file type that AP allows but nothing works.

I found the answer: it's the Hardware Acceleration. For some reason, AP doesn't like OpenCL. I don't really need it so it's just just a question of unticking the box.

Thanks for your suggestion @ChrisTheDev. However, I've now checked my Preferences and the Renderer is still the 1050 so no luck there, sadly.

For me the problem has been fixed by today's version 1.91 and I'm grateful for that. However, the update keeps throwing me out, notably when moving from the Develop to the Photo persona, though there are other occasions which I have not yet noted. If I load a RAW image and immediately hit the Develop persona button, it does it then. Another time, I was still in the Develop persona and using <Details> <Noise Reduction> <Luminance details>. It's annoying, especially if I've lost a lot of work . I know I can save frequently and I'll have to get into that habit or else go back to v.1.8.

I am using version 20H2 of Windows 10 and my gpu is NVIDIA GeForce GTX 1050 Ti with Max-Q Design. Thanks.

I have this problem too and it is serious because it severely limits what you can do with the shadows/highlights. In fact, it prevents you from processing a RAW file in the manner recommended by James Ritson in his video on RAW devlopment. See attached image.rail-0124.dng rail-0124.dng