NZezula

Super sad that I have to switch back to Adobe.... this just takes ages to fix

And Im using macOS 12.3.1 and Publisher V2 2.04

Recently I just finished a big project using V2 (a 200-page catalog with tons of images) and I must say it was not a pleasant experience (compare to previous projects with V1 and even InDesign). V2 has been crashing a lot especially when the project got bigger. I was not able to identify why the crash happened the majority of the time, but I caught some of the glitches. 1. weight of some fonts doesn't correspond to export (if you leave the text as text and don't transform it to curves): test1: font as text, test2:text as curves + Printscreen of publisher (this problem I`m able to simulate easily). (This is especially a problem when you are trying to send the file for final proofs and they usually need to have it as text, to be able to insert comments to the text in acrobat) 2. bilinear resampling of images causes artifacts (from time to time and only with really big projects) (this is not such big of a deal for me because I tend to use Lasclo... I found out because I needed just quick export, so I used) - Im not able to reproduce it right now. test3: project exported using bilinear res.. test4: same project, same time, same setting except of resampling - lasclo3 non-separable but to be honest, those were minor problems compared to the constant crashing (once, there was a problem with a pixel layer, and I was trying to do anything with it, even delete it, but whatever I did it resulted in crashing, I was able to get through after maybe 30 crashes. another time one page was cursed, and whatever I did on the whole page resulted in crash -I think I had to delete the page and make the layout from the scratch) Another thing I noticed is, that the crashing went really on another level when I turned off facing pages and stop working with the spreads layout... I know that these pieces of information are too shallow to give you guys some real insight where is the problem.... but maybe someone had similar issues and will be able to provide more To sum it up, I`m going back to V1 publisher for a while.... but keep the great jop you are doing! running macbook pro 14 M1Pro test1.pdf test2.pdf test3.pdf test4.pdf

2.1.0.1709 ... still nothing 😞

Hi, To keep this issue alive, I'm updating you that the bug is still present in 2.04. (Please do not think that I'm some kind of hater, I enjoy my time with affinity and the amount of product you offer, for such a low amount of money is extraordinary.)

Hi @MEB, I would just add that it's not only in develop persona but in the photo persona too (if you add a new white balance layer and use the picker, it will do nothing with the tint)... I guess its the same function used in two different places so it does not matter that much, but for my use case, and I think for a lot of people too, the bug in photo persona is the bigger problem.... when you need to go through hundreds of photos per day and know that it will be presented either only on the web or in a small format you usually do not bother with RAW and do some bulk conversion as the first step or just shooting to JPG in the first place. And if the photographer forgets to calibrate the camera properly, or is just shooting for a long time and a light condition changes, you need to be able to fix it with one click in the software

@MEB thanks 🙂

I just want to update that 2.03 is out and the bug is still there.... 😢

Thanks so much! really looking forward to the fix! This is the only thing that prevents me from being fully loyal to Affinity suit. Keep up the great work and have a nice day!

I just want to say that I have opened the same topic on the V2 forum... sadly the problem still prevails

To sum it up: On non-raw files, either in the photo or develop persona white balance picker does not do anything with tint, only with temperature, which results in not changing the color under the picker to be neutral gray.

Hi, its actually a super old bug still present. Here is the forum topic from V1:

Hi, a month later doing the same job, and here its again. Posting as afphoto with history. thanks and have a nice day. DSC_0072.afphoto

I was not back then, but now yes. I'm using XnViewMP to process .NEF to JPG (XnViewMP allows to do it as macro, and I don't need to spend that much time on those photos)

good idea... I will save it as .afphoto as soon it happens again, but it is much rarer on mac os, or in the newer version of AP. (I went through 300 photos in last 2 days and it happened twice - back then it would be like 100+)