Jump to content

GrahamMYC

Members
  • Content Count

    171
  • Joined

  • Last visited

Posts posted by GrahamMYC


  1. If  you export an affinity photo file as a .psd file, then any fill layers are ignored. The workaround is to rasterise the fill layers. But this depends on remembering that a specific file contains fill layers. This effectively prevents batch operations for exporting to .psd as this wold be unsafe. 

    Are there any plans to notify you that fill layers will be ignored? Or could a question such as "Convert fill layers to pixel layers?" be included if an attempt to export to ,psd occurs

    And

    Are there any other features of Affinity that do not save in .psd files?

     


  2. It was suggested to me that a workaround until the Affinity DAM is available would be to save the images in something like Photoshop Elements Organiser as .psd files (Organiser does not recognise affinity file formats). This sounded like a plan so I tried it. The relevant files are attached .

    At first it seemed to work, the ,psd file being accepted into organiser, and apparently showing properly. 

    However, when I re-exported it and tried to load it into deigner, the background had disappeared (see screengrab)

    On examining the original affinity file, I noticed that the background, which had disappeared, was a fill layer.

    So it seems photoshop elements and/or .psd format does not support Affinity fill layers.

     

    I was able to confirm this conclusion by rasterising the fill  layer before exporting as a .psd. The file was successfully uploaded to Photoshop Elements Organiser and recovery to Affinity

     

    I am now wondering whether I can take the risk of forgetting to rasterise fill layers, and pondering whether there are other fearures that would not survive saving to Photoshop Organiser and recovery to Affinity

     

    Any advice or comment would be welcome. An Affinity DAM would be even better!

    coloring-page-simple-mandala-6.afphoto

    coloring-page-simple-mandala-6.psd

    screengrab.jpg


  3. It was suggested to me that a workaround until the Affinity DAM is available would be to save the images in something like Photoshop Elements Organiser as .psd files (Organiser does not recognise affinity file formats). This sounded like a plan so I tried it. The relevant files are attached .

    At first it seemed to work, the ,psd file being accepted into organiser, and apparently showing properly. 

    However, when I re-exported it and tried to load it into deigner, the background had disappeared (see screengrab)

    On examining the original affinity file, I noticed that the background, which had disappeared, was a fill layer.

    So it seems photoshop elements does not support Affinity fill layers.

     

    I was able to confirm this conclusion by rasterising the fill  layer before exporting as a .psd. The file was successfully uploaded to Photoshop Elements Organiser and recovery to Affinity

     

    I am now wondering whether I can take the risk of forgetting to rasterise fill layers, and pondering whether there are other fearures that would not survive saving to Photoshop Organiser and recovery to Affinity

     

    Any advice or comment would be welcome. An Affinity DAM would be even better!

    coloring-page-simple-mandala-6.psd

    screengrab.jpg

    coloring-page-simple-mandala-6.afphoto


  4. Chris_K

    I think I may have found the answer. It was your question about the pen that started the train f thought. I had not tested the fault using the pen on the Huion tablet. I did try, and got exactly the same result. But on one occasion the brush size jumped up to some big number, and I noticed that the brush was set to a texture brush -something like grunge 3. I changed the brush type to a basic brush. Problem solved. I checked that this also worked with the mouse. It did.

    I would be interested to know if you can now reproduce the fault in AP 1.5!

    I wonder how long it would have taken us to logically work thru to that solution if I had not noticed the brush type by chance? Still it is a useful thing to know. It is (of course!) self evident that tools like clone and healing brush need a solid brush nozzle, so obvious that no one would think to suggest this should be checked! Perhaps a note needs to added to help files? This result would also explain why the blemish removal tools works as this is not dependent ona user defined brush.

    Anyway, many thanks for your time, and your patience.


  5. As it is clear that my previous explanations have not been adequate to explain the problem, I have made a new video. (In the meantime I have tried using factory resets as advised by Serif, without success)

    The new video shows that the healing brush is working as expected in the AP 1.6 beta, but goes wrong when I try exactly the same settings on the same photo in AP 1.5. I also show that related functions (i.e. blemish removal) appear to be working in 1.5.

    IF there is a file corruption, then I should be able to get round that by re-installing AP 1,5. But that does not work either.

    Help!!!!

     

     

    Revised_HealingBrush_vid.mp4


  6. Thanks Chris_K, but that does not seem to be the issue. I have tried reducing the brush hardness and it still corrupts the image. I think I have a file corruption somewhere. Uninstalling and reinstalling has not soved the problem, so there must be a common or reference file that is surviving that change. How can I find it, neutralise it, or reset it?


  7. Problem exists on AP 1.5.2 o/s Windows 10

    symptoms

    1: Healing brush works in unusual way causing an effect over an area much wider than set brush width.

    2; This has persisted despite using the repair feature of the instal download (twice); and after uninstalling completely and reinstalling

    3: I have tested the identical operation 1with AP 1.6.0.84 beta, and it works fine

    This fault appeared quite suddenly, the healing brish having worked perfectly all morning. The fault is reproducible,  a screen grab vdeo is attached

    Help and advie requested, please.

    HealingBrushFault.mp4


  8. I have been a Serif customer since 1991, and have kept many of their products up to date. Their achievment, capped by the still developing Affinity series is remarkable, and is to be celebrated. However, I remain an amateur, and I hope I am forgiven for occasionally seeking clarification or response to adverse comment, whether ill informed or not. At least that process provides a justification for a public refutation which might otherwise sound shrill.


  9. 1 minute ago, R C-R said:

    Affinity Photo's 'native' RAW developer does not by default do any noise reduction; along with tonal curve & exposure bias these adjustments can be enabled or not in the Develop Assistant (the same assistant mentioned in the second blog post). Apple's Core Image RAW developer does these adjustments automatically (& does not tell the user that it has or offer any way to avoid them).

     

    If the blogger had done a bit more research he might have figured this out but apparently research is not his strongest suit. When doing searches like these, the wisdom of this "meme" might be worth considering:

    59bd4171f392d_socialmediataughtme.jpg.335669b6c10007e1df5bfeb8e715b248.jpg

    xD

    My peace of mind is restored, as I was sure it would be! Thankyou.


  10. While doing a Google search I came across this rather disturbing article from 2015
    http://loewald.com/…/affinity-photo-no-good-for-photography/
    If that article is correct,then it points to a serious deficiency in Affinity. Yes, there was a later article published that went some way toward mitigating the problem, but only for Mac users
    http://loewald.com/blog/2016/09/affinity-photo-redeemed/


    Does anyone know anything about this?

    Has anything changed in recent times?


  11. Chris B: With regard to dragging to increase px ( or %) have a look at this video (Official Affinity) https://player.vimeo.com/video/187632201/

    AS it turns out,I misreportedthe problem Working with Gaussian blur, the amount can be increased beyond 100 pix either with the mousewheel or by the slider method. BUt when you add noise the wheel will not take you beyond 100% but the slider will (though the number shown does not go beyond 100%). This works properly in AP1.5. (If you are wonderng why I would want to add that much noise, it is one way of adding rain to an image on a black pixel layer - you add a motion blur to the noise, and a suitable blend mode)


  12. 12 minutes ago, crlogic said:

    GrahamMYC - do you mean 100px?  

     

    I applied a Live Gaussian Blur filter to a layer and the default layout of the blur window is to provide a Radius slider from 0 to 100px.  I can exceed 100px by clicking, holding and dragging my mouse up, down, left or right.  The readout and slider move accordingly and display above 100px (I could go as high as 1024px).

    Yes - sorry

     

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