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

Gianni Becattini

Members
  • Posts

    350
  • Joined

  • Last visited

Everything posted by Gianni Becattini

  1. By the way: the others books I created with Affinity are downloadable for free on my web page www.k100.biz.
  2. My technical/photo book about ancient electronic oscilloscopes has been released and is available worldwide thanks also to Amazon. It is for me a great satisfaction: it seems wonderful to me, with its hard cover and about 600 high quality black paper (I avoid to give you more details to not try to exploit this forum as advertisement). The first bunch of books was oversold in few days. All that wouldn't have been possible without your precious and skilled help, which allowed an electronic engineer like me to become almost a "little graphic designer". Thanks from my heart! Gianni
  3. No, or better, when AP goes mad, I change the Apple profile to Image P3 and all returns normal. With the new AP version, I didn't note the problem again, but it seems to be still present on old files with Apple color profile, which I created time ago on the Intel platform, where this problem is not present.
  4. Yes, you're right... but since many years, the virtual memory should swaps to disk and make the machine even infinitely slow... but never crash. One trillion years ago I wrote an operating system for a Z280 processor, a Z80 with Virtual Memory Manager, something that most people never heard... OK, sometimes it crashed, but I was not Apple and the Z280 was not an M2. The application should not be aware of the available memory, it's an OS duty to make it transparent (besides speed). I could bet that the crash is not due to memory but to something else. Future releases of APub or a future purchase of a fully-memorized M2 will tell us the truth... However I fully agree with you, thanks
  5. @Serif Info Bot @Serif Info Bot About the M2 Mac flashing workspace - when using Apple Wide Colour Gamut" (REF: AF-473) I still have the same problem but not always. Maybe that the old files created with the previous versions have still the problem when opened in the last AP version? I have many files with this problem. Thanks
  6. Thanks for replying, Walt, and best wishes! Changing file format for images is for me not real; it would require weeks and this is for me just an hobby. But I hope that in time all these bugs will be corrected. Having the aphoto file directly included avoids lot of errors and makes maintenance/correction very fast. I insist that a trace file of what Publisher does could be a big help for both the users and the developers; in the worst case, you could try to decode where the catastrophe happened. In the meantime, I wish a long life to my 64G Mac... Thanks for all the help you gave me in 2023 and a wonderful 2024 to you and everybody here! Gianni
  7. Sorry, I understand that I didn't give you enough information, but I believe I can confirm you that the problem is not only repetitive, but relatively independent from specific files. In my case EVERY BIG PROJECT behaves this way (I am working on FOUR). The available memory really seems an ISSUE (all the projects compile correctly on the 64G i9 and each project regularly crashes on the 16G M2). Probably it is my specific approach with aphoto files always used directly, but renouncing to this feature would be very time-consuming when you have hundredths of photos with frequent changes/corrections.
  8. I understand and agree. iCloud is very often the culprit, maybe also in this case. Clearly files are identified with a reference independent from the name. Probably references are not related to this, I will open another thread. It convinces me... thanks, friends.
  9. To be honest, I am not absolutely sure that the problems are related... I don't want to give misleading information.. so consider this just a rumour. If I have more news I will post them
  10. I discovered something new. If I move the file to a non-iCloud folder and then move it back in its original folder, the problem disappears. But there is an extra problem. After that (of file copy), cross-references are lost and must be re-created. Very *****....
  11. Sorry, I am late, but uploading all seems not practical. The project with the images is about 200 G. Could it be enough the book and the afpub files? Thanks
  12. I don't know why, but the problem is happening more often. It is not terrible, because I can duplicate the locked file, but it is a little annoying. I am not sure the problem is new, but certainly, in my case, it seems more frequent since the latest Apub update.
  13. Yes, something changes: it appears the following question. Note that: the original name of the file was "V2_CH2_500-Series.afpub" when it no longer opened I made a copy of it (which works) named "V2_CH2_500-Series copia.afpub" and renamed the original file (that which doesn't open) in "V2_CH2_500-Series non si apre.afpub" ("non si apre" = "does not open" in Italian) currently, there is not a file named "V2_CH2_500-Series.afpub", so Apub stored this name somewhere else no hidden file is present in the folder Tnx
  14. No, rebooting does not change. In addition, the file behavior is the same also on different computers synced via iCloud. The original does not open, the copy works perfectly.
  15. Sorry for having not been clear. It is an afpub file, part of a book, that I have been using normally until shortly before, than it no longer opens (I tried also CMD/O with the same effect). I tried either from inside the book, either from finder. I get no error message; simply nothing happens. The workaround is to copy it, to remove the old file, and rename the copy. I supposed that some hidden file could be present in the folder, but it isn't. I tried also to move the file in another folder, with no effect. I am using the latest version of APab, with updated version of Sonoma, on a MacBookPro M2 with 16G RAM. Thanks
  16. I have more often this problem. In finder I double click a file (or right click/open) and nothing happens. The file does not open anymore. If I duplicate the file, the duplicated file opens normally, without any problem. Thanks
  17. I could do the check. On the i9, if I just open the book (without opening the chapters) the APub process uses 848M. If I open all the chapters, it raises to 28.11 Gb. During the export process, it slowly increases up to 21 Gb. When finished, it maintains 17 G allocated until quit. On the M2 the test is not significant for the crash (at about 10 Gb used). Both have plenty of disk space available (600 on i9, 400 on M2)
  18. I wish to add something here; I also had the problem with freezing, which was not due to APub but to iCloud. I understood that the problem is that iCloud removes the local file contents after a time you don't use it. So, APub is not stuck, but it just is waiting that iCloud completes the downloads. Clearly, this does not mean that every case is so, but I continue being tricked by this behaviour (still this morning...)
  19. I also have a recurrent problem in exporting books, the system crashes (with the dump window). It seems that the problem is independent from the export setting. My problem is that now it crashes ALWAYS with TWO different (rather big) documents, which constitute my entire job. The problem now arises only on M2 MacBook Pro, while, until now, it survives on the iMac i9. They have different memory sizes: 16 on the M2 and 64 on the i9. Could this explain the different behavior? I am very concerned, because if also the i9 starts crashing I am stuck with the work. Any idea? Thanks
×
×
  • 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.