Jump to content
You must now use your email address to sign in [click for more info] ×

Gianni Becattini

Members
  • Posts

    368
  • Joined

  • Last visited

Everything posted by Gianni Becattini

  1. Sorry I forgot some points: I am using Mac, not windows - all of them with 13.0.1 Ventura I have 3 x Macs and use them all, sincyng the contents via iCloud I use only the main HD I tryed to use a space outside iCloud with no change.
  2. Thanks for your reply. Yes I tried elsewhere, but I got only quick replies. So, let's start again. my document is rather big: now is 440 pages and has more than 600 photos, diagrams etc. Perhaps is its size that creates problems (?) besides few jpg and Affinity Designer, all the images are saved as Affinity Photo; with AP 1 I never had big problems, besides a day that I could not anylonger open the file and you fixed it for me; the problem is rather repetitive. When the document is healthy, it is about 600M big. Then I add an image and when I try to save it, everything can happen, from complete AP crash, to message that says that the document cannot be saved or other kill message. I used ALWAYS the same scheme: any photo is an APhoto document, always I add a picture frame, then I place the image inside it in linked mode; when the saving does not produce a crash or other catastrophes, very often the document grows unreasonably (up to 5G) and many photos become embedded and not anymore linked; a possible workaround is to set all images as embedded and then to linked, and this often works, but I should do it every few minutes and it is not a practical way out. I cannot write the contents and continuously stop, check, recover from crashes etc. now I am trying to split the all document in sub-documents and put them together as a Book. Until now I had no crash in this way, but I worked only on a small part of the document. I will have other problems in this way, but if that is the only way, I will accept it. now the problem is almost repetitive, so it could be a case study for your developers. Herzlich thanks for your help
  3. I am not normally a troublemaker and I am very sorry that I became that in this case. But I am with my shoulders against the wall. Could please someone at least give me a workaround? I continue to propose solutions, but besides some quick answer, nobody really gave me attention. I used to be a software developer, I know well this kind of problems and I am available for any cooperation. I ask attention, because this problem became really big for me, and the last thing that I wish is a legal suite. Please, please, please.....
  4. Is there any expectation about when Affinity Publisher could allow to work normally? nI am referring to the crashes subsequent to placing images. Its instability is destroying me and my work. Is my file that has something wrong in it or is it a general problem? Is it possible that nobody is interested helping me?
  5. Thanks for yours replies. The point is that my current work (a book with 420 pages and 600 photos) has been completely ruined by my stupid idea to pass to Publisher V2, for its total instability. I don't claim anymore for that: Serif set a trap and I fell into it. But I am very practical and the point is to survive now. I am ready to accept anyything: to lose the hyperlinks, to have a different page numbering etc, but I can't live with this anguish that every time I can lose everything I've done. So the point is: using sections can I split the document in more files? Is this an advantage for the application bugs, dealing with smaller documents? I tried to use section, but the document remain exactly the same, it seems only an internal logic distinction. Am I wrong? Thanks
  6. Thanks. Both can be installed on all the Mac I want? I use normally 4 of them (MacBook i7, iMac i9, MacBook M2 and MacPro) and keep them synced with iCloud.
  7. Besides the price, there are differences in the license bought directly (e.g. if I buy the current promotion) or if I buy from Apple Store? Thanks
  8. I am having lot of troubles with AP2, perhaps because my document is rather big (?), especially managing pictures. Splitting the document in sections could be a good idea or am I going into worse problems? Thanks
  9. you are very kind and I thank you. But something seems strange: the fonts that AP requires are called "Times" and not "Times New Roman" (that is installed and not hidden). No "Times" font seems furthermore to be included in the list you sent me. I tried installing a "Times" font but it is not seen.
  10. My problem seems not to be related to V2 nor MacOS 13. I always had this message and, for what I remember, I never used these fonts, that are not installed in my system. Is it possible to detect where AP thinks I used these fonts?
  11. Preflight says that the following font are missing: Times-Roman Times-Italic Times-Bold If I press "FIX" these fonts are not present in the list, nor I remember I ever used them. These fonts are not installed in the system (I have Times New Roman). I tried to find them but with no success. How can I remove these errors? Thanks
  12. 412 pages and 589 photos. Its a free book, you can download the previous version (368 pages) from http://www.k100.biz/parade.htm or from https://archive.org/details/tekscopes-E03/Tekscopes E03 hires/
  13. I add something that can help other unhappy users. - I had not the "Save History With Document" set, so no change in my case; - A strong instability remains, but however I can work, and saving every few minutes does not fill the hard disk, being the file size however reasonable; - after few photo add, the file starts again growing; - I did an interesting discover (I don't know how much its validity is general). Every time that I add a picture, I tremble... 90% cases I will get a message "impossible to save". But if before saving I apply the trick you suggested me even only to the added photos, the saving is again possible and the file returns small. Thanks again, you saved (part of) my life!!!
  14. Wow! It seems it had a great benefit. The size of the file returned to its value and until now (last five minutes) I had no crashes. I will keep you informed, however for now A BIB-BIG-BIG THANK YOU!
  15. WARNING, DON'T USE PUBLISHER V2 if you have serious work to do. It is absolutely unreliable. I lost an entire week of hard work. The file passed from 500M to 5G and now it is no longer editable. I was already late with my work, now I go into big troubles. The only solution is now going back to rev. 1, comparing line by line each of 410 pages of graphics and re-converting 59 images by hand. Another week, if I am lucky. Very, very disappointed? Believe me, the point is not the price, I would pay 1,000€ now for having not trusted Affinity. Thanks, Serif.
  16. Now I am completely stuck. I am not able to complete my work. Probably I will have to pay for that, I am in big troubles. Thanks Adob.... ops, Affinity.
  17. Most, if not all, problems that I have seem to be related to placing images.
  18. Today with Affinity Publisher I had 34 crashes. For unknown reason, with M1 processor, the size of the file grew from about 500M to 2G (known bug). I save about every 10 minutes, so I stored today about 72G byte of various versions. Sometimes previous version cannot be reopen, so in that case I lose 20 minutes work instead of 10. Now the size of the file grew to 3.63G, without any reasonable cause. What can I do? Have I to split the document in more parts? But then, how do hyperlinks work? This is not a claim, is a humble supplication. I don't know I can go on.
  19. Today with Affinity Publisher I had 34 crashes. For unknown reason, with M1 processor, the size of the file grew from about 500M to 2G (known bug). I save about every 10 minutes, so I stored today about 72G byte of various versions. Sometimes previous version cannot be reopen, so in that case I lose 20 minutes work instead of 10. These are facts, not words.
×
×
  • Create New...

Important Information

Terms of Use | 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.