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

bsx

Members
  • Posts

    67
  • Joined

  • Last visited

Profile Information

  • Gender
    Male
  • Location
    Germany

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 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.
  2. 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).
  3. 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.
  4. 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.
  5. 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.
  6. 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.
  7. 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.
  8. 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.
  9. 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).
  10. 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.
  11. 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?
  12. 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.
  13. 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.
  14. 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.
  15. 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
×
×
  • 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.