john_wheeler6

Neural Filter to de-jpeg, Camera Raw for tone, Hue-Sat narrow band color adjustment, played with Oil Paint filter on top of the rest.

A bit of a mood change.

Thank you for the detailed analysis of this problem. The open question what did the OP do to make it happen. I do not use Photoshop Elements (only Photoshop 20XX) and the problem to me looked very similar to soft proofing in ACR with sRGB other than the result instead of the OPs green. I took the OPs original post with the Green Areas and overlayed in a GIF a screen shot of the raw image brought in with the settings being sRGB in ACR. The highlight clipping warning was turned on. The red of the raw highlight clipping overlays quite well with the green area. I saw no real dependence on whether it was 8 bit vs 16 bit and no real dependence on the dehaze slider. Where there was a big difference was if ACR was set to preview in Adobe RGB (no green) and in sRGB where the clipping was easily seen. Full screen shots in ACR would verify the conditions of the ACR settings and if I am correct, it will show having it set to sRGB causes the issue. Also note when the file is saved and brought through the same path you don't see the red/green highlight clipping as the image is already in sRGB and reduced in gamut. So it explains that behavior as well. So other than the color being green vs red, it fits pretty well. Thought it was worth posting for consideration. John Wheeler

You're welcome JPDupre

This is the visualize spots mode. Click the keybaord shortcut "A" to toggle it on or off Hope that helps John Wheeler

When amplified with a curves adjustment Layer and ignoring the JPEG artifacts it appears that this is a complete vertical section of green to cyan coloring.It just appears that the red illumination from the RBG LED illumination is very slightly weak (e.g. 251-254 on the reds instead of 255) I am not sure how much uniformity is expected from the V850 or how it behaves when aged. Also, this does not seem to be related to having an image blurred on transparency mode and not on reflective mode. So I doubt this is a root cause issue with your original issue. Just my opinion of course. John Wheeler

Hi JPDupre I have an Epson V800 and no problems so far yet all devices are subject for needed repair/maintenance. I am not looking forward to having to do that myself yet I also figure it is better to "acknowledge reality" and move on to know solutions. That primarily would be giving the problem to experts for repair or based on repair costs the purchase of a new/different scanner. Not sure about Epson's cost for repair yet another resource (which I have not used) that works on scanners (including Epson V series) is: https://www.allrepair.com/what-we-do I am skeptical of doing repairs on my own even with online instructions on how to dismantle the V800/V850. It appears to be something with the mechanism that shifts the focus point between reflective vs transparency (transparency being 2 to 3 mm above the glass surface when it is working). Hope this information is of some help. John Wheeler

Hi Izzy Glad you are looking for where the banding was introduced as that is usually the best fix. Just to show that there are options when you have done all you can and still have banding, the image below was created by adding the splatter filter to the sky. I created a copy layer of the original and then separated the scene from the sky into two spearate Layers and then grouped those separated Layers (original Layer on bottom of stack was not included in the group. I added full spatter with the minimum smoothing on the sky Layer and then used a Layer Mask on the group to adjust the boundary where the splatter took effect using a very soft brush. I believe it removed most of the banding and simulated the original sky noise in the image. Hope that helps some John Wheeler

Hi Izzy Thanks for providing the color version. As it turns out the supplied images are highly compressed JPEG images. To have a decent chance of fixing the image having the full resolution image without compression (e.g. PNG or preferably TIFF) would be really helpful (a link to an online sharing site or dropbox etc since the file will no doubt be large in size). This will help rule out that the JPEG artifacts are contributing to the issue. Also, do you remember when the banding showed up Was it in the original scan, after some PS post processing , or after resizing and compression with JPEG. Those would be good clues. Or having the original scan. Did you scan in 16 bit and post process in 16 bit. That goes a long way in reducing the banding and also there are pretty easy fixes when converting to 8 bit at the end if needed. Hard to know without more info and better image for corrections yet the spacing of the vertical bars were at 64 pixels which is a multiple of the standard 8 bit compression JPEG blocks (it may not be that yet worth fulling out. I have attached copies of your color version that you posted showing only the Hue Channel and then the Saturation Channel. It shows where JPEG is hiding the compression which is in the color components especially where the image colors are pretty consistent (e.g. relatively flat skys). As you see there is not much of the color components to work with as it is all blocked up. Hope this helps for the next steps

Banding is quite common in slowly varying color backgrounds especially when the scans are 8 bit and not 16 bit. Fixes have more options with the color version so best if you could supply that for consideration of options for repair. John Wheeler

Hi @robert_bowring I am late to the thread yet here are a couple thoughts. It has already been suggested that having the raw file for the image would be helpful in tracking down the problem. It also might be helpful (and easier for you) to provide the full exact and original image files on a file sharing site (e.g. dropbox or other). The metadata can be examined that might also help in tracking down the issue. When it is all said it done since you were new using the iPhone, it is likely just pilot error. E.g. I have seen similar types of images when the panorama mode is set (maybe even accidentally) yet you are holding the camera horizontally. The camera is recording a set of images that it will try to stitch back together. Even if you hold the camera still and wonder what is going on, a slight tilt of the camera will copy parts of the image into different locations (as it did in your image). That of course is just a guess. yet having the original image file, the metadata stores which mode of the iPhone was being used which could narrow down what was going on. Not sure it is worth more effort since I believe its not likely to occur again as you gain experience on how to use the camera and camera modes. I will leave it up to you if you want to pursue it any further by providing a link on a shared service to the original files. Just my two cents on it (two quarters if you take into account inflation :) ) John Wheeler

I decided to crop, shift the left portion of image to the right and blend in with a Layer Mask. Made both Layers a Smart Object for some tonal adjustments and a linear gradient adjustment to bring out the mountains a bit. The fence in front was too much of a distraction for me so cropped to exclude it. Just some quick edits and hope you like my rendition.

How about purchasing on Amazon: https://www.amazon.com/Plustek-Spare-Slide-Holder-Scanner/dp/B000Y19Q46 John Wheeler

Three Hue Adjustment Layers targeting different narrow band colors. Minor masking

Thought I would try and add some color. Similar to a prior challenge First Gigapixel AI to reduce color artifacting needed for this technique Hue Sat narrow band around the near yellows and color shifted to give an interesting color Group Layers as Smart Object Gaussian Blur with Color Blend Add Camera Raw Filter for Clarity and Texture increase Mask beak to original colors

Gigapixel Ai at 1X to remove some JPEG artifacts in the color channels. Very narrowband shift of the oranges with Hue/Sat adj Layer Hue and Saturation Applying Dust and Scratch filter to reduce the color noise Masking and Content Aware Fill to isolate changes to middle flowers Use Camera Raw Filter to enhance tone, colors, and texture

- Some dust particles are attached by static attraction. Any mechanism that reduces the static charge on the sensor would be helpful yet the particles still need to be removed even when the attraction is negated. - There are many other options to neutralize) any static on the sensor already mentioned in other posts and many are much less expensive that the alpha source you mentioned - The alpha source does not address other particles etc that are on the sensor not related to static charge (some type of liquid droplet such as oil/water. So the alpha source is an incomplete solution at best - No the alpha source will not damage the sensor. My recommendation is to search for a better overall solution for sensor cleaning. Just my opinion of course.

Did a content aware fill of the very bright area, hand dodge and burn, threshold layer, and multiply blend with original image.

Hi Paddler4 It would help to know the specifics of what you took from LR to Photoshop and also back. You said ""moved it to photoshop to edit it further. I then brought it back into LR as a TIF." Did you use the LR Edit in Photoshop going for a round trip, or did you export from LR with a separate image, Save As in PS as another image and re-import to LR. If you used Edit in Photoshop, which option did you choose. Also, if the ACR versions are not identical, the image will come back as a new separate image. You usually get a warning about this unless you disabled the warnings. If the above posts did not already answer your question, then the extra details would be helpful.

You did not mention the specific Noritsu scanner yet sounds as it has not been properly maintained. It may just be out of adjustment or needs a part replaced. Noritus as with many commercial level products have detailed maintenance manuals and procedures to test for problems and how to repair. Here is a link to a service manual to several Noritsu scanners (PDF). A fair amount of work for proper maintenance yet pretty step by step. I would bet high end pro labs stay on top of this yet it would not surprise me if some smaller shops wait until a customer complains or the machine breaks to have maintenance / calibration done. The link gives an idea that it is a known process yet I suspect it needs someone that has the training to do so. The fact that you were brushed off could be that you are new and being marginalized or just did not want to be bothered (e.g. too busy with other stuff). The explanation from your supervisor does not make sense to me as the issue would show up on all scans even other types of scanners if it were in the negative itself. I have seen the color fringing yet usually from certain lenses in certain parts of the field of view along high contrast edges (which would also show up in all scanners). Hard to know how to proceed depending on the culture of the lab cause you could be bucking the system if they believe the scans are good enough because they don't have customer complaints. https://tinyurl.com/ybmxtcca

Thanks Fritz. I hope they help you figure it out and it would be great to hear any updates.

Looks as if you now have it narrowed down which is good. Apparently ACR engine or Graphics card related. Note that it is not uncommon to have bugs in the software for graphics cards that can create issues. Sometimes they are specific to the OS, ACR version, and or Graphics Card (and its driver version). So this is now a bit beyond what I can help as I do not have your combination of hardware/software. I do suggest a couple more things in your debug process - When viewing previews in LR, make sure you use just the Develop Module and only at 100% (1:1) viewing. - Make sure you are viewing the original image and not a Smart Preview To further the narrowing down of the problem, the Camera Raw Preferences (in Photoshop and Lightroom) allow custom settings for use of GPU separating out vewiing and image processing. After that, seeking help on the Adobe/Apple/AMD Radeon help sites or product support to narrow down the issue. If narrowed down enough to an unresolved issue, if you can find someone that can duplicate it on their system (I cannot) then you could submit a bug report to Adobe. Thanks for sharing your information as when I do upgrade to Catalina and a more recent MacBook Pro eventually, I will know to watch out for the potential of the issue you came across.

To help narrow down the issue a question and a suggestion You said the version of LR was 3.2.1 I am confused as that would be Lightroom 3. Are you using the most recent version of Lightroom Classic or something else? Though I am skeptical that it is related, you incoming image is in Adobe RGB color space and exporting you change to sRGB color space. This should not cause a problem yet who knows. Also, there is PS and LR vs exporting vs using Save and Save As To narrow down the issue I suggest a couple steps. - In Photohosp, go to Preferences and turn off all GPU acceleration - Also make sure that the Preferences are set to go directly into Photoshop and not through ACR - Bring your original image into Photoshop and verify at 100% magnification (or 200 or 400%) that there is not fuzzy areas - Note - make sure you keep the file in Adobe RGB and don't change to sRGB - Use the File > Save As command and save as a PNG file (so no lossy compression) - Bring that PNG file back into Photoshop and verify that the is no fuzzy areas I will assume that it will come back just as the original with no fuzzy areas yet if wrong, just report back the problem and don't follow steps below If you are at this point you have a baseline where you save the file and did not have a change. Each step below should be taken individually and not in combination by making the change in the steps above to test it out 1) Do the above yet first make sure that GPU acceleration is turned on in Photoshop 2) Do the above steps with the only change use the Save for Web legacy function (do not change to sRGB and leave that unchecked) (do not change image size) 3) Do the above steps with the only change being using the Export function in PS (with and without changing to sRGB) 4,5) Add GPU acceleration with #2 and #3 6-9) Change Preferences to go through ACR before entering into Photoshop and do the prior combinations. I think one of the above combinations finally ends up with the problem occurring the way you said in Photoshop and this should help isolate which area is the root cause. It is just the divide and conquer approach. You could use using LR or not as a variable and which format you save in as a variable yet not sure that would be necessary. Hope this helps track it down.

After using your original image I could not recreate you issue. Comparing your two provided images, I did fine a 75 pixel x 75 pixel grid of pattern that coincided with the appearance of blur. Note that is a preceived blur yet I believe is a subtle change in luminosity between the sharp and duller areas. You can see the pattern that I could extract in the image below. This is definitely in the processing pipeline somewhere and apparently not in the magnification or slight resizing. I suggest several things 1) Turn off GPU acceleration and see if it goes away. 2) Make sure you have the most recent versions of you OS, PS, LR, ACR, and GPU firmware (could be bugs discovered before) 3) Let forum members know which OS, PS, LR, ACR, and GPU you are using for further help.

Hi fritzunruh To diagnose the problem the original files would be needed for both. It was not clear that the full image you provided was the full original image or a smaller size and/or i bit when started at 16 bit. Are the other images screen shots of enlarged portions? The issue is that screenshots at non 100% viewing having gone through interpolation from the actual data and as well even at 100% typically go through color mangement so you are not looking at the original data. Also, was the image resized by the printer of did you resize yourself before sending to your printer. Resizing also goes through an interpolation and depending on the rendering algorithm can introduce anomalies. So first step is to have the exact files (or crops with no enlargements/reductions) from proper comparisons at 100% magnification by forum members. I have seen such issues yet the root cause is difficult without the exact original data bits. Just a suggestion John Wheeler