Jump to content
Our response time is longer than usual currently. We're working to answer users as quickly as possible and thank you for your continued patience.

Linked PDF explodes Publisher document filesize


Recommended Posts

If have a PDF flyer (aproximately 3 MB) linked into a Publisher layout.

image.png.dd453cd0dcaf868c85c1b7212533e60d.png

image.thumb.png.144ce4195bb478dd68e8800ff5db2038.png

 

With the PDF the Publisher filesize is about 18.5 MB. If i delete the linked PDF from my document the Publisher filesize is only about 3.2 MB.

The Publisher filesize with linked PDF becomes even bigger than the linked PDF filesize itself ? This remembers me of the early v1.x behaviour before you even could link external resources properly.

 

Hardware: Windows 10 Pro for Workstations (22H2, 19045.2364, Windows Feature Experience Pack 120.2212.4190.0), 8 core Intel(R) Xeon(R) W-2145 CPU @ 3.70GHz, 64 GB RAM, NVIDIA Quadro P4000 (driver 516.94), 2 x 1GB SSD. 1 Display set to native 2560 x 1440.
Software: Affinity v1 - Designer/Publisher/Photo (1.10.6.1665), Affinity v2 (universal license) - Designer 2.0.3 / Publisher 2.0.3 / Photo 2.0.3.

Link to comment
Share on other sites

I have seen this same problem (quoting myself from another older post that seems to have lost traction) where a file containing linked PDFs is gigantic, and the file size changes every time I save it (even when using save as):
 

On 11/18/2022 at 1:38 AM, Luke Graybill said:

I'm also seeing this problem with Publisher 2. A file that under Publisher 1 was 463MB (there are a lot of images embedded), but opening the file in Publisher 2 and saving it without making any changes balloons the filesize to 777MB. Using Save As to save two more copies increased the filesize again each time, even though I made zero changes to the content:

image.png.8d8ecce6fdf873b05cb10bcd50bf142a.png

 

The "Interior (from pub 1)" file at the top of my screenshot is the original file last saved under Publisher 1, the others are copies of the same file saved by Publisher 2.

Edit: I'm using Windows 11, so technically this is I guess the wrong part of the forum for me to chime in, but it was relevant otherwise so I figured why not. Sorry if I'm just adding noise though!

I had thought this was due to moving from Publisher 1 to Publisher 2 with the same file, but perhaps not.

Edited by Luke Graybill
Link to comment
Share on other sites

I can also confirm this behavior. I have a 40 page Document with some 19 PDF's linked inside. Each linked PDF file has about 300 to 800 kb.

Without the linked PDF's the document has 6,7 MB filesize. After linking the PDF's, the size grows up to more than 100 MB.

Yesterday the same file has had more than 200 MB filesize. A trick i read here in this forum was to include all linked files listed in resourcemanager and then linking it again. This step reduced filesize by 50% to around 100 MB.

@Dan C Have a look at the file i uploaded for another thread.

Link to comment
Share on other sites

This reminds me a bit of the embedded RAW file size issue with Afphoto, in which it appears that Serif have optimized Photo for speed rather than file size, as the added size penalty for embedding a RAW file is substantially larger than the original RAW file itself.

Presumably, Publisher is saving rasterized thumbnails of the linked PDFs to speed things up, but of course, rasterization can consume much more space than unrasterized text. It would be really nice to have options for trading off speed versus file size.

Link to comment
Share on other sites

Sorry serif guys - i know at the moment you are in big trouble and try your best to answer the questions here. Of course one may not know where to start to process the big pile of bug reports here.

But gradualiy i get the the feeling that some bugs are deliberately ignored by serif ? I constantly posted a hand full of quite clear bugs during the last two weeks and got only 1 reaction from the staff. So do many other users who spend a lot of time to investigate / recreate the errors to post some reasonable reports with videos, screenshots and example files.

Meanwhile other "fresh" bugs are answered with "Thanks for reporting this. I've replicated the issue and passed it onto development." after some hours or at least 1-2 days. It feels that these bugs are more related to the "new killer features" (haha, already had a vector warp in CorelDraw in the mid 1990s...) than the "boring" basic features like boolean operations, file sizes and so on...

Hardware: Windows 10 Pro for Workstations (22H2, 19045.2364, Windows Feature Experience Pack 120.2212.4190.0), 8 core Intel(R) Xeon(R) W-2145 CPU @ 3.70GHz, 64 GB RAM, NVIDIA Quadro P4000 (driver 516.94), 2 x 1GB SSD. 1 Display set to native 2560 x 1440.
Software: Affinity v1 - Designer/Publisher/Photo (1.10.6.1665), Affinity v2 (universal license) - Designer 2.0.3 / Publisher 2.0.3 / Photo 2.0.3.

Link to comment
Share on other sites

  • Moderators

Hi 4dimage,

I apologise for the delayed response to this thread please could upload a copy of the file to the following DropBox link? This will allow me to investigate this further and hopefully identify the cause of this issue. Please could you also tell me if this file was originally created in V1?

https://www.dropbox.com/request/FDiUgWtJ89u3T5WsBpTV

Thanks
C

Please tag me using @ in your reply so I can be sure to respond ASAP.

Link to comment
Share on other sites

Hi Callum,

sorry, but i forgot to set the document priority to "linked" files in the dropbox .afpub (which should be proved). But you can reproduce this wih a fresh Publisher document yourself.

---

The initial file was created in publisher v1. I opended it in Publisher v2 and saved with new name. To reproduce the behaviour create any new v2 Publisher document.

There are two images files for this test.

I have a PDF i got from the customer (Floristik-06-22.pdf) - filesize about 3 MB and a flat JPG i exported as page 1 from the PDF.

1) I open a fresh v2 Publisher DIN A4 document - image priority "linked". I save it and it has about 1.4 MB filesize:

image.png.d31ece841e0e178236ad1c92e92db1e0.png

image.png.726d143c2ede1548e46fd9b2e03cb4c2.png

 

2) Now i create a new image frame and (link) place the PDF into the image frame via drag/drop from the Windows explorer:

image.png.1a2da2270279c595ad807668702f81f6.png

 

After saving the Publisher document now it filesize has grown extemely to about 16.5 MB. This is even about 5 times the filesize of the linked PDF:

image.png.6d175a9ffc234ecade748752fbfeaaea.png

 

 

3) TEST: if i replace the PDF by a flat JPG instead -> save as, the Publisher filesize almost drops back to about it's initial filesize. So linked JPG (maybe flat PNG, TIFF, ... too) barely increase the filesize - this is the expected behaviour for ALL linked files:

image.png.79fcc6a2d23db5843ea1822903a848df.png

image.png.93b5b22827de7145c1de742c1f2ae78e.png

 

In some other posts here in the forum other users complain about gigantic Designer and Publisher files (x GB) although they also used linked resources - not embedded them. Maybe this applies to all filetypes that contain layers somehow (.psd, .pdf, .afpub, .afdesign, ...) ?

This problem applied also to v1. For some reasons your developers seem to embed redundant data of linked resources uncompressed in the linking document.

Speed may be important, but filesize is too! It's not acceptable to have all resources on the network (properly compressed) and then explode redundant copies of them into a layout file. All data has to be backuped and take multiplied time to process and disk space on the backup media!

 

Hardware: Windows 10 Pro for Workstations (22H2, 19045.2364, Windows Feature Experience Pack 120.2212.4190.0), 8 core Intel(R) Xeon(R) W-2145 CPU @ 3.70GHz, 64 GB RAM, NVIDIA Quadro P4000 (driver 516.94), 2 x 1GB SSD. 1 Display set to native 2560 x 1440.
Software: Affinity v1 - Designer/Publisher/Photo (1.10.6.1665), Affinity v2 (universal license) - Designer 2.0.3 / Publisher 2.0.3 / Photo 2.0.3.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.