Skip to main content
khark710
Inspiring
December 30, 2019
Answered

Two Layer File Save Enormous

  • December 30, 2019
  • 8 replies
  • 4833 views

I have an image that came to me decently small for my type of work. It came at 300dpi from Getty and when resized to 100dpi and 121"w x 99"h (yes seriously) it suddenly locked my computer up. I've been resizing images to this size for this entire giant project but suddenly this one has gone insane. I have to wait over ten minutes just to make changes. I even tried changing it to 200dpi at half the size as I find that sometimes helps. 

I blurred the image twice, then added noise (to help sharpen it up), turned the layer on soft light, and added a slight gradient layer mask to the top. When I saved the psB file out it was 4.5 GIGs! Now I can't even save it to a JPG because it's running out of memory. 

I have no idea what to do to fix this. It's nuts and I've never seen this happen before. 

This topic has been closed for replies.
Correct answer davescm

Your bottom image is using 100 pixels /centimeter      100px/centimeter = 254 px/inch

 

Dave

8 replies

Kevin Stohlmeyer
Community Expert
Community Expert
December 30, 2019

When you changed it to 200 ppi, you did not resample the image - it just swapped size for resolution which is why you had a 1/2 size (W&H) with 200 ppi. You never actually changed the overall pixel dimensions of the image.  (121 x 99 x 100 ppi is the same as 65 x 49 x 200 ppi). If you want to reduce the size, turn on Resampling in Image Size then change your specs.  

 

Recreating your specs with W, H and resolution I ended up with a similar file size of almost 5 GB. That is what I would consider normal for something this large.

khark710
khark710Author
Inspiring
December 30, 2019

Okay so I understand where everyone is seeing how big the image is.

That in pixels as shown up top, it is about 400"w.

 

SO. In my industry, what I have to do to utilize linked images is this.

I'm going to utilize a different image for this example.

Open image in PS > image comes in at 18.24"w x 12.16"h. (5472px x 3648px as shown under "dimensions")

"resample" button is currently checked.

Change resolution to 100dpi (image stays at 18x12" size)

Uncheck resample, check resample, image is now 54.72"w x 36.48"h.

I need image to be, let's say 70"w.

Change width to 70"w, dpi stays at 100dpi.

Image is now 70"w x 46.667"h (pixels under dimensions show 7000px x 4667px: i understand this is about 96"w)

 

This is how all images need to be given for print.

They need to be at 100dpi and made to print size.

So this is how I have been doing it for 15 years, and all of my linked images then save out no larger than 75mb.

This is the first one that's ever acted like this.

 

I'm including a photo for reference of what the chickens (top) look like pre and post size adjustment.

And what the pigs looks like pre and post.

Kevin Stohlmeyer
Community Expert
Community Expert
December 30, 2019

Look at your previous screen shot - you have Resample unchecked.

khark710
khark710Author
Inspiring
December 30, 2019

So, to add to this fun mystery, I opened up one of the other files I had that is using this same filter and instead just dragged this photo directly onto it and literally just stretched it bigger. It resulted in a BETTER looking image, I was able to blur/noise it much less to make it look acceptable, and the whole psd file is 1.2g (similar to the others). I don't understand why it would look SO much better doing it this way. Initially I was in a little bit of a panic because the original file wasn't looking as good as we really need it, but with time constraints, it was looking like we wouldn't have a choice.

JJMack
Community Expert
Community Expert
December 30, 2019

Did you run the script to delete ancestor meta data.  A 800MP image should save as a Jpeg file less then 2GB in size. The uncompressed size of a 800MP image Pixel data is 2.4GB. Why do you need 800MP images?

JJMack
khark710
khark710Author
Inspiring
December 30, 2019

That would still be much larger than the other images I have saved at the same size with the same effects.

Also, sorry, I replied to another post that I can't manage to run any scripts.

I followed the blog post, but I'm unable to get notepad to save a jsx file so sounds like a may just be SOL to solve the actual issue at hand.

Still, I found a work around so I'm fine, but it's still bugging me as to why this is happening.

rob day
Community Expert
Community Expert
December 30, 2019

Also, what’s the bit depth and have you done any transforms that add pixels outside of the canvas?

I can get a similar file size (3GB) on a 2 layer file by working in 16-bit and scaling up one of the layers:

 

 

The same document trimmed at 8-bit (342MB):

 

Legend
December 30, 2019

As the Image Size shows, the image is over 2 GB, but that's the raw size in pixels.

If you have 2 layers, each one needs 2 GB, then there is a preview too, another 2 GB. That's 6GB. 

 

The image, 156.44 in x 125.78 in at 200 ppi is much larger than you originally stated, which was 100dpi and 121"w x 99"h. So your file is 6.5 times the raw image size you stated.  

khark710
khark710Author
Inspiring
December 30, 2019

I'm sorry, I don't understand what you're looking at.

My screenshot says 61.591 x 49.52 at 200dpi.

I said that it was at 100dpi but that I changed to 200dpi and half the size because sometimes it helps it run better.

Sorry, I stated initially it was 95"h because that's the finished size. We have to supply at 99"h for 2" of bleed on the perimeter. but I don't think that 4" is making it go from a standard 1.2 to 4.5 gigs.

 

EDIT: Nope, nevermind, I originally said it was 99"h as shown in my screenshot when you change to 100dpi and resample.

Stephen Marsh
Community Expert
Community Expert
December 30, 2019

The following code tests for the presence of photoshop:DocumentAncenstor metadata, however, it takes a long time to respond if there is a lot of ancestor code. I'm sure that there is a faster way to test for the presence of this metadata using a script:

 

if (documents.length) {
   if (ExternalObject.AdobeXMPScript == undefined) ExternalObject.AdobeXMPScript = new ExternalObject('lib:AdobeXMPScript');
   var xmp = new XMPMeta(activeDocument.xmpMetadata.rawData);
   var metaBloat = getArrayItems(XMPConst.NS_PHOTOSHOP, 'DocumentAncestors');
   for (var a in metaBloat) {
      if (metaBloat) {
         alert('NOTE: There is DocumentAncestors metadata in this file!');
         break;
      }
   }
}

function getArrayItems(ns, prop) {
   var arrItem = [];
   var items = xmp.countArrayItems(ns, prop);
   for (var i = 1; i <= items; i++) {
      arrItem.push(xmp.getArrayItem(ns, prop, i));
   }
   return arrItem;
}
khark710
khark710Author
Inspiring
December 30, 2019

I'm sorry, while I have always considered myself "good at google" this is clearly over my head.

Didn't matter what "tutorial" I followed, I can't figure out how to run this script.

Stephen Marsh
Community Expert
Community Expert
December 30, 2019

You don’t need a script to find if your file has photoshop:DocumentAncestors metadata, just use file info > raw data as mentioned in the blogpost above.

 

If you do have this metadata it may not be excessive.

 

P.S. Here is info on copying, saving and installing scripts in common Adobe software programs:

 

https://prepression.blogspot.com/2017/11/downloading-and-installing-adobe-scripts.html?m=1

Stephen Marsh
Community Expert
Community Expert
December 30, 2019

I had to take down the code samples as Blogger was mistakenly flagging my site as potentially malicious.

 

https://prepression.blogspot.com/2017/06/metadata-bloat-photoshopdocumentancestors.html

Participating Frequently
December 30, 2019

...

Legend
December 30, 2019

Please show a screen shot from the Image > Image Size dialog. Maybe there's a detail you are missing.

khark710
khark710Author
Inspiring
December 30, 2019

JJMack
Community Expert
Community Expert
December 30, 2019

That image is huge nearly 800MP that is 2.4GB uncompressed 8Bit RGB color data. It should however, be able to be saved as a jpeg file for the image has little detail and is mostly the same color blue so with any jpeg quality setting  Jpeg lossy compression should reduced the data size to well under the 2GB jpeg file limit.  Try stripping the meta data use the search I posted to get the script.

 

Why do you need a 800MP image?

 

function deleteDocumentAncestorsMetadata() {
    whatApp = String(app.name);//String version of the app name
    if(whatApp.search("Photoshop") > 0)  { //Check for photoshop specifically, or this will cause errors
        //Function Scrubs Document Ancestors from Files
        if(!documents.length) {
        alert("There are no open documents. Please open a file to run this script.")
        return; 
        }
        if (ExternalObject.AdobeXMPScript == undefined) ExternalObject.AdobeXMPScript = new ExternalObject("lib:AdobeXMPScript"); 
        var xmp = new XMPMeta( activeDocument.xmpMetadata.rawData); 
        // Begone foul Document Ancestors!
            xmp.deleteProperty(XMPConst.NS_PHOTOSHOP, "DocumentAncestors");
            app.activeDocument.xmpMetadata.rawData = xmp.serialize();
         }
}
//Now run the function to remove the document ancestors
deleteDocumentAncestorsMetadata();
JJMack
JJMack
Community Expert
Community Expert
December 30, 2019

Do you have any old backup of the file.  If you only have two layers and the document can only be saved as a PSB file that is over 4GB it sound like the document is corrupt or has Gigs of ancestor history that keeps growing.  If you have no backup you can find a script on this site that will strip ancestor history.  Use Google search this site search is useless.  Photoshop script strip ancestor history 

JJMack