transkontinental

Since the only topic covering this issue has been moved to pre 1.8, I need to reopen a new topic on this issue. As it is an existing/not fixed issue - I don't want to spend the time to recreate the whole project. DO: Create a Publisher project "photobook", say 60 pages (doesn't matter) - around 150 jpeg images (I've sometimes four per page). HAPPEN: Publisher needs too much disk space while running. MacOS locks down, halts processes, can't keep the system running. It seems as publisher copies the images to RAM/Scratch Disk as uncompressed files. Publisher closed: MacOS disk: 28GB free Publisher & Project open: 3GB frew Where all images from that project (JPEG exports) only take 2GB. Setting a warning on SSD usage doesn't make any sense other than making me sad, since that limit is exceeded easily and quickly. SHOULD: Publisher should not dump the images in a temp storage but rely on the linked files to afoid crowding the system drive. [ Currently I cannot continue my project in Publisher: after loading the project the SSD gets jammed by Publisher scratch disk - I need to recreate the project in Indesign ] Cheers, Jan

Same here, I posted under the filed bug

Version 1.8.3 I have the same problem on a 96 page project with half the pages used (say 150 images). It seems as publisher copies the images to RAM/Scratch Disk as uncompressed files: Publischer closed: MacOS disk: 28GB free Publisher & Project open: 3GB free Where all images from that project (JPEG exports) only take 2GB. Setting a warning on SSD usage doesn't make any sense other than making me sad.)

Hey Affinities, I have a feature request for Publisher: I'm working on a year book project with around 100 pages/each around 4 images. My workflow for the images takes them through Adobe Lightroom from which I export the images to the project's folder. I've set Publisher to "Auto refresh external ressources". So it often happens that I find an image needs an additional tweak when arranged with three other photos, so I make the change and overwrite the existing file (each image is around 10 MB). Here comes the catch/bug/feature request: Publisher correctly recognizes that the file has been changed, but doesn't give the system enough time to finish writing the file: an error pops up "file not readable"... So the FR would be: "Make the software try e.g. three times (with say three seconds inbetween) to auto refresh the file before throwing the error" or if the system can give the information: check if file is still being written, check for refresh afterwards... Cheers, Jan