Lukc666 Posted September 4, 2022 Share Posted September 4, 2022 Yeah. If it's not fixed by the time I finish my current project, I'll probably shift back to InDesign for a bit. It's really a pain. Every now and again I also lose trackpad gesture zoom (have to enable manual zoom, zoom in and zoom out, then it usually comes back). They're two little, persistent bugs, that really frustrate my concentration. Same setup as Pete, but 16" MBP. Quote Link to comment Share on other sites More sharing options...
Mike editor Posted September 29, 2022 Share Posted September 29, 2022 FWIW - I'm having this problem too. Just struggled with a file, 50+ pages, perhaps 100-150 images. Ballooned to ~250MB. Doing the embed/link process reduced it to ~ 10MB, which seem about reasonable, given a certain number of embedded image pages also. Mac M1, new in June 2022. Quote Link to comment Share on other sites More sharing options...
yukonPete Posted October 1, 2022 Share Posted October 1, 2022 I think the first save after a few smaller moves might get a bit bigger, up to a hundred+ MB, but after that it balloons to GBs. So my work process is to select all, embed, the make linked, then save. Crude and slow but it functions. Quote Link to comment Share on other sites More sharing options...
Mike editor Posted October 4, 2022 Share Posted October 4, 2022 Similar to what I've had to do. slow, aggravating, when I have several hundred pix in a single magazine file. Note to Affinity engineers: part of this problem feels similar to a problem I've had with the Sugarsync backup and sync service that I use. It seems to be related to the new Mac M1 and/or OS 12.6. Quote Link to comment Share on other sites More sharing options...
MatteoS Posted October 17, 2022 Share Posted October 17, 2022 Still no fixes for this issue? Quote Link to comment Share on other sites More sharing options...
Mike editor Posted October 18, 2022 Share Posted October 18, 2022 Still happens for me Quote Link to comment Share on other sites More sharing options...
MatteoS Posted October 22, 2022 Share Posted October 22, 2022 On 10/18/2022 at 3:41 AM, Mike editor said: Still happens for me Yeah, also to me. I mean... it's ridiculous that they have not yet fixed it. Quote Link to comment Share on other sites More sharing options...
jorgev Posted November 3, 2022 Share Posted November 3, 2022 Any news about this issue?! Serif? Quote Link to comment Share on other sites More sharing options...
yukonPete Posted November 9, 2022 Share Posted November 9, 2022 Anyone looked to see if new V2 has corrected this issue. V2 states that no updates to V1 so they will not fix. Quote Link to comment Share on other sites More sharing options...
MatteoS Posted November 9, 2022 Share Posted November 9, 2022 I'm testing this specific issue right now on the V2. Quote Link to comment Share on other sites More sharing options...
jorgev Posted November 18, 2022 Share Posted November 18, 2022 On 11/9/2022 at 9:23 PM, MatteoS said: I'm testing this specific issue right now on the V2. Hi MatteoS, Were you able to reproduce the issue in v2? I have to admit I am hesitant in upgrading, as if it is still doing this it's definitely a deal breaker for me. Many thanks for your feedback Jorge Quote Link to comment Share on other sites More sharing options...
yukonPete Posted November 18, 2022 Share Posted November 18, 2022 gotta admit, I see this as a statement of intent from Affinity. If this isn't fixed that doesn't bode well. I haven't upgraded yet as I have stuff that needs doing and don't want to be testing software at this point. I need stuff that I can trust! Peter Quote Link to comment Share on other sites More sharing options...
Pšenda Posted November 18, 2022 Share Posted November 18, 2022 1 hour ago, yukonPete said: I haven't upgraded yet as I have stuff that needs doing and don't want to be testing software at this point. I need stuff that I can trust! Just for your information - V1 and V2 are completely separate, so you can buy V2 (while it's on discount) and still work on V1. Quote Affinity Store (MSI/EXE): Affinity Suite (ADe, APh, APu) 2.4.0.2301 Dell OptiPlex 7060, i5-8500 3.00 GHz, 16 GB, Intel UHD Graphics 630, Dell P2417H 1920 x 1080, Windows 11 Pro, Version 23H2, Build 22631.3155. Dell Latitude E5570, i5-6440HQ 2.60 GHz, 8 GB, Intel HD Graphics 530, 1920 x 1080, Windows 11 Pro, Version 23H2, Build 22631.3155. Intel NUC5PGYH, Pentium N3700 2.40 GHz, 8 GB, Intel HD Graphics, EIZO EV2456 1920 x 1200, Windows 10 Pro, Version 21H1, Build 19043.2130. Link to comment Share on other sites More sharing options...
yukonPete Posted November 18, 2022 Share Posted November 18, 2022 yes, I understand sale and independence. However, specs say v2 doesn't work on my older macPro so I want to only go forward if I trust that Affinity will fix glaring errors. They state that they are done fixing V1. The beauty of v1 is it works on old and new macs, or at least that's what I think specs for v2 imply. Quote Link to comment Share on other sites More sharing options...
PeterAG Posted January 13, 2023 Share Posted January 13, 2023 On 11/15/2021 at 3:04 PM, MikeTO said: I recreated the issue and uploaded the before and after files with a screen recording and a readme.txt to explain the issue. I spent a couple of hours testing the issue with a backup copy of the file today and didn't find a specific trigger - sometimes I'd repeat the same series of steps, choose Save As, and the file would be 9MB. Then the next time it would be 50MB, 300MB or 500MB. Then 9MB again. Once the file has expanded in size I can't find a way to get it back to 9MB again with Save As. It seems to have accumulated some permanent baggage. Thanks! I'm having this issue too. I thought it was cache related, but sounds as if its Affinity's history function. Any ideas how you can turn this off? I have time machine back-ups for that. Quote Link to comment Share on other sites More sharing options...
MikeTO Posted January 13, 2023 Author Share Posted January 13, 2023 3 hours ago, PeterAG said: I'm having this issue too. I thought it was cache related, but sounds as if its Affinity's history function. Any ideas how you can turn this off? I have time machine back-ups for that. If File > Save History with Document is already off then it's not the history issue. If it's on then turn it off. Cheers Quote Download a free manual for Publisher 2.4 from this forum - expanded 300-page PDF My system: Affinity 2.4.2 for macOS Sonoma 14.5, MacBook Pro 14" (M1 Pro) Link to comment Share on other sites More sharing options...
PeterAG Posted January 13, 2023 Share Posted January 13, 2023 History has never been turned on. Quote Link to comment Share on other sites More sharing options...
filippoguidarelli Posted February 10, 2023 Share Posted February 10, 2023 I'm experiencing the same issue with increasing/decreasing file size (Mac mini M1). My links are into a folder on a server and the workaround of link/embed/link again doesn't work because the process of embedding is too slow/heavy. In this scenario, the solution was disconnecting the server, connect it again, save and close the file. Its size dropped form 800 MB to 65. I suppose that if you have images on your machine, you can change the name of the images folder, so to lose the links; then rename the folder with the correct name and reconnect the links. Quote Link to comment Share on other sites More sharing options...
Milleniarist Posted April 12, 2023 Share Posted April 12, 2023 I started having this problem this month after upgrading to a Macbook Pro M2. This bug has remained unfixed for almost two years now, and as you can see in this other thread it is also present in Publisher V2. I will finish the project I'm working on using my old Intel Macbook and then I will sadly switch back to InDesign. I was such a big fan of the Affinity suite since 2017 but this issue is really annoying even with the "embed/linked" workaround. Quote Link to comment Share on other sites More sharing options...
MikeTO Posted April 12, 2023 Author Share Posted April 12, 2023 10 hours ago, Milleniarist said: I started having this problem this month after upgrading to a Macbook Pro M2. This bug has remained unfixed for almost two years now, and as you can see in this other thread it is also present in Publisher V2. I will finish the project I'm working on using my old Intel Macbook and then I will sadly switch back to InDesign. I was such a big fan of the Affinity suite since 2017 but this issue is really annoying even with the "embed/linked" workaround. The issue in v1 that caused file sizes to increased was fixed in 2.0. I experienced this issue multiple times a day in v1 but have never experienced the problem with 2.0. The v2 replies to that old v1 thread you linked to are likely a more specific file size issue reported in 2.0 which is fixed in the 2.1 beta. There was an issue with linked resources on master pages causing file sizes to increase. I recommend you try your document in v2 and specifically in 2.1 before giving up. Cheers Milleniarist 1 Quote Download a free manual for Publisher 2.4 from this forum - expanded 300-page PDF My system: Affinity 2.4.2 for macOS Sonoma 14.5, MacBook Pro 14" (M1 Pro) Link to comment Share on other sites More sharing options...
Milleniarist Posted April 13, 2023 Share Posted April 13, 2023 18 hours ago, MikeTO said: The issue in v1 that caused file sizes to increased was fixed in 2.0. I experienced this issue multiple times a day in v1 but have never experienced the problem with 2.0. The v2 replies to that old v1 thread you linked to are likely a more specific file size issue reported in 2.0 which is fixed in the 2.1 beta. There was an issue with linked resources on master pages causing file sizes to increase. I recommend you try your document in v2 and specifically in 2.1 before giving up. Cheers Thank you! That's good to know. I'd rather upgrade than going back to Adobe. Quote Link to comment Share on other sites More sharing options...
EarLocust Posted September 28, 2023 Share Posted September 28, 2023 This seems to have reappeared for me in 2.2. My publisher file went from 300 MB to 5 GB. I managed to get it back down to 300 somehow (stopped saving history and did the embed/link thing), but it's worrying that this problem has reappeared. I'm on Windows 10 (if that matters for some reason). Quote Link to comment Share on other sites More sharing options...
Pšenda Posted September 29, 2023 Share Posted September 29, 2023 15 hours ago, EarLocust said: stopped saving history and did the embed/link thing If you had History saved and Embedded documents, the file size is "always" significantly larger - regardless of the version you are using. That definitely didn't "get it back" with version 2.2. Quote Affinity Store (MSI/EXE): Affinity Suite (ADe, APh, APu) 2.4.0.2301 Dell OptiPlex 7060, i5-8500 3.00 GHz, 16 GB, Intel UHD Graphics 630, Dell P2417H 1920 x 1080, Windows 11 Pro, Version 23H2, Build 22631.3155. Dell Latitude E5570, i5-6440HQ 2.60 GHz, 8 GB, Intel HD Graphics 530, 1920 x 1080, Windows 11 Pro, Version 23H2, Build 22631.3155. Intel NUC5PGYH, Pentium N3700 2.40 GHz, 8 GB, Intel HD Graphics, EIZO EV2456 1920 x 1200, Windows 10 Pro, Version 21H1, Build 19043.2130. Link to comment Share on other sites More sharing options...
EarLocust Posted October 4, 2023 Share Posted October 4, 2023 Nah, I never had my images embedded, but there was a "workaround" to set everything to embedded, then back to linked to fix it. I'm not saying that worked for me - unchecking the history seemed to fix it. It still seems larger than it should be (~450 MB with no embedded images) when my backup from June is only 140 MB. Quote Link to comment Share on other sites More sharing options...
walt.farrell Posted October 4, 2023 Share Posted October 4, 2023 5 minutes ago, EarLocust said: still seems larger than it should be (~450 MB with no embedded images) when my backup from June is only 140 MB. Did you do a Save As and give it a new filename? Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro, version 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro, version 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. iPad: iPad Pro M1, 12.9": iPadOS 17.4.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.4.1 Link to comment Share on other sites More sharing options...
Recommended Posts
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.