bsx

I've recently completed some large projects (including a 264-page catalog with over 700 images) with Publisher 1.10.5 and 1.10.6 on Windows 10, trying to work around the known issues. That worked very well and I was able to complete all projects in a good time. Adobe is not an alternative for me. I work alone and can import templates or third-party work as IDML. Serif should give the V2 buyers access to the stable 1.10.6 release for work. And give us a way to import V2 files into V1. Maybe also via IDML.

I think, there ist no difference in converting images. I don't use XnConvert. XnView (I use XNVIEW MP) is a all in one Solution, a photo viewer, image manager, image converter for all plattforms (Windows, MacOS and Linux).

Hello Leight, I have now tested it again and today I can not reproduce the crash in Publisher V 1.10.6 on my computer. I think, there was no problem with the font selection. When I opening a publisher file, the program reported missing resources. I wanted to sort in the resource manager to the status - in this moment Publisher crashes. I will continue to monitor the problem and report it here. I have just tested it with V2 (loaded the V1 files and performed some actions). V2 Publisher did not crash in this test.

Thanks Walt for the advice. Sure, the update has replaced the error workaround files. I don't want to work with these tricks in the long run, but with tested and released versions of Serif. I am not a beta tester, I have to work. In the best with a stable version.

In November, using Lacerto's solution method, I had a stable Publisher version 1.10.5. I worked daily for several weeks with no crashes. Yesterday, after finishing a larger project, I updated to version 1.10.6. Shortly after that Publisher 1.10.6 crashed when I started the Resource Manager. 😬 Please, I need a stable publisher version to work with: whether it's V1 or V2.

Hello, I am glad to see that Photo 2 can now save WEBP formats. Yesterday I had a lot of images to convert, but unfortunately there is no WEBP format to choose from in the batch job export. The dialog is unchanged from V1, so I went back to using XNVIEW MP. This does a good job.

Many thanks to @lacerto. 😀😀😀 You have saved me. Because I can not use the V2 programs at the moment (I paid for them), so I continue to use V1 for work. yesterday @lacerto's solution saved me. Publisher 1.10.5 (Windows 10 22H2 all updates up to date) crashed on every action changing Preflight Profiles. I have many Preflight Comments in a large project and could no longer access them. I found the solution recommended by the Affinity team to uninstall 9 Windows Updates not very professional and I hope there will be a solution here soon as the bug has been known for a very long time. I can recommend the solution from lacerto. Publisher V1 has not crashed since the change. I have saved the original Publisher.exe.config file and can go back at any time.

Sorry, my English is so bad that I have to use a translation service. (DeepL). What I want to say is, I don't want to put any more time and energy into the migration from v1 to v2. I think there will be more changes with the MSI installer, e.g. where the configuration files are. As soon as the first patch is available and the MSI installer and I can use V2 as a working version, then I will think about it further.

Thanks for support to R CR and walt.farrell. I'll take a closer look at the migration when I can use the V2 for work. Sure the migration options will be similar, but I don't want to explore how to move settings from V2 (MSIX Installer) to a V2 (MSI Installer).

Thanks for the help. I will give up here with the migration and wait and hope for the msi installer. Surely there will be some other changes. I use V2 at the moment only for "play" and V1 for work.

oh, thank you very much. But then I'm still missing all the settings for the user interface, the toolbar settings and the system settings. I was asked during the V2 installation whether I wanted to adopt the settings. I said no. Can I repeat this import?

I think it is important and necessary that serif staff create a detailed manual as soon as possible on how to manually transfer all personal settings from the V1 to the V2. I also mean assets brushes and so on.

I am not sure if this is a good idea. I just noticed that all .propcol files in version 2 apply to all 3 apps (.affinity\Common\2.0\user\*.propcol). In V1, each app still had its own .propcol files. For example, I have different assets.propcol files in all V1-Apps and am already thinking about how to bring them together in V2. I'm waiting for the MSI installer.

Thanks for the tip, but unfortunately only in 3 fixed levels. I already use Large, which is sometimes still too small on my monitor. Here a stepless change would be useful.

I work with 2 monitors and put individual elements on the other screen if necessary. For books or catalogues with a lot of photo pages, I drag the PAGES TAB large and full screen to the other monitor. See picture 1. Publisher V2 has a wonderful Place Images function. Especially when there are many photos to be placed, you can keep track of which photos have already been used. Unfortunately, the full screen view of the PLACE IMAGES TAB is different from what I expected. See picture 2. The function is not very usable with hundreds of photos to be placed. Please change this. Maybe it is also possible for users to customize the size of the thumbnails in the Pages and Place Images TABs. That would be great. Windows 10 / Publisher Desktop Translated with DeepL

Make a table with the Table tool. Then open the text styles. You will find a style called table body. You have to customize it.

Thank you for the video. This is a simple way. It worked for me. The other option via data merge is too complex for my small calendar.

Please bring back the checkboxes in V2. I have now all V2 applications in the light UI style, because only there the difference is well recognizable. in the dark design I do not see whether a layer is active. In the Layer Effects area the checkboxes are present in V2.

Company licenses are only available for quantities of 2 or more, but I only need 1 license in my office. Therefore, I have not read more about it. I think, for company licenses don't exist other installers and and other licensing options. This would solve most of the current V2 problems.

I bought Affinity Suite 2 immediately and was very happy to see this story continue. But now, I will continue in my projects with V1 in the near future and observe further developments. Good: There are really some basic improvements and enhancements that will be very useful in future work. And I'm sure there will also be new developments in V2, which I'm looking forward to. Bad: This hype, overstaged by Serif, has not done the reputation of the software any good. Professional users were left completely in uncertainty for months as to whether this software would be further developed, discontinued or completely changed. No roadmap, no info, no beta phase. Now these unfortunate problems with the app installation, which has irritated many users who now have to realise the workflow with other programmes in workarounds. Also bad is the online activation requirement, which affects everyone who does not connect their computer to the internet for security reasons. But this will also lead to problems in the future, as we know them from Adobe. Activation servers can no longer be reached after a few years, the purchased software can no longer be used on new hardware. Conclusion: It was exactly these advantages of version 1 (no online activation requirement, user-friendly installation, easy integration into existing workflows) that made Affinity programmes attractive to many professional users. In V2 these features are reduced step by step and I think this is not a good way. My enjoyment of new features is very limited as a result. Wishes: - Standard installer version - Backwards compatibility from V2 to V1 (saving under V1 version even with the loss of features) - IDML export Sorry, my English is bad. Translated with DeepL

Many Thanks. That's exactly my opinion too. I think the communication of such major system changes must take place BEFORE. And not just discovered by users during installation. 😡

In my workflow, I develop RAW files in Lightroom 6.14 and transfer TIFF files to Affinity Foto. This is now possible with Affinity Photo 2 with a workaround (BAT--File by Walt), but after processing in Affinity Photo 2 it is not possible to return the TIFF to Lightroom. Affinity Photo 2 wants to save the TIFF file with layers even if there is only one. This problem did not exist in V1.

This is not a solution for me. I think we all work with software here that can be bought and not rented like Adobe. So I'm still working with Lightroom 6.14 and also other software and tools in older versions. It will stay that way as long as Serif doesn't offer a RAW converter like Lightroom. So we have to hope for the compatibility of the Affinity programs so that we can continue to use our other programs.

sorry it was my fault Lightroom didn't save the settings. Now it works. Thanks Walt! But that's just a workaround. no solution

The BAT-file doesn't work with Lightroom 6.14. and Windows 10. The batch file starts Affinity Photo 1.10., not the V2 version. SORRY I also don't want to change everything on my computer just to run this new version. I would like a normal configurable program installation, like V1. Otherwise must work without these V2 programs in the future.