Jump to content

Search the Community

Showing results for tags 'affinity photo;'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Affinity Support
    • News and Information
    • Affinity Support & Questions
    • Feature Requests & Suggestions
  • Learn and Share
    • Tutorials (Serif and Customer Created Tutorials)
    • Share your work
    • Resources
  • Bug Reporting
    • Report a Bug in Affinity Designer
    • Report a Bug in Affinity Photo
    • Report a Bug in Affinity Publisher
    • (Pre 1.7) Affinity Range Bugs Forums
  • Beta Software Forums
    • Affinity Designer Beta Forums
    • Affinity Photo Beta Forums
    • Affinity Publisher Beta Forums

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 1 result

  1. This subject is being discussed in two other threads. But in each case, the discussion has shift towards peripheral considerations, leaving no chance for the initial question to be answered. I voluntarily put here no links to those threads in order to prevent readers to be parasitised by pheripherical and noisy considerations. What should be strictly discussed here : The "Merge Down Layers" (Ctrl+Shift+E) , a very common frequently used command, in some case (see details below) currently corrupts the image: contents of merged layers are blurred. Question: is there a good functional reason for this function to work so, knowing there's a simple way (doing a rasterization of the bottom layer before merging) to achieve the expected result : a merge that simply preserve the data of each layer ? Or is there currently an option to be activated to achieve in any case automatically the expected result ? Details : afphoto file attached to reproduce the bug reproduced in : 1.6.5.135 and Beta on Windows 10 and 1.6.11 on macOS Sierra reproduced with "Force Pixel Alignment" or "Floating point coordinates" options on and off: those options are no way a solution to this problem. a simple way to reproduced the bug with two pixel layers is to apply a transformation on the bottom layer before merging (note: by doing so, coordinates of the layer are no more integer ones) a simple way to prevent it : rasterize the bottom layer before merging For many users, the current behavior of the merge function is a fondamental problem (you can corrupt your work with one click if you're not aware). We would be glad to have an answer to the question above or the function to be fixed. Cos there is no technical limitation considering our use (it may not be elegant, but the merge function could simply process a rasterize operation before applying, which is the manual action required currently if you want to preserve the quality of your image). PS: actually, there's a video that illustrates this tricky behavior here Demo . See the seventh post
×
×
  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. These are the Terms of Use you will be asked to agree to if you join the forum. | 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.