Skip to main content
P
ptr22
Known Participant
October 7, 2024
Question

Latest PS (Beta) or LRC corrupt PSB files

  • October 7, 2024
  • 5 replies
  • 1324 views

I usually work with the latest version of PS Beta and LR Classic (OSX 12.6.9 M1 Max inernal drive). Going from one to the other has never been an issue. However, in the last few days, I've had several large document files getting corrupted after saving them in PS. The same happened with the latest regular PS version a couple of days ago. 

When it happens, I get an error messages (in LRC) saying 'unsupported compression algorithm' or that the 'file is damaged'. Trying to open it back up in PS gets me a different error '...appears to contain layers that are corrupt...' and I can choose to 'flatten' or try to 'open anyway'. Both leads to no success...the files are corrupt, and hours of work are gone!

Of course, this way I cannot trust or rely on either program and don't know if the error occurs when PS saves or LRC tries to read/write some Metadata during opening.  I'd love to be able to open today's file...otherwise another day's work is gone as well. Any idea what I can do?

Thanks!

This topic has been closed for replies.

5 replies

jane-e
Community Expert
jane-eCommunity Expert
Community Expert
October 8, 2024

@ptr22 

 

You can continue to run the current version of macOS, but you might want to turn off automatic updates for applications from the CC app. Adobe MAX is next week, and it is typical that Adobe will release the new version on the first day of MAX.

 

Three questions:

  • You said "OSX 12.6.9". OSX is macOS10, so you said both 10 and 12. Are you using X/10 or macOS12?
  • You said your macOS is installed on an M1 Max inernal drive.
    Are your files also being saved to the internal drive or are they on an external drive?
  • Have you run Disk Utility recently to find and repair disk errors? 
    https://support.apple.com/en-us/102611

 

Jane

 

 

P
ptr22Author
Known Participant
October 9, 2024

Thanks Jane, appreciate it! Switched autp-updates off now, thanks for the tip!

From what I know, from OS13 onwards Firewire was switched off and, currently, my audio is still relying on that. I might have some time at the end of November/December to update everything and, by then, I'll hopefully have a new interface sorted as well and can update to e.g. Sonoma (if also all neede software runs that by then).

And I meant Monterey 12.6.9...oops! Yes, everything is stored on the single internal drive (but backed up on several external drives). I haven't checked for disk errors yet but probably a good idea to do that, thanks!!


    L
    Lumigraphics
    Legend
    October 9, 2024

    The last Macs with Firewire were the 2012 MacBook Pros, which are only supported up to 10.15 Catalina. How are you running macOS 12? If its via OpenCore, all bets are off.

    L
    Lumigraphics
    Legend
    October 8, 2024

    Your OS version is not supported and will not be able to run Adobe apps VERY soon. Just an FYI.

    P
    ptr22Author
    Known Participant
    October 8, 2024

    Thanks for your replies! The computer is only 2.5 years old. I'd like to think it's not failing yet (internal SSD) and upgrading to a new OS isn't possible right now, as current work projects don't allow for any downtime (been there before). As said, the problem also happened with the regular version of PS, not just the beta version and only since the latest updates. No issues in other software.

    L
    Lumigraphics
    Legend
    October 7, 2024

    Why are you still using macOS 12? The current version is 15, what you have is no longer supported by either Apple or Adobe.

    I'd recommend updating to macOS 14 Sonoma or the (just released) macOS 15 Sequoia. You probably won't be able to use new Adobe releases after the Adobe MAX conference coming up this month.

    And yeah, beta software is just a bad idea. Stick to release versions.

    D Fosse
    Community Expert
    D FosseCommunity Expert
    Community Expert
    October 7, 2024

    Sorry to say, but file corruption is always caused by hardware failure. It can be a failing drive or bad RAM, but the most common cause is saving directly to an external drive or over a network connection. External drives are vulnerable to worn connectors/cables, as well as the extra layer of USB drivers and protocols.

     

    The bigger the file, the higher the likelihood of random errors hitting any one single file. That's just statistical probabilities.

     

    And that said, using beta software is by definition risky. The whole purpose of a beta is to weed out bugs.

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices