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

jullit31

Members
  • Posts

    38
  • Joined

  • Last visited

Posts posted by jullit31

  1. 16 hours ago, R C-R said:

    Cropping affects the entire canvas & must be (in its current form) rectilinear, so this "crop to selection" feature would [...] crop the canvas to (presumably) the smallest bounding box that encloses the selection.

    That is, imho, exactly what it should do.

    16 hours ago, R C-R said:

    I really don't see how this would be much more useful than using the Cropping Tool

    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.

  2. 14 minutes ago, toltec said:

    As far as I am aware, if you crop to selection, you can't do that? Therefore it is destructive, at least in comparison to the proper Affinity crop tool.

    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.

    14 minutes ago, toltec said:

    I'm also rather curious about what happens with crop to selection on multi layered documents ?

    Again, the same thing that happens with the current Crop-tool.

  3. 2 hours ago, Alfred said:

    but ‘Copy Flattened’ isn’t destructive: it just creates a flattened copy, leaving the non-flattened original untouched.

    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

  4. 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.

    brush_rotation.thumb.jpg.fd04a0e53f0a82de3a4802b11dd58eaa.jpg

    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 :17_heart_eyes:

  5. 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...

  6. 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.

  7. Hi, Affinity Photo isn't Photoshop. We price our applications very competitively, so we don't see an issue with recommending to our customers that they by two pieces of software if they have a broad interest in different functionalities. 

    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.

  8. Yes, a 1x1px image takes about 1,5 seconds for me. Photoshop opens such an image in 0,4 seconds.

    A 10000x5000 32bit HDR image takes 9,4 seconds. Photoshop opens that image in 5,9 seconds.

     

    My machine is a 40 core CPU, 64GB RAM workstation, so performance shouldn't be an issue.

    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.

  9. 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?

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