jullit31

@traildriver I think you should start an new topic for something like this, but you are looking for the Perspective Filter.

That is, imho, exactly what it should do. When creating a selection in an automated way (i.e. by selecting a Colour / Tonal / Alpha Range or by using the Flood Select Tool), being able to easily crop to said selection would be very useful.

With the current workarounds you can't, but if, as per shushustorm's suggestion, the new Crop to Selection just called the existing crop function, it would be non-destructive. Again, the same thing that happens with the current Crop-tool.

Well, technically that is of course true, but in that sense anything is non-destructive if you keep a copy of the original document... What I meant with destructive is that you can't just "Unclip Canvas". I also found a (destructive [by any definition]) workaround for macros: Create the selection you want to crop to > Invert Selection > Delete > Clip Canvas I've also made a macro that handles multi-layer documents. clip_to_selection.afmacro

The problem is just that this doesn't work in macros and is destructive... So I would still very much appreciate a "Crop to Selection" function.

Thanks! They should really use that description in the Windows version as well...

The Rotation slider maxes out at 50%, wich is equivalent to 180°. Rotating further is possible by keying in a larger value, but you shouldn't have to do that. Also, the unit for a rotation should be degree, not percent. P.S. Sorry for sounding so negative in most of my posts, but aside from the stuff I'm complaining about, I think Photo is a great piece of software

Nope, the Mouse Wheel just changes the zoom...

What is "Wheel" here? The Help doesn't say anything about it...

Hey MEB, Any news on this? The retail version also crashes when I attempt to open this file...

No, it's not a bug, it's a feature :wacko: There already is a feature request to implement a toggle for this in the preferences.

When I try to open a specific .afphoto file I get an Unhandeld Exception Code: 0xC0000005. I don't wish to post this file here, but I'll be happy to send it in a PM to someone from Serif.

1. Yes, I did, but not with a 20 second delay and by far not as severe (something that causes 30% - 50% load on your CPU would probably lead to 100% on mine). 2. No, but I did now: Same principal behaviour, just a bit worse (16% when showing the selection and 5% otherwise). So for you this only happens when using RDP?

I cannot reproduce this on my Win 10 pro quad-core 16 GB RAM machine: 1. create a blank image 2. make sure "View" -> "Show Pixel Selection" is checked 3. select some area -> instantly 12% CPU load @ 1.5 GHz 4. wait 20 seconds 5. no change 6. uncheck "View" -> "Show Pixel Selection" -> instantly 4% CPU load @ 0.9 GHz 7. wait 20 seconds 8. no change Maybe this problem is specific for Server 2008 R2...

Using the up and down arrows or the mouse wheel to adjust the exposure in the Develop Persona results in a change of 1, which is far too coarse to be useful.

When using the Move or Zoom Tool in any persona other than the Photo Persona, the position indicators on the rulers don't move when moving the mouse.

Changing the brush size and hardness in the Develop, Tone Mapping and Panorama Personas using Alt+RMB+LMB does not work as intended: In the first two personas the (centre-) position of the brush changes when moving the mouse to adjust size/hardness. In the case of the Panorama Persona the new brush size is used after changing it in this way, but the brush pointer still shows the old size until ending the first stroke after the change.

The orientation when using the Gradient tool in the Photo Persona can be restricted to 45° increments using the shift key. The same does not work with the Gradient Overlay tools in the Tone Mapping and Develop personas.

The saturation slider in the Tone Mapping Persona maxes out at 50%, but the Summer Glow preset (James Ritson Customs) manages to set it to 90%. Manually I cannot set it to a value above 50%. And yes, the 90% are visibly more saturated than the 50%, although not as much as one might expect...

I fully agree. However I do see an issue with recommending to customers that they switch between two pieces of software to use a function that would make sense to be integrated into both (and is integrated into competing products), just for licencing reasons. That being said, I think DxO found a nice solution to this problem: They offer three pieces of software: OpticsPro (RAW developer), FilmPack (filters) and ViewPoint (perspective correction). All of those work as stand-alone applications, but when OpticsPro and any of the other two are installed on the same machine, their functionality gets seamlessly integrated into OpticsPro. This would, IMHO, also be a nice solution for AP and AD, as it would improve the experience for users and also be a new selling point.

Indeed, I use a Roccat mouse with the corresponding software. Although it doesn't behave that way anywhere else...

That's interesting. I tried the first image I found here. The 4k2k .hdr takes about 3 seconds, the 8k4k about 4 seconds. That seems pretty much in line with your loading time using Photoshop. Now of course, we didn't use the exact same image, so maybe you could try with the one I used (or provide me with your's, if that is possible). My best guess is that PS uses more threads than AP to handle file opening. Although my CPU (6600K) can only process 4 threads in parallel, it is clocked at 4.2 GHz and may therefore actually perform better in a scenario like this one (i.e. when four or less threads are being used). If that is indeed the case, maybe the devs should consider further parallelizing file opening.

So have I, however I do experience that decrease. That's strange...

Hello sijo. What do you consider "relatively slow"? I haven't used Photoshop for a long time, so I can't compare to that. Opening a 1 Pixel jpeg takes about 1 second on my machine, a 75 MPixel jpeg takes about 2.5 sec. Is that comparable to what you experience?

I have two issues with the free hand selection tool: 1. With any other selection tool, when I click outside of the selection, I deselect. When I do the same thing with the free hand selection tool, nothing happens. This has been previously reported here. 2. With any other selection tool, the cursor changes from crosshairs to a quadruple arrow. With the free hand selection tool it does not change, however I can still move the selection by clicking and dragging inside it. Is any of this intentional?