Gabe
-
Posts
10,193 -
Joined
Posts posted by Gabe
-
-
-
23 minutes ago, UweN said:
No problem if I use two new afpub documents with text frames and add an empty page between both documents.
So it is document related then. Can you attach the document in question?
-
Hi both,
Actually this has nothing to do with hardware acceleration, nor our app. The problem here is the source EXR file, which has loads of NaN pixels. When using noise reduction or any other filter that look are based on neighbouring pixels, any math operation including NaN will result in a NaN. So what you see is expected.
What software did you use to produce that EXR? It should not have NaNs.
As a workaround, you can apply a procedural texture and that should turn all NaN values into (0,0,0)
-
42 minutes ago, sfriedberg said:
I had pointed out similar/same issues with pinned content at the top of the page in the original 1098 announcement thread and was getting ready to start a new thread on the topic, since I hadn't spotted an acknowledgement
All bugs should be reported in a new thread and not in the announcement thread...
-
Can you replicate it with a basic afpub doc with just one shape instead of using your scanned tiff?
-
Hi @UweN,
I can't replicate this here. Is it document specific?
-
16 hours ago, ABI_ said:
Will do now - yesterday was hesitant as there is a disclaimer that files may loose data as the beta version isn't tested
You can always make a copy of your file and work on that.
-
Hi all,
Thanks for spotting this. Issue logged.
- Orlon and sfriedberg
-
2
-
Hi @Sashariel,
Welcome to the forums.
What mouse do you have? That sounds like a driver/3rd party app issue to me more than anything.
-
Hi @shazoom,
Thanks for spotting this. Issue logged.
-
Have you tried what I suggested in my first from here?
-
Thanks. Issue logged.
-
Hi all,
I replicate this here and logged it with our developers.
- walt.farrell and rikkarlo
-
1
-
1
-
Hi @Pawel Chonya,
I split your post in a new thread as your issue is quite different and it's not beta related.
I wonder if you see this because of your M1 iPad. 99% of the time, issues caused by Apple RAW are Apple's bugs and we can't really do much to fix them.
Do you happen to have a non-m1 iPad and see if it's fine with the same file?
-
I know it may sound weird, but can you try and reboot your iPad?
-
Hi @anweid,
Thanks for spotting this. we are aware of it and it has already been logged with our developers.
-
Hi @balolo,
Does it freeze or crash?
Can you try and replicate this with our latest beta?
https://forum.affinity.serif.com/index.php?/forum/62-affinity-publisher-beta-forums/
-
Hi all,
This should all be fixed in the next release.
-
Hi @RosomakPL,
Your selection is on Artboard 1, but you have Artboard 2 selected in the layer panel.
-
Hi both,
Thanks for spotting this. Issue logged.
-
It's not against the rules, but will most likely cause confusion when you're describing unrelated issues with the same samples
-
Hi @NotMyFault,
this is an interesting one. I don't think you should be able to "correct" it over and over again. The same thing happens if you apply a WB adjustment and merge it.
By the way, how is this sample image related to his other post? You're both using the same image
-
Is it just with Z7 raw files or with any? It seems to be fixed on our end. also, what iPad model have you got ?
-
What Windows version are you running?
Can you attach a crash report?
1.10.0.1103(Beta) - crash - add page
in [ARCHIVE] Publisher beta on Windows threads
Posted
Thanks. This seems to be a regression and not really document related. If you add pages from any document and then try to insert an empty page in between the 2 documents, it will crash. Issue logged.