Jump to content

Tim Nikischin

Members
  • Content Count

    17
  • Joined

  • Last visited

  1. Hi @Gabe, thank you very much! Under some conditions I experienced, the media inserted in the image placeholder of the master page, Publisher somehow manages to lock those media inserted in the content page just as the content of the master page. So it is definitely inserted in the content page and not the master and also the master definitely not updated but the media inserted in the image placeholders is not editable or deletable until I select "edit unlinked from master". Is this another bug you already know about or do I need to reproduce? Probably produced by refreshing media, but saving and reopening the document might also be possible.
  2. I agree with you. Though Affinity Publisher seems to be quite well prepared for this. If I do this for the first time it works better then I would usually expect. Problems first happen after closing and reopening the document. At the first time after embedding AP seems to detect this actually. So if I save the document AP does notify something has changed and somehow auto-refresh. The document does not need to be saved again if there has nothing else changed. That's cool! Unfortunately it only works until I close and reopen the document. Not to talk about the RAM and CPU usage also which is a nightmare but at some point just a consequence of this feature and acceptable.
  3. @thomaso thank you very much for this feedback! Interesting enough you are not able to reproduce. It took me 3-4 times of closing and opening AP (and saving and changing something inbetween) each time before I was able to reproduce. I am using a Mac with the following specs in case it is something device specific. Regarding your creation date/version assumption I created a file Demo Book v3x I attached to my post which was created with the current version. However I am still able to reproduce.
  4. Thank you @Wosven, this was the solution I was thinking about at the first point. Unfortunately I forgot about it as linking it seemed more comfortable. Thank you very much for reminding me of this solution again! Hi @thomaso and @Gabe I got some interesting new acknowledgments on this topic. Actually the error has nothing to do with the fact, that the document is linked to itself. It's just more likely to happen in this case. I tried the PDF solution this time. Again it took me about 3-4 times to reproduced the error behavior described at the first point. Step 1 Export page miniatures of the document at 30dpi (or any other smaller resolution) as pdf Link page miniatures pdf within document. Behavior as expected and different pages selectable and changeable. Page count not showing the page numbers anymore but the spread number as I exported the pages as spread, but this is not an issue. Save the document and close it. Step 2 Change some detail of the document. Export page miniatures of the document at 30dpi (or any other smaller resolution) as pdf and override pdf created before. Refresh linked document. Behavior as expected and different pages selectable and changeable. Page count not showing the page numbers anymore but the spread number as I exported the pages as spread, but this is not an issue. Save the document and close it. Step 3 Change some detail of the document. Export page miniatures of the document at 30dpi (or any other smaller resolution) as pdf and do not override pdf created before. Preferable take the same file name but another path. Save the document and close it. (close AP completely) Override the old pdf file with the new one just created. Open Affinity Publisher with the document again. If you refresh the linked document, the issues will begin happening again. My updated assumption is, Affinity Publisher having troubles with unwatched changes of linked documents. This happens with both cases before, as the refreshing of the document is happening after Publisher has closed it already. Demo Files (PDF and updated Publisher Document both attached...) Demo Book v2.afpub Demo Book v2 Page miniatures.pdf
  5. Hi @thomaso, thank you so much for your constructive feedback! Just to make sure it is not because of any old file format I created a new demo file with AP 1.8.3 without any templates or anything. So this time just with default DIN A4 measurements and without any page templates but unfortunately I was able to reproduce. However, it's not reproducible at the first attempt. I needed to save it multiple times and reopen the document 3 times until it happened again. What I experienced is it might is the reason of some little detail. Step 1 Linking document to itself, saving multiple times. Pages of the linked document still changeable. No issues. When closing the document, save it before but it will still show a "save before exit?-message" -> click no as you already saved. Document closed without any issues. Step 2 (optional) Opening the document again. Pages of the linked document still changeable. Change some contents and save it multiple times. No issues. When closing the document, save it before but it will still show a "save before exit?-message" -> click no as you already saved. Document closed without any issues. Step 3 Opening the document again. Pages of the linked document still changeable. Change some contents and save it multiple times. No issues. When closing the document, save it before but it will still show a "save before exit?-message" -> click yes this time. Document closed and issues will begin with the next time you are opening it. Step 4 Opening the document again. Pages of the linked document not changeable. Save again and it will reset the pages again. My assumption is, Affinity Publisher is luckily by default well prepared for this case. If the document is linked to itself, it refreshes automatically when the content is changed which is pretty cool. However the "save bevore exit"-dialog might cause some issues here and might not work as expected. Demo File (attached) Demo Book v3x.afpub
  6. Hi @Gabe, sorry for not being clear at this point. The document is linked although I use the word "embedded" to describe it. I understand this might cause issues, but it's required to work for a professional workflow.
  7. It took me 2h15 to save my 288 page document today and another 45min until Publisher finally freed the memory and wasn't freezing anymore.
  8. I am experiencing issues having documents linked with itself and am finally able to reproduce. Issue: I have a document which is linked to itself, so at the end of my book I have a preview of all content pages of the book. As soon as I save and exit the document this link somehow seems to corrupt already. After reopening I am not able to change the page of my linked document. As soon as I make some changes to my document, and save it, it will tell me, that some of my ressources refreshed. Also it resets the page of my document embedded to some (I would say random, but it's probable not) page. Although I embedded different pages of the document, all variants embedded then show the same page. If I would save again I would pretty likely destroy my document, as all my embedded pages will reset to this one page. Workaround: After having the document saved and the pages of the embedded document change the first time, I have to exit without saving (my changes are already saved at this point) and the document will reset to the correct pages embedded after reopening. I will need to exit without saving end reopening the document after any change I want to save. It's pretty annoying working with large documents and really not a comfortable workflow. Sample Pictures: Before Saving: (Please note, that at this point I am already not able anymore to change the page of the document I have embedded9 After Saving: (changing something like the text on the yellow page before) (Please note, that all embedded elements show the same page - 10,11) If I save the document at this point again, I will notice, that all pages will stick to pages 10,11 after reopening and will be all red. I will not be able to change the pages after reopening again and it will reset after another saving again. Demo File: (attached) Demo Book v2.afpub
  9. Alright thank you. Currently I am not so much layouting but did not experience any further crash which is a good sign actually. However, it feels like being slower without Metal support but nothing I could tell for sure. Let me know when this will be fixed
  10. So this happened for me again while using OpenGL. I do still have Metal Hardware acceleration activated, should I disable this as well? Crash Report: Affinity Publisher_2020-04-22-224801_MacBook-Pro-2018.crash RAM usage was about as this screen:
  11. Ok alright, thank you very much! Two questions regarding this: - if the device does not support Metal (correctly) why is it even possible to select? - if Metal is the best, why is it not set to default for those devices? Thank you!
  12. Hi @Jon P, thank you for your reply. Renderer was set to Metall and I changed it to OpenGL. I wasn't able to reproduce, what is a good sign actually, but I will keep it set to OpenGL and let you know if I get the same behavior again. Side question: Besides this bug, what are the difference between the render modes available? Which one is the best to choose? Thank you so much!
  13. My Mac (System Info attached) crashes when resizing images in Affinity publisher. I am working in a 140MB file with 400 pages (24x33cm) filled with images (all linked with a total of less than 10GB). However I am experiencing crashes when resizing images. Crash report attached: Affinity Publisher_2020-04-18-153621_MacBook-Pro-2018.crash I would guess this has something to do with some memory overflow or memory leak. I am experiencing this issue pretty irregulary, but would guess it happens when ever my memory (I gave Publisher 28 out of 32 GB) is not enough and therefore written to my SSD. It usually happens when I have opened a document a little while ago only and not with the freshly opened document. (After the crash it is usually possible to resize this image when done directly after the restart, but also crashing). Steps to probably reproduce: Create a large document filled with images. It has to fill up all your RAM available and write stuff to the SSD. Wait for all pages to be cached in the memory (scroll slowly through the complete document after opening it) Resize any of the images within a image box. If you have any further questions, let me know. Thank you so much in advance!
  14. Hi @stokerg, yes it is exactly the same same issue. I personally reduced the pages and currently I am able to work without this issue (but some others) again. It should be easy to reproduce by creating a document and filling like 600 pages or something with fullsized pictures >300dpi and the issue probably will happen at some stage as well. Pretty much depends on how much RAM you have available but when trying with a lower equipped laptop (e.g. 16 GB RAM) it should happen even earlier. After deleting those many pages (with the images on them) it will slowly beginn to be useable again.
  15. I think I did. Just wanted to reproduce this behavior and created a demo file for it. While using linking, it works well. Also experienced this behavior before upgrading to 1.8, maybe this fixed it as well. Except for the fact when I save the document and not change it afterwards it still asks me to save even though nothing changed (but the linked document is detected as changed). But this is ok, I can live with that! Thank you very much. I think one of the documents links was still an embedd in the old document. Funny side fact I noticed: When I add an image to the document the document size grows by about 0,3 MB for a linked image with 8,8 MB displayed at full size. When this spread with the image is not included in the summary page the document has about 0,8 MB When I change linked document pages to include the spread with the picture, it becomes 1,4 MB after saving. Interesting to see, I will keep this in mind when creating my main document with all my images.
×
×
  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. 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.