Robertl594 Loc: Bloomfield Hills, Michigan and Nantucket

Hello all,
I have been experiencing some very strange artifacts coming from exports in Lightroom. Here is what is happening:

I shoot multiple NEFs in a focus stack sequence. I import them into LRClassic. I then export them using the LR export function into a new folder. I open the stack using helicon, then render.

Certain images have strange series of colored lines in the shape of boxes (see photo). It happens intermittently and only on certain images in the stack. It has nothing to do with Helicon, as it happens during the LR export.

Here is information I think will be useful:
What do you use to view the images?
I use Lightroom Classic V 11.5 and Photoshop V23.4.2

Processor 11th Gen Intel(R) Core(TM) i7-11700K @ 3.60GHz 3.60 GHz
Installed RAM 32.0 GB (31.8 GB usable)
System type 64-bit operating system, x64-based processor
Pen and touch No pen or touch input is available for this display
Display Adapters NVIDIA GeForce GTX 1070 Ti

Workflow: Shot on Nikon Z9 or D850 Import RAW images into Lightroom Classic V 11.5, Camera RAW 14.5, (The only thing I do in LR is to adjust lightness and darkness to make sure my histogram is within limits, then I sync the rest of the photos to that adjustment) then export to new folder. I then open file in HF then select the images to import into HF. I then render them in HF, then open them back up in Lightroom for further editing, then back to Photoshop. The colored lines are in specific images post export from LR.

Questions and answers below are from Helicon tech support:

Does this happen to any other images, or only to those produced in HF?
Just the HF images and in individual images in the stack

Are you observing the same effect in HF right after processing? or only when opening the saved images?
Stays within certain images in the stack, permanently

Are you running HF v.8.2.0? Are you running Win or macOS?
WIN 10 Pro 64 Bit. HF V8.2.0. Also says up to date on my version when I check for updates.

If anyone has any insight into this, I would certainly appreciate your knowledge.

Many thanks
RL

big-guy Loc: Peterborough Ontario Canada

Have had this happen before and the cause was a CF card starting to go bad. Replaced the CF card and problem solved.

letmedance Loc: Walnut, Ca.

It does appear to be a corrupted file, possibly a bad CF or SD card.

Robertl594 Loc: Bloomfield Hills, Michigan and Nantucket

If the card was going bad, then wouldn’t the original file show these artifacts? These lines do not show up on the images until I export them from Lightroom, after I have imported them from the card.

Is there a way to check the card to see if it’s going bad?

CHG_CANON Loc: the Windy City

The idea the card is bad is probably not applicable given how far downstream the problem occurs in the various software involved. I'd take the stack that generated the posted example and try a few things:

1, If the issue is the LR export, instead bring the stack into PS and do a File-Save-As and use the same target output parameters and see if the image issue repeats.

2, You gave a lot of details, but you didn't attach the example images, nor provide the specs on the LR export. What are those export parameters, and if you change them, does that impact how the example input stack exports?

3, Is there anything common in the problem stacks? Do they have more images, say above a certain threshold count? Are the files on disk above a certain threshold in bytes, GB, as compared to a stack with no problem?

4, If you start the process over for one specific stack, from the NEF import forward, does the issue repeat for that stack?

5, If you export one stack that exhibits this issue, if you exit LR, restart LR, and re-export the same image, does the same problem occur?

6, If you export one stack that exhibits this issue, if you exit LR, restart the computer, and return to LR and re-export the same image, does the same problem occur?

Robertl594 Loc: Bloomfield Hills, Michigan and Nantucket

Thank you. You always have good questions and comments. Here is what I can tell you so far. I agree with you that it probably is not the cards as it’s well downstream.

1, If the issue is the LR export, instead bring the stack into PS and do a File-Save-As and use the same target output parameters and see if the image issue repeats.

I will try this using both PS and Bridge to see if it persists.

2, You gave a lot of details, but you didn't attach the example images, nor provide the specs on the LR export. What are those export parameters, and if you change them, does that impact how the example input stack exports?

Export is to only convert from NEF to TIFF

3, Is there anything common in the problem stacks? Do they have more images, say above a certain threshold count? Are the files on disk above a certain threshold in bytes, GB, as compared to a stack with no problem?

Stacks consists of between 50 and 300 images. Typical uncompressed raw size from FF Z9 8256 x 5504. Not all images are affected. I will have to do a new export to see if it’s the same ones or random.

4, If you start the process over for one specific stack, from the NEF import forward, does the issue repeat for that stack?

Will have to check

5, If you export one stack that exhibits this issue, if you exit LR, restart LR, and re-export the same image, does the same problem occur?

Will have to check

6, If you export one stack that exhibits this issue, if you exit LR, restart the computer, and return to LR and re-export the same image, does the same problem occur?

Will no 5 first to see, then will check this.

I think that I will try PS and Bridge first to see if this occurs, then try other steps.

Many thanks
RL

jcboy3

I would also export one of the files that shows this problem individually, and see if it still has the problem.

CHG_CANON Loc: the Windy City

So, why to TIFF? If you convert just to a display-purpose JPEG, what happens?

For the file sizes, you responded with the pixel resolution. That may be something. Do those pixel resolutions distinguish the problem images from others? Look too at the file sizes on disk as this defines the memory needs of the software / computer.

rmalarz Loc: Tempe, Arizona

Very good diagnostic suggestions, Paul.
--Bob

Robertl594 Loc: Bloomfield Hills, Michigan and Nantucket

Good idea.

big-guy Loc: Peterborough Ontario Canada

My experience was that sometimes it did and sometimes it didn't. Sometimes the problem showed and the next time it didn't but showed up on export. Sometimes the photo looked fine on screen and the export manifested the problem. It was entirely a crap shoot. I tried all sorts of things but the only thing that worked was replacing the CF card. Once I did that the clouds cleared and the sun began to shine again. For the price of a card what do you have to lose?

This was my experience and indeed your problem may have a different solution.

Robertl594 Loc: Bloomfield Hills, Michigan and Nantucket

Thank you. I have so many cards. I will make sure I take your advice and keep track of which cards I use.
RL

Robertl594 Loc: Bloomfield Hills, Michigan and Nantucket

Yes, I will. Traveling this weekend. When I get home, I will look. May try JPEG instead of TIFF. I just don't like lossy formats.

CHG_CANON Loc: the Windy City

The original is available in the file(s) managed by LR. A "lossy format" has nothing to do with a 1-way output process via the LR export.

Robertl594 Loc: Bloomfield Hills, Michigan and Nantucket

Yes. I understand. I have always avoided jpegs as they are lossy. Once opened and re-saved, the algorithm re-averages the difference between the (8x8 grid) 63 pixels to the one on the upper left corner, rather than the actual data for each pixel.

Lossless formats, do not do this and maintain the integrity of the full image.