NotMyFault

@Daniel: Tank you for those suggestions. I’m already aware of several workarounds, please do not post more of them. These are non-precise and hamper the workflow . In my view this is a AP bug and should be fixed. Whenever I applied crop with e.g. 3:2, AP should respect this ratio and automatically calculate even pixel counts during export with locked ratio. Other applications behave like this, AP should do, too.

@Danielcz: This might work in theory. My expectation to AP is that the software does the math for me Really don’t want to do that manually

I can confirm this issue in 1.7.2.

The issue occurs when using crop (and not later when exporting): When selecting 3:2 crop an using the mouse to reach 4500 for x, AP shows 3001 for y, see screenshot attached. I tried to achieve 3000 for y, seems to be impossible. Either 2999 or 3001, but never 3000

Hi Ron, cropping was the single and only adjustment. Definitely no trimming. I saved the file with full history, you can check yorself. You should note that during development, some assistant are active (see below), and lens correnction will apply for example. I don't know if assistent is saved with image files, or local to every installation. And intentionally, i did a crop with uneven size (size after crop no multiple of 8). If you crop directly to the exact size of planned export, you will be ok most of the time. Unfortunately, there is no easy way to sightly round down the crop size to reach "even" dimensions, besides dragging the mouse -- wich is non-precise and near to impossible to reach e.g. exactly 2000 with mouse (no option to enter exact pixels during crop AFTER selecting 3:2 crop mode).

Bug is still prsent in 1.7.2.471 (non-beta)

Hi Chris, below you can find a sample file. AP file created directly from a raw .CR2, developed straight as it is, and applied a crop with 3:2 (6:4) aspect ratio. When you export and enter 2000, you get 2999 instead of 3000 for the other axis. _MG_1882.afphoto

below you can find a example file. 3 boxes with color gradients, red, green, blue. First step: i started with RGB values from 25 to 200 for all colors. All histograms shown correct. Second step: i reduced the red and green color ranges. after this, the curves histogram just collapses to a flat line. very strange. curves histogram bug.afphoto

Hi, unsure if this a bug or i misinterptet the functionality. i often apply first a levels, and then a curves adjustment. In some cases, the histogram within the curves shows wrong data, not including the levels adjustment below. You can see the mismatch in the curves dialog box (left) versus the histogram in the toolbar (right). Picture is RGB/16 with Adobe RGB The issue occurs only occasionally.

Hi Chris B, any update regwrding this issue? For me. there are two related problems: 1. CR2 picture dimensions shows by apps seem to differ always between Affinity Photo and all other tools (Canon, Windows 10 Explorer by up to 24 pixels in case of 6000x4000 raw file) 2. AP is off when exporting CR2 files by a few pixels, even if the files have been explicitely cropped to e.g. 3x2 ratio before.

Dear Lucja, sorry to hear that. It did work for the tiff you provided. It may not work for your original aphoto file. You May use „merge visible“ as preparation step. Can you provide the original, or at least describe how you created the logo? Timo

You may try this method: - choose Flood selection tool (W) - reduce "tolerance" to 0 (mouse) - select white background (click any white pixel) - grow / shwink selection by 1 pixel (CTRL-B) - delete slected area (DEL) - fill selected area with white again Hope that does the job. Regards Timo

Hi Chris, no decimals found (ORG was background before renaming). Please note that AP always shows different dimensions compared to Canon DPP or Windows Explorer / file properties AP 6024,0x4020,0 (EXIF while opening CR2, before any crop) CANON DPP 6000*4000 Windows Explorer:

In Windows (and Mac), its a bar only visible with move tool active. Look out for "Lock Children"

I found a solution: the “transformation” menu, and “Transform separately” is just what I was looking for