Nazario
-
Posts
316 -
Joined
-
Last visited
Posts posted by Nazario
-
-
So they've broken it now then? lol
-
It’s ‘by design’ mate lol.
Its funny though because Andy’s response in the thread below goes completely against the information in the tutorial on resizing.
-
1 hour ago, Petar Petrenko said:
As I remember, they explained that you should change pixels into any terrestrial unit (cm, mm, in...) for that to work.
Doesn't matter what unit i use it just does not work. My initial screenshots were using CM and Pixels.
-
I have posted it in the bug reports forum and linked to this thread.
-
FYI Preview app in MacOS also works exactly like Photoshop and I get consistent and more importantly 'expected' results. I'm trying to create an Automator workflow to allow me to drop files onto a workflow and to change the resolution for me but I'm struggling to find an action to change resolution. At least I can use Preview and its very quick too.
-
31 minutes ago, R C-R said:
FWIW, the developers have made it very clear several times that while they welcome feature requests & consider all of them, what gets implemented & most importantly when depends greatly on how that fits into what they already have plans to implement, how much bug testing is involved, what changes would be required in the native Affinity file format & the code base shared by all the Affinity apps, & which new features & improvenments to existing ones would benefit the greatest number of users.
I have no problem with that. My problem is that there is a bug, why include a resample tick box if it doesn't actually do anything? Plus we all get inconsistent results. But also the fact that there is no explanation of their implementation. You can't just add more pixels to an image and say the resolution has increased or take them away and say its decreased. Thats what is happening and its inherently wrong. When you change the DPI the pixels should remain constant and only the print size should change hence why its called Dots per inch and not Pixels per inch.
-
-
16 minutes ago, R C-R said:
I am not sure what you mean by that. In general, 1.0 is the first public release & anything older than that is a private alpha or beta version not available to the public. The first public release also may include a third number (like 1.4.1 or 1.4.3) indicating there were earlier versions that may or may not have been released to the pubic.
I can't remember the number versions so I'm probably wrong on 'prior to 1.0'. What i meant was i was part of the public beta's for all the apps prior to release and even before Photo was officially released as non beta retail I had the issue that we are discussing but Affinity say is by design. Hence, I'm assuming, why its still not been fixed and now simply gets ignored.
Basically we have a very expensive RIP that throws a wobbly if any images are below 300dpi. Due to Affinity's bug AND implementation of document resize I can't get any images past it so I'm unable to use Affinity Photo. Simple as that.
-
I mean prior to 1.0 release!
-
Its been like this since the betas for me.
-
3 minutes ago, R C-R said:
Yes, you are correct. That is wrong & what I get ...now. What is weird is yesterday I was getting different results, the expected ones from exactly the same file. I have no idea why. I didn't change anything in any of my Affinity Photo 1.7.0 settings.
Ive told them its a bug but i see posts whereby they state its 'by design' as Petar has said. If its 'by design' i want to know their logic. I've shown mine above.
-
Forgive me if Im wrong but i believe this is how it should work with resample OFF and that the pixel dimensions and the print dimensions, while linked, should be treated separately.
-
Here is the video where Affinity themselves say DPI is a physical measurement (50 seconds in) but they don't treat it as such. I feel this video does not explain anything very well and newbies will end up more confused after watching this.
-
13 minutes ago, R C-R said:
I think @Nazario is talking about a different issue, that being what happens when the Resample box is not ticked (so the two size fields & the resample options are greyed out) & the DPI value is changed. The issue you are talking about is an old, still unresolved one.
BTW, your two screenshots don't seem to show the before & after results, just the settings you are using -- note that the ruler has not changed. I also noticed that you have the same weird 1.7 issue many others have reported, that being two snapping magnet icons on the toolbar instead of the single multi-icon snapping group. That can be fixed by resetting the toolbar to the defaults in the Customize Toolbar dialog.
He was showing me his way of achieving what i wanted.
Basically calculate everything yourself which is not how it should be but it is a work around.
-
55 minutes ago, R C-R said:
Yes, you made that clear in your earlier post. But I can't reproduce your results on my 2 Macs, & I know that it works the same way on many other Macs & PC's because it is often mentioned in posts in these forums & elsewhere that it does.
That's why I suggested posting a screen recording. If you can't do that, maybe a screenshot of the Resize Document settings you are using & ones of the before & after results with the Ruler showing would help explain why your results are different.
The screenshots at the start of the post show that (minus the rulers) but i'll explain again here for clarity...
This image shows the document at 100mm x 50mm @ 300dpi.
In this image all I've done is change the units to pixels to show the pixels at the above 100mm x 50mm @ 300dpi. This is correct.
This third image shows what happens after I change the DPI to 150 with resample OFF. The size has stayed the same which is wrong. It should of increased to 200x100mm. Note its actually very slightly DECREASED. Also note the zoom level has changed which also confirms the pixels have changed.
The final image shows the same situation as image 3 but I've selected pixels to show what the pixels have changed to. They should be 1181x590 not what it shows here. Only the print size should change not the pixels. The fact that the pixels get treated the same as the print units in Affinity UI is part of the confusion. They should be treated and shown separately.
-
Thanks. Im thinking of creating a script so Preview can resize stuff.
-
My problem is I get the same results whether Resample is ticked or not. Which is a bug. What I don't understand is how Affinity are implementing document resize and because of the bug I have on 3 different macs it makes it even harder to grasp their thinking, especially when no one is responding.
-
I'd be happy if they just came out and explained the logic behind it. I get the sense that there may even be conflict regarding this within Affinity hence why no one has come forward to address it. I will probably not be purchasing the updates in future because of this.
-
I still have the problem even with your file. It happens across the 3 different Macs!!! I simply can't use Photo and no one at Affinity is getting back to me. Its ridiculous. It IS a bug but Im also struggling to comprehend their implementation on resizing/resampling. Their method seems to actually change the data in the image by adding pixels for increasing resolution and removing pixels to lower it. That in effect is destroying the integrity if the image and should not be happening. All the data that is required is already within the image its just the meta data that needs amending to say its now 'Xmm' x 'Xmm' @ 300 dpi.
I acknowledge your info about the pixel dimensions being different to mine. I rounded them out to make it a little easier for the post.
I simply can't use the app until its fixed and I'm seriously considering a refund now which I'm very reluctant to do.
-
1 hour ago, Petar Petrenko said:
What could I do. You were so fast. Just as Doc Holliday.
This is funny
-
1 minute ago, Petar Petrenko said:
Sorry, I've made a mistake and I corrected it.
Phew, I was a whole other level of confused for a minute haha.
-
1 minute ago, Petar Petrenko said:
Nobody say it's a bug. Just a bad implementation of PS's "Canvas Size".
But Canvas size has nothing to do with resolution?!
-
Please can you explain the logic behind it for me then as no one seems to respond from Affinity even though I've private messaged people and made numerous threads about this. Im certain i saw a video from Affinity that states "Dpi is a physical measurement" but the logic being suggested is that Affinity don't actually see it as such. Im so confused as to how they implement it.
I certainly do end up taking images into Photoshop to resize but then i just end up staying there so until this is sorted Im probably going to end up just using Adobe stuff unfortunately. Even though I'm desperate to escape.
-
So I've done some further testing on this and it seems that the Resample tick box simply doesn't actually do anything!
I had a 100x50mm image at 300dpi (1200x600px) and reduced the dpi to 150 with resample turned ON. Thus one would expect the result to be an image at 100x50mm at 150dpi (600x300px) and this is what happens.
With resample turned OFF on the same image one would expect the result to be an image at 200x100mm at 150dpi (1200x600px).
Affinity's result was 100x50mm @ 150dpi (600x300px) the exact same as if Resample was ON.
Im using 1.7.0 but this bug has been prevalent right from the early beta's.
Basically calculate everything yourself which is not how it should be but it is a work around.
Cant get my head round Document Resize?!
in Pre-V2 Archive of Affinity on Desktop Questions (macOS and Windows)
Posted
So I've just downloaded the Beta and it finally does seem to work (even though its not listed as being fixed?).
Anyhoo...
I can now see that the implementation of Document Resize is completely baffling to say the least (as I feared).
You have to set the units to Pixels. If you use any other unit it simply resamples even when you untick resample. This is just stupid and confusing! Something that compounds the confusion is the UI whereby you are unable to see the what the changes you input will be, so you have to go through with the operation you might not actually want by clicking resize, then open document resize again and then choose another unit to see the changes. If it simply showed the pixel dimensions in the window along with the chosen units and it updated live without having to click resize and then reopen document resize, it would then be just about bearable to use. WAY too many clicks are involved in a needlessly complex implementation. The same as the colour picker tool and the tab order in the Transform palette.
The UX seriously needs looking into in my opinion and the UI in parts.