NotMyFault Posted June 2, 2023 Posted June 2, 2023 Th attached file contains a 32x32px pixel layer. The Documents says it is only 31x32px large. If you copy the layer and create new form clipboard, the wrong document size will be shown again. As the layer contains 32x32 pixels (black/white alternating), it cannot be only 31x32px. 31x32 bug.afphoto Quote Mac mini M1 A2348 | Windows 10 - AMD Ryzen 9 5900x - 32 GB RAM - Nvidia GTX 1080 LG34WK950U-W, calibrated to DCI-P3 with LG Calibration Studio / Spider 5 iPad Air Gen 5 (2022) A2589 Special interest into procedural texture filter, edit alpha channel, RGB/16 and RGB/32 color formats, stacking, finding root causes for misbehaving files, finding creative solutions for unsolvable tasks, finding bugs in Apps. My posts focus on technical aspects and leave out most of social grease like „maybe“, „in my opinion“, „I might be wrong“ etc. just add copy/paste all these softeners from this signature to make reading more comfortable for you. Otherwise I’m a fine person which respects you and everyone and wants to be respected.
Hangman Posted June 3, 2023 Posted June 3, 2023 13 hours ago, NotMyFault said: As the layer contains 32x32 pixels (black/white alternating), it cannot be only 31x32px. It looks like a glitch in Photo with that particular file... Open the same file in Designer or Publisher and the Document Setup shows it as 32 px x 32 px. The Export dialog in Photo also shows it as 32 px x 32 px. Creating an identical document in Designer and opening it in Photo and it shows as 32 px x 32 px. Exported as a png or jpeg file and it shows as 32 px x 32 px. Quote Affinity Designer 2.5.7 | Affinity Photo 2.5.7 | Affinity Publisher 2.5.7 Affinity Designer Beta 2.6.0.3027 | Affinity Photo Beta 2.6.0.3027 | Affinity Publisher Beta 2.6.0.3027 MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse
NotMyFault Posted June 3, 2023 Author Posted June 3, 2023 3 hours ago, Hangman said: It looks like a glitch in Photo with that particular file... Open the same file in Designer or Publisher and the Document Setup shows it as 32 px x 32 px. The Export dialog in Photo also shows it as 32 px x 32 px. Creating an identical document in Designer and opening it in Photo and it shows as 32 px x 32 px. Exported as a png or jpeg file and it shows as 32 px x 32 px. The export shows the wrong size, too if you remove the rectangle which I added only as helper object to measure the size. Quote Mac mini M1 A2348 | Windows 10 - AMD Ryzen 9 5900x - 32 GB RAM - Nvidia GTX 1080 LG34WK950U-W, calibrated to DCI-P3 with LG Calibration Studio / Spider 5 iPad Air Gen 5 (2022) A2589 Special interest into procedural texture filter, edit alpha channel, RGB/16 and RGB/32 color formats, stacking, finding root causes for misbehaving files, finding creative solutions for unsolvable tasks, finding bugs in Apps. My posts focus on technical aspects and leave out most of social grease like „maybe“, „in my opinion“, „I might be wrong“ etc. just add copy/paste all these softeners from this signature to make reading more comfortable for you. Otherwise I’m a fine person which respects you and everyone and wants to be respected.
Hangman Posted June 3, 2023 Posted June 3, 2023 Did you create the file in Photo originally or in Designer, prior to rasterising the black and white pixel grid? Quote Affinity Designer 2.5.7 | Affinity Photo 2.5.7 | Affinity Publisher 2.5.7 Affinity Designer Beta 2.6.0.3027 | Affinity Photo Beta 2.6.0.3027 | Affinity Publisher Beta 2.6.0.3027 MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse
walt.farrell Posted June 3, 2023 Posted June 3, 2023 Also, how did you create that pixel layer? You often play around with PT filters, for example, and it's likely that the method you used is related to the issue. By the way, the thumbnail for that file is very odd in Photo 2 on iPad, and the file took a relatively long time to open. Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 18.2.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1
myclay Posted June 3, 2023 Posted June 3, 2023 38 minutes ago, walt.farrell said: the thumbnail for that file is very odd Best guess; the image for the Explorer thumbnails (128x128,256x256,512x512) need to be generated while the original image is too small. this is the result when you upscale it to 512x512 Bilinear The averaged result in the middle is odd, maybe Affinity has used a tiling method like Affine to fill the thumbnail image? This preview thing also happens on windows. The 31x32 within Affinity is truly odd, copy pasting that pixel layer into Paint results in 32x33px. Quote Sketchbook (with Affinity Suite usage) | timurariman.com | artstation store Windows 11 Pro - 23H2 | Ryzen 5800X3D | RTX 3090 - 24GB | 128GB | Main SSD with 1TB | SSD 4TB | PCIe SSD 256GB (configured as Scratch disk) |
NotMyFault Posted June 3, 2023 Author Posted June 3, 2023 I create the source image by rectangle 32x32px PT filter with osci(x,y), nested as child Duplicate (to keep the source layer) rasterize rename the thumbnail is direct product of wrong size / dpi. The whole issue is that at a unknown step Affinity remembered a wrong dpi for this layer. I noticed this only later after multiple duplicates and using the copies to stretch them, that DPI was off by 1 and nailed it down to the source layer. What I can’t understand is that a layer which contains exactly 32x32 pixels is missratend as 31x32px. You can’t store 32 individual pixel in a layer with 31px. It would lead to the thumbnail with mainly muddy grey. myclay and walt.farrell 1 1 Quote Mac mini M1 A2348 | Windows 10 - AMD Ryzen 9 5900x - 32 GB RAM - Nvidia GTX 1080 LG34WK950U-W, calibrated to DCI-P3 with LG Calibration Studio / Spider 5 iPad Air Gen 5 (2022) A2589 Special interest into procedural texture filter, edit alpha channel, RGB/16 and RGB/32 color formats, stacking, finding root causes for misbehaving files, finding creative solutions for unsolvable tasks, finding bugs in Apps. My posts focus on technical aspects and leave out most of social grease like „maybe“, „in my opinion“, „I might be wrong“ etc. just add copy/paste all these softeners from this signature to make reading more comfortable for you. Otherwise I’m a fine person which respects you and everyone and wants to be respected.
carl123 Posted June 4, 2023 Posted June 4, 2023 On 6/2/2023 at 9:14 PM, NotMyFault said: As the layer contains 32x32 pixels (black/white alternating), it cannot be only 31x32px. Rasterise & Trim the black/white alternating layer Quote To save time I am currently using an automated AI to reply to some posts on this forum. If any of "my" posts are wrong or appear to be total b*ll*cks they are the ones generated by the AI. If correct they were probably mine. I apologise for any mistakes made by my AI - I'm sure it will improve with time.
myclay Posted June 4, 2023 Posted June 4, 2023 (edited) Rasterizing and trimming is helping to fix the symptom but maybe not the root cause? I tried to replicate the bug but wasn´t able to get your error but when you scroll thru the history, the equation is vanishing in the first procedural Texture layer. Backwards scrubbing thru history keeps it intact but going forwards from step 0 it vanishes. Seems like copypasting formulars could be a culprit.32x32 test.afphoto Edited June 4, 2023 by myclay tried to rebuild error. NotMyFault 1 Quote Sketchbook (with Affinity Suite usage) | timurariman.com | artstation store Windows 11 Pro - 23H2 | Ryzen 5800X3D | RTX 3090 - 24GB | 128GB | Main SSD with 1TB | SSD 4TB | PCIe SSD 256GB (configured as Scratch disk) |
NotMyFault Posted June 4, 2023 Author Posted June 4, 2023 For this who want to investigate deeper. The issue started in another document (which I used as source before copy/pasting int a new doc), uploaded here with history. The screenshot shows the step where wrong DPI was observed the first time. I changed the size of the pixel layer in multiple small steps from 32 to 64, observing the resulting blurriness. When it reaches 64px it should show 72DPI, but shows 71 DPI. one possible cause is that i repeated a process to show gaussian blur on alpha, added a group, added a blur filter, inverted the mask. Later deleted those objects, but I duplicated the pixel layer when it was residing in the group, and my special blur filter rona alpha was active (on group level). 32x32 dpi mismathc first.afphoto Quote Mac mini M1 A2348 | Windows 10 - AMD Ryzen 9 5900x - 32 GB RAM - Nvidia GTX 1080 LG34WK950U-W, calibrated to DCI-P3 with LG Calibration Studio / Spider 5 iPad Air Gen 5 (2022) A2589 Special interest into procedural texture filter, edit alpha channel, RGB/16 and RGB/32 color formats, stacking, finding root causes for misbehaving files, finding creative solutions for unsolvable tasks, finding bugs in Apps. My posts focus on technical aspects and leave out most of social grease like „maybe“, „in my opinion“, „I might be wrong“ etc. just add copy/paste all these softeners from this signature to make reading more comfortable for you. Otherwise I’m a fine person which respects you and everyone and wants to be respected.
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.