The Corrupting Sea Pdf

[Kemal Allan]

Ive not had this issue at all until the latest update but it seems like Photoshop is corrupting files? It's happened twice since updating - at first I assumed it was some CMYK / View as "Insert Color Profile" but it's not. I can't share files due to NDA but it's happened twice where several layer colors were changed, background layers are semi transparent with bands on it, etc.

Is your Photoshop version 24.1?

Go to Help - System Info , and copy patse here.

And What exactly is the damage to the image you are experiencing?

-ecosystem-bugs/p-strange-color-box-with-data-loss/idi-p/130...

Is it similar to what I left a link? Or is it another case? Please record it with an image or a video and show it to us. I understand you're working behind closed doors, but with limited information, Adobe will find it difficult to help you. You can also reproduce the bug with a regular stock image.

You say "slide the lightness or saturation, it will jump as if I made it dark (even if I went lighter) and then I know the file is done." but are you saying after this, when you then save, the document is corrupted?

@TheDigitalDog - I am very certain it can corrupt files as it has, 5 times in the last 3 weeks or so. The corruption happens in the program. I don't save and close and then find out the next time I open, it is an immediate switch.

There is no specific reason I can find that "initiates" this corruption - the last two times being what I described in my previous post quoted below (tried to adjust to be a bit clearer):

So far the only thing I've noticed that "initiates" this bug is when I go to adjust a layer with Image > Adjustments > Hue / Saturation (via keyboard shortcut) - the sliders don't act as they normally should (will usually jump super dark) - that is when I knew the file is "done" aka broken / corrupt.

And for more background on myself, I'm an art director and illustrator who has been using Photoshop for 20+ years (15 years professionally) - I've never had these kinds of issues until now so I'm chalking it down to something related to M1 and Photoshop compatibility.

Ive had exactly the same thing happen tonight multiple times on different files that were working perfectly well before the update.

On one file it happened when I merged two layers, on another, it did it when I Desaturated the layer. There doesn't seem to be a single cause. This is what it did, and what it should look like. Lost hours of work because even the previous save had the corruption in it. Tried a different file (made a copy first) and the same thing happened to it.

I'm going to submit this as bug, but I wanted to start a discussion around this incase there have been any solutions that I may not be aware of. I ran into my first occurrence of this problem ever, yesterday, while importing images off a CF card from my Canon 60D. I'm using the latest version of Lightroom on a Mac Pro running Sierra.

Launched Lightroom and selected Import + Copy to the new catalog. During this process and copied and imported everything into the new directory. The JPG previews appear just fine, but as you click on each of the images and the (RAW) .CR2 files load into the cache, the corrupted content replaces the image and you get an unsalvageable photo. I exited and trashed this catalog.

Copied all the images from the CF card to my Desktop. I loaded up one of the .CR2 files into Photoshop and it displays OK. No data issues here at all. Launched Lightroom and created a new catalog. Followed the similar steps as above using the Import + Copy, into the new catalog directory. Same issues manifest. Manually reviewing these images from the new directory by bringing a .CR2 into Photoshop results in a corrupted file.

Start over with a fresh copy of images from the CF card, moving them into a new catalog directory. Launch Lightroom and only Add the images to the catalog. This results in usable RAW images that are not corrupted.

Lightroom is corrupting the images on copy, during the re-write to the new catalog directory. It's unclear if there are issues with the original data itself that are causing the images to corrupt. However, they copy off the CF card to the computer fine, which narrows down Lightroom as the culprit.

I've looked through the Lightroom prefs to ensure it is not able to write changes to the Raw files. A few related posts mentioned something about making sure this was disabled, however in all of those incidences the users indicated their original images were already corrupted off the card.

P.S. If you are one of the unlucky souls who in fact have corrupted raw images and just want to at least salvage a lower quality version of them... these awesome guys at created a free program that extracts preview JPGs from the CR2 files. This actually gives you a nice sized JPG, that you can at least work with vs nothing at all!!

This has all the symptoms of a hardware malfunction. Also, please keep in mind that Lightroom never writes to your original RAW images. The fact that the file displays properly in PS is because you are being shown the embedded JPG and not the RAW.

I use the MacPro extensively for other graphics work, GPU accelerated work, After Effects / Premiere, etc, etc... and everything is working just fine. If it's hardware on the machine, it's something that only Lightroom is tapping into and very obscure.

If it's Camera related, it's also a hidden bug that only manifests during the Lightroom COPY phase. As noted, my workaround allowed me to successfully work with the images. Not sure if there is a bit-to-bit check of the image during copy into Lightroom that is somehow causing the issue.

But yes, it's worth a check to see if it's the hardware. I also haven't uninstalled or reinstalled the application. I've never encountered this ever before after working with 100k+ images... but there is a first time for everything.

There is such a thing as intermittent bugs. There is such a thing as bad sectors on your hard disk so that files written to one location are fine while files written to another location are corrupted.

Many "experts" claim Lightroom cannot, will not, it's impossible for Lightroom to corrupt files. It's the card, it's the hard drive, it's the ram, but it's not Lightroom. I'm no expert, but that is simply not what I experienced! Lightroom does and has corrupted files, well visually anyway. I switched to a new camera, and a new card and and Lightroom more often began to corrupt my raw files (with horizontal colored lines) but most of the previews were perfectly fine, well most of them anyway. This would occur as I was opening the files from the SD card into Lightroom from the SD card. I'd moved those same files from the card onto my hard drive, same issues, and it would corrupt more, now even with Camera Raw, the images were corrupt. I took the SD card out and placed it back in my camera, images were all fine. I then placed the SD card back into the card reader, copied (dragged) the entire folder to a different hard drive. This time I opened the files through Photoshops Camera Raw... and all files were perfect. So Lightroom is not technically corrupting the files, but once you attempt to open the files via Lightroom from the card, it did/does something to the images that makes them appear corrupt, I've read for others, it did actually corrupt and they were unable to retrieve their files. Now if you do an auto erase after import and don't have a backup, you may very well be screwed. I've read all these experts say it's not Lightroom, then saw a software developer who strongly disagreed, with good reason as to why, but it is my opinion.... Lightroom IS somehow corrupting these files, not the card, not the ram, not the drives! The problem existed on different cards and readers but only since Lightroom. I've not tested this extensively, but I had just taken photos of my family with my dying mother that I intended to share with them and was devastated to see what happened to the images upon import. I was bound and determined to fix this issue as I can't retake these photos. It didn't take long to see MANY have this issue but are being told it's their camera, card, drives, ram.... I'd have to disagree. I've used these two camera's and cards and always imported into Camera Raw in the past with zero issues and problems. The only thing new was Lightroom. My drives are working with all other software and files, so it seems logical to me, Lightroom is doing something. Maybe I was just lucky, but I would definitely copy all files to at least two drives before attempting to open in Lightroom, but I'll be using Camera Raw from here on out!

Realize that Lightroom uses standard operating system calls to copy files of your card. It has no special code to do this. If the files get corrupted (and this is not the camera doing it, which happens not infrequently), this happens in the copy process and is due to problems with the card, the card reader, the USB cable, or the hard disk you are copying to. Lightroom simply does not write to the raw files anywhere else. The reason you see the image change is simply that it first shows you the embedded jpeg preview before it actually loads the raw file and shows you that the raw file itself was corrupted somewhere in the process. If this happens in the copy phase due to a bad reader, cable or other factor, you might be able to recover from this. If it is the card itself that is bad or the camera has an issue, it is unlikely that that is recoverable.

It's important to realize that Lightroom doesn't write to raw files except if you use dng and tell lightroom to write metadata back to the files (not the default). If your files get corrupted somewhere you have a hardware issue that need to be diagnosed. It is virtually impossible that it is Lightroom doing it.

3a8082e126