Gianni Becattini

I tried to move everything on a non-iCloud-synchronized folder but nothing changes

Additional: If I relink the images, everything seems ok until I save and then reopen the file. The files are on the same disk as the afpub file on both computers (same folder tree on both computers)

An additional info: if I rename the folder that contains the images, so that APub cannot find it, I get an error message but the problem disappears and I can edit again the file normally.

The problem arises independently from the acceleration settings and only with this file, a chapter from a book. I could edit it only on the M2 Mac, but when I need to generate the full book, the operation is possible only on the iMac, because it crashes on the M2... Resuming: iMac: just one file systematically crashes when I open it M2: the book systematically crashes on export A dead lock....

No, it seems not to be related, apart from the fact that both appears only on the i9. Currently I don't use the second monitor that is disconnected. I am at work now, I check the HW accel when I am back. I suspect that Apple is not caring too much the Intel platforms anymore.

I am currently annoyed by the following problem: when I open an Apub file on my iMac i9, it opens but not completely, i.e., some image remains in low resolution, as it uses to do for the first seconds. The user interface is partially operative; I can scroll the pages but if I click somewhere everything locks and I must kill the application (if I ask to quit, the file window closes but Apub does not quit - it seems it is doing something in background). The same file continues to work normally on M2. This behavior changes from time to time; maybe that deleting a page it returns to work. If I continue to work on the file from M2, maybe that this evening it can start again correctly or not on i9, but when it starts locking, the problem is absolutely repetitive. I already tried deleting the hidden lock files with no success. Any help is welcome, my iMac became totally unusable.

Update: it seems to be a problem of Sonoma on Intel platforms. I tried different monitors and adapters but the problem is still there. I give up and use just one monitor.

I am using now an old Dell adapter and I had no more crashes. Fingers crossed...

Hi Walt, thanks for replying. After some tribulations, I believe I found the problem, probably of hardware origin. The possible culprit could be a USB adapter used for the second monitor. After I removed it, everything seems again to work correctly, including Nicepage and I had no more crashes. This evening I will try with a different adapter. Sorry for the false alarm.

I add that the only suspect operation I did is installing a rather questionable software called Nicepage, which produced a lot of problems.

I didn't use it since some days, but this morning Photo2 does not start. After some second the Mac closes everything and asks again for the password, but it is unstable and needs to reboot. I am using Sonoma 14.4.1 on Intel i9 platform. I am completely stuck, any idea? Thanks

By the way: the others books I created with Affinity are downloadable for free on my web page www.k100.biz.

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

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.

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

Understood! I am rather... "slow"! (ehm, ehm...)

@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

I do, thanks

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

Maybe is still not in the production version currently? The problem seems to be still there.

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.

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.

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

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 *****....

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