multis

Well. It crashed far less frequently now that update is done. OUr whole team is now at 1.10.6 (most Windows users, some mac users) and frequence of crashes is not that bad. But. There is one new problem. On normal printing resolution of 600 dpi with the settings we've used since we changed to Publisher the PDF Export that used to take 20-30 sec now takes 10-15 minutes. Considering that it is just one A3 spread, one sided, this is really not what you'd expect - and like I mentioned it used to be some seconds depending on machine. My workstation is rather okay Ryzen 5600X, 64G RAM and W10 x64. It hasn't changed since last version which did this in seconds. So. What HAS changed in PDF export? I have point out that should I choose 300 dpi it STILL is seconds. 15 minutes per PDF export is truly excessive and rather debilitating. Ideas?

After updating to 1.10.6 no crashes. *knocking wood* I was saying that it started to crash 1.10.5 which was stable or relatively so, until the "new version is available" appeared and THEN 1.10.5 did start crashing. This has been ongoing case on all of your updates for a long while. It is really a bummer, if every time you release a new version your "new version notification" breaks the existing software to smithereens. Keep in mind that this behaviour has been tested to work every time, like a clockwork, if the old version sees new and the regedit is not applied. I have no idea why 1.10.6 did actually get the notification (eg. have you changed the regedit key?) or what did cause that to appear as for a long while I have been blissfully not seeing such annoying notices and thus my software has been stable. You'll find these notes from older bug report, but just to recap: If I take network cable away, my old Affinity works like a charm EVEN if there is new version existing. Publisher also immediately starts to crash on most files if I put the network cable back and the update notification finds a new version. So, yes, it has been proven quite diligently that the update checking thingy is buggy and something I'd very much want to entirely avoid. Thus, what is the new magic regedit key I need to edit in order to get rid of the new version notification?

And here we are again. New version, this time 10.6 and it creates exactly same kind of problems as all previous versions when new update notification appears. All files that used to work flawlessly start to mysteriously crash on load. For a long time 10.5 worked nicely. And now, all the files that I have done within last months are crashing on load. How really, really nice. It happens like a clockwork with the new versions - and this time despite the fact that I earlier on turned (with RegEdit) the update notification off. And it was off for a while, but no longer it seems. This is truly annoying. What can I do? I can't redo all the files when ever you create new version of Publisher. This truly isn't the first time it has happened.

Is this fixed in 10.6?

We changed away from Indesign and do not have any intentions of going back. But having worked with it for years, there are a lot of old Indesign files that occasionally need to be imported to Publisher. From customer point of view a feature that used to work and then stops working (like IDML import from .9 changed to .10) is clearly a bug. You can try to paint that to something else, but it doesn't change the facts. Serif has had 6 months to fix it and many .10 subversions were done, but IDML import is still broken. I, for one, would really like to see it fixed in the NEXT Publisher version. I wonder your view point. You have used a some effort in the replies, but do not seem to see the actual bug as a bug. I can't see what your motives are and maybe that matters not. What matters is that @Serif_Desktop team would actually fix the problem.

Wow. You really don't know what you talk about. You can not make editable files via PDF. Try having a rulebook with 500+ linked or embedded files (symbols and pictures) converted to pDF and then open it in Publisher. Then editing it is misery beyond anything. All layer groups are done, all box sizings will be random and everything is rasterized which is NOT what you want. The workflow that SHOULD work and DID work in .9 is to export IDML from Indesign (on old files that were not originally done using Publisher), Import those using Publisher and then relinking all. Kindly keep firmly in mind that if .9 of Publisher did work on these issues just nicely and now all .10 versions do not, it is not something that is fixed by changing your workflow entirely.

I like your persistence. But did you read what I wrote? If it worked on .9 of Publisher but does no longer work on .10 it is damnably hard to say 'oh, it is IDML' that is at fault. And yes, I did restart PC. But obviously I am still using same .afpub files.

Yes, I did read that. But that only applies to the crashes on font box. I did now remove the offending MS update, but still it does nothing to crashes when importing more complex IDML files, nor when you have enough (hundreds) linked files or when the embedded files grow the .afpub to over some size. No, I do not run out of RAM. And all of these did work with .9 version of Publisher. The very same files did not crash then on the same actions. Out of these the most annoying is the IDML import bug. It has been there now for 6 months. Any IDML import works on .9 and only the smallest and easiest work on .10 that cannot be right even from Serifs point of view. I'm also pretty confident that I am not only one importing IDML to Publisher.

Nice, but my issue is (and has been) with Windows 10 x64 and I have absolutely all patches applied.

Guys, it has been six months and the latest Publisher is still super prone to crashes. It crashes on IDML import (didn't use to do that with .9) It crashes if you have a lot of linked files It crashes if you have a lot of embedded files It crashes if it thinks you have font missing (even if those fonts were perfectly alright earlier) and so forth. And it's six months since I last saw anything at all from you guys on these matters. This is our primary tool. We use Publisher every day. It tends to get better if you use the same file frequently (beats me why) but these are not 'small annoyances'

So when is this fixed? I mean if I need to know the DPI of everything in advance and can never change it again without it being resized automatically this is truly annoying.

Wow. Quite unlikely bug. If changing resolution of file actually means that since then cut & paste uses the previous resolution somehow, that is quite annoying. Most often we do set files to 600 dpi at creation time, but as this is not file I originally created, it is hard to say. And yes, that truly sounds like a bug. It doesn't quite explain how I have seen symbols going to 0,01 mm x 0,01 mm in size on exactly same kind of event. I doubt I would have increased the resolution that much... But what IS possible that the linked symbol files have seen resolution set change. If this is actually working as a multiplier of some sort, that could cause very big changes. Like create a document at 300 dpi, add symbol done at 150 dpi, increase the documents resolution to 600 and symbol files resolution to 600 dpi. That would likely mean 50% * 25% = 12,5% of the original. Still far away from going to 1%, but it is not entirely impossible that symbols themselves couldn't have seen even bigger resolution changes.

I did further research. I took another copy of the chapter of the same book. Deleted all pages. Added empty pages. Copied all content there. It works. Please note that master pages of that file and the "broken" file are copies of each other. But somehow one works and another doesn't. This file works. While the one I uploaded previously does not. Same master files. Same symbols. Same content. What has changed in the file where it doesn't work? Note that also that file DID work for quite some time, but when I added two more pages and applied master pages it stopped working. This time copying all was still somehow possible. But that isnt something I can do for every file when *something* changes on master file and symbols begin to resize. So, somehow Publisher does find means to corrupt the master page in such a way that if I cut & paste specifically using frame text tool, it WILL resize the symbols. This time the resize factor is 50%. But I've seen it also resizing to 1%.

This can be replicated also by simply using following steps: - Make picture frame of 5x5 mm. CTRL+X that frame. Select Frame Text tool to insert that frame in the text. - Insert for instance this symbol in the picture frame. - Copy the said frame using MOVE tool and paste it in the same place. It works. - Copy the said frame using Frame Text Tool and paste it in the same place. It becomes 2,5 x 2,5 mm frame. Doesn't matter if the symbol is linked or embedded. It STILL works the same. I even tried to redo the whole file. I made template of same dimensions and copied the master file. If I copy the same stuff to a new file, it DOES resize. So something is causing the resizing on this particular file (and some others) and DEARLY like to know what that something is. If I copy the content to an empty file with NO MASTER file, it works okay. When the symbols are pasted the size stays the same. So. My humble observation is that something on this particular master page is causing it. Note that EVEN IF I use text frame to paste on this file OUTSIDE OF THE MASTER, it STILL resizes. It does not matter WHERE the content is copied, as if I cut & paste using text frame tool on another file and paste it here, it STILL resizes all symbols to half.

And pray tell me how this is possible with symbols that work flawlessly on many other documents on same text style font size. And considering that as I mentioned. if I set the symbol correctly (eg. the picture frame is 5x5 mm) and then copy the very same frame using frame text tool and paste it in the exactly same spot, it becomes 2,5x2,5 mm picture frame. If I copy it using Move Tool (or selecting it from layers view) and THEN paste it in exactly same place, it works as 5x5 mm picture frame. NOTE that if I COPY the symbol using 'move' tool I *CAN* paste it multiple times using Frame Text Tool without resizing. But on every occasion where COPY is done using Frame Text Tool to select the symbol(s), all symbols are resized, no matter where I paste those. And on this document the resizing is always to 50% of both dimensions.

I can reproduce the problem on any of the symbols on the 2nd column on page 2 for instance. Even if I copy symbol using frame text tool and paste the same symbol in its place. It will be changed to 50% size.

Uploaded now. Please note that like I mentioned, I have several files using the same symbols and this happens on SOME of those files. But with this file is seems to be recurring. This file experiences also from the crash problem that made separate bug report. To use this file at all, it takes 3-6 cases of opening the file. If Publisher does not crash within first 3-6 seconds, it will work. But most often it really takes several attempts before it is 'stable enough'. I had no such problems with 1.10.4 either.

Same file.

1.10.5 seems to have surfaced the old annoyance of frame text tool selected cut & paste cause symbols to resize. If I select the same symbols using the regular arrow and do CTRL+C, change to frame text tool and then CTRL+V, the symbols do not resize. But selecting things to be copied using frame text tool and pasting with the same tool (as you should be able to do) makes the symbols tiny. It seems to differ how tiny, but most often I'll get exactly half. 5x5 mm symbol turns to 2,5 x 2,5 mm and that is extremely time consuming to fix. On some occasions the resized symbol becomes 0,01 mm in size... All symbols are vector images on a fixed size picture frame. All symbols are also inserted INLINE, are using baseline positioning and work on most documents quite nicely. I would be very happy to find how to make sure this resizing does not occur. When cut & pasting, under no circumstances should Publisher unilaterally decide to rescale anything. I attached an example. When I cut & paste this segment, if I need to manually resize all 6 symbols, that is a huge problem. It increases the work hours needed to layout a single rulebook sheet considerably. Effectively doubles the time needed. And again, this did happen at some earlier point (I believe 1.9.x version) and was later fixed. Didn't happen with 1.10.4 and now does happen on SOME files with 1.10.5.

Over a week and no solutions. Sad.

Indeed. Very sad. And completely avoidable if only Serif would take their customer feedback seriously and DISABLE the update notification (or at least allow users to choose if the software ever polls it). Some versions are more stable and I'd dearly like to use those as long as *I* deem that it is good idea to change to something new. Now that decision is taken out of our hands and we're given these "new versions" and are forced to work as guinea pigs. No, not at all what I'd like to do.

... and after an hour of actually something productive, the next file. And surprise: It crashes the Publisher. Now, after 10+ crashes at launch, this is becoming desperate. And again, this is a file that worked FLAWLESSLY before 1.10.5 was released.

I even uninstalled the Publisher just now. Then removed the whole AppData for it. Then installed 1.10.5 again. And still same failures. Same crashes and NO crashreports of any kind. I have urgent deadlines and can't work. Again. Thanks to the unwanted "updates". So. I uninstalled it again. This time installing 1.10.4 instead. It *IMMEDIATELY* notifies of the new version AND crashes about 2,5 sec later no matter what I do. And again, no crash reports of any kind. Next stage. I UPDATED to 1.10.5 WITHOUT uninstalling 1.10.4. The file opens and works at least some time. So. I have now verified that I can no longer use 1.10.4 to files that were created with it. Again, ONLY THING that changed is that you released 1.10.5. And 1.10.5 update does cause files created with 1.10.4 to crash until I manage to save them with 1.10.5 when that problem ceases. I have AGAIN point out that it produces NO crash logs on these crashes and it ALWAYS happens just when opening a file within first 2-3 seconds.

New versions are not out. I have 1.10.5 installed. If remove that and re-install 1.10.4 this will re-occur immediately. This has been tested many times before. Eventually, once you have saved the old files with new version many enough times Publisher typically crashes rarely. But now it is like this (made a video for you): https://www.dropbox.com/s/3rrwxvrene266ve/Debut 1.mp4?dl=0 That is the time window when the file is accessible. It will continue to crash (notice that there are no errors of any kind) ad infinitum unless I manage to change something and resave in that period when the file is accessible. I've attached crash log from C:\Users\User\AppData\Roaming\Affinity\Publisher\1.0\CrashReports\attachments\a9d5285a-26f8-4fd5-99cc-f3e7adb50914 and likely it tells little. This has been the case earlier too. WIndows is rebooted. AMD drivers are the latest. THE ONLY THING that has changed is that you released 1.10.5 and then .4 stopped working. Backtrace folder is empty. I included also latest file from 'reports' folder, which seems to be binary and thus not readable to me. It doesn't create .dmp every time (see the frequence from PNG). You'll notice that from yesterday and today, it shows *nothing*. And just today, the crash I made video and the 10+ other crashes when I've tried to make the same file to work (not working still) have produced absolutely nothing. It is worth considering that the file did work with 1.10.4 and didn't crash. I even copied the file and still the same problem, so even if the copy of the file resided in local hard drive, is renamed and all other tricks you've been suggesting, I have now frequently/constantly crashing publisher (again) thanks to the update. Well done. attachment_Log.txt 4bea0fb8-98e7-4bd3-aeae-feb8bf277d1a.dmp

New versions are not out. I have 1.10.5 installed. If remove that and re-install 1.10.4 this will re-occur immediately. This has been tested many times before. Eventually, once you have saved the old files with new version many enough times Publisher typically crashes rarely. But now it is like this (made a video for you): https://www.dropbox.com/s/3rrwxvrene266ve/Debut 1.mp4?dl=0 That is the time window when the file is accessible. It will continue to crash (notice that there are no errors of any kind) ad infinitum unless I manage to change something and resave in that period when the file is accessible.