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

pedroterrero

Members
  • Posts

    14
  • Joined

  • Last visited

Posts posted by pedroterrero

  1. 1 minute ago, NathanC said:

    Hi @pedroterrero,

    I've now managed to replicate it with your steps, the reason I could never replicate this was because my  assistant was set to always add an adjustment as a new layer rather than based on selection so it has nothing to do with V1 files, after changing this I can now finally replicate the issue so I'll get this properly logged with the developers.

    That's what I was replying, haha. New documents in v2.2 have the issue, documents made in V1 and exported in V2 don't. Also, rasterizing the layers is a workaround to avoid it and this is what I've been doing so far.

  2. 24 minutes ago, NathanC said:

    Hi @pedroterrero,

    There does appear to be quite a sharp transition between the curves layer and the image file when the file is exported, but this can also be seen within the app if you were to Layer > Merge visible the file and then compare. I copied the Curves and image layer over to V1 for comparison, and this sharp transition between the curves and the raster image is also present on export/merge.

    Instead of applying an Outline FX to an empty curve layer, you could instead apply the stroke value directly to the curve and then align the stroke to the outside with the exact same settings used in your outline FX. After making some slight adjustments to the curve nodes and Outer Shadow FX it gives a much smoother transition between the image and the outline/border. I've attached the image and file below for reference.

    Exported as JPEG:

    image.jpeg

    Stroke Applied instead of outline.afphoto

    Thank you for your suggestion! I tried applying the stroke directly on the curve and looks better.

    I found out where the issue (the bug?) is. You have to:

    1. Import a picture and apply the curve as a clipping mask

    2. Apply the stroke as an FX. Everything should remain in the same layer

    3. Reduce the size of that layer

    4. Apply an adjustment layer, such as Bright and contrast

    5. Export

    As long as you keep the layer without adjustments, it exports the document with no artifacts, but when you apply an adjustment, the shape is jagged. I've tried with a document created in V1 and it exports with no issues. I attached that document for you to test too.

    miniatura.afphoto

  3. Hello. When you apply an outline to a curve, it looks perfect in the preview, but looks jagged/pixelated when you rasterize that layer or export the document.

    This is how it looks previewed in Affinity Photo (I zoomed it):

    iRAuWiY.jpg

    This is how it looks exported. You can also see in my right shoulder (yeah, that's me) it took some pixels from the background, so not only it pixelates the curve, but also doesn't respect it:

    V8t2l3z.jpg

    And last but not least, in case you don't notice anything special, if you resize the file while exporting, the artifacts will be more notorious:

    LJ0z9Ko.jpg

    I attached the document if you want to reproduce the issue. I tried all types of resampling while exporting and the result is the same. And BTW, this never happened in V1, just in V2.

    affinityphoto2bug.afphoto

  4. Just my two cents:

    -What you guys have achieved in this thread is AMAZING and I never imagined Affinity would bother to help make their suite usable in Linux. I’m proud that the price I paid for the Affinity suite also helps to bring us things like this. And also a big thanks to the community!

    -To the Affinity team: don’t feed the trolls and Linux fundamentalists (they are often the same), they are usually solitary people with too much free time and they don’t know how to keep themselves distracted. Just keep doing the fantastic work you’ve done so far.

    -In my opinion, Linux market share being “ridiculous” could be tricky. It doesn’t mean it’s not attractive, because “probably” most of that 3% market share consists of power users or at least users with sophisticated interests. Why does DaVinci Resolve have a Linux version? Or Blender, Houdini, Cinema 4D and other powerful creative and post production tools? Because they are aimed at a minority with very specific needs (and a lot of money to spend). Saying “making a professional graphics editor for Linux is pointless because Linux market share is ridiculous'' is like saying “making peripherals for streamers is pointless because the streaming market share is ridiculous” compared to the general market. And don’t get me wrong, I’m not telling Affinity what to do, it’s just a thought.

    To me, being able to run Affinity Photo via Wine is a dream come true and literally means breaking the ONLY bond I had with Windows. :)

  5. 1 hour ago, John Rostron said:

    For a valid comparison, you need to display the image on your screen at 100%.

    John

    It works fine in my desktop PC 🥴, but the exported picture in my laptop was exactly like the third picture I posted, so it seems to be hardware-related. 😓 Anyway, you can see it in action inside the program if you do like this:

    1. Open Affinity Photo
    2. Create a new document. FHD 1080p is fine
    3. Copy the first picture I posted and paste it into the blank document
    4. Resize it to fit the canvas
    5. Zoom in the document with Ctrl+scroll. You will see the image is pixelated. It should be fine as we are still working on it, although I would like to see an option to get best quality, like a "best quality" 
  6. 1 minute ago, John Rostron said:

    Are the images you show here the actual images as saved? Or are they screenshots? If they are screenshots, were they taken with the image display at 100%?

    Screenshots at less than 100% can often seem pixellated.

    John

    Screenshots without resizing. It's the actual size of the three pictures. As you can see, even though they are screenshots the quality varies. Better resampling in the photo resized with IrfanView, inexistent resampling in the second one (AP).

  7. Hello, I'm new to this forum. Sorry if I don't post all the required information.

    When resizing a small pasted picture, if I try to make it bigger, Affinity Photo pixelates it, losing quality. I tried resampling, rasterizing and exporting with Bicubic, Bilinear, Lanczos resampling and nothing works.

    This is the original picture:

    1*iEGdDWcgLV_1wFfIvthtig.png

    This is an example of a good resizing and resampling using IrfanView (I know the original picture is veeery small, but it's what I have):

     

    lnOlGBB.png

    And this is what Affinity Photo does, no matter how I resample the document, or the exported picture:

    JW3tLEd.png

    Is there anything I'm doing wrong? And is there any way to default resampling with a better quality filter? I'm on Affinity Photo 1.8.3.641 (W10).

    Thank you in advance.

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