Re: Saving issues, looked online for tutorials and help but coming up blank, please h
I finally had the time to examine & experiment with the OP's file. Here's what I found:
1) To see if being a PSB instead of a PSD had any effect, I saved it as a PSD (still 16 bpc, ie, unchanged). No change in the problem.
2) To see if the layer efx on his lowest (smart) layer were causing any trouble, I removed them. No change in the problem.
3) To see if (1) and (2) combined might have caused his problem I made both changes. No change in the problem.
4) To see if the problem was inside his smart object, I tried to make a minor edit to it. PW wouldn't let me save the changes and return to the original. It gave the following error:
"Can't save this document back to its original file format. Flatten layers and discard extra data as necessary and choose File > Save again."
5) To check that PS itself was working as expected, I replaced his lowest layer with my own smart object, a checkerboard pattern. I left the number of bits per channel remain at 16. I left his upper layer as is. I added my own layer effects to my checkerboard pattern, and saved the file as a PSB with a different name. The result was that I had no problems whatsoever with this file. I could edit my smart object endlessly, change the bit depth, change the layer effects, and everything I tried worked exactly as it should.
My conclusion from this is that the problem the OP was having resides in his lowest layer.
When I did a search on the error message I quoted above, I found that the usual advice given was:
(https://forums.adobe.com/thread/1602862#access_token=eyJ4NXUiOiJpbXNfbmExLWtleS0xLmNlciIsImFsZyI6IlJTMjU2In0.eyJmZyI6IlE1RzdUR0U0RElBQUFBQUFBQUFBQUFGV0FBPT09PT09IiwiYXMiOiJpbXMtbmExIiwiYyI6IkdrSWs4aXo5cDl1R1psVTNySUlLYWc9PSIsInVzZXJfaWQiOiI1ODhFNjUxRDRBRDE2MjcyOTkyMDE1QjlAQWRvYmVJRCIsIm1vaSI6IjM5MWUwZWZmIiwic2NvcGUiOiJBZG9iZUlELG9wZW5pZCxhZGRpdGlvbmFsX2luZm8uc2NyZWVuX25hbWUsdXBkYXRlX3Byb2ZpbGUuc2NyZWVuX25hbWUiLCJjcmVhdGVkX2F0IjoiMTQ3ODcyNDA4NzYyNiIsImlkIjoiMTQ3ODcyNDA4NzYyNi1lYTAxYzBiZi0wODgwLTQ0NGEtOTc2NS1hYmMwOThjYWE5OTMiLCJzdGF0ZSI6IiIsInR5cGUiOiJhY2Nlc3NfdG9rZW4iLCJleHBpcmVzX2luIjoiODY0MDAwMDAiLCJjbGllbnRfaWQiOiJmb3J1bXMyIn0.eSAVtwYemcJOa2OvzIOFduKXIphAVojRiM6otsD0lc04hY9gP4rhjwMI8LIu9eZ3YyDGLMkPoOZhSNzsDZiRgdyrmi04ihN_uauhEjTUf1xUxwmw0bTeWuKLXYtEVAIA3cQnppZ6Q-zWO9InuD4halZGf2iZDBFsF1wjb5iczBYoEGhC2hJG3PtVsc8N3YmHujmEFAqelcH5hbzWQX1ktRABTOS-9f4KAtIxiDNcO_F66sKLhpH9N7FTVVFa5Hgbk_Zc81ia6K4BZoARq2MH-9cGk9YOniu_vPEkwz8IGoOMW4k-SzjyuRUg34o8i7LvQC6DapmTDeNzvzUqKxiK7g&token_type=bearer&expires_in=86399970)
I tried reconstructing this type of error, and it indeed caused problems similar to what I saw in the OP's file. This restriction makes sense after you think about it. So, my guess is that the OP inadvertently constructed the SO improperly. I'm not sure how well this restriction on smart objects is known, but I certainly didn't know about it. Whether one would call this a PS problem or a documentation problem or a user knowledge problem is a matter of opinion.
Tom M
