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

Marquee tool not cutting the correct pixels size


Recommended Posts

1. Open the attachment image
2. Go to pixel panorama
3. Use the Marquee Tool, drag from outside of canvas and put the 672x378
4. Move the X and Y a little to the center (Not really need)
4. Press Ctrl+X and File -> New From Clipboard

Now the image has extra transparent pixels around it, or in right and bottom if is 0,0.

Space-Rangers-HD-A-War-Apart.jpg

Link to comment
Share on other sites

I don’t know which Marquee Tool you are using, or what you mean by “put the 672x378”, or “Move the X and Y a little to the center”.
Can you be a bit clearer please?
I tried to do what I could understand of what you wrote and can’t find anything wrong, so I guess that the problem is in the parts that I didn’t understand.

Link to comment
Share on other sites

Interesting.
On Windows 10 with Designer 1.9.2.1035 (current commercial version) I can replicate the result, but I don’t know why it happens.
I also tried selecting a slightly different way and get the same sort of result.
However, selecting in many other ways doesn’t give me the same result, so I think it needs more experimentation to figure out exactly which part(s) of the procedure are causing the issue.
I don’t use this feature very often so I might be missing some basic information, but it does look a little odd to me and not what I would expect.

Link to comment
Share on other sites

Already ON Pixel Alignment. Anyway, if the rectangle value has no decimals on it, should be good.
I can't turn Hardware Accleration ON with an Intel HD 4600. Anyway, what this should have to do if this is just for rendering. And not how the Rectangle Marquee Tool is cutting the image.

Basically you can cut on AD and paste it on Windows Paint and is the same result.

Link to comment
Share on other sites

2 minutes ago, AndRo Marian said:

Hmm, never used. Still the same on VM on fresh Windows 10 1803, on main is latest.
I would try 8.1 but I this will be the same result.

What happens if you disable the Clipboard History in the Windows system setting? 
I doubt that it related to this problem but just in case.

Link to comment
Share on other sites

  • Staff

Hi @AndRo Marian
Don't draw the selection then go to the Transform panel to resize it. That's the cause of the issue (this is logged/with the dev team). Use the rectangle tool to draw the shape, set the dimensions you want in the transform panel (integer values), drag the shape layer over the image's thumbnail layer int he Layers panel to use it as a clipping mask, copy it to clipboard then File > New From clipboard. You should get an image with the correct dimensions and no transparency. If you wish to merge the image and the clipping mask, right click the image layer in the Layers panel and select Rasterise.

In Affinity Photo (in case you have it) you can use the Rectangle Tool, to draw a rectangle and set its dimension in the Transform panel then go to the Pen Tool and click the Selection button in the context toolbar to convert the shape into a selection. Then proceed to copy/paste a new document as usual. This option is not available in Affinity Designer.

Link to comment
Share on other sites

16 minutes ago, MEB said:

Hi @AndRo Marian
Don't draw the selection then go to the Transform panel to resize it. That's the cause of the issue. Use the rectangle tool to draw the shape, set the dimensions you want in the transform panel, drag the shape layer over the image's thumbnail layer int he Layers panel to use it as a clipping mask, copy it to clipboard then File > New From clipboard. You should get an image with the correct dimension and no transparency. If you want to merge the image and the mask, right click the image layer in the Layers panel and select Rasterise.

This is a good workaround. But why that adds 1 empty pixel around the image?
That's seams a problem to me. Like the @GarryPsays, is not appear for every action.
Seams some @prophetcan't reproduce it on MAC...

Link to comment
Share on other sites

  • Staff

Hi @AndRo Marian,
Assuming you are entering integer values for the width and height of the rectangle, it's because the X and Y coordinates of the rectangle are not integer values (it's not correctly pixel aligned). Enable Force Pixel Alignment in the main toolbar (keep Move by Whole Pixels disabled which is the next button on the right), then move the rectangle a bit to force it to adjust/snap to integer values/pixel grid. Keep an eye in the Transform panel to confirm it's correctly aligned.

To see more decimal places in the Transform panel and elsewhere in the app, go to Affinity Preferences, User Interface section, Decimal Places for Units Types area, and increase the Pixels value to 3 or 4 so you can catch values like 235,005. By default its set to a single decimal place.

Link to comment
Share on other sites

16 minutes ago, MEB said:

Hi @AndRo Marian,
assuming you are entering integer values for the width and height of the rectangle, it's because the X and Y coordinates of the rectangle are not integer values (it's not correctly pixel aligned). Enable Force Pixel Alignment in the main toolbar (keep Move by Whole Pixels disabled), then move the rectangle a bit to force it to adjust/snap to integer values/pixel grid.

Already say I have Force Pixel Alignment enabled and values are without decimals.
I have to show 3 decimals after dot. There are a good rounded value.

Link to comment
Share on other sites

4 minutes ago, AndRo Marian said:

and values are without decimals.

Did you type the values into the Transform panel, or are you trusting the values displayed displayed there?

If you did not type the values, have you adjusted your Affinity Preferences, User Interface section, to increase the number of decimal places displayed for px measurements? It defaults to 0, so unless you've changed it (to perhaps 3 or more), it can show misleading values.

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro, version 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop:  Windows 11 Pro, version 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
iPad:  iPad Pro M1, 12.9": iPadOS 17.3, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.3

Link to comment
Share on other sites

13 minutes ago, walt.farrell said:

Did you type the values into the Transform panel, or are you trusting the values displayed displayed there?

If you did not type the values, have you adjusted your Affinity Preferences, User Interface section, to increase the number of decimal places displayed for px measurements? It defaults to 0, so unless you've changed it (to perhaps 3 or more), it can show misleading values.

I can type it or using the mouse wheel. Same result. Yes, is 3 decimals. Still should show if is not a perfect number.

Link to comment
Share on other sites

2 minutes ago, MEB said:

Do you mind attaching the file please?

Is already on first post. And a video below. I can make a project with it, but is the same thing.

Not sure, but the software seams to be is using Double as a number type. And not Decimal that would be better.

Link to comment
Share on other sites

9 hours ago, AndRo Marian said:

Now the image has extra transparent pixels around it, or in right and bottom if is 0,0.

Before making your marquee selection, disable Antialias and set Feather to 0 px.

^ Ah, strike that. Now I see from your video that it is disabled.

Edited by loukash

MacBookAir 15": MacOS Ventura > Affinity v1, v2, v2 beta // MacBookPro 15" mid-2012: MacOS El Capitan > Affinity v1 / MacOS Catalina > Affinity v1, v2, v2 beta // iPad 8th: iPadOS 16 > Affinity v2

Link to comment
Share on other sites

3 minutes ago, AndRo Marian said:

And a video below

From your video I can see that you have enabled "Move By Whole Pixels", but not "Force Pixel Alignment".
It needs to be vice versa.

MacBookAir 15": MacOS Ventura > Affinity v1, v2, v2 beta // MacBookPro 15" mid-2012: MacOS El Capitan > Affinity v1 / MacOS Catalina > Affinity v1, v2, v2 beta // iPad 8th: iPadOS 16 > Affinity v2

Link to comment
Share on other sites

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • 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.