Jump to content

Search the Community

Showing results for tags 'artifacts'.



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 14 results

  1. Hi, I'm experiencing this issue: I have an image clipped inside a rectangle (mask), and the rectangle also have a stroke set. When exporting, or rasterizing the layer artifacts appear on the image edge, it looks like there is some computation error in the subdivision. To reproduce just open the attached Test.affinity and export in Tiff with default settings. Additional info, the issue happens when the clipping mask stroke is set to be inside, see stroke setting pic. Affinity Photo version 1.7.2 release, issue reproduces both on macOS and iPadOS Test.afdesign Test.tiff
  2. I have about 90-80 slices in my project (It's and Android app) , and each slice is exported to a number of files (PNG and SVG). When using my mouse wheel scrolling up and down, folding and unfolding my slice to check that the export looks ok Designer freezes. 1. I first created a "master" export setup manually, exporting one SVG file and a number of PNG files in various resolutions to target all DPI:s 2. I used the "copy export format setup to clipboard" 3. I marked all my other slices (except the top one) 4. I used the "Add export format setup from clipboard", so all my slices is exported in the same manner (keeping the slice name unique) 5. Using mouse wheel in the Slices area up and down 6. Unfolded a few of the slices and rolled the mouse wheel up and down fairly quickly 7. Designer freezes, boom. It recovered my file when I restarted though (phew) I also created a crash dump file of the Designer process was frozen and ran it through DebugDiag Crash Analyzer, the report is attached. I suppose I could send my file to the developers if that helps reproducing the freeze, but I rather not post it on the forum Video capture Sometimes the slices are not redrawn properly in the UI, not sure how to recreate this - but here's what it looks like: Video clip with the error . Designer_MultipleRules.mht
  3. This is something I use Corel Paintshop Pro X4 for. The ability to remove JPEG Artifacts from images by first adding subtle noise and then selecting an edge preserving smooth. This removes the blocky look to highly compressed images. Interestingly the Despeckle feature did it in one step on the first Photoshop Elements app. I'd like to see this feature in Affinity Photo in the future. Maybe under an image repair persona,
  4. Hi folks, I am doing the exercises in the Affinity Photo Workbook and am doing the selection exercise. When i selected the girl, and did the refine selection and then copy to new layer with mask, everything seems fine, until I turn off the mask. When I do there are black splotches all around her hair where i refined the selection. See attached screen grabs. Thanks!
  5. This might be still be something related to problems with boolean shaping operations introduced in 1.8.x initial versions, since I think I have not always seen division operations behave this poorly: There are similar problems in all Affinity apps, and the recurring recipe to "fix" the problem is to drop the accuracy and force pixel perfection, which I have tried to do here. But I think that I have earlier managed to do things like this much better in Affinity Publisher and Designer without needing to care about pixel integers. I can realize how this can be important when exporting low-res PNG graphics from the original vector design, but here it should not matter. What appears to happen here is that the boolean operation that is supposed to divide the segments and create perfectly aligned shapes cannot do so and instead of that we see hundreds of unnecessary nodes being created. This probably would not happen when dividing rectangles, and then the standard workaround would be having nodes at pixel integers. But with curved segments node positions actually do (and cannot) have any effect on the matter. I am not sure if the sheer number of superfluous nodes explains why the subsequent "Add" boolean operations perform so terribly, to create the final shape, and produce much very odd artifacts. It would help a lot if Affinity Designer had similar features as CorelDRAW "Reduce Nodes" or Inkscape/Illustrator "Simplify" that would let automatically reduce the number of nodes without altering the curvatures. In CorelDRAW this is more or less phenomenal: a) You select a segment with the Node tool and click "Reduce Nodes": b) And very soon get you from the node mess to something like this: There is much to like in Affinity apps and I really hope these kinds of problems are just a glitch that will (soon) be fixed. But I have also read many topics that make me think that these kinds of flaws are a symptom of a more fundamental problem showing a conflict with internal accuracy and meaningful, much coarser resolving (production) accuracy, resulting in all kinds of visually discernible inaccuracies, rounding errors and artifacts. Here is the Affinity Designer file to play with: division_problem.afdesign
  6. Text Boxes have a black line above them. Every text box creates a black line somewher above the box even with no text in the box. This also prints Version 1.71.404
  7. Hi there, I have problems with Affinity Photo files. When I zoom in and out, or when I use shape tools etc. I start getting artifacts like those you see in the picture I posted, and the worst is that the is still there when I save the file to jpeg format.. it looks to me like it could be a compatibility issue with my video card... my video card is: NVIDIA QUADRO K2200 OS win 10 PRO 64bit CPU intel i7-7700K 4.20 GHz 32 GB RAM Has anyone had this problem before or knows a possible solution to it ?
  8. Hi I just discovered strange artifact within 2 of 3 my file exports (within same project file). Artifact stays there no matter the format of export (png / jpeg). Can someone please help me or try to explain what is happening. I have hundred of files and exports already and this is the first time I'm getting something like this. All files attached. UPDATE: I was started working on AD Windows, then continued on Mac, and finally get back on Windows machine to do final touches and export. Mac files are exported without artifacts!!! Only on PC I got this, but it is still a problem that should be checked. Thank you. 20180425_Yoga_tečaj_PCZ.afdesign
  9. Hello, is there any good method to remove lower quality JPEG artifacts from whole photo without loosing details and blurring? I've attached simple sample.
  10. The Gaussian blur live filter appears blocky when: the filter is set to Preserve Alpha and the object is masked with a Vector object (doesn't seem to affect raster masks). - Easiest to replicate with smaller masks (discovered this while working with UI). - The amount of blur dictates how blocky the image is. But whether it's 2px or 20px, artifacts still do appear. - It does affect exported files. - "Blockiness" intensifies with magnification. Magnification does not affect exported files. Screenshots for reference.
  11. When I use the cloning tool and I go over the same areas again that I already cloned, I get disturbing artifacts in the clone. See video. Also Clone tool wil not remember the actual image when going through parts that were already cloned, it will infinitely clone on top of a clone. Cloning problem2.mov
  12. Hey guys, I ran into this »bug« – if it is one. I’m currently working on icons on a 128 px² base. When I set an object – say a rectangle with rounded corners – with a white filling and a greenish stroke I get what appears to be artifacts of some kind. Seems like the white is shining through the contour. Though I'm not sure it’s a bug or this is just how it’s working. Anyone has any ideas how to fix this? Cheers Dennis :)
  13. I just fired up Affinity Photo Beta for the first time and had this user experience: Created a new pixel layer. Selected a brush, painted a line. Response time was not solid, brush felt floaty, jittery, and imprecise. Found no pressure sensitive thickness controls. Selected a thinner brush. Brush displayed with breaks in line. Despondancy set in. Started seeking solution. Zoomed in. Line became clear. Drew thinner line, line displayed with zoom artifacts like breaks in the line. Zoomed in further, display showed line clearly. Took screenshots, came here, posted this. Depending on response time and inclusion of error suggestion, my confidence in your company and products will be influenced. I know you're a smaller team and have a large overhead of duties to perform, and perhaps someone has already mentioned this bug, but any notice of it's receipt from a person, not a robot formula reply, will boost confidence. Personal care and service is where the line is drawn between successful and unsuccessful enterprises. Thanks for trying.
  14. I've noticed that dragging objects around sometimes leaves behind a trail of schmutz. iMac, Intel Core i7 16 GB memory OS X 10.9.5
×
×
  • 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.