Jump to content

Earlio

Members
  • Content count

    69
  • Joined

  • Last visited

About Earlio

  • Rank
    Member

Profile Information

  • Gender
    Male
  • Location
    UK
  • Interests
    Photography, Ju Jitsu, MMA, Boxing, Graphic Design, Kite Buggying, Travel, Scuba Diving, Clay & Game Shooting, Playing Guitar

Recent Profile Visitors

325 profile views
  1. In Affinity Photo 1.7, you can create a Luminosity Mask with the following key combinations: Mac: <Option-Command> Left Click Thumbnail of the pixel layer required. PC: <Control-Alt> Left Click Thumbnail of the pixel layer required. The Blend If function works well. There is also a method to create a Macro which selects each tone profile (Midtones, Highlights, Shadows) and you can then change each of the parameters to your liking and this gives a great deal of tonal control, the keystroke method for a Luminosity Mask is a "quick and dirty" way to get a quite a nice result. I have attached the Macro should you prefer this method, or have a trickier image to edit (for Mac - I don't know if this can be directly imported into a Windows environment - If required for PC users, I can set out the steps needed to create these Macros). Luminosity Masks (Tones).afmacros
  2. Hi Hangman, Yes, it is only when dragged off screen on the bottom. Once the Gradient Tool has been released, the line does not reappear making picking up the tool (or tool handles) impossible to readjust, or to select colours. On further investigation, it would also seem that this behaviour only works when the line is outside of the work area, below the tip bar at the bottom of the screen.
  3. I have come across this behaviour when using the Gradient Tool on a Pixel Layer. Just when you need the tool most, the line showing how the gradient is positioned disappears. Model Name: MacBook Pro Model Identifier: MacBookPro14,3 Processor Name: Intel Core i7 Processor Speed: 2.9 GHz Number of Processors: 1 Total Number of Cores: 4 L2 Cache (per Core): 256 KB L3 Cache: 8 MB Hyper-Threading Technology: Enabled Memory: 16 GB Boot ROM Version: 198.71.1.0.0 SMC Version (system): 2. Screen_Recording_2019-08-07_at_10_03_33.mov Screen Recording 2019-08-07 at 10.03.33.mp4
  4. Thank you for the comment. Did you also notice the Graph on Levels remembering the settings from the previous image?
  5. Hi Filipe, I am sorry that the solution I found did not work for you. This is a very old thread, and relates to the previous version of APh. You should start a new thread detailing the issues, and hopefully Serif will (at some point) try to address the problems you have been experiencing. Don't forget to include details pdf version and the hardware you are using APh on. I wish you luck, and hope that the issue gets solved in a future update. Having kept an eye on the forums, there are users experiencing a plethora of bugs with the 1.7 release. I have experienced issues myself with the Levels Panel in Photo Persona in APh 1.7.
  6. Hi, Thanks for the post. Seems to be a similar issue to that which I have been experiencing since the Mojave upgrade. The problem with the workaround is that without Metal, the speed of (for instance Batch Processing, Tone Mapping, and other Processor heavy actions) is hugely effected, so going back to OpenGL is not really an option for me. So the updating of the Levels Panel is a pain, but not enough of a pain to make APhoto unusable, just frustratingly slow when I use it. Good to know, however.
  7. Hi Chris, The Metal issue would seem to be a recurring theme with my 2017 MacBook. It is extensively discussed in another thread. Metal is enabled. I waited more than 7 months for the update to solve the Metal Acceleration issues post Mojave update, and could not use Affinity Photo during that time due to the lack of speed due to not being able to use Metal at all, and had to go back to Photoshop during this period. It happens with every image. It would seem to update immediately in the Develop Personal, I use RAW, so I would have noticed any lag. I have just tried another image, and it seems to update instantly when back in Develop Persona. The Levels layer seems to remember the last setting, and this may be where the issue lie, I cannot think of a reason to retain the setting for the previous image in Levels. I have also noted that the update of the graph (Histogram) in Levels is particularly slow when working on a selection. I have tried with Metal disabled, and the issue does not seem to replicate. I tried with several images, but all seemed to update the graph immediately, however turning off Metal is not an option for me due to the long wait when developing RAW files, and the fact that Parallel Processing is then disabled when Batch Processing. The amount of time taken for the graph to update varies hugely, and sometimes does not update at all (I left one image for over 20 minutes and the graph had still not appeared). It would seem to have no relationship to the size of the image, to what else is running (I closed down every other app running except Activity Monitor) and the CPU Usage was under 12% - so does not appear to be a resource issue. You can see the settings being retained in the video. The indicator lines in the initial graph are those from the previous image, and this information would appear to be retained until the graph updates when the lines return to the default 0% Black and 100% White. There would appear to be no retention of the previous Levels setting with Metal disabled. Obviously it is not an option to switch between Metal enabled / disabled as this requires a restart, which is time consuming. MacBook Pro (15-inch, 2017) 2.9 GHz Intel Core i7 16 GB 2133 MHz LPDDR3 I am disappointed that despite a very long wait for a solution, I still cannot use Affinity Photo to its full potential. Screen_Recording_2019-06-25_at_11_37_24.mov
  8. Hi Chris, There would seem to be a misunderstanding. There is no Levels layer in the Develop Persona. What appears to be happening is that the Levels layer is not updating immediately, and now is further manifesting with the Levels setting from the previous image, looping for a few moments, then updating. The graph also often disappears for several seconds as previously mentioned (I have been somewhat more patient and in one case waited for 14 seconds for a Levels layer to update). So far, as long as I am prepared to wait, the graphic display of the Histogram in the Levels layer has eventually appeared. Surely, this cannot be right for a layer to take this long to update? I have attached a video of the issue I am experiencing. Screen Recording 2019-06-21 at 10.32.41.mov
  9. Earlio

    Crashing while exporting

    Hi Chris, Thanks for the quick response. I have not had an actual crash (as yet) - rather I have the same issue as Anwarp, where APh just hangs, on a couple of images, these have actually saved. So what is happening: Save (I save as Affinity Openable .afphoto file - I have not noticed with any Export formats) - Box comes up "Saving" with meter APh hangs (the pinwheel starts and the meter halts) and the only way to stop this is to Force Quit Most of the time, the image has not saved, but on some images, the images has saved, so puzzling. Although this appears to be happening randomly, it does seems to be especially prevalent after resizing the image. I hope this helps.
  10. This seems to happen randomly. Sometimes the graph showing the levels shows, sometimes not, sometimes does not appear immediately, and then pops up. Very frustrating.
  11. Earlio

    Crashing while exporting

    I am having there same issue - Mojave 10.14.5. MacBook Pro 15inch 2017 2.9Ghz Intel Core i7. 16Gb Memory.
  12. Hey Filipe, How did you get on? Did this solution work for you?
  13. Hi, I am sorry to hear that you have a similar issue. Onyx is a system maintenance tool from Titanium Software: https://www.titanium-software.fr/en/onyx.html I use this about every 6 months to clean my system and clear a number of caches on the Mac. It will check the integrity of your drives, clean caches (you can choose - I usually clean all except automatically saved versions of documents which is where your "open recent documents" are stored). Caches: Internet, Apps, System, Log Messages and Reports. Also will rebuild your spotlight index and dyld shared cache, Launch Services, reindex your mailbox and more. Often takes a long time to run, especially the first time, and I remember being concerned after watching the pinwheel going round for more than 20 minutes, but once finished usually gives a small speed boost. Make sure you follow the steps indicated in the previous post, as I did, otherwise it may not work. Onyx will restart your MBP (more than once at times). Make sure you save your Macros, Styles etc., I also took a screenshot to ensure I put my back tools in the places I moved them to, and am familiar with. Hope this helps with your problems with Affinity Photo.
  14. Hi, I first reported this bug 9 months ago. I was told by Affinity that this was a specific issue with 2017 MBP, the Mojave update, and the Metal Accelerator. Tried a number of fixes, and was eventually advised by Affinity to turn off Metal in Preferences, not to use Parallel Processing, and that the bug would be addressed "shortly" in the upcoming 1.7 release. I have avoided using Photo since, there were other issues with Metal. Today I downloaded the 1.7 update to find the same issue. What the hell is going on? Why was this issue not addressed? I am totally fed up with the standard of response, and having to wait this long, finding that you ave not addressed this bug. You were aware as others have reported the same issue! I feel that this is either that Affinity are not interested in the small number of users who own 2017 MBPs with Mojave, and just do not care. UPDATE After discussing this issue with a developer friend of mine, I have solved the issue as follows: Deleted current version 1.7 from my MBP Performed Restart Downloaded Onyx and ran, ensuring that ALL caches were deleted Downloaded app again Reloaded Settings for Macros, Brushes, Styles etc. All now working.
  15. Hi, I first reported this bug 9 months ago. I was told by Affinity that this was a specific issue with 2017 MBP, the Mojave update, and the Metal Accelerator. Tried a number of fixes, and was eventually advised by Affinity to turn off Metal in Preferences, not to use Parallel Processing, and that the bug would be addressed "shortly" in the upcoming 1.7 release. I have avoided using Photo since, there were other issues with Metal. Today I downloaded the 1.7 update to find the same issue. What the hell are you guys playing at? Why was this issue not addressed? I am totally fed up with the standard of response, and having to wait this long, finding that you ave not addressed this bug. You were aware as others have reported the same issue! I feel that this is either that Affinity are not interested in the small number of users who own 2017 MBPs with Mojave, and just do not care.
×