drphoto

Not to jump in, but most likely what cje needs is how the Crop Presets worked in 1.6.5.

Excellent, thanks @Gabe!

The user created crop presets do not move the crop guides like the built in presets do, or like they did in 1.6.5. This is an issue that's been reported in a few other threads (see below) in releases after 1.6.5 to 1.8.0 betas. It was reported to be fixed in the 1.8.0 GM release, but it seems to be back. https://forum.affinity.serif.com/index.php?/topic/81215-fixed-user-created-crop-tool-presets-have-no-effect-170258/ https://forum.affinity.serif.com/index.php?/topic/87288-the-user-created-crop-presets-dont-seem-to-work-properly/ https://forum.affinity.serif.com/index.php?/topic/96392-user-created-crop-tool-presets-have-no-effect-172471/ https://forum.affinity.serif.com/index.php?/topic/94979-crop-problem-still-not-fixed/

Excellent, can't wait to try the 1.8 release, I've been looking forward to the performance improvements!

@Chris B Did you ever hear back from the dev team on this? Thanks!

@MEB Just curious, is this still an outstanding issue in the newer versions? Id like to upgrade from 1.6.5, but with no easy way to roll back, I dont want to mess up my currently working 1.6.5 install. Thanks!

Are the cropping issues reported in these threads fixed in 1.8? I don't see them mentioned in the changelogs for 1.8 (or unfortunately 1.7.3). Id love to use the new version, but I've gone back to 1.6.5 as the cropping problems make the newer version a no-go:

I run a lot of batch conversions, but typically from afphoto files, and I havent noticed that. My workflow typically goes: Canon DPP to convert RAW to TIFF (16 bit), then batch convert in AP to afphoto, edit, then convert to JPEG. If you have Canon DPP available, Id convert a RAW file there, then see if the batch processor changes exposure. If it doesnt, then bug confirmed.

There have been a lot of changes to the crop tool in 1.7 (I lost my presets too, and the presets in 1.7 don't work like I need them to either). The way you (and I) used the presets, the new tool wants to be set to "unconstrained", which in 1.7 wont let you save as a preset. Hopefully they are working on it, but If you need things to work like before, you may have to roll back to 1.6.5, which I plan on doing for now since I have some jobs coming up and I need it to just work! I wish we could install them side by side, because other than this, the performance of 1.7 is quite good. Note: Any afphoto file you save in 1.7 cant be edited by older versions, keep that in mind if you roll back.

Ah yes, thats what I need, an Absolute preset. I had quite a few in 1.6.5, they do make the editing process easier.

Seconded, I'm missing this as well in 1.7.2. Hopefully in the next update, I really don't want to have to roll back to 1.6.5 for a second time; I really do enjoy the performance of the new version, but for a large image set, the crop tool without my presets would just really slow me down.

After looking at it a bit more, I understand what the option should do, I think the confusion comes in is from the guide "behavior". If you select resample and change the entries by keying, the guides dont move like they did in 1.6 to show you the end result. Custom ratio moves the guides, but not in a way that makes any sense, "the ratio" is in pixels, and the guides dont really show you what the results will be. The only option that works as I expect is Unconstrained, but it wont let me save that as a preset! Thats the option Id use the most in my edits when cropping, so thats now a bit of a time sink in 1.7.

Sure, see attached. The numbers change, but the guides do not. I also noticed while doing this, that the crop tool seems to select the previously selected size automatically (see the History list on the second image, It already says Apply Preset. I had to roll it back). Its the exact same behavior I noted in a previous beta version (see posts), which was fixed, but now it seems off again.:

I think a bug from 1.7.0.258 has returned, I just upgraded from 1.6.5 to 1.7.2, and recreated a few crop presets that arent carried over during the upgrade, but none of them actually do anything. This is a repeat of the bugs reported in these threads: [Fixed] User Created Crop Tool Presets have no effect - 1.7.0.258 The user created crop presets dont seem to work properly

I'm curious, what was the behavior of the Crop Tool in 1.6.5. Did cropping also resample the image? Also, I noticed that you cant save Unconstrained Crop sizes as Presets in 1.7.2.471. Is that by design?

Well, its probably not that critical. If I still have the issue after reinstalling 1.7, Ill record it then. I just imported the settings from the most recent beta because there was no other way to get my presets I had saved in 1.6 into 1.7.

Ill have to install 1.7 again to give it another shot. Re: deleting the presets, Im not trying to delete the built in presents, I was trying to delete the imported presets (Presets that I created in the 1.7 Beta). It wouldn't let me do it. Perhaps Ill have to recreate them all manually. If you want to try it, Ill attach them to this post. DRP Prints.aftoolpresets DRP Sizes.aftoolpresets

Note, if you do this, back up all of your settings! Macros, custom brushes, etc.

The User Created Crop Presets seem to be broken again, its an issue that was resolved in the Beta. I imported my presets from the Beta (The ones I had in 1.6.5 didn't seem to survive the upgrade to 1.7), but when you click on the presets, the behavior is the same as mentioned in the below thread. I was going to delete them and recreate them, but it wont let me do that either, the delete option is grayed out.

Sure, see below: Dropbox Link

Sure, the TIFF files I work with are pretty big, but it seems to also happen with JPEGs as well so thats what Ive attached here. I generate the TIFFs and JPEGs with Canon DPP 4.7.20.0. What I did notice is that if you export a file from the TIFFs that show both lens names, the resulting output file shows the correct data everywhere.

I believe the latest version doesnt use ExifTool.

I wonder if its an Affinity Photo + Windows 10 issue, I'm on Windows 8.1 Pro, and other than two issues I've noted (feature operation related), so far performance is much better than 1.6.5, especially with large 16-bit TIFF files.

I noticed in the 258 beta, the camera and lens are identified correctly in the EXIF Tab (Canon EOS 5D Mark IV/EF24-70 f2.8L II USM), but at the top of the main Photo Window, it says Canon EOS 5D Mark IV (Canon EF 24-70 f2.8L II USM or Sigma 24-70 F2.8 DG OS HSM | A).